[WG: I18N & L10N] Recommendations from crowdin support

Jean-Francois Leveque jean-francois.leveque at upmc.fr
Tue Apr 8 06:51:57 PDT 2014


Hi,

It seems the option has to be set file by file.

Under "File Export Options", the available options are :
- Do not escape single quote
- Escape single quote by another single quote
- Escape single quote by backslash

The files already seem to be set with the first option.

This should already work.

Could you try one file and report with the complete file path if this 
works or not?

Cheers,
J-F

On 04/04/2014 11:36, Alex Ballesté wrote:
> Hi, some minutes ago I received the last answer about the single quote
> escaping from crowdin support:
>
> ----
>
> Our engineers say that currently we're not planning to improve behavior of *.properties file format import/export, because it may be confusing and may impact negatively on other projects at Crowdin.
>
> Hope for your understanding.
>
> Meanwhile, we suggest you the following workaround:
> 1) Disable "escape single quote by another single quote" option for all files (switch to "Do not escape single quote);
> 2) Exported files will be equal with made translations ( ' will be exported as ' , '' will be exported as '').
>
> Though, it would be necessary to check all translations from all languages containing quotes [ ' ] and correct ' to '' if needed ( in case string contains {0} ).
>
> Also, you may use MessageFormat method to render all strings in your app with "Escape single quote by another single quote" option enabled in project settings.
> In result, everything should work as you need.
>
> Will that work for you?
>
> Please let us know if you have any other questions.
>
> ---
>
>
> And my question is the same. Will that work for us?
>
> Now we are trying to repair all the catalan string bundles that are
> wrong, and I hope that we'll be able to commit them today.
> Does anybody else detected this problem in their property files?
>
> Thanks.



More information about the i18n mailing list