WesCamp - Revision history

Shadowm at 23:43, 22 May 2021

2021-05-22T23:43:55Z

2019-05-18T03:04:37Z

Delete the part that's moved to GettextForWesnothDevelopers, update the note that this page is obsolete

2018-05-26T12:10:57Z

Link to GettextForWesnothDeveloper's copy of WesCamp's docs

2018-02-27T06:53:28Z

‎Preparing your add-on for WesCamp: Syntax hiliting

2018-01-12T09:44:04Z

2016-05-25T03:51:14Z

‎The translatable strings

2015-04-04T01:55:24Z

2014-02-22T20:57:17Z

2013-11-10T16:52:20Z

2012-06-04T14:27:37Z

‎Encoding and Filenames

@@ Line 13: / Line 13: @@
 * Contact the translation team for your target language for guidance.
-If you have questions, join the [irc://irc.freenode.net/wesnoth #wesnoth] channel on the Freenode IRC network and ask in there. Of course, you will also get answers if you ask your questions in the [http://forums.wesnoth.org/viewforum.php?f=7 Translations & Internationalization forum], or e-mail [mailto:AI0867_AT_gmail.com AI/AI0867].
+If you have questions, join the [irc://irc.libera.chat/wesnoth #wesnoth] channel on the Libera.Chat IRC network and ask in there. Of course, you will also get answers if you ask your questions in the [http://forums.wesnoth.org/viewforum.php?f=7 Translations & Internationalization forum], or e-mail [mailto:AI0867_AT_gmail.com AI/AI0867].
 == See Also ==

← Older revision		Revision as of 12:10, 26 May 2018
Line 1:		Line 1:
	''Note: As of April 4th, 2015, Wescamp appears to have been abandoned for about a year. It might be back soon, it might not. Someone with knowledge of the project should update this page.''		''Note: As of April 4th, 2015, Wescamp appears to have been abandoned for about a year. It might be back soon, it might not. Someone with knowledge of the project should update this page.''
		+
		+	''Note: The documentation about how to mark up WML has been copied to [[GettextForWesnothDevelopers]], and documentation about translation without WesCamp has also been added to that page.''

	This page is dedicated to describing how to translate user-made content with the help of the [https://github.com/wescamp WesCamp-i18n] project.		This page is dedicated to describing how to translate user-made content with the help of the [https://github.com/wescamp WesCamp-i18n] project.

@@ Line 1: / Line 1: @@
 ''Note: As of April 4th, 2015, Wescamp appears to have been abandoned for about a year.  It might be back soon, it might not.  Someone with knowledge of the project should update this page.''
-This page is dedicated to describing how to translate user-made content with the help of the [https://github.com/organizations/wescamp WesCamp-i18n] project.
+This page is dedicated to describing how to translate user-made content with the help of the [https://github.com/wescamp WesCamp-i18n] project.
 This project is hosted at [https://www.github.com/ GitHub] and maintained by AI/AI0867. Add-ons are uploaded to git repositories and .po files of the content are created. The .po files are updated regularly and the stats can be found at http://gettext.wesnoth.org.

← Older revision		Revision as of 03:51, 25 May 2016
Line 92:		Line 92:

	Since those are not in the catalogues, they will not get translated.		Since those are not in the catalogues, they will not get translated.
		+
		+	If you think a translatable string needs additional guidance to be translated properly, you can provide a special comment that will be seen by the translators. Just begin the comment with '#po:' above the string in question:
		+
		+	#po: "northern marches" is not a typo for "northern marshes" here.
		+	#po: In archaic English, "march" means "border country".
		+	story=_ "The orcs were first sighted from the north marches of the great forest of Wesmere."

	=== The gettext helper file ===		=== The gettext helper file ===

← Older revision		Revision as of 01:55, 4 April 2015
Line 1:		Line 1:
		+	''Note: As of April 4th, 2015, Wescamp appears to have been abandoned for about a year. It might be back soon, it might not. Someone with knowledge of the project should update this page.''
		+
	This page is dedicated to describing how to translate user-made content with the help of the [https://github.com/organizations/wescamp WesCamp-i18n] project.		This page is dedicated to describing how to translate user-made content with the help of the [https://github.com/organizations/wescamp WesCamp-i18n] project.

@@ Line 135: / Line 135: @@
 === Translators ===
-Translating add-ons works the same as translating mainline. All of the information about this already exists in the wiki (see the links below). The files you need are located in the project’s [https://github.com/wescamp Github repositories] (they might take a bit of effort to locate. Alternatively, you can use [http://gettext.wesnoth.org gettext.wesnoth.org]). When they are translated, mail them to [mailto:AI0867_AT_gmail.com AI/AI0867].
+Translating add-ons works the same as translating mainline. All of the information about this already exists in the wiki (see the links below). The files you need are located in the project’s [https://github.com/wescamp Github repositories] (they might take a bit of effort to locate. Alternatively, you can use [http://gettext.wesnoth.org gettext.wesnoth.org]). When they are translated, send them to [mailto:AI0867_AT_gmail.com AI/AI0867].
 Before you start translating you should:

@@ Line 13: / Line 13: @@
 === Encoding and Filenames ===
-Your files '''must''' be in UTF-8 (not whatever other encoding you might happen to be using/want to use, such as ISO-8859-15) and there '''must''' be '''no''' spaces in any of your add-on’s files’ filenames.
+Your files '''must''' be in UTF-8 (not whatever other encoding you might happen to be using/want to use, such as ISO-8859-15) and there '''must''' be '''no''' spaces in any of your add-on’s files’ names.
 === The textdomain declaration ===