[jboss-l10n] Fixing BRMS / BPMS 6.0 translations

[Toshiya Kobayashi]

Thank you for pointing that, Mike and Salaboy.

I'll check with translators (I guess most of them are subscribers of this mailing list) and coordinate "fix" and "education".

Regards,
Toshiya

----- Original Message -----
From: "salaboy" <salaboy at redhat.com>
To: "Michael Anstis" <manstis at redhat.com>
Cc: "Toshiya Kobayashi" <tkobayas at redhat.com>, jboss-l10n at lists.jboss.org, "Mauricio Salatino" <msalatin at redhat.com>, "Pedro Zapata Fernandez" <pzapataf at redhat.com>, "Edson Tirelli" <etirelli at redhat.com>, "Mark Proctor" <mproctor at codehaus.org>, "Kris Verlaenen" <kris.verlaenen at gmail.com>
Sent: Monday, November 4, 2013 8:55:22 PM
Subject: Re: Fixing BRMS / BPMS 6.0 translations

The current state is:
1) All the languages that are not causing issues are enabled
2) All the languages that are causing issues are commented out and not included in the builds

Look here: 
https://github.com/droolsjbpm/kie-wb-distributions/blob/master/kie-wb/kie-wb-webapp/src/main/resources/org/kie/workbench/KIEWebapp.gwt.xml

It’s just matter of enabling the languages again to see all the error that those files are causing. 
Once we have all the languages working we can start to translate the missing screens, so we can add the new variables to all the languages files.


On 4 Nov 2013, at 11:52, Michael Anstis <manstis at redhat.com> wrote:

> Hi Toshiya,
> 
> IDK if you're who we need to talk to, but I'm sure you can direct me to the appropriate person.
> 
> We've started pulling in various translations from Zanata and some are causing problems. These are examples I've witnessed:-
> 
> (1) Use of certain characters, e.g. apostrophe. These need to be escaped with i.e. replaced with two apostrophes.
> 
> (2) Removal of variable place-holders. A source string may contain {0} (or 1, 2, 3 etc). This represents a place-holder where our code substitutes a value at runtime. These are sometimes been removed which breaks our code.
> 
> There are various Jenkins jobs that can be examined to check our code compiles; but failures due to i18n issues are hard to spot (or at least you'd need to know what to look for).
> 
> How can we educate translators as to these issues; and ensure fixes are made to the translation files in Zanata?
> 
> With kind regards,
> 
> Mike