• State Suggested Answer
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 4231 views
  • Users 0 members are here
Options

Encoding problems with Java parser

Nina Lorenz

Hi there,
We are facing some encoding problems. In Java options for the Java Parser we set the encoding for target files to UTF-8. Nevertheless, the exported files are UTF-8 with BOM.
Have we missed something in our settings, or is there another way to solve this?
Thanks for your help!
Kind regards
Nina

Detailed description:

We have a source file, abfrage_artikel_de, which is encoded UTF-8. See screenshot.

Notepad++ screenshot showing 'abfrage_artikel_de.properties' file with encoding set to ANSI instead of UTF-8.

The java parser is set for the exported target file to be UTF-8.

Java Options dialog box with 'Kodierung fuer Ziel-Property-Dateien' set to 'UTF-8' without an option for BOM.

However, the target file abfrage_artikel_en has a "UTF-8 with BOM" encoding after successful export.

Notepad++ screenshot showing 'abfrage_artikel_en.properties' file with encoding set to UTF-8 BOM instead of UTF-8.

Generated Image Alt-Text
[edited by: RWS Community AI at 3:16 PM (GMT 0) on 14 Nov 2024]
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    All Java files without BOM will be treated as ANSI coded. Please try to setup Source List Properties for the Java properties files w/o BOM in a way that Passolo is able to recognize that these are UTF-8 files. 

    Trados Studio Properties dialog showing Source List for test UTF-8 with file path, title, parser set to Add-in Java File Parser, segmenter to determine on next update, language as Neutral, and Codepage field set to 65001.

    Insert 65001 into the Codepage field.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:49 AM (GMT 0) on 5 Mar 2024]
  • 0 in reply to Achim Herrmann

    Hello,

    thank you very much for your answer.

    Unfortunately it did not work.

    My source file is UTF-8.

    Notepad++ screenshot showing the Encoding menu with UTF-8 selected for abfrage_artikel_de.properties file.

    In this source file, I went to Properties - Source List and set the Codepage to 65001:

    Trados Studio Properties window for source list abfrage_artikel_de showing Codepage set to 65001 and language set to German.

    I have set the "Add-In Java File Parser" to get UTF-8 without BOM.

    Java Options dialog in Trados Studio with 'UTF8 without BOM' selected for Source Property-Data files.

    I then generated the properties file and it is again with the wrong encoding.

    Notepad++ screenshot showing the Encoding menu with UTF-8 selected for abfrage_artikel_en.properties file.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:49 AM (GMT 0) on 5 Mar 2024]
Reply
  • 0 in reply to Achim Herrmann

    Hello,

    thank you very much for your answer.

    Unfortunately it did not work.

    My source file is UTF-8.

    Notepad++ screenshot showing the Encoding menu with UTF-8 selected for abfrage_artikel_de.properties file.

    In this source file, I went to Properties - Source List and set the Codepage to 65001:

    Trados Studio Properties window for source list abfrage_artikel_de showing Codepage set to 65001 and language set to German.

    I have set the "Add-In Java File Parser" to get UTF-8 without BOM.

    Java Options dialog in Trados Studio with 'UTF8 without BOM' selected for Source Property-Data files.

    I then generated the properties file and it is again with the wrong encoding.

    Notepad++ screenshot showing the Encoding menu with UTF-8 selected for abfrage_artikel_en.properties file.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:49 AM (GMT 0) on 5 Mar 2024]
Children