There's a Google code repository for the IDE. You have to have access rights to check in though. The setup doesn't work to well with anonymous translators.
Also while testing I found some translation issues in general. These might be that I'm running too old version (0.7.2) etc, but anyway decided to report them here.
SimpleIDE Properties:
- Tabs "Folders" and "General" are not included in translations (appear in English and I cannot find any string from the supplied .ts file).
New files:
- All new files appear in English as "Untitled", no string in .ts file to change this new file name into local language.
About dialog:
- Version string is not localized, I mean the string between SimpleIDE text and version number at the first line. No string in .ts file.
- "email bug reports to.." string is not localized. No string in .ts file.
Save dialog:
- Save, Save All and Discard are not localized. No strings in .ts file, except for "Save" which is used elsewhere.
Tools menu:
- From some reason there's two times "Bigger Font" with different keyboard combinations. This seems to be the case without translations too, so I guess this is OK.
Goodness, I step away for one day (to celebrate the 4th) and I come back and we have two language translations done! You guys are awesome!!! I've updated the table on the first post to reflect the newest information. I'll PM those who have finished to verify things and get hardware "payments" worked out.
Thanks to Heater. I received one Propeller ASC board for testing and I was able to test compiling + loading with actual hardware too. I made couple adjustments to the translations based on what I saw, so here's version 3 attached with .ts and .qm file.
Also I came up with couple more issues where translations do not apply:
Simple Terminal Window:
- Window title not translated (Simple Terminal). No string in .ts
- Enable / Disable button translation works when you open the window, you get the "Disable" string localized, but when you press it, it loses the localization and "Enable" is shown in English. When you press it again, it shows "Disable" as not localized. So initial view is ok but pressing Disable / Enable it comes up with non-localized string. Translation is available in .ts / .qm file properly.
Build status window:
- Ignoring "simple printf" text is localized except for "simple printf" text in the middle. You can see this from the screenshot attached. There is translation available and it's properly shown in the options at the left bottom where you can select different options. For example in Finnish it looks like this: J
Thanks to Heater. I received one Propeller ASC board for testing and I was able to test compiling + loading with actual hardware too. I made couple adjustments to the translations based on what I saw, so here's version 3 attached with .ts and .qm file.
Also I came up with couple more issues where translations do not apply:
Thank you so much for all your feedback. It is very important and will be incorporated where possible as time permits.
Most of the build status text comes from GCC (except loader messages). Can the GCC build process localize errors and warnings?
There is no provision for the propeller-load program messages to be localized. It may be possible to capture "error" messages (and others) then replace them with localized text in the IDE.
It seems that GCC does have localization support. I was testing in Windows and there are lots of reports that it's not properly working in Windows, so it might be the case here. I will check in Linux how LANG and LANGUAGE variables work there with GCC. If there's a way to pass the variables into the process that is launching it, it might help. If there's something else I can help with, just let me know.
It seems that GCC does have localization support. I was testing in Windows and there are lots of reports that it's not properly working in Windows, so it might be the case here. I will check in Linux how LANG and LANGUAGE variables work there with GCC. If there's a way to pass the variables into the process that is launching it, it might help. If there's something else I can help with, just let me know.
Ok. Can you give me a link or more information about "lots of reports that it's not properly working in Windows ..." ?
It seems that both are related to MinGW port here, but quoted from the last thread:
I can now confirm that the Microsoft "bug" exists on both the 32-bitand 64-bit editions of Windows 7. I.e. users of msvcrt.dll are screwedup if they use putchar for multi-byte characters, like Chinese,Japanese, or Korean. Not only is GCC affected, many of other old toolsI am used to using are screwed up too (dependent on msvcrt.dll;probably built by MinGW).
It might be that this is not related after all, but I was running 32-bit Windows 7 when I posted about those output issues.
Forgive me if I am wrong but is it so that the loader is a separate program launched by the IDE and that it is written with no internationalization support?
If so is it possible that:
a) It can be linked in with the IDE binary and as a part of the IDE make use of the Qt translation system.
b) Remain as a separate program but be built with Qt and use the same translation system.
Forgive me if I am wrong but is it so that the loader is a separate program launched by the IDE and that it is written with no internationalization support?
If so is it possible that:
a) It can be linked in with the IDE binary and as a part of the IDE make use of the Qt translation system.
b) Remain as a separate program but be built with Qt and use the same translation system.
Will talk to David about this when he comes back from vacation.
Daniel will be out for part of this week as part on a Field Application Engineering assignment for Parallax Semiconductor. I don't know how much time he'll have to check in on this thread and coordinate our team. We might not see him until the end of this week.
In the meantime, I'm just sending a note of appreciation and encouragement to keep going on this effort so we can do this properly. Keep in mind that this can be one of those never-ending efforts; once you start working with us on a translation project. . . .
Looks like we're stuck with English and other ASCII only output for now from the GCC compiler.
--Steve
IMHO it does not matter.
More over, it's desirable to not translate GCC compiler output.
In case of GCC error, there are more chanсes to localization of it, by googling with text error.
Hi Daniel!
Can You update instruction for efficiency the translation process on the whole, and append steps for getting source code from the repository?
Not needed to gain write (upload) access to repository for translators, You can upload .ts files sending to forum by hand (at last, until You become overweary)
What do you think about?
You have to pay for MS products. As a paying customer you can have an expectation of getting a finished product and to not have to take on the role of tester/quality control for them.
Conversely propgcc is free and open source as are the projects/libraries and tools they derive from. A propgcc user is not a customer of those opensource projects. If there can be said to be any payment due it is in terms of keeping to the licences,reporting bugs, offering patches to fix them, donating new code features, helping out with documentation, or as here providing translations.
It's a whole different relationship and philosophy.
I can try to make Polish translation if I can find some time and manage to install all needed tools My operating system is OpenSuse 12.1 x64. Or Win XP in virtualbox.
Comments
EDIT: I just updated this file after I found couple bugs while testing with Simple IDE. New file attached with suffix v2, so use that.
SimpleIDE Properties:
- Tabs "Folders" and "General" are not included in translations (appear in English and I cannot find any string from the supplied .ts file).
New files:
- All new files appear in English as "Untitled", no string in .ts file to change this new file name into local language.
About dialog:
- Version string is not localized, I mean the string between SimpleIDE text and version number at the first line. No string in .ts file.
- "email bug reports to.." string is not localized. No string in .ts file.
Save dialog:
- Save, Save All and Discard are not localized. No strings in .ts file, except for "Save" which is used elsewhere.
Tools menu:
- From some reason there's two times "Bigger Font" with different keyboard combinations. This seems to be the case without translations too, so I guess this is OK.
Goodness, I step away for one day (to celebrate the 4th) and I come back and we have two language translations done! You guys are awesome!!! I've updated the table on the first post to reflect the newest information. I'll PM those who have finished to verify things and get hardware "payments" worked out.
Let me know if you guys need anything!
Thanks,
Daniel
Also I came up with couple more issues where translations do not apply:
Simple Terminal Window:
- Window title not translated (Simple Terminal). No string in .ts
- Enable / Disable button translation works when you open the window, you get the "Disable" string localized, but when you press it, it loses the localization and "Enable" is shown in English. When you press it again, it shows "Disable" as not localized. So initial view is ok but pressing Disable / Enable it comes up with non-localized string. Translation is available in .ts / .qm file properly.
Build status window:
- Ignoring "simple printf" text is localized except for "simple printf" text in the middle. You can see this from the screenshot attached. There is translation available and it's properly shown in the options at the left bottom where you can select different options. For example in Finnish it looks like this: J
Thank you so much for all your feedback. It is very important and will be incorporated where possible as time permits.
Most of the build status text comes from GCC (except loader messages). Can the GCC build process localize errors and warnings?
There is no provision for the propeller-load program messages to be localized. It may be possible to capture "error" messages (and others) then replace them with localized text in the IDE.
Thanks,
--Steve
Ok. Can you give me a link or more information about "lots of reports that it's not properly working in Windows ..." ?
Thanks for your help.
--Steve
http://sourceforge.net/mailarchive/message.php?msg_id=27693377
http://sourceforge.net/mailarchive/forum.php?forum_name=mingw-users&max_rows=75&style=nested&viewmonth=201108
It seems that both are related to MinGW port here, but quoted from the last thread:
It might be that this is not related after all, but I was running 32-bit Windows 7 when I posted about those output issues.
Thanks for clarifying.
Looks like we're stuck with English and other ASCII only output for now from the GCC compiler.
--Steve
If so is it possible that:
a) It can be linked in with the IDE binary and as a part of the IDE make use of the Qt translation system.
b) Remain as a separate program but be built with Qt and use the same translation system.
Will talk to David about this when he comes back from vacation.
Thanks,
--Steve
Hi Sumeet_sic,
Thank you for starting the Indian translation! I've updated the table on the front page.
I started a french translation.
Any remarks and improvements proposed by french readers are welcome.
Jean Paul
Daniel will be out for part of this week as part on a Field Application Engineering assignment for Parallax Semiconductor. I don't know how much time he'll have to check in on this thread and coordinate our team. We might not see him until the end of this week.
In the meantime, I'm just sending a note of appreciation and encouragement to keep going on this effort so we can do this properly. Keep in mind that this can be one of those never-ending efforts; once you start working with us on a translation project. . . .
Thanks again,
Ken Gracey
More over, it's desirable to not translate GCC compiler output.
In case of GCC error, there are more chanсes to localization of it, by googling with text error.
Can You update instruction for efficiency the translation process on the whole, and append steps for getting source code from the repository?
Not needed to gain write (upload) access to repository for translators, You can upload .ts files sending to forum by hand (at last, until You become overweary)
What do you think about?
french translation
after some corrections !
Jean Paul
Are you going to perform the independent back-translation into English to ensure correctness, as suggested?
I don't see a column for that in the table in post #1 yet. (Got to ask, process guy and all).
How very Microsoft! I guess that's one way to do it.
You have to pay for MS products. As a paying customer you can have an expectation of getting a finished product and to not have to take on the role of tester/quality control for them.
Conversely propgcc is free and open source as are the projects/libraries and tools they derive from. A propgcc user is not a customer of those opensource projects. If there can be said to be any payment due it is in terms of keeping to the licences,reporting bugs, offering patches to fix them, donating new code features, helping out with documentation, or as here providing translations.
It's a whole different relationship and philosophy.
Thanks for your update!
Does this mean that you are done, Jean Paul, with the French translation?
Perhaps some lines to improve.
Jean Paul
-Tor