Hi! I noticed you reverted my translation markup twice (1 & 2) with a "wrong markup" summary. I'm not sure what I'm doing wrong. Could you help me by showing me how to do it right? Thanks!
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.
(1) Your rough markup makes translation hard. (2) Module documentations have never been marked for translation.
I see. Translating this documentation would be useful because the module aims directly at being used on multiple wikis (see Multilingual Templates and Modules). Tomorrow I'll look deeper into proper markup and do another attempt. Any help would be appreciated, thanks!
Templates can be marked for translation directly (e.g. Template:Note), but modules cannot.
hello Had a question: Wikipedia and Wikipedia, how to search engines like Google To introduce? Thank
Hello!
I'd like to inform you that today, I'm going to make major changes on these pages, and I'd like to ask you to withhold any edits today.
By the way, is it really encouraged to mark each sentence for translation separately? Is it a commonly followed good practice? Or is it a practice of some (a minority of?) translation admins?
I know that having long paragraphs as one pieces for translation is not useful from the translators' perspective, but imagine an opposite case: if each sentence is marked separately, it may (and does) happen that some sentences are up-to-date and some are brand new and not translated, and thus, there is no pink background in such a paragraph, and at the first glance, it appears as it was fully translated. This, in my opinion, isn't convenient for readers.
if each sentence is marked separately, it may (and does) happen that some sentences are up-to-date and some are brand new and not translated, and thus, there is no pink background in such a paragraph, and at the first glance, it appears as it was fully translated
I think this is wrong. Outdated sentences have pink background.
Yes, outdates sentences do have it, but I didn't mention outdated ones, but a situation when you've got translated sentences and totally new ones. Not updated/outdated, but new ones added.
Hello Shirayuki,
I see no reason to revert my translation preparation. If I have made a mistake, you can fix it instead of reverting my whole contribution. And please, explain me why you consider my edits contain “wrong markup“.
Your markup makes translation hard. I fixed Help:Extension:GWToolset. My edits indicate the reason.
I don’t speak you about Help:Extension:GWToolset which I had not finished (my edit summary said it).
I speak you about Talk pages project for which I have well put all needed tvar’s.
Hello. I spend big piece of time to prepare this page for translation - and now I see you've just reverted most of this edit so the bulk of the page remains untranslated. It's not so easy to quickly restore translation tags now.
Your wrong markup makes translation hard.
Hi, I think your edits to prep Template:Partial for translation caused an error here - Alternative parsers
how?
Oh, it seems fine now actually, there was a Lua script error where it was used and that page hadn't been edited recently. Sorry about that!
Good morning, I apologize in advance for the inconvenience. I am an admin of vec.wiki, I wanted to ask for information. Among the interwiki on the right of the page, by clicking, the names of the languages localized by continent come out. The Venetian language is found correctly on Europe, however it is official and spoken by 5 million people in southern Brazil (South America). I wanted to ask how it could be done to add it to that list too? Thank you very much in advance for your reply and a good job!
The feature is a part of Universal Language Selector. Its locale data is retrieved from CLDR.
Search "Brazil" in the page https://unicode-org.github.io/cldr-staging/charts/37/supplemental/territory_language_information.html
CLDR says that the following languages are used in Brazil: Portuguese, English, German, Italian, Japanese, Spanish, Korean, Kaingang, Guajajára, Nheengatu, and Xavánte.
Thanks a lot for the answer! I'm sorry to say it, but the data is extremely incorrect, even that of the speakers. In Italy the site states that the speakers in Vèneto (vec) are just over 800,000, totally incorrect data compared to the data that is disclosed by ISTAT (Italian national statistics body). Here too: https://glottolog.org/resource/languoid/id/vene1258 it is said that Vèneto is spoken in Brazil. Glottolog seems to me to be a more than reliable source.
translatewiki:CLDR describes how to request on CLDR. But glottolog.org looks to be reliable.
Hello, thank you very much for the great availability and for the indication. Let's say that in such technical areas I am not prepared, as I have never talked about technical things with anyone, I simply do them. Could you give me some advice on what to write exactly? PS. glottolog.org is also used in the language infoboxes on Wikipedia, which is why I consider it reliable. Thanks in advance for your reply
I think that translatewiki:Support can help you. There are experts of localization.
thank you very much! A good job!
 |
The Original Barnstar | |
| Because of your work in Help:TemplateData |
How can I add a link to phabricator: It can be interesting for newbies (we must facilite as much as possible to newbies).I hope translations are not graved in stone, this would not be good for an agile tool.BoldLuis (talk) 22:12, 16 May 2020 (UTC)
Hi, just a heads-up that your recent edits Template:Translatable template somehow made it's documentation to be visible on all pages that used that template.
Sorry.