This is a problem. It creates invalid HTML on that page (Help:Links), since it results in two identical 'id' values on the same page. What are we going to do about this?
Topic on User talk:Shirayuki
As I wrote, it is required for translation pages. If it is a problem, please file as a bug on Phabricator.
You would have to do that, since I am not familiar with the technical details of how translation works. (I'm not even sure what we would be asking them to do, exactly.)
This seems more like a "cultural" problem (i.e., we've decided to do things this way, mostly for convenience) than a technical one (it is actually required to do it this way).
Could such redundant anchors be <!-- commented out --> on the English version and then uncommented on the non-English ones?
Do you know if this has been discussed before (say, at Project:Current issues)?
I was asked to chime in, so I'm here. As a translation admin elsewhere, I usually don't care that much about anchors. I know Translate has some flaws and this seems to be another one. Raising at the talk venue or in Phabricator is a good idea. Anyway, no edit warring please.
There is no edit warring.
I still don't understand why inserting redundant anchors is somehow "required". What technical limitation is involved here? AFAICT, this is being done merely to aid translators who may not realize that they should include anchors in the translated versions that work with existing section links (in the English version). In other words, a cultural issue, not a technical one. Am I wrong about this? How?
File as a bug on Phabricator or discuss at Project:Current issues. There is nothing I can do any more.
I can't file a bug report if I don't understand what makes this a bug. Why aren't you getting this?
You are the one who claims duplicate anchors are somehow "required". I don't believe that is true. Thus, I don't think this is a bug at all. And therefore I have no reason to file a bug about it.
I can, however, ask someone else who might deign to answer my question instead of just repeating the same non-answer. So, yeah… goodbye.
I don't think this is a problem. Nothing to do.