Burim Bektesi

If I was you I would simply use the SuperText JSON filetype on the appstore.  This supports bilingual JSON ad you can set the source and target language in the filetype options;

https://appstore.sdl.com/language/app/file-type-definition-for-json/561/

Hi all!

I had created a fileytype for json based on Regex Delimited Text File Type as I learned here and on Pauls blog. That worked great... until now, when we discovered that the finished file contains wrong sepcial characters.

In Slovenian it ist only "č", all other characters are ok. In the Trados Editor we have translated č, but in the final file we get an "è".

The original json file seems to be in ANSI, but even when I save it to UTF8 an translated it, I have the same problem.

Any idea?

Thnx!

Burim

Hi all!

I had created a fileytype for json based on Regex Delimited Text File Type as I learned here and on Pauls blog. That worked great... until now, when we discovered that the finished file contains wrong sepcial characters.

In Slovenian it ist only "č", all other characters are ok. In the Trados Editor we have translated č, but in the final file we get an "è".

The original json file seems to be in ANSI, this seems to be the problem. Is there any chance to tell Trados to convert it back in unicode?

Thnx!

Burim

Burim Bektesi

Burim Bektesi said:

Is there any chance to tell Trados to convert it back in unicode?

Probably better to add a BOM to the file before you process it in Trados Studio so it's handled as unicode.  If you have many of these files use this tool:

https://appstore.sdl.com/language/app/fec-file-encoding-converter/788/

Burim Bektesi

Probably better to add a BOM to the file before you process them in Trados Studio so they are handled as unicode.  If you have a lot of these files use this app:

https://appstore.sdl.com/language/app/fec-file-encoding-converter/788/

Yes, I have a lot of them, some in Unicode, some not. I always thought you would alreadysee in the Studio Editor if it was ANSI, that's why I didn't notice from the beginning.

I downloaded the app you suggested, thx a lot, this should help. But somehow it doesn't work with my files. It is strange, that changing the coding didn't even work directly in Notepad++. After changing and saving, it is ANSI again. Only when I open it in the MS editor and save as "Unicode" it converts and shows in Notepad++.

In FEC nothing changes after processing. (The 3 other files have already been Unicode).

Yes, I have a lot of them, some in Unicode, some not. I always thought you would alreadysee in the Studio Editor if it was ANSI, that's why I didn't notice from the beginning.

I downloaded the app you suggested, thx a lot, this should help. But somehow it doesn't work with my files. It is strange, that changing the coding didn't even work directly in Notepad++. After changing and saving, it is ANSI again. Only when I open it in the MS editor and save as "Unicode" it converts and shows in Notepad++.

In FEC nothing changes after processing. (The 3 other files have already been Unicode).

Burim Bektesi

Sometimes the problems are down to not knowing how to use the FEC.  Can you review this video and see if it helps?

Hi Paul,

can I not choose the "File Encoding" on the right-hand panel just as you did with the BOM? While you changed and assigned the encoding manually. How to do that for a greater number of files?

@Paul Filkin: I found it... Associate Active Encoding +... the plus is the secret. Thnx a lot.

It saves the UTF-8- coding in the final files only if I also assign a BOM though...