Author Topic: English language file error (file encoding) + fix (for next version?:))  (Read 9216 times)

0 Members and 1 Guest are viewing this topic.

zytep

  • Full Member
  • ***
  • Posts: 11
First 3 lines says:
encoding=utf-8
output_charset=utf-8
output_encoding=utf-8

Real encoding says something different: (think its really iso-8859-1)
Notepad: ANSI
Dreamweaver: Western European

This will give others problems, when trying to translate into languages with "weird" :P non latin characters.

It can be changed verry easy - open the file with notepad, choose "Save-as" and use utf-8 as the new encoding (works on other files already showing up wrong).

(Doubble check it actually works on your systems - does on mine.^^)

Inspirer

  • Mibew Project founder
  • Native
  • *****
  • Posts: 262
    • Mibew Messenger
English properties file contains only symbols from the first part of ascii table, therefore it can be interpreted as iso-8859-1 (if you like). So, the problem you describe is the problem of the software you use to edit properties :) I use eclipse, it allows to set encoding for any file.

PS: It is better to use utf-8 as output encoding to be able to read (in chat, history etc) non-latin characters. Most of our localizations use utf-8 encoding to reduce the number of conversions in runtime.