Mailinglist Archive: opensuse-translation (81 mails)

< Previous Next >
Re: [opensuse-translation] How to translate patterns in YaST software manager?
  • From: Alexander Melentev <minton@xxxxxxxxxxxx>
  • Date: Fri, 20 Nov 2015 17:49:29 +0300
  • Message-id: <CAMe-c7VH1t2Ed_hB5VLoC9h04hGbdTt_Q1sns1VBCRtz+=z1Ow@mail.gmail.com>
2015-11-17 23:36 GMT+03:00 Karl Ove Hufthammer <karl@xxxxxxxxxx>:
Den 17. nov. 2015 05:07, Alexander Melentev skreiv:

If we can split how we want it to split, then I wouldn't take media in
account anymore. Leap doesn't have CDs and Tumbleweed has no physical
media at all, so it will be much more logical and convinient to just
get the packages descriptions from the repo and split them by src
package name into pieces of reasonable size.


Why split them at all? Just have one ‘packages.pot’ file. The translation
software we use (Lokalize and poEdit) have no problems handling large
translation files (e.g. 50,000 strings).
Not everything that is possible for software is possible for a human
being. For instance, 200 messages is my personal maximum for one time
translation, so files bigger than 2000 make me sad, cause I cannot
make reasonable progress in decent time.
Also I can hardly imagine how to split the translations tasks between
several people while having one huge file. In good old days 15 people
translated to Russian and I even saw 50% overall progress (well,
before the bug with messages generation was fixed and a huge bunch of
new messages appeared).


(Having separate kde.pot and gnome.pot would be OK, though, i.e. separate
files for truly separate subsystems. But arbitrarily splitting files will
cause more problems than they help, e.g. where a string may move from file
to file in different releases.)
kde.pot and gnome.pot don't refer to the software, but for the
non-common packages of corresponding LiveCDs (common packages are in
base1 and base2). Since LiveCDs are not available for both
distributions in question, as I mentioned earlier, I see no practical
sense to split those out. Right now my intention is to split out
several meaningful package groups to ease the distinction of what is
inside and what to translate. For example, leave patterns in a
separate file for quicker translation. Or have perl*, php*, python*
and texlive* split out so that their translations can be postponed due
to the specifics of target audience. The same is true for libraries
(lib* not including libreoffice).
I am open to suggestions about other package groups that can be split
out to ease the translations.

Old splitting was done by number of packages, so string movement was
possible at every update/merge. Right now the splitting is by name, so
from-fi-to-file transitions are possible only on package rename, which
doesn't happen too often.
--
Regards, Minton.
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-translation+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups