CiviCRM Community Forums (archive)

While doing some translation work on CiviCRM PO files in Japanese we had sent along some other PO files for proofing in other languages to our translators for internal certification.

I would like to formally caution people that is seems that Pootle (i assume) is being used inappropriately to attempt to translate text strings to meet specific personal purposes and in a great many cases the translations are total bunk. You are better off using the default en_US localization when dealing with an English speaking audience IMHO unless there is something I am totally missing here.

Certainly understood.

Thinking Out Loud
I think we should probably somehow place a quality indicator on the specific translation. An easy one would be in the English world as the en_GB, en_AU are just way way off and I could see someone going through an install and in all their excitement set the localization to en_GB or en_AU and get a bunch of non-sense on the screen with utter confusion.

I don't think however it is the fuzzy translation, there are things intentionally mistranslated. I can only speak for what I saw and that was a diff on en_US(pot) against en_AU, en_GB. Unfortunately I have my hands full with the Japanese translation and localization work so I don't want to tackle the English stuff just yet. But we will most certainly internally hit the en_AU and en_GB English variations as well as we need to internally certify each language we intend to allow our clients to use.

We will return that work back into the community naturally for inclusion as entire works for community. Though I would recommend you keep our works out of Pootle as they are in fact professional translations and go through significant peer review.

Cheers!

Hi Piotr,

For our first round of translations we will send them off to you manually as we have setup an internal translation environment that includes the full l10n branches as we reset all the pos for each local on our set to start closed translations as complete works. You can of course add our pos back into the svn and do with them as you like.

The second round we will figure out how best to approach it as obviously the POT itself will be updated. We are just trying to protect the integrity of our translations. Let me rephrase, we know our Japanese translations are 100% correct so when it goes public on the SVN we are not sure then so much unless it is a publically closed branch. Meaning only a certain group maintains it that knows proper Japanese.

Sorry my english is not the best. Kazuki can explain better 

 Oops! I made up some Japanese translations with Pootle as they were empty! Now reading this article, I just found that Japanese translation had been finished in a few months ago. Unfortunately, my uncompleted Japanese translations seemed to be reflected to the current 1.9 source tree.
 Please overwrite those recent Japanese .po files with your completed Japanese translation files.

> your translation is an all-covering, coherent/consistent and of high quality, so there’s no point in exposing it through Pootle.

Oh I see, they just announced their change and forked the code.

 There had been some translation into Japanese in this thread and another (http://civicrm.org/node/252),
however, I'm very sorry that they did not send you back any code in spite of your reply at this forum.

 Maybe they have less resrouce to describe their language rule and contribute their code, so choose just only localize their CiviCRM.

Well, I gonna update my translation a little after 2.0 code freeze.