Text file encoding

Hey guys... Is there a reason why the encoding for the action of writing to a text file is UCS-2 LE BOM?

It is causing no end of problems as any other program that wants to write to the file.. it comes out gobbledeegook! (Chinese characters etc)

Can you please change it? To UTF8 or ANSI?

Please?

Hello!

To my knowledge, the format of a file written to by a trigger is UTF-16 LE (provided that the file did not exist prior to the trigger trying to write into it). If the file had already existed before you wrote to it with a trigger, check what program created it and what encoding it chose.

Not sure that is the case Oxa...!

Brand new file.. never before been created...

Open it up in notepad++ after MF Pro has written to it and it will say UCS-2 LE BOM for the encoding!

Try it if you don't believe me!

Screenshots if you wish..?

I believe what you are saying.

I also know what I'm seeing when I open a file my trigger has created. The encoding is UTF-16.

So there could be differences in our systems, as the program does not intentionally choose that UCS encoding to create a file with.

Hi
If it's any help I tested this. For me a MF generated text file encoding is detected as follows:

notepad > automatic detection > UTF-16LE
notepad++ > automatic detection > UCS-2 LE BOM
word > conversion dialogue > Unicode

for info, Notepad++ documentation does refer to encoding detection as not being an exact science  

All I know is .. I let MF Pro create a file.. then use another program (Filemaker) to write to that text file a selections name.... and it comes out in Chinese writing!

It's not really a problem.. I am a resourceful guy and have found a way around it! Just thought I would bring it up in case other people might be having problems....