Skip to main content
  • EN

Hi,

 

 

I'm facing an issue when using a published paramater which is in cyrillic.

 

 

When i set the published paramater manually in the workbench and it is properly fetched and written at the ouput. (I'm using version 2013)

 

 

When I try running the workbench from command line (defining the parameter directly in batch file and also tried to use it within parameter file) the parameter is badly encoded at the ouput. I tried to search on this topic, so I tried the set the code page as 1251 in the batchfile but with no success.

 

 

Do you have any idea if this is dos/windows issue or an FME issue and is anyone able to use published parameters in cyrillic (or other language with special chars)?

 

 

Thanks for the tips.

 

 

Zdenka

Extended characters and non-Latin character sets can be a pain to use in batch files, it is a known limitation in Windows/DOS. There are some workarounds that may and may not work properly, depending on a lot of factors, but it can be more trouble that it's worth, in my opinion.

 

 

Personally, I suggest moving your parameters away from the command line and into a text configuration file, then use either a Python Startup Script or a series of Python Scripted Parameters in FME to read and parse this text file into your workspace parameters. The key is to avoid passing these parameters from the batch file.

 

 

Hope this helps.

 

 

David

Reply


Community Stats

30,147
Posts
114,431
Replies
37,791
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.