We should expand upon the "don't add translate tags" warning and explain what the

languages /



tags are and how they should be handled.

(It seems like it didn't like the tags so I removed the <> for convenience.)

(This is mostly a note to myself, but if someone has time to do it before me - go ahead if you want.)

17:50, 21 September 2010

For future reference, you need to use <nowiki></nowiki> tags around anything that mediawiki would see as a command.

07:19, 22 September 2010

Hm, I think I tried <pre></pre> and <nowiki></nowiki> but it still complained. Maybe I missed the latter, I'll find out when I write the text. :)

11:16, 22 September 2010

What exactly are you going to write about? We have covered it in the appropriate pages. And pages are linked, wherever appropriate. Dulpication makes it hard to maintain.

12:40, 22 September 2010
Edited by another user.
Last edit: 08:14, 4 June 2011

Which pages would that be, Edit Markup? I think it's very relevant on this page, since you'll see it if you edit some pages, and many contributors are probably unsure of how to handle them. The first two tags only need a short mention, but <!--T:n--> should be explained in my opinion (what to do if you add, move or remove text etc.).

14:35, 22 September 2010
Edited by 0 users.
Last edit: 17:39, 22 September 2010

The description of the task this page refers to says "Modify existing content, fix a spelling, clarify a description, add more details." Adding markup is not part of that task at all. The only markup that is relevant to this page is the warning to leave tags alone.

Please keep the tasks discrete.

17:39, 22 September 2010

It's not about adding markup, it's about how to handle the existing markup - i.e. the <!--T:n--> tags.

For most parts the contributor can just ignore them (modifying existing content), but what if he/she moves some text around or deletes some text? I also think we need to clarify what we mean by "NEVER add new translate section tags.", since some may not realize what <!--T:n--> are for and add them for the new text.

17:46, 22 September 2010

The instructions for handling markup are on the page about preparing for translation, where they belong.

18:13, 22 September 2010
Edited by 2 users.
Last edit: 08:20, 4 June 2011

I would still argue that the information belongs on this page as well, at least a mention and link to further information.

  • Contributors who edit pages will encounter them.
  • There will be people confused about how to handle them (this happened during the Plasma doc writing, for example).
  • As you said these people aren't necessarily interested in preparing pages for translation. They shouldn't have to read that page to find out if then can delete <!--T:n--> or not, or how to move a bulk of text.

I would say that this is even more relevant on this page than on preparing for translation page for the reasons above.

By the way (not directly related to the issue above), I couldn't find the <!--T:n--> tags being mentioned in Edit Markup.

18:24, 22 September 2010

There is already, in the Warning box, a link to EditMarkup and the Typographical_Guidelines. The purpose of that warning is that anyone editing text as described should not be touching the tags at all. I will think about whether it is appropriate to write more about the tags, but it will not be on this page. It is entirely inappropriate to the task.

I have changed the warning slightly.

09:52, 23 September 2010

@annew, the problem is a simple cut and paste to a page section can result in <translate> tags appearing in preview and incomprehensible garbled internal errors like "Unbalanced </translate> tag."

Maybe leave the general instruction, but please can those errors link to something that gives you enough info to fix the problem? (I've spent 25 bloody minutes fighting --T5-- warnings and unmatched </translate> after a 2-line edit, and I've worked with SGML/HTML/XML for 26 years.)

(later...) I now realize that when editing a section, you're often presented with unmatched translate tags from this section title and the next section's title. Maybe they should always go inside the === === title markup?!
00:49, 13 January 2012

No, they should not. Perhaps you would like to share a link so that we can see where your struggles have been?

18:03, 14 January 2012