New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i18n for Windows? #148
Comments
Using iconv (on Linux) you can convert to code page 1251. Change directory to the i18.
Please send me a notice if it solves the issue. |
@zsiki say:
This is a bad decision! This will fix localization under win, but ruin under linux! May be use https://tcl.tk/man/tcl/TclCmd/encoding.htm . I just didn't understand how to get the system encoding. |
I just asked you to try it, if it solve the problem I will make a solution for it. |
Ok. I can do this in a separate branch. But I am not doing assemblies (freewrap). How can I test the result? |
If you have a Windows installation just replace the geo_easy.rus file in the i18 folder and restart the program. |
Make new branch and commit: Geo-Linux-Calculations@561e22f @zsiki say:
https://github.com/Geo-Linux-Calculations/GeoEasy/releases/tag/3.1.4-dev-cp1251 |
Hi, I'm following this issue because I asked myself which code page when I started french localization (which stays at a very early state today). I looked in the doc, but I didn't find any guideline about that (but I may have messed it).
Zoltan, could you, please help us in giving us some guidelines for character encoding in l10n? |
@XRolland, I did not investigate much in this issue so far. Probably the best solution would be to maintain all language files in the same code page and convert it to the local one during installation or at the program start up. Please help me to find a good solution! |
Searching for solution I realized there are more language settings on Windows beside install language: |
Issue #75 was opened 2 years ago... |
@XRolland , if under win, then you can use https://notepad-plus-plus.org/ for transcoding. |
@zsiki I'm not a coder, isn't it better to use, if possible, UTF-8 for all l10n files? But I won't be able to help you to manage a correct display under Windows... In fact, I stupidly thought that Windows was using UTF-8 since Seven! Crazy man... @zvezdochiot Thanks for your suggestion. It's my default text editor! ;-) |
Source utf-8 encoded message with proc encsource from here: |
When building under Windows, it is necessary to translate Russian localization files from UTF-8 to CP1251. Is it possible to somehow solve this problem?
See also: https://geodesist.ru/threads/geoeasy-3-0-3.70513/
The text was updated successfully, but these errors were encountered: