Difference between revisions of "WesCamp"

From The Battle for Wesnoth Wiki
(More cleansing...)
(Delete the part that's moved to GettextForWesnothDevelopers, update the note that this page is obsolete)
(29 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
This page is dedicated to describing how to translate user-made content with the help of the [https://developer.berlios.de/projects/wescamp-i18n WesCamp-i18n] project.
+
''Note: WesCamp was a translation project, but activity stopped around 2014. Please follow the links in the See Also section for updated documentation.''
−
 
 
−
This project is hosted at [http://www.berlios.de/ BerliOS] and maintained by [mailto:david_AT_torangan.de Torangan] and [mailto:Majora700@gmail.com Espreon]. Add-ons are uploaded into the Subversion repository 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.
 
  
 
== If you are someone who just wants to translate  ==
 
== If you are someone who just wants to translate  ==
  
 
Then, simply go to http://gettext.wesnoth.org, and download the .po file of your chosen add-on and language. Then read the information '''for translators''' on this page here to know whom to tell what you are working on, and where to submit your translations.
 
Then, simply go to http://gettext.wesnoth.org, and download the .po file of your chosen add-on and language. Then read the information '''for translators''' on this page here to know whom to tell what you are working on, and where to submit your translations.
−
 
−
== How to contribute to this project ==
 
−
 
−
=== Add-on maintainers ===
 
−
 
−
If you wish to contribute to this project, you should:
 
−
* Make sure that there are underscores ( _ ) in front of translatable strings.
 
−
* '''Never''' mark an empty string ("") as translatable since wmlxgettext will abort upon detecting an empty string marked as translatable. In other words, avoid this:
 
−
  attribute= _ ""
 
−
* Make sure that you've got the #textdomain directives right. More information in this thread:  [http://forums.wesnoth.org/viewtopic.php?t=5535 Changes to translating user campaigns in wesnoth (post 0.9.1)].
 
−
* Notice that when you reuse official units, you can put them into the wesnoth-units textdomain and the game will automatically use the official translations. This does not work for textdomains from other content hosted here, only for the official textdomains! It also makes sense to have the description in your textdomain and to put an #textdomain wesnoth-units before the [attack] part. There's no real need to translate "sword", "bow" and friends in every add-on.
 
−
* If you want the names of attacks to be translatable, you need to add a field description = _"whatever" into the [attack] tag. This should be the same value as used for name= but that one can't be translated. As mentioned above, this only makes sense if you're using a new name.
 
−
* Add the "translate" attribute to your .pbl file and set it to true, and the rest will then happen automatically.
 
−
* If you have further questions feel free to join the #wesnoth [[Support#IRC|IRC]] channel on irc.freenode.net and ask in there. You can also ask your questions in the [http://forums.wesnoth.org/viewforum.php?f=7 Translations & Internationalization forum], or directly contact Torangan ( david AT torangan.de ).
 
  
 
=== Translators ===
 
=== 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 [http://svn.berlios.de/viewvc/wescamp-i18n/ Subversion repository]. When they are translated, mail them to [mailto:Majora700@gmail.com Espreon] or (as a last resort) [mailto:david_AT_torangan.de Torangan].
+
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:
 
Before you start translating you should:
Line 29: Line 13:
 
* Contact the translation team for your target language for guidance.
 
* 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:Majora700@gmail.com Espreon] or [mailto:david_AT_torangan.de Torangan].
+
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].
  
 
== See Also ==
 
== See Also ==
  
 +
* [[GettextForWesnothDevelopers|GetText for Developers]] - how make code translatable (both mainline and UMC)
 
* [[GettextForTranslators|GetText for Translators]] - how to translate Wesnoth using [[GetText]]
 
* [[GettextForTranslators|GetText for Translators]] - how to translate Wesnoth using [[GetText]]
 
* [[WesnothTranslations|Wesnoth Translations]]
 
* [[WesnothTranslations|Wesnoth Translations]]
 
* [[TranslatorsGuide|Translators' Guide]]
 
* [[TranslatorsGuide|Translators' Guide]]
 
* [http://gettext.wesnoth.org Translation statistics]
 
* [http://gettext.wesnoth.org Translation statistics]
−
* [https://developer.berlios.de/projects/wescamp-i18n WesCamp-i18n project at Berlios.de]
+
* [https://github.com/wescamp WesCamp project at Github]
−
* [http://svn.berlios.de/viewcvs/wescamp-i18n/ WesCamp-i18n SVN tree]
+
* [[Wescamp.py_Instructions|Wescamp for Maintainers]]
  
 
[[Category:Translations|*]]
 
[[Category:Translations|*]]
 
[[Category:Campaigns]]
 
[[Category:Campaigns]]

Revision as of 03:04, 18 May 2019

Note: WesCamp was a translation project, but activity stopped around 2014. Please follow the links in the See Also section for updated documentation.

If you are someone who just wants to translate

Then, simply go to http://gettext.wesnoth.org, and download the .po file of your chosen add-on and language. Then read the information for translators on this page here to know whom to tell what you are working on, and where to submit your translations.

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 Github repositories (they might take a bit of effort to locate. Alternatively, you can use gettext.wesnoth.org). When they are translated, send them to AI/AI0867.

Before you start translating you should:

  • Look at the subpage of the add-on you wish to translate to see if someone is already working on it.
  • Contact the translation team for your target language for guidance.

If you have questions, join the #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 Translations & Internationalization forum, or e-mail AI/AI0867.

See Also

Retrieved from "https://wiki.wesnoth.org/index.php?title=WesCamp&oldid=61018"