Feed The Beast Wiki:Conventions for translation administrators


 * This guide is designed to replace the previous translation markup guide.

Conventions for translation administrators serves as a guide for properly marking up templates, articles, pages and for properly editing and maintaining marked up pages. It largely applies to those attempting to mark up pages, but normal editors should pay attention as well so as to not damage existing translations. For simply writing translations of pages, see the translation guide and/or the translation portal.

Applying translation markup
Note: This should only be done by a translation administrator or under their guidance.

The majority of applying translation markup to pages is the appropriate insertion of and  tags. These tags should be inserted around all of the displayed text in the page. However, while they can contain some basic formatting, they should contain as few complex template calls or larger structures (such as tables) as possible. In the case of templates and tables, insert tags around textual template parameters, and around the contents of cells within tables.

The second stage of applying translation markup to pages is to fix page links. All standard links should be changed to uses of L, in the form of. A similar rule applies to Templates. All translateable templates should have an appended to their calls, in the form of. Categories should be treated similar to templates, in the form of.

Finally, as is noted in the article creation guideline, all pages should be created including the final line required for translations to function. Before saving the page, make sure that the "langbar" (as it is called) is present at the end of the page.

Once the required edits have been performed, make sure a translation administrator approves, and then the "Mark for translation" button that appears at the top of the page can be pressed by them or by someone with the Editor role. This button will activate the translation extension, which will divide the page into a series of translateable units. If all units have been created appropriately, the page can be saved, the will register the markup, and translators can begin their work on the page.

Editing around translation markup
Translated pages can still be edited mostly like normal pages, with a few advisories.
 * All sections of the page that have been marked by the Translation Extension will contain tags and  comments. These comments refer to individual sections, usually paragraphs, of the translated page. Do not add or modify these T:# comments under any circumstances.
 * Do not delete these tags or comments, unless your edit to the page fully deletes the paragraph with which the comment is associated. A full rewrite is not the same as a deletion; if the paragraph still serves the same purpose, keep the tag. Deleting one of these comments results in the deletion of that paragraph from all translated versions of the page.
 * If you are going to change the order of sections or paragraphs in a page, move the along with their associated paragraphs, and ensure that all existing T:# paragraphs are fully contained within  tags.

If you are either improving existing content or adding new content, without deleting existing content, you the editor should not worry.

As is noted in the ACG, all pages should be created including the final line required for translations to function. As such, if a page is encountered that does not have that as its final line, please put it there.

Misc stuff

 * All test pages and user pages should be "discouraged" from translation. Although users may translate their user pages if they so desire, it should not be considered as a priority for regular translators.