Hi Nina Lorenz,

I have slightly different settings, and target files are encoded in UTF-8 WITHOUT BOM, i.e. Encoding for source property files: UTF8 without BOM.

Do you mind trying that and let us know?

Hello,

we have tried your settings, but unfortunately our target files are still UTF-8 with BOM.

Hi Nina Lorenz,

Which version of Passolo are you using? I used Passolo 2018, version 18.0.171.0, collaboration edition.

I think your issue may be caused by the source being UTF-8 without BOM. Mine are UTF-8 with BOM. All non-XML files that do not contain encoding declaration within source files may have similar issues like this. I always add BOM to all UTF-8 encoded source files.

In case you don't have a tool to add or remove BOM, I use Rainbow from:

https://okapiframework.org/wiki/index.php?title=Main_Page

Distributions:

https://okapiframework.org/wiki/index.php/Distributions

• Recent releases: https://okapiframework.org/binaries/main

Hello,

we are currently using Passolo 2018 Professional Edition 18.0.152.0.

It is required that source and destination files are UTF-8 without BOM. We cannot change the source files to UTF-8 with BOM.

Since our source files are UTF-8 without BOM, it is not clear to us why the target files are generated as UTF-8 with BOM, especially when we explicitly select "Encoding for target property files: UTF-8" in the Java Options. Is this perhaps a bug in Passolo?

It doesn't seem to be the right approach to generate all target files and then use a third party tool to change the encoding from UTF-8 with BOM to UTF-8 without BOM.

Related:
https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/29166/encoding-of-target-file-not-as-set-in-target-file-options 

https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/13431/java-add-in-does-not-create-files-with-escaped-unicode-characters 

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. 

Insert 65001 into the Codepage field.

Hello,

thank you very much for your answer.

Unfortunately it did not work.

My source file is UTF-8.

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

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

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

I used the latest CU 18.0.178.0 and it worked without any issue. My target file has no BOM. Maybe try to update to the latest CU.

Hello,

thank you very much for the quick reply.

We updated to 18.0.178.0 and tried again, but again it did not work

• I would like to provide more details so you can reproduce the behavior.
  Here is a properties file if you want to reproduce it with that file:
  https://tacoss-my.sharepoint.com/:u:/g/personal/o_dreja_tacoss_de/ES2mN0x6M0pOgOiOR6oZhc4BeUnrCKAAN6xsuCDuXkTrSg?e=xioXNd 
  
  
• If it is helpful, I can provide log files if you tell me where to find them.
  
  
• Additionally, I can show you with TeamViewer that it does not work. Please send me an E-Mail for this purpose to support@tacoss.de