![]() So that the sentence is displayed as: The account has been added to the bz_sudo_protect group. #Bugzilla tutorial codeThe previous code will be shown as: The account has been added to thebz_sudo_protect group. This is the same when a member is at the beginning of a new line: Will then be displayed as: This bug has been marked as duplicate of bug 12345 Instead you should add a "+" sign in the second member: This has been marked as a duplicate of įor instance, the previous line of code will display in the browser as: This bug has been marked as duplicate of bug12345 When two members are following each other, the second member will not be separated with a space from the first one, even if you separate them with a space: Generally, you should follow the English model, but if you need to change the order of in a line, you should be aware of those rules: Other common lines through the templates are text enclosed between an opening and a closing tag: DO NOT translate lines with type="hidden": Whenever you see this, the only line that needs to be localized is the one with type="submit". You will encounter many buttons you will want to localize. Supprimer le composant « »ĭu produit « » Some other examples of what needs to be translated: Now, you can start translating the other templates. Īs previously, translate the word after the =>. As a general rule, never translate capitalized words enclosed between. "" => " ",ĭO NOT translate here PROCESS or USE. # across all templates-see VARIABLES in Bugzilla/Template.pm. [%# field_descs is loaded as a global template variable and cached In templates, they will be replaced in the user interface with the value you put in this file.Īnother file that is used by several templates is /template/en/default/global/. Whenever you see expressions like &terms.ABug or &terms.bugs These terms will be used in the templates. What is to be translated here, is the word between the quotes after "zeroSearchResults" => " Zarro Boogs found",ĭO NOT translate terms here. 2.0.ĭO NOT translate text located between : the text inside is comment. # defined by the Mozilla Public License, v. # This Source Code Form is "Incompatible With Secondary Licenses", as If a copy of the MPL was not distributed with this [%# This Source Code Form is subject to the terms of the Mozilla Public 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. #Bugzilla tutorial windowsOr 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. #Bugzilla tutorial how toIt 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |