Jump to content

Kisegami

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by Kisegami

  1. 6 minutes ago, Darbury said:

    Visual Studio Code and Atom are both fine cross-platform options.

    Down in the lower right of their editing windows, they'll show you the current encoding of a file and let you re-encode it before saving.

    I have opened the file that encoded with Notepad++ (USC-2 LE) in VSC. But VSC show that it's already in UTF-16 LE. Do i need to convert all of the files (ks and tjs) to that encoding? Even when i haven't translated anything of them

  2. 1 minute ago, Darbury said:

    Was about to say the same thing. I've run into this problem as well, and saving as UTF-16 LE with BOM always fixed it.

    How to tell if you did it right? Crack open your UTF-16 LE .ks file in a hex editor. It should start with "FF FE".

     

    5 minutes ago, Zakamutt said:

    Are you sure it's using BOM (byte-order mark)? The real encoding you want is UTF-16 LE with BOM, which is very close to UCS-2 LE but not quite methinks. Yes even if the badly translated sourceforge docs say the opposite. Other than that the other tip I've seen is to convert every file to UTF-16 LE BOMc including all the systme script files.

    Any suggest about a tool that can convert all of it to UFC-16 LE? Notepad++ cannot do that @@

×
×
  • Create New...