Project:Requests/User rights/Epok

ここを見ながら成長して行くものがある！ それが俺達から生まれたものであったなら、ここには美しいものが満ち溢れていてほしい！ 人には簡単に理解出来るような、痛み、悲しみ、苦しみの様なものをこの子達は何回朗読したのたのだろう？ ここに書いてある事が正しいと思い、自分自身で勉強して行くのだから、それが真実でなければならない！ 真実ではない事に気付いた時は、治したいらしい！

User: Epok
I was actively working on french translations these days, and I've encountered a limit on what a user can or can not do. When dealing with translations, the process is limited to translating what's on a page at the day a translation administrator marked the page for translation. When going a little further, i.e., editing the original english page (such as [//www.mediawiki.org/w/index.php?title=Parser_functions&diff=2536822&oldid=2413461 this edit I made]), you can't translate your own edit until a translation administrator marks the page as translatable again.

This is why I would like to gain the translation administrator right, as I think I may encounter such a limit again in the future. Moreover, I could use this status to help updating translation status on other pages that need such an action.

I also have one question, and I will use this opportunity to ask it: I've encountered different approaches in the way the namespace is translated on the title page item. Two approaches are used: e.g. for a page named Project:Example, one will translate it to Project:Exemple (leave original namespace), while other will translate it to Projet:Exemple (translate namespace). I've been using the second approach, believing that it's better to have a kind of "virtual namespace" according to the language of the page you're reading. Furthermore, it is more like Wikipedia's wikis (even if MediaWiki is not Wikipedia), in which the namespaces are translated. But I may be wrong, and did not find any information on that topic.

Have a nice MWday, Epok (talk) 08:27, 15 August 2017 (UTC)


 * It's ok to translate the namespace (and I agree it's preferable for help pages for instance). If one doesn't want the namespace translated, they can ask the translation administrator to prevent title translation.
 * As a translator you shouldn't normally need to remark pages for translation yourself. I see we now have 394 out of 3413 potentially outdated translatable pages right now, while they used to be very few. Probably the translation administrators have not noticed that Shirayuki has taken a break from his outstanding quick service. :-)
 * Back to your request: do you have any example of pages you marked for translation according to the page translation manual? --Nemo 10:39, 15 August 2017 (UTC)
 * Thanks for the info.
 * I did not mark any page for translation, as this require to be translation administrator. Did you mean tagging? If so, I haven't yet, but I've noticed a few pages which I want to migrate from the old raw translation page to the translation extension.
 * Epok (talk) 10:50, 15 August 2017 (UTC)
 * Yes, we say "prepare for translation" for the operation which includes tagging. Please let me know when you have prepared some such pages for a migration to Translate then. Thanks! --Nemo 11:04, 15 August 2017 (UTC)
 * That's right, I'll do soon. Do you have a specific page in mind that would require being translated? Epok (talk) 11:05, 15 August 2017 (UTC)
 * No, but Project:Language policy links some suggestions at Project:Language policy/Migration list and the first section of Special:PageTranslation probably contains some pages whose preparation is not complete yet. If you have trouble finding something to do, let me know. Nemo 11:10, 15 August 2017 (UTC)
 * Ok, enough choice in these pages I think!
 * I'll let you know when I've carried on a preparation.
 * Have a nice MWday, Epok (talk) 11:13, 15 August 2017 (UTC)
 * Hi again,
 * I've made a test using the Transclusion page. But as I had some doubts, I didn't published it yet. The diff can be seen here.
 * As a main concern, I wanted to know about  variables naming. I encountered some repetitive content I wanted to put into vars ("includeonly", "noinclude" and "onlyinclude" tags). So I named the var the same each time I encountered the same content. I was wondering if this is correct behavior or if it requires different variables names?
 * Thanks in advance, Epok (talk) 14:45, 15 August 2017 (UTC)
 * Any remark on the above concern about redundant tvar naming? Epok (talk) 16:58, 26 August 2017 (UTC)
 * Looks good, I have marked the page for translation. MacFan4000 (talk) 16:29, 1 September 2017 (UTC)
 * Thanks for your answer. The tool seems not to bother about the duplicate tags. I've commited the translation tags to the original page. Epok (talk) 19:06, 1 September 2017 (UTC)

Hi Epok, sorry for missing the updates here. From your diff I can't tell whether you understood the impact of newlines on translation units. Can you please prepare another page for translation, given you probably got more experienced in the meanwhile? Thanks, Nemo 15:05, 5 December 2017 (UTC)
 * Dear ,
 * It's OK, as I've not been very active recently... Thanks anyway for considering my request.
 * I've tried preparing the page Extension:Parser function extensions for translation, although I'm not sure about how to handle the big table: if I put it into a single translate tag, will the software be able to separate the cells by itself, or do I have to manually handle each wikilink?
 * Thanks again,
 * Epok (talk) 20:40, 9 December 2017 (UTC)
 * In that table there is nothing for translate, except headings. All content non wrapped by translate tags will be copied to translated versions of page. --wargo (talk) 00:54, 10 December 2017 (UTC)
 * Actually, the links' text is translatable. Well, at least built-in, the other texts being extensions names.
 * Epok (talk) 08:49, 10 December 2017 (UTC)