Is it possible to change the file encoding in lua?

[dsyrock]

I created a script to write some information to a csv file. Then I realized that the file is encoding in utf-8. I need to convert it to ANSI. Now I have to open it with windows built in notepad and re-save it as ANSI.

I'm looking for a way to save to ANSI directly in lua, skipping the notepad. Is it possible?

[Meo-Ada Mespotine]

You could try fiddling around with the utf8-module-functions. Though I don't know, how to do that exactly for conversion stuff.

[Lokasenna]

You could try: https://stackoverflow.com/questions/...ii-in-pure-lua

I'm surprised that your script is saving the data as UTF-8 though, since Lua doesn't use it by default.

[dsyrock]

Originally Posted by Lokasenna

You could try: https://stackoverflow.com/questions/...ii-in-pure-lua

I'm surprised that your script is saving the data as UTF-8 though, since Lua doesn't use it by default.

I'm not sure. I just simply using io.output to creat a csv file. Is it because reaper forcing everything output from itself as UTF-8 by default?

[dsyrock]

Originally Posted by Lokasenna

You could try: https://stackoverflow.com/questions/...ii-in-pure-lua

I'm surprised that your script is saving the data as UTF-8 though, since Lua doesn't use it by default.

I sort of found out the reason lua save data as utf-8. When the data contain any non-English words, in my case Chinese, then it will change it to utf-8.

[Meo-Ada Mespotine]

Hmm...some sort of control over the encoding would probably better.

[cfillion]

REAPER uses UTF-8 so all strings obtained from the API are UTF-8. Lua string literals (which are just arrays of bytes) are encoded as they are written in the script (so if the script file itself is UTF-8 you'll get UTF-8 out). Which ANSI codepage are you targeting? (looks like there's a few chinese ones)

[dsyrock]

Originally Posted by cfillion

REAPER uses UTF-8 so all strings obtained from the API are UTF-8. Lua string literals are encoded as they are written in the script (so if the script file itself is UTF-8 you'll get UTF-8 out). Which ANSI codepage are you targeting? (looks like there's a few chinese ones)

I'm using GB18030

[BartR]

Originally Posted by Lokasenna

You could try: https://stackoverflow.com/questions/...ii-in-pure-lua

I'm surprised that your script is saving the data as UTF-8 though, since Lua doesn't use it by default.

I just got the confirmation now, that the text file I was exporting in LUA is UTF8 and not ANSI. I need to solve this as well.
On my case I just use things like that

local variable = "ààà"
file:write(variable)

but it writes it in UTF8 not in ANSI and I have not clue how to convert it within LUA

[cfillion]

The string literal contains UTF-8 because the text editor (REAPER IDE?) encoded it as such. Writing a string variable to a file in Lua copies the bytes as-is.

You can specify characters using their byte value in any encoding, without having to change the encoding of the script itself:

local variable = "\xc3\xa0\x0a" -- utf8 for à (3 bytes)

Just curious, why do you need to downgrade from the universal UTF-8 to a system-specific ANSI codepage?

[BartR]

Originally Posted by cfillion

The string literal contains in UTF-8 because the text editor (REAPER IDE?) encoded it as such. Writing a string variable to a file in Lua copies the bytes as-is.

You can specify characters using their byte value in any encoding, without having to change the encoding of the script itself:

local variable = "\xc3\xa0\x0a" -- utf8 for à (3 bytes)

Just curious, why do you need to downgrade from the universal UTF-8 to a system-specific ANSI codepage?

For a script I have made (ChapterRegion.lua) that exports a sidecar TXT file, readable by some radio-automation software based on ANSI (accented letters were totally screwed-up)

BUT the good news is: after have told to the company what the issue is, and that it will be much better for them to switch from ANSI t UTF-8, they answered to me just few minutes ago, that from next releas on, they will read the SideCars in UTF8.

They have tested on a sample I sent them, and everything is now fine.

So: problem solved to the root :-)