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?
User talk:Shirayuki
About this board
Not editable
|
This is a MediaWiki.org user page. If you find this page on any site other than MediaWiki.org, you are viewing a mirror site. Be aware that the page may be outdated, and that the user this page belongs to may have no personal affiliation with any site other than MediaWiki.org itself. The original page is located at https://www.mediawiki.org/wiki/User_talk:Shirayuki. |
 |
 Archives
| |
|---|---|
| |
Previous page history was archived for backup purposes at User talk:Shirayuki/LQT Archive 1 on 2015-07-10.
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.
Hello,
@shirayuki thank you for marking for translation the pages at Wikimedia Hackathon 2020. Can you please help again to mark for translations also the below pages:
- Wikimedia Hackathon 2020/Venue and Tirana
- Wikimedia Hackathon 2020/Travel
- Wikimedia Hackathon 2020/Register
Shortened redirect pages are necessary for better searching and linking within the wiki, as well as for generating shorter hyperlinks and interwikilinks to pages on mediawiki.org. The benefits gained from having both SimpleMathJax and Extension:SimpleMathJax on the wiki far outweigh any costs. Nicole Sharp (talk) 08:00, 4 June 2019 (UTC)
Use [[Special:MyLanguage/Extension:SimpleMathJax|SimpleMathJax]] or {{ll|Extension:SimpleMathJax|nsp=0}} on mediawiki.org.
That's even longer. It's just faster and easier to type "SimpleMathJax" when linking or searching, than having to type in "Extension:" as well, if it can be made unnecessary with a simple redirect: https://www.mediawiki.org/wiki/SimpleMathJax is faster to type and easier to share. For the redirect, there isn't any risk of conflation or need of disambiguation (like there would be for "MathJax"). Nicole Sharp (talk) 18:50, 5 June 2019 (UTC)
When I came here, I barely understood the translation system here on MediaWiki and tended to add as seemed intuitive based on the code already present.
I've now discovered Help:Extension:Translate/Page translation administration and will try to operate based on it in the future.
Also, I'm assuming that <tvar|1> and <tvar|2> work the same as <tvar|first variable name> and <tvar|second variable name> when within <translate> tags, right?
No, "1" and "2" are variable names. I think variable names should be untranslatable, because some translators translate variable names.
Okay, should've just read that help page closer again. So they get shown to editors as "1" and "2" to discourage them from translating.
Hi, can you remark Extension:CentralAuth for translation? Can't seem to get it shown on the translated page. Thanks. ~~~~
Why is there only an edit and review/accept link, but no reject change option, for previously entered translations? Or if there is such an option - where would it be located? Couldn't find an undo option on it anywhere.
What are you talking about?
When I was trying to blank/undo the invalid translation earlier:
https://www.mediawiki.org/w/index.php?title=Developer_hub/nl&diff=prev&oldid=3582906
I deleted your wrong edits on Translations:Developer hub/Page display title/nl and Translations:Developer hub/67/nl.
To nominate a page for deletion, use {{speedy}} or {{delete}}.
About the translation interface, ask on Project:Support desk or request on Phabricator.
Hello, I've partially reverted your edit at Help:Growth/Tools/How to claim a mentee, because it seems it broke the displaying of {{Growth/Active wikis}} – on my computer, it looked like . Is the use of {{TNT}} in this case discouraged for some reason, or is that a mistake? Thanks for your care of translatable pages!
Thanks. Fixed by adding {{#switch:...}}.
Thank you!
Just for my own curiousness, could you please explain why what you did is preferable? Feel free to link to relevant docs.
I borrowed this idea from Meta-wiki. There are no docs.
The source page have <translate>...</translate> tags, but translation pages do not have them. See:
Hi, thanks for your work of keeping hooks up to date!
FWIW, hooks (to the extent they can be identified from extension.json) are available in structured form via Module:ExtensionJson. If you are familiar with Lua coding, a more sustainable approach might be to make the extension template read them from there when no hook parameters are manually provided. (The same goes for a number of other extension fields as well.)
Thanks. It's a cool approach, but some hooks are not listed in extension.json. See Topic:Ve7nni3u3s2xw4wa.
Yeah, I imagine we'll have to end up with some way to manually add hooks to the template. Maybe just interpret hook1 etc. as additional hooks (but then the template would have to deduplicate), maybe have dynamichook1 or something like that.
(The structured data also wouldn't work for extensions which have not been ported to extension registration yet.)
I found that name of the page for maintenance script transstat.php is Manual:transsat.php – it's wrongly. Is there a reason why it's called differently? I ask you because when you marked the page for translation you had to find out that it is different name. Or is it mistake and I can do repair?
Ask the original author.
I could start a template, called "red link", which is to link to nonexistent pages, but prevent the page from showing on special:WantedPages. Its code is:
<span class="plainlinks">[{{fullurl:{{{1}}}|action=edit}} <span style="color: #ba0000">{{{2|{{{1}}}}}}</span>]</span>
It'll be mostly used on talk pages, and on Help:Magic words to remove MediaWiki:xyz from the list of wanted pages.
It looks good. Go ahead.
By making this edit, you added the template page Red link to the category Template documentation pages, but you stated it'll be easier to translate the documentation.