User talk:Shirayuki

Jump to navigation Jump to search

About this board

This is a user page.

If you find this page on any site other than, 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 itself. The original page is located at

The MediaWiki logo

Possible block evasion by The IP address

Nieuwsgierige Gebruiker (talkcontribs)
Reply to "Possible block evasion by The IP address"
Adamw (talkcontribs)

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?

Shirayuki (talkcontribs)
Adamw (talkcontribs)

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!

Shirayuki (talkcontribs)

Compare paragraphs. "<translate> tags don't need to be closed and opened again immediately" is wrong.

Adamw (talkcontribs)

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?

Shirayuki (talkcontribs)

Compare the above two links. Compare the section "Dependencies". Why don't you find???

Adamw (talkcontribs)

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?

Shirayuki (talkcontribs)

I don't understand what you wanted to do. You broke the page.

Adamw (talkcontribs)

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 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.

Shirayuki (talkcontribs)
Reply to "My bad translate tags"
Pokai (talkcontribs)

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)

Shirayuki (talkcontribs)
Reply to "Request for page creation"

Setting up XTools pages for translation

MusikAnimal (talkcontribs)

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:


* Number of revisions.</translate>


* <translate>Number of revisions.</translate>

Is that correct? Many thanks for the assistance!

Shirayuki (talkcontribs)

Untranslated translation units are enclosed in div tags. It will be resolved by translating them.

Pols12 (talkcontribs)
MusikAnimal (talkcontribs)

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.

Nikerabbit (talkcontribs)

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: 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.

Reply to "Setting up XTools pages for translation"
Ciencia Al Poder (talkcontribs)

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.

Reply to "Renaming variables"
Baris6161TURK (talkcontribs)
Reply to "Moving pages"
Tacsipacsi (talkcontribs)

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.)

Pppery (talkcontribs)

Yes Done

Reply to "Template:Free screenshot"

Help about move translatable page

Want (talkcontribs)
Reply to "Help about move translatable page"

TemplateData's content translation (in Wikidata) of a local template

Summary by Shirayuki

Yes Done

BoldLuis (talkcontribs)

I suggest translate a template (i.e. template description field) for a local template into another local templete (i.e. from a local Wikipedia to another one) using Mediawiki translation tools in its TemplateData.

Shirayuki (talkcontribs)

I don't understand.

BoldLuis (talkcontribs)

One could translate a w:template documentation from another language to another one, translating the TemplateData of this template. This includes description and parameter description. For templates, in Wikidata would be stored the data from TemplateData (and also its description translations to other language from the original TemplateData).

Shirayuki (talkcontribs)

What are you talking about? What do you want me to do?

BoldLuis (talkcontribs)

I have done it in Wikipedia Template:Short description. I have translated the TemplateData from English to Spanish (you can edit TemplateData and select "español" -this is, Spanish- to see the translation into Spanish).

The problem: I have to translate the template documentation (TemplateData of the template) in the English Wikipedia and copy and paste it into the documentation page o f the template in the Spanish Wikipedia.

This is not good. The best idea is that I could see the translation in the Spanish Wikipedia, without copy and paste, in a Wikidata manner (global documentation from TemplateData).

Also, this translation into Spanish could be seen in Wikibooks in Spanish, Wiktionary in Spanish and so on, without copy and paste the TemplateData from the English Wikipedia to Wikibooks in Spanish, Wiktionary in Spanish and so on.

Shirayuki (talkcontribs)

I can do nothing about it.

BoldLuis (talkcontribs)
Shirayuki (talkcontribs)
Trizek (WMF) (talkcontribs)

Hello Shirayuki

Thank you for the help you provide regarding translations!

I have a question about this diff. I understand the reason why you're removing detailed names, since they can be translated and then can break.

But, on the other hand, it is more comfortable to translate while you have some context. For instance, if an expression is added as a parameter, I prefer to have a more descriptive parameter.

What is your opinion on this?

Thank you!

Shirayuki (talkcontribs)

Some translators translate variable names, so they should be untranslatable.

Trizek (WMF) (talkcontribs)

Yes, but some translators badly translate things because they have no idea of the context. Experience allows me to fix bad links, but I can't fix bad translations. :)

Shirayuki (talkcontribs)
Reply to "Untranslatable variables"