[HOME] [DOWNLOAD] [DOCS] [BLOG] [SUPPORT] [TIPS] [ISSUES] [Priority Support]

Translations Technical Developer Discussion


#1

Hi to everyone,

I am a native speaker of Tamil language.I would like to volunteer as a Translations Coordinator for translating the documentation to my native language.So pls guide me how to join as a volunteer in this project. :smiley:

Edit by Patrick:
Changed title


#2

Great! This is much and long needed!

Could you sign up for a whonix.org wiki account please?

We still have not figured out how to use the mediawiki translation extension. It is installed on whonix.org wiki already and working. So we just have to use it. Documentation can be found here:
https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle

Please have a look.

Then pick a wiki page and start prepare it for translation. Maybe https://www.whonix.org/wiki/Starting_Whonix. And translate to your language.

Let’s see how it works.


#3

[quote=“macofe, post:1, topic:322”]Hi,

I’ve started the Spanish translation of some of the wiki pages.

The infobox in the https://www.whonix.org/wiki/Main_Page only appears in English. For other languages it says: {{#invoke:Infobox|infobox}}. Maybe the tags are breaking something.[/quote]
Moved to separate topic:
https://www.whonix.org/forum/index.php/topic,433.0.html


#4

Since I went through the hassle of setting up the wiki locally, I’m willing to help test the translation extension. Just give me a sample of foreign text to use if needed.


#5

Great! See:

[quote=“Patrick, post:2, topic:321”]We still have not figured out how to use the mediawiki translation extension. It is installed on whonix.org wiki already and working. So we just have to use it. Documentation can be found here:
https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle

Please have a look.[/quote]

If you want to test it without revealing any additional languages you might speak (which is fine),

  1. make a copy of the https://www.whonix.org/wiki/Starting_Whonix page, for example, copy its contents to https://www.whonix.org/wiki/Dev/Starting_Whonix
  2. prepare the page for translation as per mediawiki translation extension documentation
  3. use some free online translation service such as google translate to translate it to some language (such as German)
  4. try to pick a translator’s perspective and translate that test page

We can’t / shouldn’t use some free online translation service for serious translations. 1) unclear licensing of translated text - okay to read, but not sure if allowed to license under GPLv3+ 2) very poor translation results. This is just for testing. When we figured out how to use it, we rely on human translators.


#6

This won’t be that simple. Will probably require quite some documentation reading as well as asking the devs of that extension. If it was easy, I would be already accustomed to it.

Just doing it the simple way.

full wiki source

Just won’t make it.

Example wiki source:

= Verify the Whonix images =
It is important to check the integrity of the virtual machine images you downloaded to make sure no man-in-the-middle attack or file corruption happened. (See [[Download Security|Download Security]].)

{{mbox
| type      = critical
| image   = [[File:Ambox_warning_pn.svg.png|40px|alt=OpenPGP verification warning box]]
| text       =

Warning:

Do not continue if verification failed! You risk using infected or erroneous files! The whole point of verification is to confirm file integrity.
}}

Whonix virtual machine images are cryptographically signed using OpenPGP<ref>OpenPGP is a standard for data encryption that provides cryptographic privacy and authentication through the use of keys owned by its users.</ref> by Whonix developer Patrick Schleizer.

If you know how to use an OpenPGP key, download the [[Whonix Signing Key|Whonix Signing Key]] and the [[#Download Whonix|Whonix signatures]] straight away.

Otherwise, follow the instructions:

* [[Verify_the_virtual_machine_images_using_Linux|For Linux: Ubuntu, Debian, Whonix, etc. using kgpg]]
* [[Verify the_virtual_machine_images_using_the_command line|For Linux with the command line]]
* [[Verify_the_virtual_machine_images_using_other_operating systems|For Windows or Mac]]

In this example users may or may not be able to enter the }}. Hence the page will look messed up. Manually fixing that makes quite some work. So to keep this maintainable for loads of translators, users must not be asked to translate that in the first place so they can not mess up.

