AssetLocalization - Revision history

Celtic Minstrel: Some updates – note that the system also works for sounds, remove some obsolete info

2025-01-11T21:32:50Z

Some updates – note that the system also works for sounds, remove some obsolete info

Celtic Minstrel: Celtic Minstrel moved page ImageLocalization to AssetLocalization: It now applies to sounds too, so make the name more generic

2025-01-11T21:28:55Z

Celtic Minstrel moved page ImageLocalization to AssetLocalization: It now applies to sounds too, so make the name more generic

Bssarkar: /* Gimp For Translators */

2024-04-25T06:36:22Z

‎Gimp For Translators

Bssarkar: /* BfW Logo */ Insert link to updated documentation.

2024-04-25T06:33:33Z

‎BfW Logo: Insert link to updated documentation.

Bssarkar: /* BfW Logo */

2024-04-24T15:57:45Z

‎BfW Logo

Bssarkar: /* BfW Logo */ Update information for GIMP 2.10

2024-02-27T09:35:57Z

‎BfW Logo: Update information for GIMP 2.10

Octalot: The l10n-track file is obsolete, and instructions about using SVN were very obsolete

2020-08-08T03:30:21Z

The l10n-track file is obsolete, and instructions about using SVN were very obsolete

Soliton: Updated all svn links to github. Text still needs more adjustements for the svn -> git transition.

2019-08-22T17:43:31Z

Updated all svn links to github. Text still needs more adjustements for the svn -> git transition.

Show changes

Vultraz: Remove DevFeature1.11

2015-04-17T07:26:16Z

Remove DevFeature1.11

Vultraz: Fixed the TRoW template link still pointing to the old SVN repo

2014-10-10T08:06:39Z

Fixed the TRoW template link still pointing to the old SVN repo

@@ Line 1: / Line 1: @@
-Being a game, Wesnoth's graphics data carries higher significance than it would in utilitarian software. An image containing English text in an otherwise native language environment, may bite at user's immersion. For example, a mismatch between geographical names in translated text and on maps (like "Blackwater Port", "Ford of Abez", etc.) will certainly not improve user's feeling of completeness of localization effort.
+Being a game, Wesnoth's graphics data carries higher significance than it would in utilitarian software. An image or sound containing English text in an otherwise native language environment, may bite at user's immersion. For example, a mismatch between geographical names in translated text and on maps (like "Blackwater Port", "Ford of Abez", etc.) will certainly not improve user's feeling of completeness of localization effort.
-To offset this, a willing translator can also localize images into the world of Wesnoth.
+To offset this, a willing translator can also localize images and sounds into the world of Wesnoth.
 == How Does It Work? ==
-Quite not unlike with text. Most text appearing in Wesnoth is up for translation, but given language's translators may leave some untranslated -- either deliberately (i.e. just copying English original), or because they didn't get to it yet. Likewise with the images: any can be localized, but none needs be; if there is no localized version of a given image, the user is presented with the original one. The only difference between text and images is that, unlike text, very few images possibly need to be localized -- presently, about 30 in total.
+Quite unlike with text. Most text appearing in Wesnoth is up for translation, but given language's translators may leave some untranslated -- either deliberately (i.e. just copying English original), or because they didn't get to it yet. Likewise with the images and sounds: any can be localized, but none needs be; if there is no localized version of a given image or sound, the user is presented with the original one. The only difference is that, unlike text, very few images and sounds possibly need to be localized.
-Once the localized image is made, putting it to work is simple. If the path of the original image in the source tree is:
+Once the localized image or sound is made, putting it to work is simple. If the path of the original image or sound in the source tree is:
   foo/bar/baz/image.png
-then the localized image should be put in:
+then the localized image or sound should be put in:
   foo/bar/baz/l10n/ll/image.png
@@ Line 17: / Line 17: @@
 where <tt>ll</tt> is the given language's code, like that used for names of PO files (e.g. <tt>de</tt>, <tt>pt_BR</tt>, etc.) That's it.
-Before trying to test any localized images at runtime, it is also necessary that the following message in <tt>wesnoth-lib</tt> catalog is properly translated:
+Before trying to test any localized images or sounds at runtime, it is also necessary that the following message in <tt>wesnoth-lib</tt> catalog is properly translated:
   #. TRANSLATORS: This is the language code [...]
