-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-07-30 17:19, Karl Ove Hufthammer wrote:
Carlos E. R. wrote:
Well, lokalize, being a KDE program, is very well suited to the directory structure and procedure organization used by KDE, but apparently not so well to ours.
Ah, that’s true. I’ve been wondering why openSUSE has such a strange directory (and file naming) structure for translations. I would have guessed it was because it made things easier for the developers, but obviously it does not.
I don't know about devs, I only know about translators ;-)
Personally, for openSUSE translations, I use the the Pology summit workflow detailed at http://pology.nedohodnik.net/doc/user/en_US/ch-summit.html (but with a custom config file the Pology creator helped me with, since the openSUSE doesn’t use either of the two standard directory structures). The result is a standard directory structure for translation files (.po and .pot) files, just like for KDE, which means I can use the project viewer in Lokalize:
├── templates │ ├── activedoc │ │ ├── ad-blocks.pot │ │ ├── ad-contact.pot │ │ ├── ad-fields.pot │ │ ├── … └── langcode ├── activedoc │ ├── ad-blocks.po │ ├── ad-contact.po │ ├── ad-fields.po │ │ ├── …
It is similar. This is what I get on CVS (svn? I forget) for the 13.2 branch: |-- openSUSE-13_2-Branch | |-- lcn | | |-- 50-etc | | | |-- VERSION | | | |-- html-stats.sh | | | |-- i18n_branches.txt ... | | |-- 50-html | | | |-- MAINTAINERS | | | |-- Makefile.am | | | |-- help-boot | | | | |-- navi.html | | | | |-- opt.html | | | | |-- opt::help.html ... | | | |-- help-boot.html | | | |-- help-install | | | | |-- main.html | | | | |-- main::bits.html | | | | |-- main::driverupdate.html | | | | |-- main::failsafe.html | | | | |-- main::firmware.html ... | | | |-- html-help-install.pot | | | `-- projects.mk | | |-- 50-memory | | | `-- memory.es.po | | |-- 50-pot --> templates? | | | |-- MAINTAINERS | | | |-- RELEASE-NOTES-openSUSE.pot | | | |-- SUSEgreeter.pot | | | |-- apparmor-parser.pot | | | |-- apparmor-utils.pot | | | |-- apparmorapplet.pot | | | |-- bootloader.pot | | | |-- command-not-found.pot ... | | |-- 50-tools | | | |-- checked-fix-plural.awk | | | |-- checked.awk | | | |-- concat-html.sh | | | |-- desktop-files-extract.pl | | | |-- desktop-files-list.sh | | | |-- desktop-files-pull.sh | | | |-- desktop-files-split.sh | | | |-- desktop-files-update.sh | | | |-- desktop-files-update.urls | | | |-- fix-init.sh ... | | `-- es --> langcode? | | |-- Makefile.svn | | `-- po | | |-- RELEASE-NOTES-openSUSE.es.po | | |-- SUSEgreeter.es.po | | |-- apparmor-parser.es.po | | |-- apparmor-utils.es.po | | |-- apparmorapplet.es.po | | |-- bootloader.es.po | | |-- command-not-found.es.po And another for "packages" and another for "yast". I marked above what I think are the equivalent sections.
We do have an svn server, but few translators use it. Many use an intermediate platform, vertaal, that is used mostly for organization (who translates what and when). It is this platform which emails the translator assigned to a file that it needs work. The details of this depends on each language team.
OK. I thought most translators still used SVN. Yes, using a Web platform certainly makes thing less efficient. (But if people prefer it, who am I to argue, as long as I can still use SVN.)
I use both. I use svn to do the actual pulling and sending of files. But first, I use vertaal to locate a file that is asigned to me or to nobody, and I mark that I'm working on it, so that nobody else modifies it. Then I work directly on my copy of the file on my svn copy; but others instead pull the .po file using vertaal web interface. When finished, I just commit it, and others send it in a gz via same platform. This platform does some checking, and if passes, will commit the file in a cronjob sometime in the day. If not pass, will tell immediately the translator. Vertaal can also do other things, like apply changes in the pot to the po file. It's a flexible platform. It acts as intermediary to svn, yes, but most importantly, it controls assignation of files. This eases a lot the job of coordinators. Depending on the team, a translator can simply pick himself a free file. What it does not do is present some type of editor to do the actual translation job. That does exist, I think ubuntu does it that way.
The devs are on a different server, git, I think. I guess there is not a single directory that has all the catalogs, but probably many, which is why they have to be collected by people for submission. This is a part of the process I don't see, so I don't know how exactly it works.
OK. In KDE, all applications *used to be* on a single SVN server. Now, they’re scattered across different (mostly Git) servers. But I believe they are automatically fetched when building (or perhaps only when packaging) the applications.
That's the part that needs help currently.
This is not unique to openSUSE. The Translation Project is also convoluted: translators are told of pending work by email, retrieve the file via http download, then submit back via email.
There is also a script one can use for this. But I agree that The Translation Project translations process could be more streamlined!
The only actual problem I find with it is that although they send emails to translators to tell them of work pending, I rarely notice them, in the mass of emails from the robot.
On other projects I participate (xine), I have to download the sources from packman, translate, then upload to a paste site that I can find (google drive, for instance), then post a link in an email to their mail list so that the devs them pick it.
That sounds terrible!
It is. The issue is that their mail list server has a size limit for attachment, or a block, so that I simply can not attach the translations in the mail. Ah, I have to pull the pot from packman because their build tree doesn't have the pot files readily built. I don't remember the exact problem, I just found it easier to pull from packman. They don't do releases, I never know when there is work to do.
Luckily, for most applications I have translated, I have been given commit access to SVN. Some require patches attached to bug trackers or sent to e- mail lists. These are also the projects with the fewest number of (updated) translations …
Some are impossible: have a look at Alpine: last time I looked, the help texts were in the .pot. But each line a different string! We need a paragraph per string, more or less. Entire sentences at least.
Convolution seems to be the norm; only some projects, like KDE, have it very well organized :-)
Yes, we’re lucky in KDE. :)
Yes, you are :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlW6YP0ACgkQtTMYHG2NR9XG6ACgi/b3GrVBFi/G681qtSJ5FLLK RrcAn2Ow5JU23E4IfK26ZES3AXxYeKI7 =jZsP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org