Hello, thanks for marking the article for translation. Why did you remove <translate>...</translate>
tags from the first sentences though?
User talk:Shirayuki
I removed the respective sentences from translation because translation variables were missing.
I see. I added them.
Hello,
Per the consensus from conference organizers, we need to rename the "MediaWiki Users and Developers Conference 2024" page into "MediaWiki Users and Developers Conference Spring 2024" because there will probably be a MediaWiki Users and Developers Conference Fall 2024. Your help would be much appreciated.
CC: @CCicalese (WMF) in case a +1 is needed.
Done
Thanks!
Is there a handout to understand this stuff?
About Special:Diff/6296767:
- Avoid fragmented or "patchwork" messages.
- Separate heading and body text with a empty line to make them individual translation units.
- Do not add unwanted html comments like
<!---->
.
OK, in that diff I can not see any fragmented or "patchwork" messages and also is not related to the <translate>
stuff.
One thing I don't understand is when a <translate>
tag is set and when it is skipped.
- When you use empty lines within the
<translate>...</translate>
tags, it is split into different translation units at those positions.
<translate> == heading1 == sentence1. == heading2 == sentence2. </translate>
- If you want each sentence to be a separate translation unit, you cannot omit the
<translate>
tags.
<translate> == heading == </translate> <translate>sentence1.</translate> <translate>sentence2.</translate>
"If you want each sentence to be a separate translation unit, you cannot omit the <translate>...</translate>
tags."
This is my point. In many part there are no <translate>...</translate>
tags, but only <!-- T:xy-->
tags. But you told me
- Do not add unwanted html comments like
<!---->
.
so I get confused. :-(
Below, there is my reply beginning with "Additional explanation," but does it answer your question?
So far, it has turned out that every time I thought I had understood it, I was wrong again.
The whole thing is far too complicated, error-prone and contains too many "extra tricks", especially when it comes to the links to be translated.
I guess I'll keep making mistakes. But your explanations have brought some clarity. Thank you!
For today at least, the goal has been achieved and the documentation for an - in my opinion important - extension has been successfully made translatable. Also thanks to a lot of help from your side. :-)
Additional explanation seems necessary to answer your question in Special:Diff/6296870.
In translation pages, untranslated or fuzzy translation units are enclosed with either <div>
or a <span>
.
If there is no newline character immediately before the translation unit marker (<!--T:XX-->
), it is considered inline and enclosed in a <span>
; otherwise, it is enclosed in a <div>
.
In my edit, inline style was used to display the version numbers on the same line as the preceding text.
- When the original text is cut off mid-sentence, as in
The extension was tested with MediaWiki
, it is unclear that version numbers follow. This leads to difficulties in accurately translating it into many languages. - Punctuation marks should also be translatable.
The idea is not to touch the existing translations if only the version numbers are updated.
MediaWiki:Sidebar does not work for translations. :-(
Hello Shirayuki please can you mark this header for translation Wikimedia Tech Safari Program/Header. Also the final gif banner uploaded is currently on reflecting on the overview page and the header page but the other sub pages currently have the old gif banner. If that can be fixed for me i will be greatful.
I was wondering about the margin of this image, but it turns out to be an animated GIF. In my environment, the animation doesn't play, and only the outline of the African continent is displayed.
From my end it works perfectly, tried viewing it on commons and it also works perfectly. The African image is static and the other content is animated.
On the page, the image at the following URL is embedded, and it is not an animated GIF:
Oh okay i can now see it via this URL. I don't know how this can be fixed.
See Manual:$wgMaxAnimatedGifArea (Default value: 12,500,000).
920[px] x 424[px] x 127[frames]=49,540,160 is larger than the default value.
oh okay i do understand it now.
Also to be marked: Extension:SkinCustomiser
Hello @Shirayuki please can the pages be marked for translation again
Right now the only changes i will do is for the schedule, discussion, organizers and team. So the overview can be marked for the overview and participate can be marked for translation.
Hello @Shirayuki Please can you mark this page for translation Wikimedia Tech Safari Program/Terms and Conditions apply
@Shirayuki Please can you mark the overview page for translation again, this is the final schedule. Wikimedia Tech Safari Program
Pages that need to be marked for translation are listed on Special:PageTranslation, and in most cases, they are marked by one of the translation administrators within 24 hours.
So, there's no need to notify each time.
Oh okay well noted with lots of thanks
Recently, you undid my revision to {{main}} to make it use {{ll}} instead to automatically localize link names, with the summary "It does not localize". I am confused. As you can see on {{localized link/ja}}, the pagenames are automatically changed into their Japanese translations. The changes also hadn't been propagated to the translated versions yet.
Passing a second parameter to {{ll}} overrides the automatic localization of link names, so they are not automatically localized. Using that template compromises readability.
But if the corresponding parameters are empty, as {{main}} is often used, the second parameter would not be passed. By readability, if you mean that of the template code, that can easily be fixed by enabling syntax highlighting.
I'll go ahead with restoring the edit in a day.
Hi Shirayuki, Thank You for your edit. Can I ask you, if it is generally possible, instead of 1, 2, 3, 4 to use something like 5, 10, 15, 20. Than there is space for later passages to insert. Maybe in this case it doesn't matter, but in more complex texts it makes it a bit difficult from the perspective of an editor to insert later a passage, E.G. in this edit I was happy, that there was T:39 still free for use, but if not..T:170?. Another idea could be, starting for each chapter with a new 10. eg. 1, 2, 3, - 10, 11, 12, - 20, 21, 22,.. or with more space inbetween: 2, 4, 6, - 10, 12, 14, 16, - 20, 22, 24, 26, ... That will keep enouph flexibility for future changings. Is this a usefull idea? Regards
Do NOT manually add translation unit markers (T:NN). They are automatically added by the system, not by translation administrators.
For example, even if T:39 appears to be free, it may have been previously used for an entirely different English sentence, or translations may exist for it, causing confusion.
Someone has assigned the translation unit T:39 for "Description" to the unrelated "Maps is a single data structure..." text!
As a result, incorrect translations for "Description" exist in languages other than English, causing inconvenience to readers and translators in other languages!!
hmm, ok. So using T:39 was wrong, I had to use T:172 ?
By the way: Did we accidentally edit the same time or do you not like the Capital Letters? They were intended as a navigational aid. Regards
I just didn't want the braces to be included in the link, similar to {{Mbox templates}}.
Feel free to add the capital letters if needed.
ok, done. funny by the way, "layout!" - "style!" :-D Best Regards By the way, 2009/10 I was living for one year in Osaka, was nice! My beginning was the total solar eclipse in 2009 Amami Oshima. Where are you from or living?
Instead of the correct English text "Maps is a single data structure...", "説明" (the Japanese translation of "Description") has been mistakenly inserted.
hmm, ok. Sry for the chaos!!
You are welcome to stop sabotaging my work
お世話になっております。rxy でございます。日頃より日本語への精力的な翻訳、ありがとうございます。
さて、掲題のとおりですが、MediaWiki における日本語環境での元号処理を変更するパッチを gerrit に gerrit:995056 として送りました。関連タスク: phab:T356419
可能であればお手すきの際に code review いただけますと幸いです。
私の環境で動作を検証し、変換結果が修正されたことを確認しました。
記述も分かりやすくなったと思います。ありがとうございました。
Review ありがとうございます。 テストケースの説明における誤植の指摘も助かりました! VSCode で複数行を丸ごとコピーした際に元号の部分と数値だけ変えていました…
What does "you can use "listen" on the multiple server names. " mean exactly?
QUOTE: Enable your web server to share your MediaWiki install with all wikis.
For multiple (sub)domains, you can use "listen" on the multiple server names.
For multiple subdirectories, you could use: rewrite rules, aliases, or symlinks.
https://www.mediawiki.org/wiki/Manual:Wiki_family#Wiki_Farm Thanks in advance.
- Bawolff hi again bawoff thanks for response.
- It sounds like they are talking about virtual hosts (some web servers use a config directive named listen for that), but i agree its terribly phrased.
- no idea; listen may refer to TCP listen.
- LISTEN server TCP/IP call :::This LISTEN call tells the TCP⁄IP address space that the server is ready to begin accepting connections.
Is the statement trying to convey the following idea?
By specifying the correct IP address for each (sub)domain on the DNS server, each domain will point to the same web server.
You reverted my edits but it does not work as you want it. :-(
Please klick on "Deutsch" to see:
- "Advertising blocks" appears as "Werbung-Blöcke", but I have to translate it into "Werbe-Blöcke"
- "If Sitenotice is defined" appears as a red link. Tip-text is "Ll (page does not exist)".
Regarding "If Sitenotice is defined," use {{}} as in the original text, not [[]].
This is really hard stuff. Too much for me. Thank a lot for your help.
Looks good now! :-))