New Chinese simplified translation for FDM 3.9.5 6v252i
s: Alex 1a6c65
New Chinese simplified translation for FDM 3.9.5 6v252i
it from here: https://raw.githubcontent.com/lychi ... er/chs.lng
And I want to blame all your developers. You said that you give for Unicode, and what's that ugly text encode in the language file and your program? And last year I send a email to @freemanager.telechargerjeux.org to give them a translation. But after a year I still have to bear that silly translation built in program.
And I want to blame all your developers. You said that you give for Unicode, and what's that ugly text encode in the language file and your program? And last year I send a email to @freemanager.telechargerjeux.org to give them a translation. But after a year I still have to bear that silly translation built in program.

Re: New Chinese simplified translation for FDM 3.9.5 40b6f
Could you provide file as follows:
- use Windows end-of-lines (EOLs), 0x0d0a, not EOLs provided by the server-side (0x0a);
- convert the file to Unicode (UTF-16 LE) charset, f.e. using Notepad, as it's been described in FDM 3.9.5 topic;
- zip the lng file to prevent another EOL conversion when ing it to the server.
That way the lng file will stay untouched and properly recognized also in Windows using other languages.
- use Windows end-of-lines (EOLs), 0x0d0a, not EOLs provided by the server-side (0x0a);
- convert the file to Unicode (UTF-16 LE) charset, f.e. using Notepad, as it's been described in FDM 3.9.5 topic;
- zip the lng file to prevent another EOL conversion when ing it to the server.
That way the lng file will stay untouched and properly recognized also in Windows using other languages.
Andrzej P. Wozniak, FDM and forum
Read FDM FAQ and the reporting rules
"How to report a bug or a problem with FDM" before posting
Read FDM FAQ and the reporting rules
"How to report a bug or a problem with FDM" before posting
Re: New Chinese simplified translation for FDM 3.9.5 40b6f
Usher wrote:Could you provide file as follows:
- use Windows end-of-lines (EOLs), 0x0d0a, not EOLs provided by the server-side (0x0a);
- convert the file to Unicode (UTF-16 LE) charset, f.e. using Notepad, as it's been described in FDM 3.9.5 topic;
- zip the lng file to prevent another EOL conversion when ing it to the server.
That way the lng file will stay untouched and properly recognized also in Windows using other languages.
Done.
Use the same link to the latest translation file. Thanks for pointing out.
Who is online 3p6y2t
s browsing this forum: No ed s and 3 guests