WesnothTranslationsHowTo - Revision history

Octalot: /* Tools */ updating all the files needs "po4a-update" and "manual" too

2024-03-02T15:54:14Z

‎Tools: updating all the files needs "po4a-update" and "manual" too

Octalot: /* Files */ Split the section into Files, Tools and Summary. Mention SCons and CMake before individual tools.

2023-10-20T11:11:02Z

‎Files: Split the section into Files, Tools and Summary. Mention SCons and CMake before individual tools.

Octalot: /* Specifying typefaces and fonts for a translation */ Refer to data/hardwired/fonts.cfg

2021-10-11T21:54:31Z

‎Specifying typefaces and fonts for a translation: Refer to data/hardwired/fonts.cfg

Octalot: /* Translations How-To */ Dump the msgmerge part of GettextForTranslators here, I'll return to editing it here after that page is ready

2021-10-11T20:02:30Z

‎Translations How-To: Dump the msgmerge part of GettextForTranslators here, I'll return to editing it here after that page is ready

Pentarctagon: /* See Also */

2021-01-23T06:46:59Z

‎See Also

Fluxbird: /* How to submit your translations */

2020-03-14T13:25:30Z

‎How to submit your translations

Octalot: /* Translations How-To */ Update link for changes in GettextForWesnothDevelopers

2019-05-18T09:47:03Z

‎Translations How-To: Update link for changes in GettextForWesnothDevelopers

Octalot: /* Translations How-To */ Add a link for how-to translate UMC, drop text about the cvs-Gna migration

2018-06-10T23:37:41Z

‎Translations How-To: Add a link for how-to translate UMC, drop text about the cvs-Gna migration

Xudojnik: typo

2014-10-30T16:29:04Z

typo

Mattsc: /* How to submit your translations */ Add comment about not accepting translations as PRs

2014-10-10T14:06:27Z

‎How to submit your translations: Add comment about not accepting translations as PRs

@@ Line 57: / Line 57: @@
 For the main Wesnoth repository, the build system can handle updating these files.
-* Using SCons, '''scons pot-update''' will do everything. '''scons -j8 pot-update''' is quicker, because it does it in parallel. This can be done without building the Wesnoth executables.
+* Using SCons, '''scons pot-update po4a-update manual''' will do everything. This can be done without building the Wesnoth executables.
 * Using CMake, enable '''ENABLE_NLS''' and '''ENABLE_POT_UPDATE_TARGET''', then run '''make -C po pot-update''' to generate the files.

@@ Line 53: / Line 53: @@
 The first of these files, we update every once in a while, when there is new or modified text,
 for instance when a new campaign scenario hits the repository.
 Then, ''msgmerge'' is used to merge this new "state of the game strings" with your current translations, and generate a new, up-to-date, ''sv.po''.
@@ Line 58: / Line 68: @@
 Then, a tool called ''msgfmt'' is called, which generates a new ''wesnoth.mo'' file from your ''wesnoth.po'' file, which will be used by the game once installed.
-"make -C po update-po" does these three steps in one pass.
+=== Summary ===
 That was for the "Big Picture".

@@ Line 71: / Line 71: @@
 ==  Specifying typefaces and fonts for a translation  ==
-Translations in a language which mainly uses characters outside of the Latin1 character set may want to specify different typefaces. In the translatable strings, there is a string named
+Translations in a language which use characters outside of the Latin, Greek and Cyrillic character sets may want to specify different typefaces. There are some translatable strings in data/hardwired/fonts.cfg which specify the fonts to use; these strings appear in the ''wesnoth'' text domain, and can be configured by putting the required fonts' names as the translations.
-  "DejaVuSans.ttf,wqy-zenhei.ttc"
-which specifies the order in which fonts are to be tried, for each character, before the program finds a font which contains this character: the font appearing first in the list is tried first. Translators may change this string in the translation.
+Note the documentation in data/hardwired/fonts.cfg.
 == See Also ==

