Signboard updating; ASCII to EUR-KR

[iwillnot]

Hello there, I need some help.

I'm trying to update signboards on my RO server so that newbie game experience and usability is improved. So I'm going over the data/À¯ÀúÀÎÅÍÆäÀ̽º/item folder, looking for nice BMPs to use. I use GRF Editor to open the GRF and view lots of BMP files quickly, and copy the filename of the BMP i want to use.

I found one that I wanted to use, which was the following:

Æ÷¸µ¸ðÀÚ.bmp // Text that I get when I extract the BMP and copy the filename
Æ÷¸Μ¸ÐÀÚ.bmp // Text I get when I copy the filename from within the GRF Editor tool

So I copied the filename and replaced it in the target signboard that I want to update in signboardlist.lub.
Since it uses suffragium.bmp as plain text, I'm imagining that if I just simply copy-paste the filename of the BMP that I want to use, it will work.

Error

However, this does not work (for both ASCII versions) as shown in the error below. Curiously, that's not the ASCII code that I wrote down but it got transformed when the client was trying to read the file. Why is that?

Question

Is this an encoding problem? The signboardlist.lub is opened using my Text editor (Visual Studio Code) with the EUC-KR encoding. 

Changing the title of the signboards (e.g. from korean letters to "Ship to Alberta") and saving the document reflects correctly in the game, which means I have not corrupted my file.

 

Edit: 

I apologize in advance, I posted this in the 3rd party support because I first thought that (a) this is an encoding error (b) Unbolloxer did the transformations from korean to ascii (c) I want to know how to do that on my own so that I can build a tool that does that work.

I realize now that it should be in the client support forum instead. Please, mod, move it when you have the time. Thanks.

Edited December 17, 2018 by iwillnot

[anacondaq]

For avoiding problems, use always korean as main language everywhere.

[anacondaq]

8 hours ago, iwillnot said:

Is this an encoding problem? The signboardlist.lub is opened using my Text editor (Visual Studio Code) with the EUC-KR encoding. 

 

yes, it is.

This is broken twice encoding:

 

Use next

 

 

 

 

 

Your text must be always korean, not broken cp1252 encoding into EUR-KR, or mixes of cp1251, cp1251, euk-r, utf8, etc.

 

 

 

 

[iwillnot]

You are a lifeboat in a sea of problems.

Thank you for your effort (images and explanation) in documenting how to solve this issue @Anacondaqq!

[anacondaq]

Also, there can be an issue with VSCode (as far as I see you're using VSCode). By default, they work only with UTF-8 Like or will open cp1252 (depends on your system).

So, ideally if you will open any LUA files with next encoding:

 

EUC-KR to make sure that everything will be good.

 

Edited December 18, 2018 by Anacondaqq

[iwillnot]

12 hours ago, Anacondaqq said:

Also, there can be an issue with VSCode (as far as I see you're using VSCode). By default, they work only with UTF-8 Like or will open cp1252 (depends on your system).

So, ideally if you will open any LUA files with next encoding:

EUC-KR to make sure that everything will be good.

 

Yes. I was experiencing this often when I modify the iteminfo.lub file - it kept corrupting my items (and their resource filenames) which, after I have saved the file, makes it difficult to reverse.

It was kind of annoying to always 'remember' to re-open with a different encoding, and I was considering sticking with Notepad++ whenever I do my LUA/LUB edits. (But I love plenty handiness of the VS Code /sob)

Thank you again!