User talk:Shirayuki

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.

The MediaWiki logo

Previous page history was archived for backup purposes at User talk:Shirayuki/LQT Archive 1 on 2015-07-10.

For example, Extension:Cargo/Storing_data/zh is so-called "100% translated", but still a large proportion is not translated actually. Please fix the translation markups for these pages again. Thanks.

I tried and added trans-tags to the first chart/table. I noticed we have two identical indicators: T:34. Sorry, but not working on the second table, or await fix for that one.

Hello there,

Would you have a look whether two captions are mismatched? Translation target #182 vs #177 on Reading/Web/Desktop Improvements/Repository/Sticky Header and Table of Contents User Testing:

• Dot type but placed for floating

• Floating box type but placed for dot type

Cheers, and please take care,

Hello sir, Hope you are well. I am a contributor at Ks Wikipedia. The community is small so we have to get help from outside, so sorry to bother you. Actually I imported a number of templates from enwiki occassionally as needed locally, However In few template there is an error. Eg in Template:Display. Can you please fix it. That will be really appreciated.

Hi, #ifexpr assumes that parameters are written in Latin characters, so language code "en" should be added to #time .

Thankyou so much.

The reason why I want to mark them (function names as headings) as translatable is, when translating the page, translators can better know which section they are translating. You can see also LUAREF, where titles are all translated.

	The Admin's Barnstar
	Shiela panoso Shiela050 (talk) 19:47, 27 August 2021 (UTC)

 Done

Currently the page Manual:Wiki family is extremely outdated with the emergence of latest Wikimedia packages. People wasting their valuable time while following the outdated instructions thereon. The edit which I have done regarding "$wgServer" setting was very essential to run latest mediawiki installation. I too waste a lot of my valuable time in this regard and finally found the real cause. So it is the benefit of many people like me those who wanted their mediawiki farm run locally. So If you are in big reverting spree please publish a better solution than my edit and be a responsible person

We need a solution aganist the rewriting prooblem with Mediawiki at browser address bar while loading a page. As this problem makes all of the solution given this page useless, especially in case of XAMPP localhost mediawiki farm setup.

We need a solution aganist the rewriting prooblem with Mediawiki at browser address bar while loading a page. As this problem makes all of the solution given in this page useless, especially in case of XAMPP localhost mediawiki farm setup.

So please bring back my edit or provide better alternae.

Because time is precious for every person.

Your edit(s) contained unwanted <translate>...</translate> and <tvar> tags. Please do not use them in talk pages.

Thanks for your concern and the following corrections on my edit

I further modified the edit and willing to publish the same on the Manual page. So please check for the currections, as per your requirement but please keep the content.

Regards.

Thanks for your generosity to keep the edit afloat,

But

" Final and very important step to modify "Manual:$wgServer"

What's the meaning of such heading?

Should the reader/visitor modify the page Manual:$wgServer on MediaWiki?

or Modify his/her variable "$wgServer" at LocalSettings.php ?

My intended meaning was the later one, i.e modify the variable "$wgServer" for the required result.

If anybody reading and confused with the name "$wgServer" they can find more of its details through the given link. That's what the purpose of the link added with that word "$wgServer"

So Please remove the word Manual from Manual:$wgServer otherwise, and if it cause contradiction with your policy, remove the link and make it plain $wgServer at least as it was indented.

Requesting you to keep the edit meaningful and informative by acknowledging the efforts and pain we took in background for getting that small bit of information.

Regards.

Hi, you marked the page for translation, but you rermoved the whole translation units, so, only the headings are translatable, while the text is not. Please fix that.

Please do not add translation unit markers manually.

Hello! Would you be able to translate this message about the Desktop Improvements? I will post it on Wikipedia in Japanese. I'd like to do that within 3-4 days.

As you can see, at the bottom, there's an invitation to an online meeting which will be taking place on Friday at 16:00 UTC. We know people in Japan sleep at that hour. I won't publish this part on Wikipedia in Japanese. Instead, we will see how many (America/Africa/Europe-based) people participate and if there's a lot, then we'll organize next office hours at a Eastern Asia-friendly time.

Thank you!

Hi, about your newest change - I understand and agree that <translate>==Heading==</translate> is generally better than ==<translate>Heading</translate>==.

However, let's take a look at the page you've linked to. Why the second option is better? "This way someone can quickly translate the table of contents before going into the contents."

In the case of my message, there is one heading, and the message will not be sent if it's not 100% translated.

IMHO in this particular case, it makes little sense to additionally encourage the translators to translate the only heading first, and the rest later.

Apart from that, I take the point, and I'll be paying attention to this difference. Thank you!

 Done

Hi, on [Wikilove] :

<syntaxhighlight lang="JavaScript">
$.wikiLoveOptions.types.puppy = {
	name: 'Puppy', // name of the type (appears in the types menu)
	fields: [ 'header', 'message' ], // fields to ask for in form
	header: 'You get a puppy!', // header that appears at the top of the talk page post (optional)
	text: '[[File:2009-08-16 Puppy at Duke East 1.jpg|left|150px]]\n$1\n\n~~'+'~~<br style="clear: both;"/>', // $1 is the custom message
	icon: 'http://www.mysite.com/images/wikilove-icon-puppy.png' // appears in the types menu
};
</syntaxhighlight>

you have deliberately cancelled my work with tag 'wrong markup' without providing a solution. I told in my comment that this was done to be coherent with the upper situation in the upper paragraph where the comments ARE translated. So it is not convenient to keep only EN page coherent; translated page but be too. Then can you please formulate the 'right' format teaching everyone, so that I could continue my work ? Thanks.

Christian 🇫🇷 FR (talk) 16:56, 6 August 2021 (UTC)

Use ‎<translate nowrap> instead of ‎<translate> in ‎<syntaxhighlight>...‎</syntaxhighlight> tags. See Help:Extension:Translate/Page translation administration .

done, hope its ok now.

Christian 🇫🇷 FR (talk) 16:43, 7 August 2021 (UTC)

Hello! Thank you for your edits. If you're planning to translate that page, I'd be grateful if you gave me some time before you begin translating. I need to cut the longest sentences into shorter pieces.