[opensuse-translation] [Leap 42.1] Release Notes French Translation
Hello, I have noticed that the release notes are not translated in French in Leap 42.1 GM. The pot file was moved to Weblate but there is no started French translation in the release-notes-openSUSE project: https://l10n.opensuse.org/projects/release-notes-opensuse/master/. There is no fr.po file in https://github.com/openSUSE/release-notes-openSUSE. So I'd like to start the translation. Yesterday, I have clicked on "Start new translation" in the openSUSE Weblate: a message told me that my request was sent but nothing more. Can you tell me what can I do? Do I have to do a manual pull request via GitHub? -- Antoine -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Op maandag 2 november 2015 23:46:38 schreef Antoine Belvire:
Hello,
I have noticed that the release notes are not translated in French in Leap 42.1 GM.
So are the release notes in Dutch. I got totally lost in github, so I am afraid there will not be translated release notes in Dutch. On SVN I could cope to keep them 100% translated within days. But now I can't even start. I also went to Weblate and wanted to start a new translation (to Dutch). IT FAILED. Why start something new without proper testing with users? Can we have the pot file for the release notes back in SVN? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Dne St 4. listopadu 2015 11:02:55, Freek de Kruijf napsal(a):
Op maandag 2 november 2015 23:46:38 schreef Antoine Belvire:
Hello,
I have noticed that the release notes are not translated in French in Leap 42.1 GM.
So are the release notes in Dutch. I got totally lost in github, so I am afraid there will not be translated release notes in Dutch. On SVN I could cope to keep them 100% translated within days. But now I can't even start.
I also went to Weblate and wanted to start a new translation (to Dutch). IT FAILED.
It didn't fail. It told you that administrator was notified and will create you the po file. Like it was for the others. Last 2 were added by request for pl and fr 20 hours ago. So we even act fast. https://github.com/openSUSE/release-notes-openSUSE/commit/e38d79c2fea238e2d0... https://github.com/openSUSE/release-notes-openSUSE/commit/5a442d6cd1f6684fe7... The weblate admin will be around again in few hours and at that point the da po file will become available. Also nobody is forcing you to go with the weblate. You can just copy the po file in the git repo and do everything right away. Tom
Op woensdag 4 november 2015 11:12:39 schreef Tomáš Chvátal:
The weblate admin will be around again in few hours and at that point the da po file will become available.
The Dutch language code is nl.
Also nobody is forcing you to go with the weblate. You can just copy the po file in the git repo and do everything right away.
Git is too complicated for my simple brain. Maybe with a cookbook explanation I can cope with it. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-11-04 13:17, Freek de Kruijf wrote:
Op woensdag 4 november 2015 11:12:39 schreef Tomáš Chvátal:
The weblate admin will be around again in few hours and at that point the da po file will become available.
The Dutch language code is nl.
Also nobody is forcing you to go with the weblate. You can just copy the po file in the git repo and do everything right away.
Git is too complicated for my simple brain. Maybe with a cookbook explanation I can cope with it.
Right. I have no idea how to copy that file and submit it. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlY6CP0ACgkQtTMYHG2NR9WCSgCdEczvATe+Y+qECl1RU/FID6wP wu8Anjk6reER6n2Tgnro83W/5ip+6PJ9 =HLGY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Dne St 4. listopadu 2015 14:32:47, Carlos E. R. napsal(a):
On 2015-11-04 13:17, Freek de Kruijf wrote:
Op woensdag 4 november 2015 11:12:39 schreef Tomáš Chvátal:
Also nobody is forcing you to go with the weblate. You can just copy the po file in the git repo and do everything right away.
Git is too complicated for my simple brain. Maybe with a cookbook explanation I can cope with it.
Right.
I have no idea how to copy that file and submit it.
Does this https://rogerdudler.github.io/git-guide/ help? One needs account on GitHub and permission to write to particular repository. If You don't have it, You can ask maintainer to get it. Otherwise You can fork the repository https://help.github.com/articles/fork-a-repo and clone it locally, do the changes, blah, blah and: git add <changed files> # add modified files to new commit git commit -m "blah blah“ # describe the commit git push origin master # put the local changes on-line And finally make pull request as described on https://help.github.com/articles/using-pull-requests (the maintainer will them merge your changes). Seriously, I don't see much difference compare to SVN. Git is more powerful, so it has more functions, and, yes, more commands... Well, if You don't like git in command line, use GitHub's web interface or weblate. Other option is to make it graphically - download selected *.po files, modify and upload over GitHub interface and create a pull request. Sorry, I'm confused. Some people were complaining they don't like web interface. And now there are complains about command line...? SVN is little bit deprecated, projects are commonly moving to Git... Sincerely, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-11-04 14:52, Vojtěch Zeisek wrote:
Dne St 4. listopadu 2015 14:32:47, Carlos E. R. napsal(a):
On 2015-11-04 13:17, Freek de Kruijf wrote:
Op woensdag 4 november 2015 11:12:39 schreef Tomáš Chvátal:
Also nobody is forcing you to go with the weblate. You can just copy the po file in the git repo and do everything right away.
Git is too complicated for my simple brain. Maybe with a cookbook explanation I can cope with it.
Right.
I have no idea how to copy that file and submit it.
Does this https://rogerdudler.github.io/git-guide/ help?
No, sorry. It has to be a page at opensuse.org, documenting the exact process for opensuse translation process. Including how to assign a file to a particular person, by the team coordinator.
One needs account on GitHub and permission to write to particular repository.
Which are the repositories corresponding to the current svn yast and lcn? A single directory or two, please, I can't go searching for files all over the place.
If You don't have it, You can ask maintainer to get it. Otherwise You can fork the repository https://help.github.com/articles/fork-a-repo and clone it
Sorry, I don't understand any of that. ...
Seriously, I don't see much difference compare to SVN. Git is more powerful, so it has more functions, and, yes, more commands... Well, if You don't like git in command line, use GitHub's web interface or weblate. Other option is to make it graphically - download selected *.po files, modify and upload over GitHub interface and create a pull request. Sorry, I'm confused. Some people were complaining they don't like web interface. And now there are complains about command line...? SVN is little bit deprecated, projects are commonly moving to Git...
We only needed two commands for svn: up, and commit. Nothing else. Browse to the directory holding all the lcn po files, and do "svn commit --message "arbitrary comment". That's all. Copypaste a command. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlY6GJoACgkQtTMYHG2NR9XWVQCePE5JhzERnon6cJt6FP4SW/5w hUAAn3jEH0M8hm1Tx/sboQRk9xN53wUi =0Ydu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Dne St 4. listopadu 2015 15:39:24, Carlos E. R. napsal(a):
On 2015-11-04 14:52, Vojtěch Zeisek wrote:
Dne St 4. listopadu 2015 14:32:47, Carlos E. R. napsal(a):
On 2015-11-04 13:17, Freek de Kruijf wrote:
Op woensdag 4 november 2015 11:12:39 schreef Tomáš Chvátal:
Also nobody is forcing you to go with the weblate. You can just copy the po file in the git repo and do everything right away.
Git is too complicated for my simple brain. Maybe with a cookbook explanation I can cope with it.
Right.
I have no idea how to copy that file and submit it.
Does this https://rogerdudler.github.io/git-guide/ help?
No, sorry. It has to be a page at opensuse.org, documenting the exact process for opensuse translation process. Including how to assign a file to a particular person, by the team coordinator.
It is just a git repository. Like any else. So that general information about how to use Git is enough. Don't look for complexity where there is no any. Although I agree I miss documentation on the wiki...
One needs account on GitHub and permission to write to particular repository.
Which are the repositories corresponding to the current svn yast and lcn? A single directory or two, please, I can't go searching for files all over the place.
E.g. https://l10n.opensuse.org/projects/release-notes-opensuse/ says https://github.com/openSUSE/release-notes-openSUSE ...
If You don't have it, You can ask maintainer to get it. Otherwise You can fork the repository https://help.github.com/articles/fork-a-repo and clone it
Sorry, I don't understand any of that.
OK, basically, there is no difference in purpose and basic logic of SVN and Git. If You wish to edit someone's else repository, You must make Your own copy (=fork it), modify it and then ask owner of original repository to include Your changes (=create pull request). Have You tried to learn Git? If You refuse Git, what is wrong with download/upload po files over web? If any possibility fits Your needs, then, I'm sorry, I'm unable to help You...
Seriously, I don't see much difference compare to SVN. Git is more powerful, so it has more functions, and, yes, more commands... Well, if You don't like git in command line, use GitHub's web interface or weblate. Other option is to make it graphically - download selected *.po files, modify and upload over GitHub interface and create a pull request. Sorry, I'm confused. Some people were complaining they don't like web interface. And now there are complains about command line...? SVN is little bit deprecated, projects are commonly moving to Git...
We only needed two commands for svn: up, and commit. Nothing else. Browse to the directory holding all the lcn po files, and do "svn commit --message "arbitrary comment". That's all. Copypaste a command.
Less features, less commands... It is like to complain about changes when moving from Windows Notepad to real text editor, at least KWrite. For some purposes Notepad is enough. But in some point it is not anymore. Basic usage is also more or less same, although the latter has more possibilities what to do... So what is the big difference between SVN and Git? # Initial clone of the repository git clone https://github.com/openSUSE/release-notes-openSUSE.git work, edit, ... git pull # get newest changes from the repository git checkout # see which files are changed git add ... # select modified files for commit, use TAB git commit -m "Some description" git push origin master # send Your changes Is it really too complicated over the old SVN? Note it is common practice to abandon SVN in favor of Git. openSUSE is not reinventing wheel... It took me one afternoon to learn basic usage when I needed to... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-11-04 16:15, Vojtěch Zeisek wrote:
Which are the repositories corresponding to the current svn yast and lcn? A single directory or two, please, I can't go searching for files all over the place.
E.g. https://l10n.opensuse.org/projects/release-notes-opensuse/ says https://github.com/openSUSE/release-notes-openSUSE ...
But that is a single file. lcn contains 43, yast 96. And there are 13.1, 13.2, TW, Leap versions. How do I find all of them?
If You don't have it, You can ask maintainer to get it. Otherwise You can fork the repository https://help.github.com/articles/fork-a-repo and clone it
Sorry, I don't understand any of that.
OK, basically, there is no difference in purpose and basic logic of SVN and Git. If You wish to edit someone's else repository, You must make Your own copy (=fork it), modify it and then ask owner of original repository to include Your changes (=create pull request). Have You tried to learn Git? If You refuse Git, what is wrong with download/upload po files over web? If any possibility fits Your needs, then, I'm sorry, I'm unable to help You...
The problem is how you organize the translation files. They have to be all in a single directory, a single repo.
We only needed two commands for svn: up, and commit. Nothing else. Browse to the directory holding all the lcn po files, and do "svn commit --message "arbitrary comment". That's all. Copypaste a command.
Less features, less commands... It is like to complain about changes when moving from Windows Notepad to real text editor, at least KWrite. For some purposes Notepad is enough. But in some point it is not anymore. Basic usage is also more or less same, although the latter has more possibilities what to do... So what is the big difference between SVN and Git?
I'm too old a dog to start learning new tricks on my own.
# Initial clone of the repository git clone https://github.com/openSUSE/release-notes-openSUSE.git work, edit, ... git pull # get newest changes from the repository git checkout # see which files are changed git add ... # select modified files for commit, use TAB git commit -m "Some description" git push origin master # send Your changes Is it really too complicated over the old SVN? Note it is common practice to abandon SVN in favor of Git. openSUSE is not reinventing wheel... It took me one afternoon to learn basic usage when I needed to...
Yes, no problem with that. The problem is the organization. Translators are not developers, we work differently and we have different skill sets. We can not start creating repositories. We simply need to be told of a single directory (or two or three) to use. With proper separation for the supported releases. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlY6Jh4ACgkQtTMYHG2NR9VpMQCfQ4Is725SGUzCFjAJE4TYtbiE QPcAn2z2z/zogIP8U4/RSr6/4qJ8NQKI =KDuT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Dne St 4. listopadu 2015 16:37:03, Carlos E. R. napsal(a):
On 2015-11-04 16:15, Vojtěch Zeisek wrote:
Which are the repositories corresponding to the current svn yast and lcn? A single directory or two, please, I can't go searching for files all over the place.
E.g. https://l10n.opensuse.org/projects/release-notes-opensuse/ says https://github.com/openSUSE/release-notes-openSUSE ...
But that is a single file. lcn contains 43, yast 96. And there are 13.1, 13.2, TW, Leap versions. How do I find all of them?
In this case, yes. I haven't checked, but aren't lcn files in one repository? If not, it would be our feature request to have sort of „metarepository“ for translations. I went only through projects already presented in https://l10n.opensuse.org/ and as far as I understand, except solving bugs etc, it should be enough to work with trunk, or not? Yes, let's not re-open here the documentation topic.
If You don't have it, You can ask maintainer to get it. Otherwise You can fork the repository https://help.github.com/articles/fork-a-repo and clone it
Sorry, I don't understand any of that.
OK, basically, there is no difference in purpose and basic logic of SVN and Git. If You wish to edit someone's else repository, You must make Your own copy (=fork it), modify it and then ask owner of original repository to include Your changes (=create pull request). Have You tried to learn Git? If You refuse Git, what is wrong with download/upload po files over web? If any possibility fits Your needs, then, I'm sorry, I'm unable to help You...
The problem is how you organize the translation files. They have to be all in a single directory, a single repo.
Not necessary, but of course convenient. Well, if someone (from SUSE) would be so kind to write simple BASH script to check for all the repositories, it would also be enough. I don't feel enough oriented in the structure yet...
We only needed two commands for svn: up, and commit. Nothing else. Browse to the directory holding all the lcn po files, and do "svn commit --message "arbitrary comment". That's all. Copypaste a command.
Less features, less commands... It is like to complain about changes when moving from Windows Notepad to real text editor, at least KWrite. For some purposes Notepad is enough. But in some point it is not anymore. Basic usage is also more or less same, although the latter has more possibilities what to do... So what is the big difference between SVN and Git?
I'm too old a dog to start learning new tricks on my own.
Everyone is becoming lazier, me too. :-) This wasn't big challenge, thought.
# Initial clone of the repository git clone https://github.com/openSUSE/release-notes-openSUSE.git work, edit, ... git pull # get newest changes from the repository git checkout # see which files are changed git add ... # select modified files for commit, use TAB git commit -m "Some description" git push origin master # send Your changes Is it really too complicated over the old SVN? Note it is common practice to abandon SVN in favor of Git. openSUSE is not reinventing wheel... It took me one afternoon to learn basic usage when I needed to...
Yes, no problem with that. The problem is the organization. Translators are not developers, we work differently and we have different skill sets. We can not start creating repositories. We simply need to be told of a single directory (or two or three) to use. With proper separation for the supported releases.
Yes, I also rather spend time by doing the work than by figuring how to do it... I don't wont argue on that point. Timing was not very lucky, but I see progress so I hope we will have needed information ASAP... Sincerely, V. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
Hello, Now release-notes are translated in French in Weblate, thanks to Weblate team reactivity :) But there are three issues: 1) It looks like English version has been updated (https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/, see 4.1 about CUPS) but new strings doesn't appear in fr.po. I see that other languages have them, so I guess there is something wrong with fr. How can I update the po file? Shouldn't be automatic, or at least with a message telling that the po needs to be updated because it differs from the pot file? 2) Release Notes are not available in YaST yet, nor at https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/RELEASE-NOT..., what can I do to trigger the publication? 3) Not directly related to translation but I noticed that the release notes were mentioning firewall issue when installing Leap 42.1 with the LiveCD. But as far as I know there is no LiveCD for Leap 42.1 yet. Could you help me with these issues please? Regards, Antoine -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Hello, Somebody did a merge (thanks!) and now I see the new strings in fr.po. References to the LiveCD have been removed as well so issues 1) and 3) are solved – though I still don't know why the merge isn't automatic. I have translated the new strings so now fr.po is 100% translated. Only 2) remains ;) Le 08/11/2015 12:37, Antoine Belvire a écrit :
2) Release Notes are not available in YaST yet, nor at https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/RELEASE-NOT..., what can I do to trigger the publication?
Regards, Antoine -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
participants (5)
-
Antoine Belvire -
Carlos E. R. -
Freek de Kruijf -
Tomáš Chvátal -
Vojtěch Zeisek