← Older revision		Revision as of 20:02, 11 October 2021
Line 43:		Line 43:

	If you are a developer or UMC author, gettext internals for Wesnoth are discussed here: [[GettextForWesnothDevelopers]]. For UMC authors, the tool for generating .po files is linked to from [[GettextForWesnothDevelopers#Generating the_.pot_and_.po_files_for_UMC]].		If you are a developer or UMC author, gettext internals for Wesnoth are discussed here: [[GettextForWesnothDevelopers]]. For UMC authors, the tool for generating .po files is linked to from [[GettextForWesnothDevelopers#Generating the_.pot_and_.po_files_for_UMC]].
		+
		+	=== Files ===
		+
		+	We will use the Swedish (sv) language and the ''wesnoth-editor'' domain as an example. There are three important files for each text-domain:
		+	* ''wesnoth-editor/wesnoth-editor.pot'' file, which is a template containing all the strings used in the domain, but with empty strings instead of a translation. You can see how a ''.pot'' file looks like in the repository : [https://github.com/wesnoth/wesnoth/blob/master/po/wesnoth-editor/wesnoth-editor.pot#L50 Current repository version].
		+	* ''wesnoth-editor/sv.po'', the file containing the translation, you can see how a ''.po'' file looks like in the repository: [https://github.com/wesnoth/wesnoth/blob/master/po/wesnoth-editor/sv.po#L50 Current repository version].
		+	* ''{translations_dir}/sv/LC_MESSAGES/wesnoth-editor.mo'', which is a binary version of <lang>.po that the game will use for efficiency reasons. This is not found in the repo, but is created during compilation of the game.
		+
		+	The first of these files, we update every once in a while, when there is new or modified text,
		+	for instance when a new campaign scenario hits the repository.
		+
		+	Then, ''msgmerge'' is used to merge this new "state of the game strings" with your current translations, and generate a new, up-to-date, ''sv.po''.
		+
		+	Then, a tool called ''msgfmt'' is called, which generates a new ''wesnoth.mo'' file from your ''wesnoth.po'' file, which will be used by the game once installed.
		+
		+	"make -C po update-po" does these three steps in one pass.
		+
		+	That was for the "Big Picture".
		+	But you really just need to be concerned with the po file:
		+	translating new strings, checking "fuzzy" entries.
		+	We can handle the administrative tasks of updating etc.
		+	You really don't need to bother with any of these commands, unless you want to compile .mo files to check in-game.
		+
		+	Ivanovic is now responsible for integrating translations into Wesnoth, with the help of Torangan and ott.
		+	You should contact Ivanovic (crazy-ivanovic AT gmx DOT net), and he'll put them in the game.

	== Specifying typefaces and fonts for a translation ==		== Specifying typefaces and fonts for a translation ==

@@ Line 57: / Line 57: @@
 * [[TranslatorsGuide]]
 * [http://gettext.wesnoth.org Translation statistics]
 [[Category:Translations]]

@@ Line 26: / Line 26: @@
 the maintainer for their language to see if there is some work to do.
 After you have done some work on the translation you should email it
-to your language maintainer. He/she will then (if needed) check it over
+to your language maintainer. They will then (if needed) check it over
 before sending it on to the language coordinators. A list of all translators
 currently working on a language is found on each language page.

@@ Line 42: / Line 42: @@
 If you are a translator, see [[GettextForTranslators]] for more information.
-If you are a developer or UMC author, gettext internals for Wesnoth are discussed here: [[GettextForWesnothDevelopers]]. For UMC authors, the tool for generating .po files is linked to from [[GettextForWesnothDevelopers#Gettext_for_UMC_Developers]].
+If you are a developer or UMC author, gettext internals for Wesnoth are discussed here: [[GettextForWesnothDevelopers]]. For UMC authors, the tool for generating .po files is linked to from [[GettextForWesnothDevelopers#Generating the_.pot_and_.po_files_for_UMC]].
 ==  Specifying typefaces and fonts for a translation  ==

@@ Line 41: / Line 41: @@
 Notes:
-* If you haven't got Wesnoth from the souece-code repository, start out by doing so. Take a look at [[WesnothRepository]] for instructions about that.
+* If you haven't got Wesnoth from the source-code repository, start out by doing so. Take a look at [[WesnothRepository]] for instructions about that.
 * The old translation system, using cfg files and some wesnoth-specific tools (make_translation, merge_translation, weslang) was abandoned in the 0.8.3 release of Wesnoth in favor of the standard [[GetText|GNU GetText]] system.
 * Info about how the two branches do work can be found in the  [http://www.wesnoth.org/forum/viewtopic.php?t=7618 Forum].

← Older revision		Revision as of 14:06, 10 October 2014
Line 3:		Line 3:
	== How to submit your translations ==		== How to submit your translations ==

		+	Important: Please '''do not submit translations as pull requests''' on the Wesnoth github repository site. While that seems like a good idea, it causes potential complications that we cannot always easily resolve. As a result, we cannot accept translations submitted via pull request and will close such PRs immediately.

	'' ''' Translation Maintainers ''' ''		'' ''' Translation Maintainers ''' ''