Hi there. I've seen you reverted this edit twice, which added a custom anchor to a section name. That is the recommended way to add anchors to section headings (see w:Template:Anchor for details). What must I do for the edit to not be reverted again?
User talk:Shirayuki
Use {{anchor}} and respect the existing translation units. "#Message file" is unused.
It's unused in that particular page, but it's used from other pages. I can use {{anchor}}, which unfortunately will result in polluted edit summaries that won't link to the right section, but that's a minor problem if that's what it takes for the anchor to stick. But what do you mean by "respect the existing translation units"?
The heading is translated by translators.
By adding a span to the heading, the existing translations (corresponding to the translation unit) will be invalidated and will wastes translators' time.
Hmm, I see.. but won't {{anchor}} have the same effect? Or are you suggesting I insert it somewhere other than the heading?
For example, see Growth/FAQ
Got it, so the idea is to place the anchor on top of the section title and outside the <translate>
tags. Thanks for clarifying!
And if you'd allow me some constructive criticism, it would have saved us both the time and back-and-forth if you had clarified this from the start. I notice from other threads here that it's a recurring issue that other people tend to have with how you edit pages and the very short edit summaries you use. I am not sure if the efficiency of the edits themselves balances out with the friction from the communication that ensues from your reversals of others' edits. Have you perhaps considered creating a FAQ page (or maybe one exists already?) that you could link to in the edit summaries when you do such reverts?
But, this is a typical example, why you should consider it, and create FAQ page.
I am sorry, it was to Shirayuki.
I understand that there is a lack of explanation. I've never really found FAQs useful, so I don't think I'll try to make my own.
Documentation of procedures is very important. For example, it's own help page about multilanguage links, and others.
Please respect the Inuse template to avoid edit conflicts.
Thanks.
The language bar is usually at the top. There are few exceptions.
The location doesn't matter. What matters is that you are not supposed to edit a page that is marked with the Inuse template by another user at all.
I see. Consider putting {{draft}} and/or {{DoNotTranslate}} as well.
If you continue to destroy my work unjustly... Then you can do the dirt yourself! At least give reasons...
Your trivial edit will invalidate the existing translations. The workaround for this is time-consuming, so I have reverted it.
I don't understand... One can simply change strings, the extension detects that and re-registers them? Doesn't it do that?
By marking your edit for translation, the existing translations will be invalidated. You should respect the existing translations.
I'm sorry, but are you kidding me? Surely the community has put work into their translations, what probably no one believes to know better than me! But to destroy MY work again, only because then existing translations are invalid...
God, that is sense and purpose of the thing! Otherwise this possibility would not exist at all! And if one goes after it, NO spelling, grammar and language errors should be corrected! There are errors in the strings, there is sometimes a word misspelled, a word was forgotten, then sometimes the formatting is wrong... This should be corrected, of course...
People know or should know that their translations then become invalid! Besides, it's not like that's the case on numerous other wiki pages here (cough, cough, irony, cough)...
Sorry, but if you really stick to it...
What are you talking about? What is so important about this edit?
Well, admittedly, it's something to argue about.... But let's be honest... It looks like crap in the source code!
Moreover, there is an option, where the hook can removed... This has the consequence that existing translations are not declared invalid or obsolete...
And... Really? @Clump you too? Like i said... I can also gladly stop my work, I do not care! However, you would then have to regulate everything alone, as far as the German translations are concerned...
The html generated by wikitext with or without spaces before/after the heading markup is the same. Please do not keep changing it just to reflect your personal style.
As mentioned before, it looks like crap in the source code and translation.
Someone once told me that a person who does not respect the existing translations is not suited to be a translation administrator.
In addition, then also this should not be
Sorry, but should I explain it again in Turkish? Or Ukrainian? I have already explained it once...
So, that's it! I don't let my work be destroyed by someone who is an administrator for God knows why, and thinks he's something better, knows it all.... It's not about whether edits are 'wanted', but relevant, which was the case with the latter! Sorry, but with a guardian like you I can not and will not work!
I'm going to retire for now, eventually I'll resume my work someday.... Till then, regulate the dirt nevertheless itself!
And before one gets the idea: Wow, one less... No, this 'one' also has feelings and takes the time and effort to work here... And if something is not right, reasons like 'not wanted' are the last! But please, you don't want my work? I like to go...
Think for yourself a little. Special:Diff/5635068
Yes, that's why I'm taking a break! It's not about whether I'm doing something wrong, because I am, I'm only a human too!
But one should already explain my mistakes to me? So that I can learn from them?
I don't see why one couldn't translate that....
Could you please move Gerrit/Tutorial to Gerrit/Git tutorial and Gerrit/Tutorial/tl;dr to Gerrit/Git tutorial/tl;dr?
Also, thank you so much for keeping up with my changes and marking them for translation!
I think we need to discuss whether those moves are necessary.
I made a lot of refactoring changes yesterday and now the page functions as the "Git tutorial". The original tutorial contained a brief explanation of how Gerrit works overall. That explanation has been expanded and moved to Gerrit/How Gerrit works. It also contained the web tutorial and how to comment on a change. That has been moved to Gerrit/Web tutorial.
I did this to make it more clear that users can can choose between using the Git interface or the Web interface when creating or modifying a change. The original tutorial page was also very long some useful contents could be missed if someone didn't read it all. The new Gerrit/How Gerrit works page acts as the new tutorial and allows beginners to follow the code submission and review process completely in a broad overview with specific links on how to do things part of that process. That way they don't have to scroll through the entire original tutorial page just to find how to comment on the code in a change.
The translatable page cannot be moved to a new name because of the following error:
Gerrit/Tutorial
- This translatable page consists of over 500 pages. Moving this many pages has been found to be unreliable. Please contact a system administrator to do this via a maintenance script.
hm okay then. it's fine if we don't move it. The links to it on other pages already reference it as the git tutorial so we're fine.
Request the page move at Project:Village Pump or on Phabricator.
As I expressed in Phabricator, in my understanding the page is NOT a Git tutorial. It is a tutorial how to use Gerrit (and how to use Git for Gerrit). Thus it should not be renamed I'd say...
Well it's a tutorial on how to use Git with Gerrit. That's why it's a subpage of Gerrit... It's not a general git tutorial.
I agree with Shirayuki and Andre that we should not rename it. When we migrate to GitLab we'll need an entirely different tutorial anyway, and as the two systems will exist in parallel for months or years we won't want to merge them into one.
I think I'm missing something though because whiki/Telepedia is not changing when I view it on other pages and encyc is not appearing.
wait... you got it. thanks!
https://www.mediawiki.org/w/index.php?title=API&diff=5680004&oldid=5679881
What's wrong about that markup? I thought that's the right markup if you want to enable translations.
You must imagine it as a translator. The TU as you created was totally wrong. The main task of markup is simple TU without wiki markup for minimize potentially problems.
I recommend read manual before for markup examples – Help:Extension:Translate/Page_translation_administration
Hello, thank you for your work. I assume that the reverts of Special:Diff/5661747/5661751 were done because of something about the translation tags, but I don't immediately see the problem. Would you mind explaining how I can improve the edits? I think it's important that the changes are reflected in the documentation and I'm happy to adjust how I'm editing, if I understand why this was reverted.
Sorry, I made a mistake while undoing a large number of edits by user User:Proactive programming. See Topic:X8tfolmmwpaww3r3.
Great, I'll reapply the changes in that case!
Ah you're much faster than me. And thank you for the additional cleanup.
Howdy! I see you reverted my edit on the {{Used by}} template because it doesn't work, or it broke the template? I tried adding it again, but I'm not entirely sure what I'm doing wrong, or why it won't display — do you have any idea why it isn't working?
Your edit contained extra -->
Oh perfect, seems I fixed it in the latest revision — can you mark it for translation?
Hi,
may I ask you a couple of things, please?
- Could you activate BOT for edit I did in the section Troubleshooting?
- It seems some parts inside the section T:23 are not marked for translation
thanks a lot
have you a nice day
Hi, wanted to ask what your opinion is about my request.... The rights would be quite practical!