Hi! In case you’re not yet aware of it: there’s a new, more HTML/XML-compatible translation variable syntax <tvar name="1">...</tvar>, which will hopefully help editor tooling. Old syntax still works and will probably work forever, but new code should use the new syntax, and we should gradually update old code as well.
User talk:Shirayuki
About this board
|
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.
After updating old code, check all checkboxes feature is needed to avoid invalidating the existing translation units.
@Shirayuki Can you please slow down your editing? You are making RecentChanges extremely hard to look at for actioning edits such as spam, and there is also complaints from other people about their watchlists.
"Old syntax still works and will probably work forever, but new code should use the new syntax, and we should gradually update old code as well."
Since it's indicated that the old method still works, There shouldn't be such a rush in what feels like to edit every single translated page on this wiki.
This seems like a task that would be prefer for a Bot Flagged account so the edits can be hidden.
I see. Sorry about that. I have edited pages containing more than 30 <tvar>s.
You used a sad smiley... Sorry to have you bothered. I'm sorry for not being familiar with translation-interface. But I used a fair amount of my time to check what this paragraph meant, so I thought I help the next user to save upon this time. I'd really appreciate, if you explain to me, what I should have done to avoid the sad smiley on your behalf :(.
Especially, since the warning doesn't seem to be translateable now and in my version, they should have, or am I wrong?
Regards
No problem. Be bold.
I was and you frowned... That didn't feel well. And actually I experienced this a lot in Mediawiki-Projects. I mean being bold and obviously not doing the right stuff. And instead of getting an explanation there usually happens one of three things: a simple revert, a "correction" (meaning changed in a way somebody else liked better, who didn't care for the stuff for month) or like in your case just an editing comment that does not help... BTW: You still did not explain, what I should have done. I'll probably refrain from editing again, so just not to bother. I'm sorry I don't mean to offend. Regards
See Help:Extension:Translate/Page translation administration.
<translate><!--T:X--> ...</translate> is a translation unit, so please do not add sentences or new lines to inside of the unit.
Thanks! But on the contrary, that's noted otherwise there: Help:Extension:Translate/Page_translation_example#Step_4:_Making_changes
Or am I misunderstanding the example?
Do I understand it correctly, I put the already translated, not changed, paragraph out of translation-synch (which isn't so bad after all, but causing the necessity to translate the whole text again, because the translation-IF gets messed up)? It would have been fine, if I just would have added my text before the < ! - - T:53 - - > -Tag? Cause then, the system would have known, that there is "only" a new paragraph and the old paragraph didn't change?
Regards
Hi, apologies for making the bad changes to various translated pages, and thank you for helping clean up the mess I left. I was wondering if you could explain what went wrong with a change like this, and how I can better verify my work next time. Maybe the mistakes are more visible in the translation admin interface?
Compare with the previous revision:
I tried to compare the rendered English and Japanese pages at each revision and they look identical to me. Where should I be looking to see a problem?
The thought behind my edit is that <translate> tags don't need to be closed and opened again immediately, they can span multiple translation units safely and this makes the wikitext easier to understand. I was hoping that my change wouldn't invalidate any of the translated units, but maybe that wasn't the case?
If you agree this is a worthwhile change but I made a mistake somewhere, I'd be happy to apply in smaller bites so we can experiment carefully and still improve the markup. If this page doesn't feel important enough to spend time on, I would understand that as well!
Compare paragraphs. "<translate> tags don't need to be closed and opened again immediately" is wrong.
Please let me know which paragraphs to compare, and in which language, or maybe post a screenshot? I still don't see where the mistakes occur.
The documentation suggests that <translate> can and should span multiple translation units, maybe the documentation is wrong, or I misunderstood it?
Compare the above two links. Compare the section "Dependencies". Why don't you find???
I see it now, thank you for your patience. I was looking for a text or translation unit change, but you were pointing out the extra newline in my version. I see the documentation about this under "splitting units", it seems that the translate extension requires the extra newline to automatically split units, otherwise they will be considered part of the same paragraph.
My suggestion is that the translation units (T:6 and T:94) should be merged, since they are meant to be rendered as a single paragraph—do you know why this hasn't been done already? Maybe just to avoid the invalidation and extra work for translators?
I don't understand what you wanted to do. You broke the page.
I was trying to reduce the number of unnecessary translate tags, they clutter the wikitext and make it difficult to edit.
The extra line break hardly "broke" the page, but I agree that my cleanup change should have been pure markup and not caused any visible differences on the page. Since it's partly my responsibility as a developer to help maintain mediawiki.org pages, I'll continue to do translation cleanup when possible, so I appreciate your help. In the future, at least while I'm still learning the nuances of page translation, I'll make smaller changes so they can be reverted individually.
See:
- Special:Diff/4526296 cleanup
- Special:Diff/4526304 fix wrong markup
As we already explained you Shirayuki, your “fix” still produces wrong markup with post-2020 Translate syntax: we need to exclude bullets from translate tags, like this.
But your edit makes the existing translation units outdated.
True, indeed, but easy to fix in any language: if you mark it now, I commit to fix all translations today. 
Done, thank you Shirayuki!
Hi Shirayuki,
I suspect that The IP address has attempted to evade a block which you have imposed, I have requested a CU https://meta.wikimedia.org/w/index.php?diff=21352622 .
Hey! @Shirayuki I request you to create a page for Gyaanipedia. It is a wiki farm, having various language wikis. So I think like Miraheze and WikiApiary, Gyaanipedia is also eligible to be here as it also uses MediaWiki software for its wikis. So it's my humble request kindly create a page for Gyaanipedia. Thanking you with due respect. Pokai (talk)
Ask at Project:Village_Pump. Thanks.
Thanks for the help getting the XTools pages set up for translation! I just did XTools/Page History, going by the corrections you made to the other pages, so hopefully I did it properly time time :) I intend to set up all the pages listed at XTools#User documentation, should you feel inclined to help.
Just one issue I noticed... Putting the <translate> tags around bulleted items breaks accessibility in the translated pages. For instance view the HTML of the bulleted items at XTools/de#ArticleInfo gadget. Each one is in its own <ul> tag, when there should only be one <ul> tag. I'm assuming we can fix this by changing the message from:
<translate>
* Number of revisions.</translate>
to:
* <translate>Number of revisions.</translate>
Is that correct? Many thanks for the assistance!
Untranslated translation units are enclosed in div tags. It will be resolved by translating them.
Yes, MusikAnimal: with post-2020 Translate syntax, we need to exclude bullet points/hash signs from translate tags, as it is shown in markup examples of Translate syntax doc.
Thanks, I will remove the bullet points from the messages as it seems they haven't been translated yet, so it's not too late.
Shirayuki, please follow the recommended syntax for lists per the documentation linked above. I see you have used the wrong syntax on other pages too, for example on MediaWiki history.
I have also observed a while that you are splitting a lot of existing translations units, for example here: https://www.mediawiki.org/w/index.php?title=MediaWiki_history&diff=4305770&oldid=4048950&diffmode=source. I understand this makes sense for translators, as it is easier to translate shorter units. However, you are needlessly invalidating existing translations (causing more work for translators) and making the page source more cluttered with the translation markup (which makes page editors less likely to edit and update the page). I think this practice does more harm than good, and I suggest you stop doing it.
I'd like to prevent changes such as those, which sole purpose is renaming variables. This makes no benefit to existing translations. In fact, it causes all of them to become invalid/outdated, consuming valuable translators time in fixing them. It's good to use this on new translations but please don't change them on existing translations unless there are also other changes to do in such translation units. Thanks for your cooperation.
Hello. Can you try to move Help:Edit Review Improvements/Gadgets and Help:Edit Review Improvements/Glossary to Help:New filters for edit review from parent pages? Thanks.
Hi! Please turn off translation-aware transclusion of Template:Free screenshot, otherwise my revert doesn’t have any effect (as it can be seen at the first two examples, which should show valid licenses instead of error messages). (Also, as I have indicated in several edit summaries, translation-aware transclusion simply doesn’t work for templates used on file description pages, as they always have page language set to English, so it shouldn’t have been turned on in the first place.)
Done
Hi Shirayuki, I can prepare page Help:Extension:Translate/Move_translatable_page for translate?