Hi Andrey,

you are certainly not wrong. While cleaning up cordova-docs
documentation (about how to develop and build the documentation
website) I found many bits and pieces of processes that seem to have
worked one time, including many things about translations. I don't
know why or when this all got broken by what changes and what the plan
was back then.

So I just collected all that content at
https://github.com/apache/cordova-docs/blob/master/doc/translate.md

But as this unfortunately doesn't seem to have been used in the last
~2 years, the current state is - in my opinion - too broken to fix
(without major effort).

Best,
Jan

2018-02-27 19:18 GMT+01:00 Andrey Kurdumov <kant2...@googlemail.com>:
> From my perspective, as a person who was trying to do translation of Russian 
> language alone, translation is already bankrupted after new docs website 
> design was implemented.
> The reason for my opinion was following
> - Documentation website was changed without thinking that keep translation 
> intact is difficult. As a result it was broken
> - People who change generation of website seriously think that machine 
> translated content is usable. I recommend them read in Chinese recent 
> articles in computational biology, or for example latest news about politics 
> each day and try to understand not ‘idea’ of what’s going on, but actually 
> understand details.
> - All tools which I create to support quick iteration of translations has to 
> be rewritten in the new implementation and now has to be re-implemented.
> - During migration all files was changed location and has to be revalidated 
> again for whole docs
>
> If documentation website would not be touched, and if any change in 
> implementation of docs website could be vetoed by people who do localization, 
> I don’t see point investing time in the localization to my native language 
> again. If I finish Russian , I could start translating to Ukrainian after 
> that, since this is language which I also know relatively good.
>
> Translation is time consuming, and if such efforts would be discarded just 
> for pure change of internal implementation, there no reason to even try.
>
> Sent from Mail for Windows 10
>
> From: Jan Piotrowski
> Sent: Tuesday, February 27, 2018 7:22 PM
> To: dev
> Subject: Translation Bankruptcy?
>
> Hi all,
>
> while doing some work on cordova-docs I also took a look at the
> translations again.
>
> Translations are (theoretically) done on Crowdin, synced from and to Github:
> https://crowdin.com/project/cordova
>
> Unfortunately this doesn't really seem to work:
>
> 1. There is no (working) documentation on how to import or export
> files from or to Crowdin:
> https://github.com/apache/cordova-docs/blob/master/doc/translate.md
>
> 2. There is no way to figure out the current state of the translations
> vs. the actual documentation.
> 3. From looking at the languages I understand: Translations are _very_
> outdated vs. the actual documentation.
>
> 4. There are translated files for files that do not exist in English any more:
> https://issues.apache.org/jira/browse/CB-13161
>
> 5. There seem to be lots of auto translated bits in different
> languages, also Source Code and other technical stuff was
> (automatically) translated in several languages:
> https://issues.apache.org/jira/browse/CB-11414
>
> To summarize:
> No translating is happening because of the above facts. The current
> translations are out of date, unmaintained, contra productive or even
> misleading.
>
> My suggestion:
> Let's just face it and declare translation bankruptcy.
>
> We remove all translated content from the docs repo (latest + dev
> version only) and redirect each link to the matching English version.
>
> Agree?
> Disagree?
> Suggestions?
>
> Best,
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Reply via email to