Search the Community
Showing results for tags 'internationalization'.
Found 2 results
-
I decided to start working on image internationalization and localization. This is mostly important for those languages that translate game names, however, any image might need to be somehow modified for a certain locale. The approach I plan to follow is that of The Battle for Wesnoth. In The Battle for Wesnoth, any image can be translated. When the game loads an image, it first checks if within the folder where the image is there is a localization folder with a localized version of that image for the current locale. For example, if the current locale is "gl", and you have a file in "folder/image.png" and a localized version in "folder/localization/gl/image.png", when the game is required to load "folder/image.png" it first checks if "folder/localization/gl/image.png" exists, and since it does exist, it loads "folder/localization/gl/image.png" instead of "folder/image.png". Simple To help translators to keep images up to date, they have a system which basically generates checksums of translated and original images, and if developers update an original image, translators can check in a file that the original image was modified after they localized it the last time, so they know they might need to update the localized image. Another important part of the image localization is explaining to translators how to localize specific types of images. It is important to supply translator with either source versions (for example, in Gimp format) of images, or with detailed steps to generate certain images from scratch. Here is where there is not much I can do, and I need your help. Can anyone point me to an editable version of "public/art/textures/ui/pregame/shell/logo/0ad_logo.png", "public/art/textures/ui/pregame/shell/logo/fundraiserlogo.png" and "public/art/textures/ui/pregame/shell/logo/product.dds" if there is one? What font are we using for "A.D." in "0 A.D." or for "Empires Ascendant"? How are DDS images compressed? (if I save a version modified with Gimp uncompressed it takes 3 times as much space as the original one).- 3 replies
-
- 1
-
-
- localization
- internationalization
- (and 1 more)
-
Currently, unit template files have a translatable field called Tooltip. This field, as far as I’ve seen, may contain the following information: • Unit classes (recently prefixed by ‘Classes:’). • Units that this unit counters (prefixed by ‘Counters:’). • Units that counter this unit (prefixed by ‘Countered by:’). • Unit description. In the XML, these are differenciated by line breaks. What would you think about providing separated fields for each one of these? • DisplayClasses (as opposed to the class names used in the game logic) • Counters • CounteredBy • Description Pros would be: • Easier to keep consistency between tooltips. • Ability to use a different font or text style on different elements. • Ability to reorder the elements in the interface easily, without changing all XML files, nor affecting translations. • Ability to show a different combination of these bits of information in different contexts. • Easier for translator, as they would only need to translate the "Prefix: <data>" strings once, and the rest of the strings will have a decreased size. And I honestly cannot think of cons here. Also, if you agree, should I let you do this yourselves in master, or should I do this myself in my i18n branch? Or should I maybe write a patch against master only for this?