= <translate>Verify the Whonix images</translate> =
<translate>It is important to check the integrity of the virtual machine images you downloaded to make sure no man-in-the-middle attack or file corruption happened. (See </translate>[[Download Security|<translate>Download Security</translate>]].)

{{mbox
| type      = critical
| image   = [[File:Ambox_warning_pn.svg.png|40px|alt=<translate>OpenPGP verification warning box</translate>]]
| text       =

<translate>
Warning:
</translate>

...

For the syntax

[[wiki link|description of wiki link]]

translators most times translated “wiki link” even they were only supposed to translate “description of wiki link”.

I don’t know if

will work.

Maybe that broke internal links on a wiki page in wiki table of contents.

So maybe

<translate> = Verify the Whonix images = </translate>

has to be used.


#7

About the offline documentation, I’m not worried about it becuase the kiwix workaround should be fine whenever it becomes stable in the repos. There is a bug or something wrong with dumphtml. The cryptic permissions error is of little help.

After I read the mediawiki guide, I started playing around with the translation and I’m seeing the ‘changes marked for translation message’ at the top. Clicking it doesn’t open a translation unit editor like so https://www.mediawiki.org/wiki/File:Translate_manual_-Page_example-_10._Mark_changes.png

However if your experience is better than mine but the problem is with the tag placement and types then a real life example should be useful:

https://techbase.kde.org/index.php?title=Getting_Started/Sources&action=edit

KDE uses mediawiki, making the tag syntax relevant.
The entire text body on the page is wrapped in translate tags.
Section titles take a translation unit tag right at the end of it.
Each text paragraph needs a Translate unit tag preceding it to split it up for the translator.


#8

Problem is, translators don’t know anything about wiki syntax. Murphy’s law will hit hard here.

For example.

<!--T:56--> [[Category:Getting Started]]

Will ask translators to translate.

Which is untranslatable.

But… It will be translated as

anyway.

Instead as leaving it as is.

So you can either,

  • a) cause lots of confusion, answer lots of support requests why “[[Kategorie:Erste Schritte]]” resulted in a broken link, teach every individual translator the wiki syntax and put a lot effort into that or,
  • b) have a knowledgable translation coordinator who prepares wiki pages in a way for translation so translators aren’t even asked to translate non-translatable things such as “[[Category:Getting Started]]”.

Same issue with [[internal wiki link is not translatable|to be translated description of link]].

Same issue for…

{{mbox | type = notice | image = [[File:Ambox_notice.png|40px|alt=Whonix default password info box]] | text = here comes the text }}

Where they translate the wiki markup keywords type, image, text while only “here comes the text” and “Whonix default password info box” is translatable.

Once they translated “type” to a language you don’t know (example: “изображение” (Russian)) and the page looks broken, they will be coming for you to ask to fix the page. And fixing a page where all keywords are translated and broken speaking by experience is quite a time consuming task.

To keep this maintainable, I think we really should go for b).


#9

Good example is this support request:
https://www.whonix.org/forum/index.php/topic,433.msg3259.html#msg3259

If it can go wrong - it will go wrong.


#10

I see what you mean. however I don’t think direct translations of categories is needed by translators. when viewing sources for another language in their example page I see paragraph titles translated only. Any reference to an English extension name is used as it is.

Should someone offer to translate a page I can prepare it for them with tags. Translation should be straightforward after, because the edit option gives gui boxes for each separate paragraph, but I need to make sure nothing breaks. Please try them and tel me what do you see when you add these tags?


#11

It isn’t needed. I didn’t want to imply that. I just don’t want the translate extension to even ask the translator to translate it. Because that will result in issues.

Should someone offer to translate a page I can prepare it for them with tags.
We had lots of offers already. So I guess starting with the most important pages would be beneficial.
Translation should be straightforward after, because the edit option gives gui boxes for each separate paragraph,
It is quite simple if users aren't asked to translate untranslatable things (keywords, internal links, ...).
Please try them and tel me what do you see when you add these tags?
I'll try.

If you want to start with something easy, copy to a testpage:
https://www.whonix.org/wiki/Starting_Whonix

For something harder, copy the main or download page.

Or don’t make an edit and test preparation of the page without a copy. Shouldn’t go much wrong either way. Up to you.


#12

Hello Everyone.

I’m second year CS undergraduate and I volunteered as a Translation Coordinator.
For now I will be preparing MediaWiki Language Extension markup for future translations.
https://www.whonix.org/wiki/Starting_Whonix/pl can be considered ready and there you can find small sample of Polish translation (in which I’m native) and markup.

One major problem is incapability of LE tags to handle other MediaWiki markup (as pointed earlier in the thread).
Even more we can’t divide translation units (hence sentences) with nested markup to separate phrases because it would make impossible to properly translate some of them in some of the languages (in which where order is different from English). Intuitively we thought of adding instructions in documentation section for translators, but it’s impossible to add them in all languages simultaneously, as well as adding documentation to native British English without making actual changes in translated sentences.

As a solution for that, we decided to create separate page on which I will write instructions and guidelines for future translators.

At this moment four translations are planned: Ukrainian, Russian, Turkish and Polish.
All will be done by native speakers (which I know personally).


#13

Terrific! Finally we have someone to work on these things.


#14

Update:

as I said yesterday documentation couldn’t be added without making
actual changes to translation and it seemed like it, because no
documentation was saved when I tried to save it multiple times.

I’m reporting just so you know, when I checked it today, documentation
I was trying to add yesterday actually got saved and now is available
(at least in most parts and in the other languages only, not in British English itself where I was working.)

Also, I gave translation rights to two new translators who just made
their accounts: Taras.baran (Ukrainian) and Piotr Gierach (Russian).


#15

Hey IvoHerka,

I tweaked your permissions a little bit. Let me know if you run into more issues. Just trying to ensure least privilege necessary. Not that I don’t trust you, but you never know. :slight_smile:


#16

Sure, no problem, I get it.


#17

Today I run into following issue:

After editing MainPage markup and marking updated version for translation everything seemed to work. New units appeared as they should.

When I started making Polish translation some of the units (completely random) would give me this error:

‘Saving the translation failed: The modification you tried to make was aborted by an extension hook’

Any ideas what it means and how to fix it?

Edit: I made Support page markup from scratch and started translating: got same issue.


#18

No idea.

If there are open questions, could you try asking the support of that extension please?

They have IRC as well as a forum:


#19

I’ve contacted Service Support, those are answers I got:

Issue 1: When translating, some of the translation units would give me the following error: ‘Saving the translation failed: The modification you tried to make was aborted by an extension hook’

fortasse, please look into that.

Issue 2: After adding documentation for translation units in the core language (British English), documentation would usually appear on the next day, but only in other languages (not even in all of them) and in pieces. Saving documentation to particular languages fails completely.

It seems your wiki is misconfigured and believes that all edits come from localhost: this is bound to produce a number of problems, including unexpected behaviour for blocks and ConfirmEdit.

Those are two main things, the original thread you can find at:
http://www.mediawiki.org/wiki/Extension_talk:Translate#x_.27Saving_the_translation_failed:_The_modification_you_tried_to_make_was_aborted_by_an_extension_hook.27_and_Documentation_problems_49724

Also, it seems there is method of hiding markup in translation, called ‘tvar’ syntax, so this is something I will look into.


#20

Thanks for the update IvoHerka.

Issue 1 should be resolved. I updated permissions for translators.

Issue 2: the configuration is deliberate - we don’t log visitor IPs. This makes mediawiki a little confused, which is why editing from usernames is recommended (to keep people’s contributions accurate).

Try again with updated permissions, and see if that fixes the saving issue.

Thanks!