-
Notifications
You must be signed in to change notification settings - Fork 38
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
Translations Wanted #73
Comments
I'd like to have a try. I can translate it to Simplified Chinese (and maybe Traditional Chinese). So how can I get started? |
What I'll need is the Locale you plan to work or run under. Currently we have en_US (mainly for plural word forms and formatting of srings returned by Connman), and ru_RU which is a full translation. Once I know your Locale I'll add it to the main .pro file and run the command to extract the strings. That will create 2 files in the translations directory: cmst_YOUR_LOCALE.ts and cmst_YOUR_LOCALE.qm. I'll upload the files to GitHub and you then open the .ts file with qt-linguist and start the translations. I'm assuming you've not used qt-linguist before, so if not it might be useful to get it installed and look at one of the .ts files already there. It is a multi pane application which shows files, a graphical representation of the widgets (when you are working on one), the raw code, and boxes in the bottom for the string you are working on, the translated string, and below that guesses made by the program for each string. For instance if you translate "ethernet" in one place, the next time you run across that word the first guess, which you can accept or not, will be your previous translation. At good breaking points just run "release" under the "file" menu and linguist will write the .qm file as it currently exists. The translations, if one exists, are loaded automatically at program start based on the Locale you have set on your machine. Fallback is the en_US translation if a translation is not found that matches the Locale installed on the machine.. I'm still playing around with a few GUI elements, but in a few days I'm planning to declare a string freeze. Linguist is really good about accomodating strings that move around, but the freeze will give me time to catch my breath. There is a huge amount of text in the program, I was a bit surprised the first time I extracted it all. This will also give you the opportunity to look at linguist, the amount of text in a .ts file, and see if it is something you still want to tackle. It is likely to take a couple of weeks at best. |
OK. I'll take it. My locale is zh_CN. |
I just uploaded a version to add the zh_CN translation files. Strings are pretty well fixed for now, holding my options open "just in case", but I'm really not expecting to make any string changes between now and the next release. I'll make a formal announcemnt in this thread once I'm completely sure. Thanks and have at it. |
I've decided we are officially in a string freeze. No user visible text will change until after the next release. |
I'd be happy to help translating that beast of an application to de_DE (aka german) :) |
Thank you. Just uploaded a new version with the de_DE .ts and .qm files. There are various ways of getting the files into the program, but simplest is probably if you do a fork and then when you want me to add your work in initiate a pull request. Not necessry that you do the whole thing first, we can do a PR (and as many as you want) whenever you feel it is appropriate. Thanks again. |
Here's some first work in translation: https://github.com/Sqozz/cmst/tree/translation_german I'll do a PR when the most strings are done. |
I've grabbed your in progress translation and a copy is now here in this repo. For the honorifics I'll leave that to you, but if it matters at all I do agree with your choice of doing only one and making it the more informal. A long time ago in a galaxy far, far away I some how managed to pass the New York State Regents exam in German. It has been almost 40 years and I still don't know how I pulled that off, but I do vaguely recall what you are saying. |
Forked here: https://github.com/swordfeng/cmst [ajb reply] grabbed it and the in progress files are now copied here as well |
I have a problem. The word technology in connman does not have exact translation in Chinese. The corresponding word sounds more like technique. Is it all right if I translate it into device? |
Congratulations on the exams. Always a nice feeling when those are behind you. Device sounds perfect, go with it. |
swordfeng and Sqozz: I'd like to add each of you to the contributors list so if you reply here with your name I'll do so. Thanks again for this - this is a major undertaking. |
Ok. My name is Jianfeng Zhang. And for my email address, please use [email protected] and [email protected] as backup. (It is not easy to login gmail in mainland China...) |
@andrew-bibb: wow… learning german must be a real pain. It's very amazing that you can still remember this strange rule in our language ;) |
Thanks both - names are in the "About CMST" dialog. They are in the "devel" branch because if I put them in master I'll violate the string freeze. |
I'm glad to announce that the Simp. Chinese translation is almost completed. |
Thank you very much. I'll grab this and build it in, probably this weekend. |
The new zh_CN files are now in the master and devel branches. |
I'd like to translate it to polish (pl_PL). |
Thank you very much. I just uploaded the blank pl_PL.ts and pl_PL.qm files to the master branch. Master is fairly stable at the moment. There may be some things changing way down in the Agent dialog, discussed in issue #94. Only other thing I may work on is a page for the peer interface, but peers are still marked "experimental" by the connman devs so anything I do there will be in the "devel" branch, not master. If you let me know how you wish for your name (or nickname) to appear in the credits list I'll add you in. |
Hello, I can begin the italian translations... |
I just uploaded the it_IT translation files. I'm assuming that is what you wanted, but if I'm wrong and you need it_CH let me know. Both you and napcok let me know hou you'd like your name or nickname to appear in the "About" credits and I'll add you in. Thank you for taking this on. I do appreciate it. |
@andrew-bibb it's ok, I ment it_IT. And my name is Matteo Castelli. But before, explain me please. I've downloaded the 2 files you uploaded, cmst_it_IT.qm and .ts. Now I have to install qt-linguist, wich is in qt4-dev-tools (right?) under Ubuntu and do load the .ts one (right? or the other, or both..?). And also, where do I have to upload the files when translation will be done? Sorry for that, I'm quite a newbie |
Matteo, There are several QT5 only functions in this project. I don't think running a QT4 version of qt-linguist will be an issue, but if you could arrange to get a QT5 version then I know there won't be. I run Arch so I'm not entirely sure where that is packaged in Ubuntu, but yes, qt-linguist is what you need. With Linguist you open the .ts file. It is a multi-pane editor with a small file manager pane so you can see where in the project you are. When you are done with a line you can check it off so it is easy to see what you've done. When you are editing the UI files a representation of the element is on the screen to help. I use the en_US.ts one to manage plural forms and changing text returned from Connman (always lower case) into a form I wish to display (often all upper case), but my usage is a lot simpler than what you'll need to do. This is a huge undertaking, but the nice thing about linguist is that you can start and stop wherever and whenever you feel like it. When you want to create a package to build or to test go to the "File" menu pick "Release" which will create the .qm file. Then run through the whole "make" process (and maybe "make install") and your translations should show up automatically if you have your locale set to it_IT. Best way to get the files to me is probably fork the project and then work on the files in your fork. When you want me to build them back in do a pull request. You don't need to be finished for that, I can do as many pulls as you want. If you would rather you can also work completely locally and then post here or email we can work out a way to get the files back in. For some of the other guys I've just gone into their GitHub repo's and manually downloaded the files bypassing the entire pull request stage. For your or anybody else, my email is ajbibb_AT_myfairpoint_DOT_net. Usual substitutions apply. |
First time that has happened. I just tried the .ts file here and it opened fine. I've got Linguist 5.4.1. Maybe try this.
This should build a clean cmst_it_IT.ts file on your computer in the translations subdirectory. At this stage you don't need the .qm file, that will be created when you select "Release" from the File menu. |
I've got Linguist 5.4.1 too, and also I've solved downloading the whole master.zip. So i began the translations and finished the 'Agent' block (41 items) already, just to try... 2 quest: 1.sometimes I did preserve the english name, because translating WPS or EAP or also SSID has no sense, I guess, altought CMST report the acronimus intere (WiFi Protected Setup, for example); sometimes I'm in doubt. Do you have any translations guidelines?
thank you and sorry, this is my first time with github! |
I'm glad you got it working, and no problem with the questions. I have no guidelines for translations. I leave that up to the individual translators as they are the resident experts on their language. For things like wpa, eap, etc. all I do for the en_US translation is change them to all capital; WPA, EAP, etc. I think it looks better in the display widgets, but that is english. I have no clue what is typical in Italian, so whatever you pick I'll be happy with. The colored checkmarks are only for you. You can click or or not, whichever is the best for the way you work. The color change is just to let you know what you have done on each string. When you (or I) click "release" the .ts file will be copied and the copy converted to a binary .qm file. It is this binary file that is built into the program. The binary is stripped of all the comments, context notes, and things like checkmarks that are there for you. |
@andrew-bibb |
I'm sorry about the the .qm file, my oversight. I just uploaded a new cmst.qrc file with that corrected. Thank you for pointing it out, I never would have discovered it on my own. For you other guys, my intention is to try and implement issue #98 for the next release. We have just started our very short summer around here so for the next couple of months I won't be doing a lot of programming on much of anything. I'd expect the next release to occur sometime early Fall. |
Been meaning to post for a while. I've got the icon manager (issue #98) and the options for bypassing setting (issue #103) all coded up, so I think I'm now set for the next release. I'm thinking mid to late September but if you guys need more time post and we can change that. When ever anyone gets a set done post and I'll pull it in. Thanks |
I can help with es_CO or es_ES |
The es_CO and es_ES files are up on GitHub. Let me know which one you do and I'll remove the other. Whenever you need me to do a pull just submit a request and I'll pull in the files. Not necessary to be done for that to happen. I can do it at whatever milestones you feel are appropriate. Thanks. |
I can translate it to fr_FR if you want ! |
Been dealing with issue #118 (plus a half dozen other things around here). Thank you for the offer, I'll create the files and post here when they are ready. Probably be two or three days hence. |
I've just updated all the translation files and added fr_FR. There are a bunch of text changes from the last release and I'm going to hold the strings as they exist until the next release, hopefully at the end of the month. If anybody updates your translation files let me know or request a PR. Thanks |
Found this thread only now... |
stefonarch, Been getting the PR's and everything so far has been pulled in. Thank you for setting this up. In response to the license question you left in the Bulgarian translation thread the MIT license is perfect. |
Ok, your welcome. There is actually an issue with the naming. If an user adds a new language this will be in the format |
Hello, |
They are built in during compiling AFAIK, you need to compile it from source. |
Ok but do you know why it's not in the debian package? It's a 2015 translation, the debian package is from 2019. |
I remember there were other changes needed to include present translations, see be86661 |
I just uploaded to here the linguist files from the past few translation updates. My hope is to have a new release built in the next couple of weeks that will incorporate these plus the outstanding bugfix and maybe the one feature request. Intentions are one thing, finding time is another, but I'm going to try. |
Ok thank you. qmake: could not find Qt installation of '' I change debian for antix, same issue. |
Not sure what is missing. I just ran 'make clean', 'qmake', then 'make', three times in fact just to make sure, and the program compiled properly all three times. Is there any other message you are getting? |
Here in debian bullseye no error too, compiles fine. |
@andrew-bibb How is the current process of synchronizing translations from https://translate.lxqt-project.org/projects/andrew-bibb/cmst/ ? |
Hey. I'm translating to Polish and noticed a couple of typos in the source strings. What can I do about those? e.g. <html><head/><body><p>When checked use WPS push button authentication. </p></body></html> contains a double space or Wi-Fi is spelled wrong multiple times. Is there a way for me to report them directly through Weblate or do I have to change the source and submit a PR? Thanks |
You need to do a PR here, and then |
We just released the first version of CMST with translations implemented, and Russian as the first language. If you would like to contribute a translation for your native language please respond and we'll add the appropriate lines to the files to get you started.
Note that we may be reworking some of the code to simplify and isolate the strings needing translation (or at least some of them) to separate files , so if you do wish to volunteer I'll update with the status on that effort. I'm also thinking of declaring a fomal string freeze date for each release if we get people on board to translate.
The text was updated successfully, but these errors were encountered: