|
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
| |
|---|---|
| |
About your revert of my edit.
If you have specific comments/claims to my edit, please explain them. If not, please return the template to my version. Now on the main page the phrase "Other languages:" is always displayed in English. After my edit, this is synchronized with the displayed language version (if translations is provided), or displayed in the user interface language.
When I checked the source, the Template:Languages did not have a parameter '2'. That is why I reverted your changes and suggested using sandbox pages for prototypes of such high-impact pages.
However, I agree with the idea of synchronizing the phrase with the user interface language.
This change is on the one hand small and on the other hand difficult to verify outside of the current usage chain. That's why I did it on the Main Page directly, and also in the real templates.
Using {{ll|Project:Language policy|{{int:tpt-languages-legend/{{SUBPAGENAME}}}}}} in Template:Languages also justified - IMHO, there is necessary to first use a translation that matches the current language version of the subpage being called (regardless of the interface language). And then, if there is no translation, in the user interface language.
Check if this change on Template:Languages about 4 days ago resolved the issue.
Hi,
Sometimes you do it by splitting the paragraph several lines like here, and sometimes you add <translate> tags in the middle of the paragraph like here.
Is there a suggestion documented anywhere to split paragraphs into smaller translation units? Or is it just something that you do yourself?
I thought I wrote it down somewhere, but I couldn't find it.
Topic:Xnd7su3ew0fba4py#flow-post-xpd5yauhp5kj864w
> By making translation units as small and simple as possible, translations become easier and are less likely to be left untranslated.
Have you measured it? Are pages where you did this split actually more likely to have more translations?
> Moreover, simplifying variable names increases the likelihood of hitting the translation memory, thereby making the translation process more efficient.
It's not significant. Sentences within paragraphs of body text are not likely to be in translation memory anyway.
Making translation units shorter is generally a good idea, but the way in which you do it is not great. It adds a lot of markup, which makes the page hard to edit.
It's better to make the paragraphs shorter and rely on the Translate extension's capability to mark each paragraph for translation.
That's OK, but is it worth adding so much markup to achieve that? Just making sure that paragraphs are no longer than four sentences achieves a much better balance of translation ease and markup heaviness than splitting everything to single sentences. Besides, keeping paragraphs shorter is a good thing in general for readability in the source language.
Hello, thanks for marking the article for translation. Why did you remove <translate>...</translate> tags from the first sentences though?
I removed the respective sentences from translation because translation variables were missing.
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.
About Special:Diff/6296767:
<!---->.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.
<translate>...</translate> tags, it is split into different translation units at those positions.<translate> == heading1 == sentence1. == heading2 == sentence2. </translate>
<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
<!---->.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.
The extension was tested with MediaWiki, it is unclear that version numbers follow. This leads to difficulties in accurately translating it into many languages.The idea is not to touch the existing translations if only the version numbers are updated.
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.
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.
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.
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?
 Warning: | NEVER add translation unit markers (T:NN) manually! |
Instead of the correct English text "Maps is a single data structure...", "説明" (the Japanese translation of "Description") has been mistakenly inserted.
お世話になっております。rxy でございます。日頃より日本語への精力的な翻訳、ありがとうございます。
さて、掲題のとおりですが、MediaWiki における日本語環境での元号処理を変更するパッチを gerrit に gerrit:995056 として送りました。関連タスク: phab:T356419
可能であればお手すきの際に code review いただけますと幸いです。
Review ありがとうございます。 テストケースの説明における誤植の指摘も助かりました！ VSCode で複数行を丸ごとコピーした際に元号の部分と数値だけ変えていました…
