Downloads « New template files « All .pot templates for YACS 6.10 «
Comment: All .pot templates for YACS 6.10
| << Previous | Next >> |
Comment inspired from fw_crocodile
Fw_crocodile: Yes, other modules will be localised after release 6.10. It will be the main effort of the team for the next release, i guess.
The .mo files are those that are actually used by YACS at run time. They are expected in the i18n/locale/it directory for Italian translation.
To summarize the localisation environnement:
The .mo files are those that are actually used by YACS at run time. They are expected in the i18n/locale/it directory for Italian translation.
To summarize the localisation environnement:
- .pot files are created manually, based on strings put in reference scripts, and all of them are available in the official archive in directory i18n/templates. There is one .pot file per module (i.e., per directory).
- .pot can be used as input for translation by specialised editors, such as poEdit or similar, to produce .po files (text format) and .mo files (binary format). YACS can only use .mo files. The .po and .mo files for locale xyz are put in the directory i18n/locale/xyz
- In addition to .mo files, a manifest.php can be added in localized directories, that will be used to describe available localizations in the configuration panel
- At execution time, YACS loads .mo files and, to further optimize response times, attempts to derive related PHP scripts, with the extension .mo.php. These files should be considered as cache, and can be safely deleted if necessary. If a .mo file is updated, YACS will re-create an updated .mo.php file.
by Bernard on Nov. 22 2006
