You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had some issues creating the console.rc file. Yes, it generated the console.rc file, but with the LocalizeRC error: "Could not copy file! The system cannot find the file specified."
I can commit the files and you can have a look at them. The fields only need re-sizing. Sadly I don't have Visual Studio.
I've had some issues creating the console.rc file. Yes, it generated the console.rc file, but with the LocalizeRC error: "Could not copy file! The system cannot find the file specified."
console/resource.h is missing.
have you download all the project?
I can commit the files and you can have a look at them. The fields only need re-sizing. Sadly I don't have Visual Studio.
I could not find iconv at the location you supplied, so is used the solution from here.
Once I've compiled the binaries. How do I start consoleZ with that specific language? It did create console_DEU.dll, but in the build window it mentiones "build target does not exist"
I change iconv download location in the documentation.
Localized dll and console.exe must be in the same folder.
Localized dll and console.exe must have the same version.
Console.exe loads the localized dll corresponding to your current Windows language.
If you want to test another language, you must rename the localized dll (change the three-letters code).
So just copy (your choice upon your OS and target you are building):
the binaries bin\(Win32 or x64)\(Release or Debug)\*.* in localized dll into l10n\Release
the binaries bin\(Win32 or x64)\(Release Legacy or Debug Legacy)\*.* in localized dll into l10n\Release Legacy
And launch console.exe from l10n\Release or l10n\Release Legacy.
Unfortunately I did not have success with consolez loading the dll.
I can see no problem if you respect these rules:
Localized dll and console.exe must be in the same folder.
Localized dll and console.exe must have the same version.
Console.exe loads the localized dll corresponding to your current Windows language.
If you want to test another language, you must rename the localized dll (change the three-letters code).
We must resolve your issue.
Please do a pull request.
The identity of the translator must appear in the commit. I wish not be responsible for the translation. I will not control that translation is correct and I will not maintainer.
You can add your name in the "about" window (the string can be found in console.ini).
So I spent some more time on it. It seams I had two problems that masked each other.
My iconv.exe produces an incorrect output and the build process didn't give me an error for that, so I didn't detect it. Once I replaced my version with yours, I got an error that stuff was missing.
The missing RES folder might be generated by LocalizeRC, but is not included in your committed project. To remedy that I included the console project in the l10n project (.vcxproj) , which allows me to compile the other languages without manually copying in a RES folder.
LocalizeRC must have "Coy Resource Header and RES Folder" checkbox active, else it will not generate a console.rc file that is correctly built. This option is needed even if the RES folder is deleted and not needed for building.
For these reasons, no matter how many times I tried to rename console_AAA.rc to my language, it would simple be ignored without error. The same happened for console_FRA.rc, as it was not correctly compiled.
After all that work I completely forgot the "about" string. I'll have a look at that next.
Please do a pull request.
The identity of the translator must appear in the commit. I wish not be responsible for the translation. I will not control correctness of the translation and I will not maintain the translation.
You can add your name in the "about" window (the string can be found in console.ini).
Sorry, but I have to mention that the german translation is very incomplete and full of bugs. There are many fundamental mistakes which make it almost unusable.
To mention only a few as example (I could mention numerous more): The menu Edit is never called Editieren in german. Everybody is used to find it as Bearbeiten. Or the Button Clone would never be called Klonen everybody would say Duplizieren. Button would never ever be called Knopf everybody knows it as Schaltfläche and so on.
Translators should at least follow some naming conventions, Windows users are used to! There should be some quality check (community based or something) before a language is included or at least the possibility to switch the language back to a good native english (I didn't find any option to switch the language, if it exists it must be lost in some strange german).
The german is unusable (at least for me). It looks like is was done by a translating software and not by a human thinking about it. Many words are translated word by word instead of meaningful translations as a human would do it or as you can find it in other softwares.
Yes I know I could fix it and do a pull request. But I think not doing any quality check (at least a community based) before including it into the stable release is a main problem that needs to be discussed!
//Edit:
OK I found out to delete the german dll results in falling back to english. But it would be nice to have the option to switch it in the settings of ConsoleZ. This is what users are used to and I don't have to change it on every software update.
OK I found out to delete the german dll results in falling back to english.
This is mentioned in FAQ section.
But it would be nice to have the option to switch it in the settings of ConsoleZ. This is what users are used to and I don't have to change it on every software update.
ConsoleZ language loading follows Windows standard order: first the user language, second the system language and last the neutral language (english). Resource dlls, named (console_<(ISO 639-2/B>.dll), are optional. They can be renamed or deleted.
So:
If you prefer english language, be consistent and configure your user profile. In this case, you configure your preferred language for all Windows compliant applications.
If you dislike ConsoleZ translation: contribute and fix the translation! That is the goal of open source software. To fix the translation, you just need to edit an ini file and do a pull request.
Activity
cruzzer commentedon Feb 14, 2016
You can put me down for German
cruzzer commentedon Feb 15, 2016
Hi Christophe,
I've create that translated ini file for German, but I'm currently not setup to with Visual Studio.
What would you want me to do?
Regards
cbucher commentedon Feb 15, 2016
@cruzzer HI
Thank you for contributing.
So, you created the directory
l10n/DEUand translated the filel10n/DEU/console.ini.Have you generated the file
l10n/DEU/console.rc?The
l10nproject will automatically generate all localized dll by parsing l10n sub directories.There is nothing to add in Visual Studio.
Do you have Visual Studio? Can you build the solution?
Regards
cruzzer commentedon Feb 17, 2016
Hi Christoph,
I've had some issues creating the console.rc file. Yes, it generated the console.rc file, but with the LocalizeRC error: "Could not copy file! The system cannot find the file specified."
I can commit the files and you can have a look at them. The fields only need re-sizing. Sadly I don't have Visual Studio.
Regards
cbucher commentedon Feb 17, 2016
console/resource.his missing.have you download all the project?
Visual Studio Community is free.
See https://github.com/cbucher/console/wiki/How-to-compile
There are links to all needed tools.
cruzzer commentedon Feb 18, 2016
I could not find iconv at the location you supplied, so is used the solution from here.
Once I've compiled the binaries. How do I start consoleZ with that specific language? It did create console_DEU.dll, but in the build window it mentiones "build target does not exist"
cbucher commentedon Feb 19, 2016
I change iconv download location in the documentation.
Localized dll and console.exe must be in the same folder.
Localized dll and console.exe must have the same version.
Console.exe loads the localized dll corresponding to your current Windows language.
If you want to test another language, you must rename the localized dll (change the three-letters code).
So just copy (your choice upon your OS and target you are building):
bin\(Win32 or x64)\(Release or Debug)\*.*in localized dll intol10n\Releasebin\(Win32 or x64)\(Release Legacy or Debug Legacy)\*.*in localized dll intol10n\Release LegacyAnd launch console.exe from
l10n\Releaseorl10n\Release Legacy.cruzzer commentedon Feb 23, 2016
I'm just uploading these files. Unfortunately I did not have success with consolez loading the dll.
german.zip
cbucher commentedon Feb 24, 2016
I can see no problem if you respect these rules:
We must resolve your issue.
Please do a pull request.
The identity of the translator must appear in the commit. I wish not be responsible for the translation. I will not control that translation is correct and I will not maintainer.
You can add your name in the "about" window (the string can be found in console.ini).
cruzzer commentedon Feb 25, 2016
So I spent some more time on it. It seams I had two problems that masked each other.
For these reasons, no matter how many times I tried to rename console_AAA.rc to my language, it would simple be ignored without error. The same happened for console_FRA.rc, as it was not correctly compiled.
After all that work I completely forgot the "about" string. I'll have a look at that next.
cbucher commentedon Feb 26, 2016
Thank you for your work. I fixed the build process. Copy of resource.h and RES folder is no longer required.
rosolino commentedon Apr 8, 2016
Hello.
I upload Japanese localization file.
It is a small place that is the translation ...
JPN.zip
cbucher commentedon Apr 8, 2016
@rosolino Hello,
Thank you for the translation.
Please do a pull request.
The identity of the translator must appear in the commit. I wish not be responsible for the translation. I will not control correctness of the translation and I will not maintain the translation.
You can add your name in the "about" window (the string can be found in console.ini).
pcr-coding commentedon Apr 13, 2016
Sorry, but I have to mention that the german translation is very incomplete and full of bugs. There are many fundamental mistakes which make it almost unusable.
To mention only a few as example (I could mention numerous more): The menu
Editis never calledEditierenin german. Everybody is used to find it asBearbeiten. Or the ButtonClonewould never be calledKloneneverybody would sayDuplizieren.Buttonwould never ever be calledKnopfeverybody knows it asSchaltflächeand so on.Translators should at least follow some naming conventions, Windows users are used to! There should be some quality check (community based or something) before a language is included or at least the possibility to switch the language back to a good native english (I didn't find any option to switch the language, if it exists it must be lost in some strange german).
The german is unusable (at least for me). It looks like is was done by a translating software and not by a human thinking about it. Many words are translated word by word instead of meaningful translations as a human would do it or as you can find it in other softwares.
Yes I know I could fix it and do a pull request. But I think not doing any quality check (at least a community based) before including it into the stable release is a main problem that needs to be discussed!
//Edit:
OK I found out to delete the german
dllresults in falling back to english. But it would be nice to have the option to switch it in the settings of ConsoleZ. This is what users are used to and I don't have to change it on every software update.cbucher commentedon Apr 13, 2016
@pcr-coding You can contribute and correct the translation.
cbucher commentedon Apr 14, 2016
This is mentioned in FAQ section.
see FAQ (and #334)
ConsoleZ language loading follows Windows standard order: first the user language, second the system language and last the neutral language (english). Resource dlls, named (console_<(ISO 639-2/B>.dll), are optional. They can be renamed or deleted.
So:
cbucher commentedon Apr 29, 2016
@ya158 @cruzzer @rosolino @pcr-coding Stable version should be released next week. Please, verify/complete/fix translations.
cbucher commentedon Sep 10, 2016
@ya158 @cruzzer @rosolino @pcr-coding @ys-nuem Hi,
Stable version should be released next week. Please, verify/complete/fix translations.
ya158 commentedon Sep 12, 2016
I`m verify/complete/fix translations.
cbucher commentedon Nov 11, 2016
@ya158 @cruzzer @rosolino @pcr-coding @ys-nuem Hi,
Stable version should be released next week. Please, complete translations.
cbucher commentedon Feb 10, 2017
@ya158 @cruzzer @rosolino @pcr-coding @ys-nuem Hi,
version 1.18.0.17041-beta0 has been released
Stable version should be released next week.
Please, could you complete translations?
madcampos commentedon Oct 8, 2017
Hi, I'm interested in translating for Brazilian-Portuguese. Will send a PR.
cbucher commentedon Oct 9, 2017
@madcampos Hi, all translators/contributors are welcomed.
You will find localization documentation here.
Steps 4 to 6 require Visual Studio for building. Tell me if this is a problem.