x2go-i18n February 2012

x2go-i18n@lists.x2go.org

4 participants
12 discussions

Swedish translation for x2goclient
by Daniel Lindgren 06 Apr '12

06 Apr '12

Hi. Attached is the first version of the swedish translation for x2goclient. I couldn't verify the translation since the build scripts seem to be broken, this is the result when running config_linux.sh: RCC: Error in 'resources.rcc': Cannot find file 'x2goclient_de.qm' RCC: Error in 'resources.rcc': Cannot find file 'x2goclient_fr.qm' RCC: Error in 'resources.rcc': Cannot find file 'x2goclient_nb.qm' RCC: Error in 'resources.rcc': Cannot find file 'x2goclient_ru.qm' RCC: Error in 'resources.rcc': Cannot find file 'x2goclient_zh_tw.qm' Cheers, Daniel

2 12

Re: [x2go-i18n] pyhoca-gui in Swedish and Bokmal?
by Mike Gabriel 06 Apr '12

06 Apr '12

Hi Daniel, On Sa 18 Feb 2012 21:34:58 CET Daniel Lindgren wrote: > Hi MIke, > >> are you also willing to translate pyhoca-gui??? If so, I can provide empty >> language files for your languages. > > Sure, I'll have a look. Is it in the same git repo as x2goclient? > > Cheers, > Daniel > git clone git://code.x2go.org/pyhoca-gui.git The translation file is in pyhoca-gui/po/sv.po. http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=commitdiff;h=e4cf19f755c4736… You have to use a gettext based i18n editor, like e.g. poedit. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 8

Re: [x2go-i18n] [X2Go-Dev] I18n - how to do it
by Terje Andersen 20 Feb '12

20 Feb '12

Hi Moritz, Mike & all Den 20. feb. 2012 11:12, skrev Moritz Struebe: > Hi Mike. > > On 2012-02-20 10:46, Mike Gabriel wrote: >> Most important thing is that such a translation service does not >> conflict with manual translation commits. > No, this should of course not be the case. Basically I am thinking of an > upload and a download script. The upload-script will take the latest > files from GIT and upload them to the server. This _can_ be triggered > using a cron job or done manually. The download script will download the > files and update the git. I'm not sure yet, whether it is better to do > this manually or by using a cron job. None the loss the workload should > not be lower than accepting a patch. > Using the client is described in [1]. It even denies to update the local > files when updating from the server, if you made local changes. :) Or if > someone else checks a new version into git you can automatically update > the version on the translation server. > > Cheers > Morty > I've used transifex, rosetta and pootle before and I'm not a big fan, the only two positive things (in my view) with them is that they make it easy for "drive-by" translation (not dedicated translation). This might be a big plus if what you want is a greater numbers of languages (which might, or might not be completely translated), but I think the quality goes down on the actual translation. With the web-based solutions also the amount of collected words, with their potential translation, from all the different projects using the service might be of help to someone, but still might lead the translator into using wrong words because of the missing context and the fact that others have chosen this word (in another, not related project). With Qt Linguest, often the dialog will be shown (Wow! I wish this would be the case for all the strings :p) which helps tremendously in understanding the context of the strings currently being translated. With po-edit it's more like the web-based ones, it's not easy to understand the context. I too have some concerns on how to do the practical merge of the manual translation patches sent over mail with the download from the web-based service. Which "wins" when there are strings which are translated both manually and on the web-based service? In relation to the work of committing the translation patches, I think that with the first patches from new translators there will be questions, something went wrong and uncertainness on how things are done. I see two ways of making the time to commit the patches sent from translators less time-consuming. 1) Keep clean and concise (and always updated) instructions on how to do the actual translation, how to create the patch, and finally where to send the patches. 2) Give translators git commit access (somehow I see this one as being the least likely to happen :p). In my view, translators, web-page admins and documentation writes in a project on equal footing as those who commits small code-patches - all being potential committers to either git, or wiki/web. As people show commitment, trust should be given in different levels and on different arenas. This isn't an argument for giving me git, or any other access, it's just my point on view and my points towards the web-based translation services. Anyway, I guess I'll be committed either way in translating X2Go, (as long as you want me, that is :-)), it's your choice what to use ;-) Best regards, Terje

1 0

Re: [x2go-i18n] [X2Go-Dev] I18n - how to do it
by Mike Gabriel 20 Feb '12

20 Feb '12

Hi Morty, On Mo 20 Feb 2012 10:37:16 CET Moritz Struebe wrote: > X-Posting to i18n and dev (Please make sure we continue this) > > Hi there, > > as i18n is getting more dynamic at the moment, I remembered our > discussion from September last year. One of the things we looked at was > www.transifex.net. I think we should reconsider looking at this, as it > will allow to translate x2go without the need of using git, but using a > web interface. And they have an API, as well as a simple client, so we > can script the up- and download of translation files. As it is just used > as a tool for translation, we take no risks. In the worst case, we can > just switch to a different service or go back to the current workflow. > Any comments? I am not a fan of such web services. However, I get that it might make things easier for translators. I am not against such a service, if you find time and others like it this may be the way to go. Most important thing is that such a translation service does not conflict with manual translation commits. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

