Skip to main content

We've had a strange behaviour importing data using FME Quick Translator.

 

One user (Admin) had the following entry in the log file when he experienced wrong string encoding in the target database:

2021-06-29 22:11:16|  3.5| 0.0|INFORM|Shapefile reader: Reading dataset with encoding 'windows-1252' as determined by 'System Encoding as Fallback'

 

Another user got the right encoding in the target database and the same line number of the log output instead showed:

2021-06-30 00:32:56|  3.0| 0.0|INFORM|Shapefile reader: Reading dataset with encoding 'UTF-8' as determined by 'Codepage File'

 

diff_encoding_fme_quick_translator 

Both users could read the .CPG Codepage File without a problem, but it turned out that the first user did not have "full control" access to the .CPG file which lies next to the .SHP shapefile.

As soon as we gave him "full control" access to that file the log output regarding the encoding was the same.

 

Seems to me as if FME (Quick Translator) tries to exclusively read the .CPG file which makes no sense to me. Seems like a bug.

Be the first to reply!

Reply