![]() ![]() You can see in this file lines like these: This file contains several terms that will be substitutedĪll around the templates files. A good idea is to start with the localization of Here are some examples to help you localizing the right stuff. Which has great syntax highlighting for Template Toolkit files. Or Notepad++ under Windows systems and localize the templates using UTF8 encoding. IMPORTANT: Use an UTF8 compliant editor like Gedit, Kate or Emacs under GNU/Linux systems Localizing The TemplatesĬurrently, these templates contain code and localizable strings mixed together that makes the localization of Bugzilla a bit difficult. It is used to display information or error messages during Bugzilla's setup and is located in the It is used to generate the picture of the different states in a bug lifecycle. bzLifecycle.xml: It is a source xml file generated with the diagramming tool Dia. It is a short document explaining how to installĪnd run Bugzilla quickly. ![]() README: This file is in plain text and located in Bugzilla's root directory. There are located in the docs and extensions/Example/docs/en/rst subdirectories. *.rst files: These files are used to generate the documentation files in different formats. The extensions and template subdirectories. There are used to generate with Template Toolkit the html pages of the user interface of Bugzilla application. There are different types of files to be localized: *.tmpl files: These files are the templates. Pt-BR for Brazilian Portuguese or zh-CN for Chinese (Simplified). You can also use a four-letter locale code: YouĬan pick the locale code matching your language inįor instance, you can use fr for French or ca for Catalan. Now, rename all the en subdirectories with your locale code. You should have the following tree structure (note: all subdirectories and files are not detailed here):Īll the localizable content are located in the highlighted directories, so you should only Uncompress the tarball with your favorite tool in an empty directory. ![]()
0 Comments
Leave a Reply. |