There are packages qt3-linguist and qt4-linguist for which ever versions of Debian are appropriate.
I'm sure there are packages for other distros.
I just installed the full Qt SDK from Nokia's Qt downloads page. The linguist program ends up in QtSDK/QtCreator/bin/linguist in my home directory.
You can also use the smaller Qt Creator package from the same page which is a smaller download. http://qt.nokia.com/downloads/
There are packages qt3-linguist and qt4-linguist for which ever versions of Debian are appropriate.
Debian only seems to only have qt4-linguist-tools, which only contains 'lupdate' and 'lrelease' command line tools. They don't seem to be sufficient for the job, from what I can tell (I may be mistaken of course).
I just installed the full Qt SDK from Nokia's Qt downloads page. The linguist program ends up in QtSDK/QtCreator/bin/linguist in my home directory.
Thanks for the URL, I hadn't seen it before. I'm wary of having to install the full SDK though, and I prefer packages (so that it's known to apt/dpkg), and the installation is a binary executable, not a shell wrapper around e.g. a tar file, and I intensely dislike installing completely blindfolded. Will have to think about this.
@Heater: Thanks a lot for that! For some reason apt-file failed me here and I didn't find those packages as source for linguist (or linguist-qt4 as it's called). Well it's probably because my fingers tend to write 'linquist' whenever I mean to write 'linguist'.. anyway, all's sorted out now! I will take a closer look at what I have now installed and maybe I can volunteer for Norwegian. Will not promise anything just yet though..
I've asked Daniel to quickly bring the opportunity for additional translations to a close since we're hitting our budget, focusing on those on our list on the first post because we need to move forward with what we've started and get the files integrated into Simple IDE. For now we will not add more translations for the $500 hardware credit. If people want to do them for free we will still gladly accept them.
500 dollars, nah, I have a few translations I would like to make from American to English English. All I ask is a minimal Prop II board when it comes out, signed by Chip of course:)
I agree, Portuguese for what? Here in Portugal the unique "propellers" that are known, are of boats and planes.
I was hoping to avoid the "this language is important, this one is not" discussion. Clearly they're all important to us!
But here's the details from our perspective, again, in short:
- we need to integrate the files we've got into SIDE
- we've used up our budget for funding translations for now
- we can add more translations as soon as our SIDE team is able to handle what we've got
- new volunteer translations are now welcomed and appreciated; we'd need some time to integrate them to our SIDE tool (if you've got Portugese underway please see below)
This isn't about Parallax not being concerned with lack of Portugese support. We are.
If you've started it and have some progress underway, let's incorporate it! We'll gladly support the effort with hardware, recognition and appreciation.
Hello,
Portuguese translation.
Ken, if you have questions, contact me.
Thank you.
Thanks.
Portuguese is in the top 10 languages of Propeller-GCC site visitors, Brazil is locale number 15.
Translation files will be added to SimplIDE beta downloads very soon for version 0.7.x IDE.
We will need more help from participants for the version 0.8.x IDE later.
I install the Proppeller GCC, and copy the files Portugueses to folder translations. Start GCC, and the language don't change. What should I do? I want to try the Portuguese, to see if it takes some adjustment. Thank you
1) The SimpleIDE version must be 0-7-2
2) The spelling must match: SimpleIDE_pt.qm
3) The file must be in the SimpleIDE translations folder:
Windows7 C:\Program Files (x86)\SimpleIDE\translations.
Linux and MacOSX users have different folders.
4) You must restart the program once the file is copied to translations.
Here's a screenshot from my computer. My file was named SimpleIDE_en.qm because "en" is my locale.
I'm not sure if this issue had been discussed before but I'm just thinking about the infrastructure in future translation need.
The .ts file format is actually in xml format. So, here's my thinking:
1. We could have a simple web page (maybe in php or jsp) that will load each .ts file & populate to a MySQL DB with fields like English-US (Main), UK, French, German, CS, CT, etc.
2. Then, when Steve or any dev team updates the main .ts file, he/she could upload & update the DB.
3. Then, Steve could hit a global-update key & the web-site would issue an email to each translator that there are updates required.
4. Each translator would then log-in to the web-site & update his/her local language.
5. Once done, Steve or dev team could download to each .ts file in its correct format.
I'm thinking that all of us still has to run errands & sometimes do some travelling. So, if the translation work could be done simply by login to a web-page, then the turn-around could be a lot faster for each updates.
I need your ".ts" files for translating to the version 0-8-0 IDE.
The ".qm" and .qph files will only work on version 0-7-2.
Please post your .ts files.
Everyone,
All I have right now is French, Finnish, German, Simplified Chinese, and American English.
We need Italian and Spanish from the committed contributors.
Also,
I'm attaching "ported" simpleide-de.ts, (fi, fr, and zh) files for the new 0-8-x IDE.
Please check them for missing phrases. Terminal -> options for example.
Also attaching a newly updated blank propside-ts-new.zip file for new translations. Rename propside.ts to simpleide.ts (sorry).
Kenichi, I don't fully understand your system right now - perhaps I'm too tired. Will review in the morning.
As for my comment, it is more like an on-going process. I think I could help in setting up a VM server, MySQL DB but will take some time in doing up the web-site (using jsp). I'm just thinking out loud to see if this would be beneficial in the long-run as I don't want to spend time doing something that will be discarded (-_-"... again). It might turn out more work on your part as I'm not sure what transpires before you dishes out the .ts file in each language to all translators but my initial thought was this could help cut-down that process for you. On top of that, translators would simply focus on those words that needs translation (newly added or amended) on the web-site. In the meantime, let me dig a little deeper into the process.
Here's updated + checked Finnish version attached for 0-8-x.
Regarding MacTuxLin's idea I have nothing against that, but usually problem is not how the translations are done. Usually problem is the distribution of updated translations without creating a new version / build / installer from the software. This usually comes up when somebody notices that there's an error in the translations after the software is already launched to the public. This could be avoided if we just have some time to check the translations using 0-8-x IDE before its launched. Second choice is to have the program check for updates automatically for new translations etc, but it might be a bit more too complicated at this point (beta).
MacTuxLin, it's not a bad idea in general. Actually we use exactly that kind of system where I work. We used commercial product called "Multilizer" earlier, but when new version was released, there was a non-editable file was released together with the software for each locale (generated from the translation file we send to development). When software was used and problems with translations were noticed, there was no way to update the translation without first modifying the translation package, then sending it back to development, which then created a new package / patch that was installed into customers system. This usually always meant that when new release was available (and translations done for it), it needed to be checked to see where all new strings are in the program and does the made translation fit into that place (should the translation be different length or phrasing correct etc). This is specially important in Finnish language, because the structure of the language is completely different than most other languages. Our Grammatical case is pretty weird since we use prepositions completely different way. We don't add words like "on", "in", "at" etc into the front of the word, but actually alter the whole word. For example when talking about "house", which is in Finnish "talo". In English you say "in the house", we just change the suffix of the word and "talossa" is the same in Finnish. "at the house" is "talolla" etc. This means that for defining the right translation we need to understand where this string is used, so we can then define proper preposition of the word.
So anyway this cycle might have taken couple days, which was a bit slow and heavy for updating just couple strings. Because of this we changed to this web based system where the main translation package is at server and translations were done using a browser and after changes it was possible to download new package straight away. This couple day process became couple minute process after the switch, which naturally did improve things and customer happiness.
But our scenario is different here, because 1) We can output the binary file for testing straight from Qt Linguist 2) We can test the translations before the software is actually launched (that's what I understood from jazzed's post) and see that translations made fit properly into their places.
If we want to come up with improvements for the process, then I think first phase should be adding the translation files into source control (which has been mentioned in this thread before). This way translators could subscribe to changes into their translation file (= see when jazzed has added something there) and get notified by email when there is something new to check / translate. This doesn't require much effort, so its easy & fast to implement if wanted / needed. Currently I have anyway archived pretty much the same by subscribing to this thread, so I get email alert when something is added to this thread. Not all is relevant to my role, but at least I'm not missing anything.
Sorry about the long email, but just wanted to share my experiences from other projects.
Ok, finally I've been able to post some reasonable packages for Linux (debian), OSX, and Windows.
Sorry it's taken so long. Please read the notes for each package. The translations "should" work in your locale.
Documentation is a work in progress and initially will be described as differences on the propellergcc site. https://sites.google.com/site/propellergcc/ See the SimpleIDE page (test packages are not linked).
I'll be gone most of the day today. Back on-line in about 10 hours if I'm lucky, but intermittently then.
I just installed Windows package and all seems good so far. It's firing up with Finnish without problems. I use English Windows 7 (64-bit), but have set program locale to Finnish.
OK. I looked through version 0.8.1 and here's my findings. I know this is beta and some of these I have mentioned earlier, but I guess better to point out issues than be silent.
Translation related:
- First of all I created new .qm file from my translations, since some of the new strings were missing (I guess old .ts file was used when creating .qm). After this situation improved.
- In about box "email bug reports to" is not localized (mentioned before)
- In editor when you hover the mouse of top of close mark (X) in a tab, "Close tab" pops up, but is not localized (new)
- In main window at the left bottom "Code size" line is not localized (mentioned before)
- In main window above "Code size" line there's three tabs where you access project options, compiler and linker settings. Only "Project options" is localized, "Compiler" and "Linker" appear in English. Contents of the tabs are OK (new)
- New files appear as non localized / untitled (mentioned before)
- In settings popup all tab names except "Highlight" are not localized (new)
- In Simple terminal name of the window is not localized (mentioned before)
- In Simple terminal enable / disable is not localized (mentioned before)
- In Simple Terminal settings and general settings "OK" and "Cancel" buttons are not localized. (new)
- When closing a file or project without saving, popup warns do I want to save the file. Buttons in this dialog are not localized. (new)
Functionality related:
- Simple terminal doesn't work. Window is just completely black and settings do no affect (for example changing background color to something else). Cannot see anything from the terminal. (new)
1. Under Help, the "Credits" still shows as English even though .ts file already have the CS (&Credits and Credits in MainSpinWindow)
2. When selecting Projects/Open Project, the title on the window have problem on the 3rd character. The sentence in .ts file looks fine, though.
Below are words and sentence still in English even though there are CS in .ts file:
3. Menu Projects/Save As Project.
4. Menu Projects/Clone Project.
5. Compiler Tab title.
6. Linker Tab title.
7. Under Linker Tab, Create Project Library
8. Ballon help for Save As Project.
9. Ballon help for Back
10. Ballon help for (Browse Ctrl+Left Click)
11. Stop Build or Loader
12. Build Status Tab title
13. Inside About, "Visit SimpleIDE for more information"
14. Inside About, "Email bug reports to .. "
15. Inside About, "Show this window at startup"
16. Inside Project/Properties:
a. GCC Folders Tab Title
b. Spin Folders Tab Title
c. General Tab Title
d. Highlight Tab Title
17. Compiled & Terminal is working but buttons "Options" & "OK" still in English. There's one thing very weird. On first launch & Run Console, the Terminal's button "Disable" was in CS. After I click "OK" & click Run Console again, it shows up in English. On subsequent clicking of Run Console, it stays in English. But if I quit & launch & Run Console, the first time would always be in CS ...
It seems that you might have old .qm file in translations directory?
I had the exactly same problem that some (mostly same) translations didn't work, but after I took the latest .ts I made (where these new strings are) and released it into translations directory of SIDE, then most of the issues got fixed. I guess this involves your issues 1-13 and 15-16. 14 is a real issue since (mentioned couple times in this thread) and also 17 (was having this behavior already in version 0.7.2).
Try to release the latest .ts file and see what comes up. This .ts file should have some of the strings moved into another category and some already marked as obsolete (first one didn't).
Comments
There are packages qt3-linguist and qt4-linguist for which ever versions of Debian are appropriate.
I'm sure there are packages for other distros.
I just installed the full Qt SDK from Nokia's Qt downloads page. The linguist program ends up in QtSDK/QtCreator/bin/linguist in my home directory.
You can also use the smaller Qt Creator package from the same page which is a smaller download.
http://qt.nokia.com/downloads/
Thanks for the URL, I hadn't seen it before. I'm wary of having to install the full SDK though, and I prefer packages (so that it's known to apt/dpkg), and the installation is a binary executable, not a shell wrapper around e.g. a tar file, and I intensely dislike installing completely blindfolded. Will have to think about this.
-Tor
On my Debian.
# apt-get install qt4-dev-tools
did the trick just fine. qt4-dev-tools contains the linguist program and is available for squeeze, wheezy and sid.
See http://packages.debian.org/search?keywords=qt4-dev-tools
and http://packages.debian.org/squeeze/qt4-dev-tools
-Tor
I've asked Daniel to quickly bring the opportunity for additional translations to a close since we're hitting our budget, focusing on those on our list on the first post because we need to move forward with what we've started and get the files integrated into Simple IDE. For now we will not add more translations for the $500 hardware credit. If people want to do them for free we will still gladly accept them.
Everybody has done a fantastic job!
Ken Gracey
I was hoping to avoid the "this language is important, this one is not" discussion. Clearly they're all important to us!
But here's the details from our perspective, again, in short:
- we need to integrate the files we've got into SIDE
- we've used up our budget for funding translations for now
- we can add more translations as soon as our SIDE team is able to handle what we've got
- new volunteer translations are now welcomed and appreciated; we'd need some time to integrate them to our SIDE tool (if you've got Portugese underway please see below)
This isn't about Parallax not being concerned with lack of Portugese support. We are.
If you've started it and have some progress underway, let's incorporate it! We'll gladly support the effort with hardware, recognition and appreciation.
Okay?
Ken Gracey
Please post the Portugese translation here and we will include it in SIDE, and follow through with our $500 hardware appreciation.
Thanks -
Ken
Thanks.
Portuguese is in the top 10 languages of Propeller-GCC site visitors, Brazil is locale number 15.
Translation files will be added to SimplIDE beta downloads very soon for version 0.7.x IDE.
We will need more help from participants for the version 0.8.x IDE later.
Thanks for all contributions!
Cheers,
--Steve
1) The SimpleIDE version must be 0-7-2
2) The spelling must match: SimpleIDE_pt.qm
3) The file must be in the SimpleIDE translations folder:
Windows7 C:\Program Files (x86)\SimpleIDE\translations.
Linux and MacOSX users have different folders.
4) You must restart the program once the file is copied to translations.
Here's a screenshot from my computer. My file was named SimpleIDE_en.qm because "en" is my locale.
I'm not sure if this issue had been discussed before but I'm just thinking about the infrastructure in future translation need.
The .ts file format is actually in xml format. So, here's my thinking:
1. We could have a simple web page (maybe in php or jsp) that will load each .ts file & populate to a MySQL DB with fields like English-US (Main), UK, French, German, CS, CT, etc.
2. Then, when Steve or any dev team updates the main .ts file, he/she could upload & update the DB.
3. Then, Steve could hit a global-update key & the web-site would issue an email to each translator that there are updates required.
4. Each translator would then log-in to the web-site & update his/her local language.
5. Once done, Steve or dev team could download to each .ts file in its correct format.
I'm thinking that all of us still has to run errands & sometimes do some travelling. So, if the translation work could be done simply by login to a web-page, then the turn-around could be a lot faster for each updates.
What do all of you think?
Jean Paul and DamirX,
I need your ".ts" files for translating to the version 0-8-0 IDE.
The ".qm" and .qph files will only work on version 0-7-2.
Please post your .ts files.
Everyone,
All I have right now is French, Finnish, German, Simplified Chinese, and American English.
We need Italian and Spanish from the committed contributors.
Also,
I'm attaching "ported" simpleide-de.ts, (fi, fr, and zh) files for the new 0-8-x IDE.
Please check them for missing phrases. Terminal -> options for example.
Also attaching a newly updated blank propside-ts-new.zip file for new translations. Rename propside.ts to simpleide.ts (sorry).
Kenichi, I don't fully understand your system right now - perhaps I'm too tired. Will review in the morning.
Thanks,
--Steve
I've updated the latest CS.
As for my comment, it is more like an on-going process. I think I could help in setting up a VM server, MySQL DB but will take some time in doing up the web-site (using jsp). I'm just thinking out loud to see if this would be beneficial in the long-run as I don't want to spend time doing something that will be discarded (-_-"... again). It might turn out more work on your part as I'm not sure what transpires before you dishes out the .ts file in each language to all translators but my initial thought was this could help cut-down that process for you. On top of that, translators would simply focus on those words that needs translation (newly added or amended) on the web-site. In the meantime, let me dig a little deeper into the process.
Cheers
Kenichi
Regarding MacTuxLin's idea I have nothing against that, but usually problem is not how the translations are done. Usually problem is the distribution of updated translations without creating a new version / build / installer from the software. This usually comes up when somebody notices that there's an error in the translations after the software is already launched to the public. This could be avoided if we just have some time to check the translations using 0-8-x IDE before its launched. Second choice is to have the program check for updates automatically for new translations etc, but it might be a bit more too complicated at this point (beta).
I'll be posting some updated 0-8-1 packages with translations for testing in about 4 hours.
--Steve
So anyway this cycle might have taken couple days, which was a bit slow and heavy for updating just couple strings. Because of this we changed to this web based system where the main translation package is at server and translations were done using a browser and after changes it was possible to download new package straight away. This couple day process became couple minute process after the switch, which naturally did improve things and customer happiness.
But our scenario is different here, because 1) We can output the binary file for testing straight from Qt Linguist 2) We can test the translations before the software is actually launched (that's what I understood from jazzed's post) and see that translations made fit properly into their places.
If we want to come up with improvements for the process, then I think first phase should be adding the translation files into source control (which has been mentioned in this thread before). This way translators could subscribe to changes into their translation file (= see when jazzed has added something there) and get notified by email when there is something new to check / translate. This doesn't require much effort, so its easy & fast to implement if wanted / needed. Currently I have anyway archived pretty much the same by subscribing to this thread, so I get email alert when something is added to this thread. Not all is relevant to my role, but at least I'm not missing anything.
Sorry about the long email, but just wanted to share my experiences from other projects.
Cheers!
Kenichi
Sorry it's taken so long. Please read the notes for each package. The translations "should" work in your locale.
Please find v0-8-1 packages here for testing: http://code.google.com/p/propside/downloads/list
Documentation is a work in progress and initially will be described as differences on the propellergcc site.
https://sites.google.com/site/propellergcc/ See the SimpleIDE page (test packages are not linked).
I'll be gone most of the day today. Back on-line in about 10 hours if I'm lucky, but intermittently then.
Thanks,
--Steve
Downloaded but doesn't show in CS, still in English. I'm on MacOS. Should I be doing any changes or am I missing something?
Cheers
Kenichi
MaxTucLin, I guess SIDE will read your locale settings, so have you set them up properly?
That's was my initial thought too. I've switch between Singapore to China to CS Hong Kong but still no help. Hmm...let me try Taiwan (which is CT) ...
Nope, still in English.
The locale should be China, Singapore, CS Hong Kong & CS Macau...
Translation related:
- First of all I created new .qm file from my translations, since some of the new strings were missing (I guess old .ts file was used when creating .qm). After this situation improved.
- In about box "email bug reports to" is not localized (mentioned before)
- In editor when you hover the mouse of top of close mark (X) in a tab, "Close tab" pops up, but is not localized (new)
- In main window at the left bottom "Code size" line is not localized (mentioned before)
- In main window above "Code size" line there's three tabs where you access project options, compiler and linker settings. Only "Project options" is localized, "Compiler" and "Linker" appear in English. Contents of the tabs are OK (new)
- New files appear as non localized / untitled (mentioned before)
- In settings popup all tab names except "Highlight" are not localized (new)
- In Simple terminal name of the window is not localized (mentioned before)
- In Simple terminal enable / disable is not localized (mentioned before)
- In Simple Terminal settings and general settings "OK" and "Cancel" buttons are not localized. (new)
- When closing a file or project without saving, popup warns do I want to save the file. Buttons in this dialog are not localized. (new)
Functionality related:
- Simple terminal doesn't work. Window is just completely black and settings do no affect (for example changing background color to something else). Cannot see anything from the terminal. (new)
I'm checking & will upload the updated CS .ts file....
Results:
1. Under Help, the "Credits" still shows as English even though .ts file already have the CS (&Credits and Credits in MainSpinWindow)
2. When selecting Projects/Open Project, the title on the window have problem on the 3rd character. The sentence in .ts file looks fine, though.
Below are words and sentence still in English even though there are CS in .ts file:
3. Menu Projects/Save As Project.
4. Menu Projects/Clone Project.
5. Compiler Tab title.
6. Linker Tab title.
7. Under Linker Tab, Create Project Library
8. Ballon help for Save As Project.
9. Ballon help for Back
10. Ballon help for (Browse Ctrl+Left Click)
11. Stop Build or Loader
12. Build Status Tab title
13. Inside About, "Visit SimpleIDE for more information"
14. Inside About, "Email bug reports to .. "
15. Inside About, "Show this window at startup"
16. Inside Project/Properties:
a. GCC Folders Tab Title
b. Spin Folders Tab Title
c. General Tab Title
d. Highlight Tab Title
17. Compiled & Terminal is working but buttons "Options" & "OK" still in English. There's one thing very weird. On first launch & Run Console, the Terminal's button "Disable" was in CS. After I click "OK" & click Run Console again, it shows up in English. On subsequent clicking of Run Console, it stays in English. But if I quit & launch & Run Console, the first time would always be in CS ...
I had the exactly same problem that some (mostly same) translations didn't work, but after I took the latest .ts I made (where these new strings are) and released it into translations directory of SIDE, then most of the issues got fixed. I guess this involves your issues 1-13 and 15-16. 14 is a real issue since (mentioned couple times in this thread) and also 17 (was having this behavior already in version 0.7.2).
Try to release the latest .ts file and see what comes up. This .ts file should have some of the strings moved into another category and some already marked as obsolete (first one didn't).