[opensuse-translation] Leap
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, Are we getting a "Leap" branch? How do we handle it? - -- Cheers / Saludos, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWcpOoACgkQja8UbcUWM1yXIQD/eMXhitxjJSQGbPWvRDfbv2x+ wK4Wy14D8rxpu/+C/GgBAJkMBz9xLeM66p6LIAqQWXDg0gt6g7sTXPX30pRnhSuS =tIJ9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Onsdag den 8. juli 2015 06:19:42 skrev Carlos E. R.:
Are we getting a "Leap" branch? How do we handle it?
I guess we should be looking for a SLE12sp1 branch, if we want to translate "Leap". Though of course "Leap" will hopefully have significantly more and newer desktop files than SLE12. And there's a big questionmark about what to do for the languages which are translated for SLE by paid translators. Afaik DA is not supported in SLE anymore, so I don't need to worry about that. -- 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: SHA256 On 2015-07-08 12:46, Martin Schlander wrote:
Onsdag den 8. juli 2015 06:19:42 skrev Carlos E. R.:
Are we getting a "Leap" branch? How do we handle it?
I guess we should be looking for a SLE12sp1 branch, if we want to translate "Leap".
Derived from it, yes, but in its own branch.
Though of course "Leap" will hopefully have significantly more and newer desktop files than SLE12. And there's a big questionmark about what to do for the languages which are translated for SLE by paid translators.
Afaik DA is not supported in SLE anymore, so I don't need to worry about that.
Spanish is, though. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWdAuoACgkQja8UbcUWM1yUpAD9G1Lbb+9AiIqS3E2d+D9CYN3u hcXFssxfZgqi9LAERD8A/R3zufePaBISHEpjG78jf1z9QmNt57fFcZZi7hzKWBHW =hy2e -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Den 08. juli 2015 06:19, Carlos E. R. skreiv:
Are we getting a "Leap" branch? How do we handle it?
I know nothing about a ‘Leap’ branch, but if openSUSE is beginning to have several branches which must be translated simultaneous, I recommend moving to a ‘Pology summit’ framework, like some translation teams for KDE do: http://pology.nedohodnik.net/doc/user/en_US/ch-summit.html https://techbase.kde.org/Localization/Workflows/PO_Summit#Software_Branches_... Basically, the translator’s work with .po files called summit .po files, which are ‘supercollections’ of the corresponding .po files in the various branches. If a string exists in several branches (as most strings do), you only have to translate it *once*. If a string is modified in one branch but not others, the two similar strings are placed (as separate strings) after one another in the summit .po file, so that that it’s easy to compare them and see what the difference is, and to make the appropriate changes. (In many cases one would use the same translation for both strings. This is the case when translation done for a stable and a development branch, where the stable branch is in ‘string freeze’, so that no changes to the original (English) string is allowed. If the original string is badly worded (or contains a spelling mistake), this can only be fixed in the development branch. However, the translation should be based on the improved string in both cases.) The summit workflow handles .po files which are split (e.g. an application is split into a library and a UI file, but only in one branch), merged or renamed. I have done some tests on the openSUSE branches, and it seems to work fine. (The config file needs some changes from the one listed on the Pology Web site, to deal with the directory structure and file naming scheme used by openSUSE.) The individual teams can decide themselves if they want to use the summit workflow, i.e., not all teams need to use it. -- Karl Ove Hufthammer -- 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: SHA256 On 2015-07-12 12:22, Karl Ove Hufthammer wrote:
Den 08. juli 2015 06:19, Carlos E. R. skreiv:
Are we getting a "Leap" branch? How do we handle it?
I know nothing about a ‘Leap’ branch, but if openSUSE is beginning to have several branches which must be translated simultaneous, I recommend moving to a ‘Pology summit’ framework, like some translation teams for KDE do:
http://pology.nedohodnik.net/doc/user/en_US/ch-summit.html https://techbase.kde.org/Localization/Workflows/PO_Summit#Software_Branches_...
Interesting. (lokalize
can handle several branches, too, somehow; not so completely) Although... we only translate the stable branch, factory is mostly ignored. For two reasons: strings can change a lot in (non frozen) factory, and we need some one to get the strings (pot files) from the developers, and the translated strings back to them. Pology looks complicated to me. It would mean some one doing whatever scripts or processes need to be done. Karl can't, and most of the translators can't, for different reasons. We need more admin types. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWiUSoACgkQja8UbcUWM1yWyAD+K+ysdhTzpz86sDhhi7dmOCas 1uz6Jny6mmwWrSrmzswA/jEAuCv0aJuG3iHTNmNGiRwx3AWGrUORDgbH+QgZaJMp =0AwF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Den 12. juli 2015 13:36, Carlos E. R. skreiv:
Pology looks complicated to me. It would mean some one doing whatever scripts or processes need to be done. Karl can't, and most of the translators can't, for different reasons. We need more admin types.
*When* the system set up is set up, it’s *extremely* easy to use. You just run a single command to update the summit .po files with the latest changes from the POT files. And then you run a single command to copy the strings from the summit .po files to the various branch po files. Basically, the translator (or anyone) just needs to run: update-summit … translate the PO files … update-po (‘update-summit’ and ‘update-po’ are just example names for the scripts) -- Karl Ove Hufthammer -- 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: SHA256 On 2015-07-12 14:33, Karl Ove Hufthammer wrote:
Den 12. juli 2015 13:36, Carlos E. R. skreiv:
*When* the system set up is set up, it’s *extremely* easy to use. You just run a single command to update the summit .po files with the latest changes from the POT files. And then you run a single command to copy the strings from the summit .po files to the various branch po files. Basically, the translator (or anyone) just needs to run:
update-summit … translate the PO files … update-po
(‘update-summit’ and ‘update-po’ are just example names for the scripts)
Yes, but somebody has to set it up... Then we have to adjust our procedures. Probably adapt vertaal, too. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWiX5MACgkQja8UbcUWM1xyVwD+Mqz+bDogVgXljbMRhKgQGgJC kHoSyucJiOedlyNg3GYA/0Frm4YUkv57C+sWCub2j2X7AVProD9yFhY+XWkdPrno =u6Ko -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Den 12. juli 2015 14:37, Carlos E. R. skreiv:
(‘update-summit’ and ‘update-po’ are just example names for the scripts)
Yes, but somebody has to set it up...
Then we have to adjust our procedures. Probably adapt vertaal, too.
Sure. And there’s no problem that people are *not* using it. But if someone *wants* to use it, to make their translators’ lives easier, it’s an option. My translation team (currently a one-man team, and not a very active one at that) currently use the Pology summit framework when translating (but I am only keeping the summit .po(t) files locally, not in openSUSE’s SVN repository), and would be happy to assist any translation teams that wish to use it in setting it up. -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
participants (3)
-
Carlos E. R. -
Karl Ove Hufthammer -
Martin Schlander