Topic on User talk:Shirayuki

Is there a handout to understand this stuff?

About Special:Diff/6296767:

1. Avoid fragmented or "patchwork" messages.
2. Separate heading and body text with a empty line to make them individual translation units.
3. 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.

1. 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.
2. 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. :-(