GettextForTranslators - Revision history

Octalot: /* Textdomains and getting the files to translate */ Use wesnoth-tsg instead of wesnoth-httt as an example

2026-02-28T13:11:54Z

‎Textdomains and getting the files to translate: Use wesnoth-tsg instead of wesnoth-httt as an example

Egallager: /* Tools */ add some additional links

2024-02-29T20:20:20Z

‎Tools: add some additional links

Celtic Minstrel: Link to the redirect instead of the section (so it still works if we ever make it not a redirect anymore)

2024-02-22T03:39:38Z

Link to the redirect instead of the section (so it still works if we ever make it not a redirect anymore)

Celtic Minstrel: /* FAQ */ Commas

2024-02-22T03:12:57Z

‎FAQ: Commas

Celtic Minstrel: /* Markup */ Fix markup

2024-02-22T03:12:14Z

‎Markup: Fix markup

Celtic Minstrel: /* Markup */ Turn that question into a paragraph

2024-02-22T03:12:01Z

‎Markup: Turn that question into a paragraph

Celtic Minstrel: /* Dollar signs */ Be consistent about terminology

2024-02-22T03:11:07Z

‎Dollar signs: Be consistent about terminology

Celtic Minstrel: /* Dollar signs */ Slightly more on when to add a vertical bar

2024-02-22T03:10:30Z

‎Dollar signs: Slightly more on when to add a vertical bar

Celtic Minstrel: /* Dollar signs */ Decided to remove the default value explanation. The full rules are linked to anyway, for those who want to know, but default values should rarely if ever be used in translatable strings.

2024-02-22T03:09:15Z

‎Dollar signs: Decided to remove the default value explanation. The full rules are linked to anyway, for those who want to know, but default values should rarely if ever be used in translatable strings.

Celtic Minstrel: Extract FAQs about markup into the sections actually documenting that markup.

2024-02-21T15:14:14Z

Extract FAQs about markup into the sections actually documenting that markup.

@@ Line 25: / Line 25: @@
 * wesnoth-units
 * wesnoth-lib (contains strings shared by game and editor)
-* wesnoth-httt (the Heir to the Throne campaign)
+* wesnoth-tsg (The South Guard campaign)
 * wesnoth-utbs (the Under the Burning Suns campaign)
 * etc

