![]() For example, for English versions the folder should be named en.lproj.ĤD will automatically load the XLIFF files in the folder corresponding to the current language of the database. ![]() The name of the folder must comply with the international standard (see the following paragraph). Lang.lproj is a folder that contains the XLIFF files for the Lang language.MyDatabase is the folder that contains the database files and MyPackage is the database package under Mac OS.Mac OS: MyPackage:Resources: Lang.lproj: MyEnLoc.Windows: MyDatabase\Resources\ Lang.lproj\ MyEnLoc.xlf.To implement an XLIFF architecture for your localized application, you just need to build one or more valid XLIFF file(s) and copy them into the Resources folder of the database.įor more information about the Resources folder of the database, refer to Managing the Resources folder. Example (table form) To translate the title of the button whose object name is “SaveButton” in the “Form1” form of the table, the XLIFF file simply need to contain the lines:.The principle is to surround the trans-unit elements in the XLIFF file by two group elements whose resname attributes contain, respectively, the table name and the form name. ObjectName syntax (based on the “Name” field in the Property list) The purpose of this syntax is to facilitate the translation of forms - unlike the other syntaxes, it is only used with forms.In this case, the referenced value ( OKButton in the example) designates the resname attribute of the trans-unit element. :xliff:OKButton syntax This alternative syntax can only be used with loaded XLIFF files.In all cases, loaded XLIFF files have priority over resource files if the same string is present in both locations. With this mechanism, you can implement an XLIFF-based system in an application without having to edit your existing dynamic string references: you just need to copy an XLIFF file at the correct location (see below) and it will be taken into account by 4D. In fact, 4D will first try to locate and use the values corresponding to 15115,3 in all loaded XLIFF files then, if it does not find the string, it will search for it in all the open resource files. This way you can keep a resource-based system in a converted database while installing a new XLIFF system. ![]() For example, “:15115,3” means that 4D must use the 3rd element of the STR# resource number 15115. Compatibility note: This syntax is exactly the same as that of the “former generation” STR# resources, of the type “:xxxx,yyy” where xxxx is the number of the STR# resource and yyy is the element number. The second value (3 in the example) designates the id attribute of the trans-unit element. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |