Hi Friends,
I'd like to know if it's possible to disable the auto split in units?
When the page is mark for translation, the system will insert tags like inside the wiki-text.
I'd like to avoid that, so that the entire text inside the <Translate> tag will be translated in one string (Even if there is a hard return inside the <Translate>).
I hope I am clear. Thanks a lot for your help.
Hi. Could you give us a link to the page you're working on, so that we can understand the use-case/problem you're trying to solve?
And/or, paste the content (or similar) into a sandbox? (Feel free to use User:Quiddity (WMF)/sandboxtranslation).
Hi @Quiddity (WMF), thanks for your quick reply.
Unfortunatly, I can't share a link with you since I am working on a local environment.
However, on the sandbox, if you switch to the wikitext edit mode:
You can see that
<!--T:1-->
,
<!--T:2-->
,
<!--T:3-->
,... have been inserted inside the wikitext to split all the content inside <translate> and </translate> into translatable strings (Witch is fine).
However, on my wiki, when I switch to the VE edit mode, I see little grey mark that looks like !T:2 in lieu of the
<!--T:2-->
tag (witch is not very convenient for the user).
On the sandbow, however, those little marks don't seems to show up. Is it something that as been solved in a new version of VE maybe?
---
Another question, is their a way to simply disable the auto split? (so disable the fact that the extension automatically insert
<!--T:1-->
,
<!--T:2-->
,
<!--T:3-->
into the wiki-text)
Thanks a lot.
Re: Visual editor - no, I'm afraid that editor does not currently support Extension:Translate (which is an old and complicated extension).
Re: merging all "translatable units" into a single unit - I don't think so, beyond using <br> at the end of every line. (Which I strongly advise against) -- The extension is designed to make it easy for various people to do "little bits, one at a time" (So if they get bored or busy, halfway through the work, then at least some of the page is translated); therefor, to have "multiple paragraphs all in a single translation unit" isn't possible (as far as I know, and I cannot think of any other hacks/workarounds to make it do that). Sorry, but hope that helps.
Re: Re: merging all "translatable units" into a single unit - I don't think so, beyond using <br> at the end of every line. (Which I strongly advise against) -- The extension is designed to make it easy for various people to do "little bits, one at a time"
How to insert a fully translated text to the place of the translated text?
Maybe there is a ready-made fully translated text. In addition, texts for different languages may differ in content and may be they are not a direct translation of one into another.
"texts for different languages may differ in content and may be they are not a direct translation of one into another."
This extension is generally intended for direct translations. It is primarily used for keeping multilingual copies of documentation updated.
"How to insert a fully translated text to the place of the translated text?"
Section by section.
Probably, it is time for you to expand the idea of why a CMS exists. Not only to translate texts in it.
Where do you discuss system tasks?
I'm not sure what you mean by "system tasks". We track software issues (bugs and feature requests, etc) in https://phabricator.wikimedia.org/ (documentation at Phabricator). This wiki's purpose is described at Project:About. Some discussion happens here, and some in all the other places listed at Communication. It's a complicated place!
I think that another extension is needed, which only keeps track of whether there are language-versions of text, and by analogy of the <languages /> tag shows a switch of languages.
Links or examples almost always help! They can show other people what you're thinking of, or what you've found that wasn't ideal (and why), or related examples from elsewhere. Your current comments are too short and abstract for me to understand quite what you mean. Please link to or explain the specific use-case(s) that you are thinking of.
The <languages /> tag works only when the text is translated into other languages with the Translate extension.
But in a situation where the text is not translated, but simply there are other corresponding texts in other languages, the <languages /> tag does not work. But it does need to work.
I think it would be helpful to have a tag capable of displaying a language switch for cases where the texts are not "translated section by section".
