Feature #67
Finish Internationalisation/Localisation support.
| Status: | In progress | Start date: | 2008-12-19 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Robert Clipsham | % Done: | 100% |
|
| Category: | i18n | |||
| Target version: | - |
Description
All the code is there, it just needs finalising. Make sure everything uses t( 'string' ) rather than t( $string ), then we can use gettext to pull out the strings and generate the language files. We can then add a setting to change the language and we're good to go! Language packs should be able to be released separately from the main distribution, so we can add new languages as we get them, rather than increasing the size of the packages.
Related issues
History
Updated by Robert Clipsham about 3 years ago
- % Done changed from 0 to 60
Everything now uses t('string') instead of t($string) as of r2013. Just need language files creating and maintaining now.
Updated by Alex Cartwright about 3 years ago
The pagelink titles still need the use of t(), as they are currently hard-coded in.
Updated by Alex Cartwright about 3 years ago
All Zula_ControllerBase::setPageLinks() calls now use t() as of r2067
Updated by Robert Clipsham about 3 years ago
- % Done changed from 60 to 90
We now have an almost (there are a couple of issues that need working out) complete script to parse the language strings and generate .pot files in utils/locale.sh. We just need to make sure that all strings are wrapped in either {L_[]} or t('') now and we'll be good to go!
Updated by Robert Clipsham about 3 years ago
Just the $op things to work out now, the it is complete. The spell checker ignore list needs updating, and there are a couple of words that might still need checking, but then i18n is done!
Updated by Alex Cartwright about 3 years ago
As of r2115 all the $op code has been changed over to allow the Locale script to pick them up as properly translatable strings
Updated by Alex Cartwright about 3 years ago
- Status changed from Approved to Closed
- % Done changed from 90 to 100
As of r2180, HTML from lang strings (only a few) has been removed
Updated by Alex Cartwright almost 2 years ago
- Status changed from 21 to In progress
- Target version deleted (
2.3.0) - % Done changed from 100 to 80
We just need to figure out a good workflow for extracting language files and importing new translations, as well as selecting the interface language.
Updated by Alex Cartwright over 1 year ago
All page titles and page links need to ensure the words are of the correct case, what I mean by this is 'Add article' is correct whereas 'Add Article' is incorrect. These can still be styled to display like that via CSS, however the translation should be in correct English.
Updated by Alex Cartwright over 1 year ago
I think the only things left now are:
1) locale.json on our server
2) Export lang strings and merge them into Launchpad
Updated by Alex Cartwright about 1 year ago
Done but we still need to export lang strings.