nb_NO.po file added to pyhoca-gui
by Mike Gabriel 20 Feb '12

20 Feb '12

Hi Terje, in case you find some time... I have added an empty nb_NO.po file to pyhoca-gui: http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=commitdiff;h=06c5b76ff81fd17… Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 4

Re: [x2go-i18n] [X2Go-Dev] Several Typos in X2Go-Client, Windows, English (was: German)
by Mike Gabriel 19 Feb '12

19 Feb '12

Hi Stefan, On So 05 Feb 2012 13:32:12 CET "newsgroups.mail2(a)stefanbaur.de" wrote: > Also, can I change the English parts of the file as well, if I > notice inaccuracies, or will that break the build process? I have fast-read through the .ts files of x2goclient as well now and agree about the inaccuracies in the English originals. My suggestion is to translate the hard-coded passages within the C++ code into English. Something similar to what we do with non-English languages we can do with the English language. Thus linguistic quality of X2Go Client is no business of the code developers anymore but can be given into the hands of an English native speaker. I have provided an empty x2goclient_en.ts file. Do you think you could take a look? Or maybe any of the native speakers here on the list? Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

i18n wiki page updated...
by Mike Gabriel 19 Feb '12

19 Feb '12

Hi guys, I did some proof reading: http://wiki.x2go.org/wiki:development:i18n Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Norwegian x2goclient translation
by Terje Andersen 19 Feb '12

19 Feb '12

Hi, I have just finished translating the Norwegian (Norwegian Bokmaal) version of x2goclient, and I will continue on the the rest of the packages. I intend to try to keep them updated as new strings appear. What I did to add the new translation follows here, and if I did something wrong here I hope you will advise me on how to do it correct. (for the initial git setup, I followed the wiki here to my set name and email: http://wiki.x2go.org/wiki:development:git ) 1. "git clone git://code.x2go.org/x2goclient.git" 2. "cd x2goclient" 3. "git checkout" 4. Copied the German translation into a new file named "x2goclient_nb.ts" 5. Editied the x2goclient.pro file and added the line: "TRANSLATIONS += x2goclient_nb.ts" 6. I then updated the *.ts-files with the command: "lupdate x2goclient.pro" (This lupdate command also updated all the other language files too, so I replaced them with the originals) 7. Translated the x2goclient_nb.ts in Qt's Linguist translation application 8. "git add x2goclient_nb.ts" 9. "git commit" 10. "git format-patch -1" The last command (step 10) created a patch-file for emailing which I've attached here. What is your preferred way of receiving language files/changes? Is it ok for you to get them as patches which are prepared with the 'git format-patch' method here? Should the address patches(a)x2go.org be used instead, or maybe get a copy? I wrote the way I did the whole git and translation process because it's missing on the wiki (where I thought it would be written down, it says "TODO" - both on the devel page, and also on the documentation of the Translation). If this is an approved way of doing the translation process, or if you can correct me, I can write this up on the wiki if you would like me to. How can I go about to get write access to the wiki? wow! I guess I've asked a lot of questions here - sorry for that! But as I'm new to the project and there are "black holes" in the documentation, I hope you will be lenient with me :-) Best regards, Terje Andersen

2 7

pyhoca-gui in Swedish and Bokmal?
by Mike Gabriel 18 Feb '12

18 Feb '12

Hi guys (meaning Daniel and Terje), are you also willing to translate pyhoca-gui??? If so, I can provide empty language files for your languages. Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Suggestions
by Terje Andersen 16 Feb '12

16 Feb '12

Hi all, I've been thinking here (I know, that's dangerous :p) and I've got two suggestions: 1. I've been thinking about the translation of X2Go into languages with less widespread usage (like Norwegian is because of the small population). When someone gets an error message and he/she wants to search for more information on that error, they got less chance on finding any help/information because the text they search on is in a "small" (less used) language. Knowing what the text is in the original (English) language isn't possible/easy as the translation isn't done word-for-word, so the user can't search in English. What I propose is to add an error-code/number which is the same regardless of the language used. If this could be something more than just a number, like "[x2go-1234568]" it would be real easy to find information with search engines. This would greatly improve the success rate in resolving any errors, and reduce the potential for frustration. A list, with the potential for translated versions, on the wiki could be kept updated with the error-code and a short helpful explanation/help text. I really hope this can be considered for X2Go. 2. In the original text (English) in the X2Go client the words "suspend" and "resume" gives the impression (at least for me) that the session is paused when suspended. I remember the early version of the NX libraries which actually paused the session when suspended, but that's a long time ago, and no longer the case. I therefore propose to use the words "disconnect" and "reconnect" instead, as this would more correct indicate the functionality that actually takes place. Regards, Terje

4 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

x2go-i18n February 2012