@@ Line 159: / Line 159: @@
 * [http://www.gnu.org/software/emacs/emacs.html Emacs with po-mode] (Multiplatform)
 * [http://www.vim.org/ Vim] with [http://www.vim.org/scripts/script.php?script_id=695 PO plug-in] (Multiplatform)
 Of course, you can edit po files with any UTF-8 capable text editor, but the tools listed above have great advantages over any text editor regarding .po translation, like going to next fuzzy/untranslated string, searching only in specific fields (msgid, msgstr, comment), ...

@@ Line 118: / Line 118: @@
 === Dollar signs ===
-Most placeholders start with a dollar sign (<code>$</code>), for example, <code>$number</code> or <code>$gold_amount</code>. The details are in [[SyntaxWML#Variable Substitution|SyntaxWML]], but for translation the general rules are:
+Most placeholders start with a dollar sign (<code>$</code>), for example, <code>$number</code> or <code>$gold_amount</code>. The details are in [[VariablesWML#Variable Substitution|VariablesWML]], but for translation the general rules are:
 Characters that appear in placeholders are letters, numbers, square brackets, underscores, full stops and question marks. Square brackets always appear in balanced pairs, and often enclose a secondary (nested) placeholder.

@@ Line 143: / Line 143: @@
 ** You can ask in [[Support|Discord or IRC]]. Ping Ivanovic in Discord's #development or IRC's #wesnoth-dev channel. If you don't like IRC, send a mail to crazy-ivanovic AT gmx DOT net, or pm him (ivanovic) at the forum.
 * '''Why is the diff from the previous version so huge? I have only made a small change to the .po file with poedit.'''
-** When saving .po file poedit unwraps all strings. Usually, all .po files are wrapped at 80 characters so if you want smaller diffs and less merge conflicts you can execute the following commands each time after editing with poedit:
+** When saving a .po file, poedit unwraps all strings. Usually, all .po files are wrapped at 80 characters, so if you want smaller diffs and less merge conflicts, you can execute the following commands each time after editing with poedit:
     msgattrib file.po > file.po1

@@ Line 135: / Line 135: @@
 Like HTML, help markup consists of tags enclosed in angle brackets (eg <code><italic></code>), with a slash added to the closing tag. The difference lies in what comes between the tags, which takes a key=value format where the value is usually enclosed in single quotes. There can be multiple key=value pairs, separated by spaces. Generally, all of that should be left untouched, with the exception of the <code>text</code> key. If you see something like <code><italic>text='some text'</italic></code>, the only part that should be translated is "some text". Or if you see <code><nowiki><ref>dst='movement' text='zones of control'</ref></nowiki></code>, then only "zones of control" should be translated, and the rest should be left untouched.
-If you need to include a single quote within <code>text='...'</text>, you can add a backslash before it. However, most of the time it's preferred to use [[Typography_Style_Guide#Character_Usage_Summary|typographic punctuation]] instead.
+If you need to include a single quote within <code>text='...'</code>, you can add a backslash before it. However, most of the time it's preferred to use [[Typography_Style_Guide#Character_Usage_Summary|typographic punctuation]] instead.
 ==  FAQ  ==

@@ Line 126: / Line 126: @@
 * A vertical bar (<code>|</code>) ends the placeholder, and the vertical bar isn't displayed to the player.
 * If you need to put a full stop or question mark immediately after a placeholder that doesn't end with a vertical bar, add a vertical bar to separate them. Although it's not ''always'' necessary, it ''never'' hurts to add the vertical bar to be on the safe side.
-* A dollar sign at the end of the string, or directly followed by a pipe (<code>$|</code>), is displayed as a dollar sign.
+* A dollar sign at the end of the string, or directly followed by a vertical bar (<code>$|</code>), is displayed as a dollar sign.
 * Obscure cases should have a hint about the string.

@@ Line 77: / Line 77: @@
 === Carets ===
-These lines in the tutorial both have the hint "[message]: speaker=student"; they're spoken by Konrad and Li'sar respectively:
+There are ambiguous strings which should be translated in a different way depending on where they appear. For example, we have "General" in the preferences as "General preferences" and we can also have "a General". These strings can have different translations for a given language, so we use "context" to solve this. The prefix only tries to give a hint about the string, and should be not translated, for example:
 * "A quintain? You want me to fight a dummy?"
 * "female^A quintain? You want me to fight a dummy?"
@@ Line 84: / Line 91: @@
 These caret hints are very commonly used in Wesnoth for strings where the translation may depend on the gender of the speaker, or the person spoken to. They're also used for strings such as "Prefs section^General", where the string is the label on the "general preferences" tab, not a military rank.
 === Warnings ===
@@ Line 118: / Line 135: @@
 Like HTML, help markup consists of tags enclosed in angle brackets (eg <code><italic></code>), with a slash added to the closing tag. The difference lies in what comes between the tags, which takes a key=value format where the value is usually enclosed in single quotes. There can be multiple key=value pairs, separated by spaces. Generally, all of that should be left untouched, with the exception of the <code>text</code> key. If you see something like <code><italic>text='some text'</italic></code>, the only part that should be translated is "some text". Or if you see <code><nowiki><ref>dst='movement' text='zones of control'</ref></nowiki></code>, then only "zones of control" should be translated, and the rest should be left untouched.
 ==  FAQ  ==
 * '''What are "Plural-forms"?'''
 ** Some languages have different word forms for different numbers of things (for example in English we have "1 thing" but "2 thing'''s'''"). The rules are different for different languages. You can find them [http://translate.sourceforge.net/wiki/l10n/pluralforms here].
 * '''Who can I ask for further information?'''
 ** You can ask in [[Support|Discord or IRC]]. Ping Ivanovic in Discord's #development or IRC's #wesnoth-dev channel. If you don't like IRC, send a mail to crazy-ivanovic AT gmx DOT net, or pm him (ivanovic) at the forum.