@@ Line 25: / Line 25: @@
   msgstr ""
-The translation should basically be the same language code as used in paths of localized images (<tt>ll</tt> from the example above), but read the longer explanation in comments of this message for other possibilities.
+The translation should basically be the same language code as used in paths of localized images and sounds (<tt>ll</tt> from the example above), but read the longer explanation in comments of this message for other possibilities.
 === Overlay Images ===

@@ Line 359: / Line 359: @@
 Being a general-purpose bitmap-editing tool, beginners' tutorials on Gimp usually assume that the reader wants to go from the basics towards becoming a proficient Gimp user one day. This, however, provides too much breadth for the limited scope of retouching images for localization, as we are doing in this article. Of course, if you indeed would like to learn about bitmap editing in general, by all means do go through such tutorials (there are books too) in detail, and then return to this article to apply the obtained knowledge.
-If, on the other hand, you'd rather "just get the job done" (such as, for the most part, the initial author of this article), the following subsections shortly explain some crucial elements of Gimp needed to follow the instructions on [[#Creating Localized Images|creating localized images]]. You can also consider them a guideline to what to pay special attention to, if the next thing you do is look for a more in-depth tutorial text.
+If, on the other hand, you'd rather "just get the job done" (such as, for the most part, the initial author of this article), the following subsections concisely explain some crucial elements of Gimp needed to follow the instructions on [[#Creating Localized Images|creating localized images]]. You can also consider them a guideline about what to pay special attention to, if the next thing you do is look for a more in-depth tutorial text.
 === Orientation ===

@@ Line 146: / Line 146: @@
 === BfW Logo ===
