Important | |
---|---|
This feature is unlikely to be implemented in the short term, but is a longer term feature, possibly in release 2.0, for which no release date has been specified. |
Likely changes include:
-
An extra language field on the subsidiary tables and then in the drop down picker, filter out the strings we do not need.
-
Modification of all list views to add a language column, plus sort and filter abilities.
-
Each table to have an additional identifier so that the same 'type' is any language is connected. i.e A defect in one language is the same type as a defect in another language.
-
Need to decide what language back end displays in (en-GB) ?
-
This is going to be a major change impacting all over the place.
-
First step is to create the additional language field in all our tables.
-
At the same time need an extra id fields so that a specific 'type' in different languages can be associated.
-
An index on the language field will also help.
-
Then add extra code in the model and views.
-
Modify select to include language selection for site. Need to think how to make the upgrade easy as well.
-
Can we assume that there is only one language set in use, probably yes so make that the default and then copy it to make it the current language default.