+6Hello,
we have some trouble running FME Server (2017) workbenches. Italian characters are interpreted using Server system configuration instead of the italian one. Is it enough to include in the "environment" section of the fmeCommonConfig.txt file the LOCALE=it_IT ? Other configuration needed?
Thanks
Roberto
Best answer by virtualcitymatt
I think it will depend on where the problem is taking place. If the issue is when reading or writing data then you might/should be able to configure the reader/writer to interpret the data as whatever encoding system you want. This can be set for example in the shape reader and CSV reader. If you don't specify the encoding the it will use the system encodingby default.
I'm not sure what that config file local setting defines but it might help. I suspect not with the way the workspaces are run though.
+39I think it will depend on where the problem is taking place. If the issue is when reading or writing data then you might/should be able to configure the reader/writer to interpret the data as whatever encoding system you want. This can be set for example in the shape reader and CSV reader. If you don't specify the encoding the it will use the system encodingby default.
I'm not sure what that config file local setting defines but it might help. I suspect not with the way the workspaces are run though.
+6I think it will depend on where the problem is taking place. If the issue is when reading or writing data then you might/should be able to configure the reader/writer to interpret the data as whatever encoding system you want. This can be set for example in the shape reader and CSV reader. If you don't specify the encoding the it will use the system encodingby default.
I'm not sure what that config file local setting defines but it might help. I suspect not with the way the workspaces are run though.
Hi @virtualcitymatt. The error happens in an AttributeCreator where "Società" is converted into
"SocietÃ".
+6Hello. Sorry for the post. It seems that the error is not in the transformer but in the Oracle query that populate one of the variable that are concatenate in the AttributeCreator. :-(
+39Hello. Sorry for the post. It seems that the error is not in the transformer but in the Oracle query that populate one of the variable that are concatenate in the AttributeCreator. :-(
Interesting - so your query to oracle has a ' à ' in it? Are you able to see how the query looks on the Oracle side? Is FME sending the wrong thing? Or is FME interpreting the result incorrectly?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