-The sworded shield logo with "The Battle for Wesnoth" text is shown on loading screens and at the head of the main menu, thus being the foremost target for localization (for languages which have translated the game's name, of course). Here are the steps to create the localized logo with Gimp. Note: in order to make sure the logo fits properly in the title screen it shall not be larger than 550x250.
+== New Instructions ==
 Fetch the template logo from here:

@@ Line 154: / Line 154: @@
 There is just one layer in the file, <tt>shield</tt>, with the sworded shield on a transparent background and without any text. Rename the file to e.g. <tt>bfw-logo-LANG.xcf</tt>, to work on it and keep it as "source" of your localized logo.
-Pick a font in which you would like to write the logo text. The English logo uses "Celtic Garamond the 2nd" font, easily found by Google for free download, as the starting point. This font, however, contains only English letters (not even Western European), so some creativity may be needed to make use of it. One could, for example, manually add any diacritics (copied over from suitable letters of another font). Another option is to simply use another font, which both has the glyphs of required characters, and is somewhat fantasy-looking.
+Pick a font in which you would like to write the logo text. The English logo uses "Oldania Adf Std" font, easily found by Google for free download, as the starting point. This font, however, contains only English letters (not even Western European), so some creativity may be needed to make use of it. One could, for example, manually add any diacritics (copied over from suitable letters of another font). Another option is to simply use another font, which both has the glyphs of required characters, and is somewhat fantasy-looking.
 The hardest part of localizing the logo is that of producing a single-color version of the text of translated game name. This may seem surprising at first — why not just use the text tool to write out the text in proper size, and be done with it? The problem with this is that, as a rule rather than exception, the letters will not be mutually spaced in visually pleasing manner. For each font size, the spacing between any two paired letters needs to be manually adjusted, a process which is called ''kerning''. Only high quality fonts have kerning instructions built in, and then usually only for small font sizes. Therefore we have to perform kerning manually.

@@ Line 192: / Line 192: @@
 Switch to <tt>text-map</tt> layer and start Gaussian blur filter ('''Filters→Blur→Gaussian Blur...'''). In there, set both the horizontal and vertical blur radii to 5 pixels. The preview pane should show that the text got quite blurry; click '''Ok''' to apply the blur. Repeat this filter operation for <tt>text-outline</tt> and <tt>text-shadow</tt> layers (you can just switch to each of them and use '''Filter→Repeat Last''').
-Some layers should now be given colors other than black. Switch to <tt>text-final</tt> (the topmost layer, which wasn't blurred), and start '''Colors→Colorize...'''. In the dialog, set hue to 50, saturation to 40, and lightness to 60. As you do this, the text in the image should reflect the modifications, and in the end it should have a pale sand-like color. Click '''Ok''' to apply colorization. Change to <tt>text-map</tt> layer (one of the blurred layers), also use '''Colors→Colorize...''', but this time only set lightness to 100. This should make the blurred text white.
+Some layers should now be given colors other than black. Switch to <tt>text-final</tt> (the topmost layer, which wasn't blurred), and start '''Colors→Colorize...'''. In the dialog, set hue to 50, saturation to 40, and lightness to 60. As you do this, the text in the image should reflect the modifications, and in the end it should have a pale sand-like color. Click '''Ok''' to apply colorization. Change to <tt>text-map</tt> layer (one of the blurred layers), also use '''Colors→Colorize...''', but this time only set lightness to 100. This should make the blurred text white. (Gimp 2.10: Hue/Saturation/Lightness sliders now range from 0.0 to 1.0, adjust accordingly so you get the same color as mentioned here.)
-Switch to <tt>text-final</tt> and start '''Filters→Map→Bump Map...'''. From the '''Bump map:''' drop-down list in the top right corner of the dialog, select the <tt>text-map</tt> layer (the layer name may be somewhat strange and possibly shrunken, so look for the small icon to the left for the white pattern produced by the white text on that layer). Check '''Compensate for darkening''' (if necessary; it should be checked by default), then set the sliders: azimuth 135, elevation 40, depth 10 (rest should be all zero). In the preview pane to the left you should now see the final bevelled text:
+Switch to <tt>text-final</tt> and start '''Filters→Map→Bump Map...'''. From the '''Bump map:''' drop-down list in the top right corner of the dialog, select the <tt>text-map</tt> layer (the layer name may be somewhat strange and possibly shrunken, so look for the small icon to the left for the white pattern produced by the white text on that layer). Check '''Compensate for darkening''' (if necessary; it should be checked by default), then set the sliders: azimuth 135, elevation 40, depth 10 (rest should be all zero).
 <center>https://raw.githubusercontent.com/wesnoth/resources/master/image-localization/tutorial/text-bump-map.png</center>

← Older revision	Revision as of 21:28, 11 January 2025
(No difference)

@@ Line 26: / Line 26: @@
 The translation should basically be the same language code as used in paths of localized images (<tt>ll</tt> from the example above), but read the longer explanation in comments of this message for other possibilities.
 A tracker script is run periodically on the repository to indicate that localized images need updating when the original image has been changed or moved. There is a file named <tt>l10n-track</tt> in the root of the source tree, which tracks the state for every localized image, grouped by language:
@@ Line 59: / Line 63: @@
 === Resolving Fuzzy Images ===
-When a localized image got fuzzy due to changes to the original, it is necessary to ascertain what is it exactly that had been changed, between the point when the localized image was made and current state. To do this, enter the root directory of appropriate branch in the repository, and observe the fuzzy entry in <tt>l10n-track</tt>:
+When a localized image got fuzzy due to changes to the original, it is necessary to ascertain what is it exactly that had been changed, between the point when the localized image was made and current state. This has to be done by manually comparing it, which is probably easiest to do with Gimp's support for layers.
 == List of Images for Localization ==

@@ Line 268: / Line 268: @@
 === Maps ===
-As of {{DevFeature1.11}}, the maps and the localization process for them have changed. See [[MapLocalization]] for the new localization instructions.
+See [[MapLocalization]] for the up-to-date localization instructions.
 Each campaign comes with a map, where locations of events are highlighted as the scenarios progress. Since these locations are frequently mentioned in narration and character conversations, it may be more than merely a "nice touch" to match the map labels to in-game texts. In particular, the main map of Wesnoth, which is used by several campaigns, also figures as the background of the main menu.

@@ Line 228: / Line 228: @@
 The logo with the "The Rise of Wesnoth" text is displayed on one of the story screens of the first scenario of ''The Rise of Wesnoth''. It is only seen once and is fairly easy to make.
-First, fetch the logo from the Subversion repository:
+First, fetch the logo template here:
-http://svn.gna.org/viewcvs/*checkout*/wesnoth/branches/resources/image-localization/templates/trow-logo/trow-logo.xcf
+<https://github.com/wesnoth/resources/blob/master/image-localization/templates/trow-logo/trow-logo.xcf>
 As with the main logo, the TRoW logo uses "Celtic Garamond the 2nd".