Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [babel-dev] Eclipse Platform SDK 3.2 translations

One things that came up in the conference call today was talk about the format the imported strings are going to be in. It sounded like it had been decided to use escaped Unicode strings. I had no luck finding a PHP way to use the escaped Unicode strings Kit commented on bug #217311 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=217311#c3). Maybe I am just missing something obvious, but I did some searching and didn't find anything simple. The only way I was able to use the escaped Unicode strings was to pass them through JavaScripts 'unescape' function.

Does anyone know of a way to decode escape Unicode strings in PHP?

gO'


Denis Roy wrote:
Team,

I'm almost ready to import the Eclipse Platform SDK 3.2 translated strings that were made available. Kit has kindly packaged everything up in a format that I can easily import. I have 2 questions:

1. The files Kit gave me have translations for much more than just Platform: GMF, VE, BIRT, DTP etc. are there. I can't import translations for which I don't have a corresponding English string. How should we go about 'asking' projects to define their map files in Babel?

2. I think we want to use the Eclipse Platform SDK 3.2 strings to pre-populate Eclipse Platform SDK 3.3.1 (*gasping for air*) translations... Is that correct? If so, I'd need to define the 3.3.1 map files, import the 3.2 strings into the 3.3.1 tree (where the string names match). Does this approach seem sane?

Thanks for helping me out with this ... this is a bit of a gray area for me.

Denis




Back to the top