[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: Different formulas for plurals in Qt and KDE
From: Vít Pelčák <vit () pelcak ! org>
Date: 2014-05-15 6:16:50
Message-ID: CACq8bh5=3_LausN=4qx-GrZh4c_RE+MG_d3sv+mzPH3GJ1v=XQ () mail ! gmail ! com
[Download RAW message or body]
I agree with Alexander. Just please document this and provide some examples
for languages with multiple plural forms.
Dne 15. 5. 2014 8:09 "Alexander Potashev" <aspotashev@gmail.com> napsal(a):
> 2014-04-11 1:49 GMT+04:00 Chusslove Illich <caslav.ilic@gmx.net>:
> > For branch POs the issue is academic though, as Albert says, since there
> is
> > no reason for there to be a PO file containing both types of messages (a
> > framework uses either Ki18n or Qt, never both). Well, except for Scripty
> > forcing the plural form header on all POs (I'd simply kill that).
>
> Hi Chusslove,
>
> Thanks for all the useful info! As I have understood we have two options:
> 1. Have KI18n-style plurals in all translation files under l10n-kf5
> and convert plurals just before running lconvert for *_qt.po files.
> This will required changes to
> extra-cmake-modules/modules/ECMCreateQmFromPoFiles.cmake.
> Pro: translators are not confused with two different plural formulas.
> Cons: msgstr[3] in *_qt.po need translations which will be
> truncated at lconvert stage and never be used.
> 2. Have Qt-style plurals in *_qt.po and KI18n-style plurals in other
> .po files. This can be done as easy as changing plural headers of
> _qt.po files in SVN.
> Pro: translators see in .po files what exactly will be in the
> resulting binary files (.qm and .mo).
> Cons: it takes some brainpower from translators to remember what
> each msgstr[i] stands for in two plural formulas.
>
> I suggest we use the second option - to have different plural headers
> in different files. The reason I think of as most impotant is full
> translator's control of what will be in the resulting .qm and .mo
> files.
>
> == Forcing plural headers in Scripty ==
>
> Now will talk about Scripty forcing plural form header on all POs. It
> does not do that currently since scripts/check_po_files can force
> plural header only when a kdelibs4.po exists, and it does not exist
> anymore in l10n-kf5.
>
> But still I would like to have plural header adjustment done by
> Scripty. Many translators don't pay attention to plural headers and
> therefore don't change it before committing files to SVN or forget to
> do that (including me) or just rely on Scripty.
>
> I'm going to modify l10n-kf5/scripts/check_po_files (will make a
> patch) in a way that it grabs the plural header
> 1. from kcoreaddons5_qt.po for all *_qt.po files,
> 2. from ki18n5.po for all other .po files.
>
> Does this plan sound good?
>
> --
> Alexander Potashev
>
[Attachment #3 (text/html)]
<p dir="ltr">I agree with Alexander. Just please document this and provide some \
examples for languages with multiple plural forms. </p> <div class="gmail_quote">Dne \
15. 5. 2014 8:09 "Alexander Potashev" <<a \
href="mailto:aspotashev@gmail.com">aspotashev@gmail.com</a>> napsal(a):<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> 2014-04-11 1:49 GMT+04:00 \
Chusslove Illich <<a \
href="mailto:caslav.ilic@gmx.net">caslav.ilic@gmx.net</a>>:<br> > For branch \
POs the issue is academic though, as Albert says, since there is<br> > no reason \
for there to be a PO file containing both types of messages (a<br> > framework \
uses either Ki18n or Qt, never both). Well, except for Scripty<br> > forcing the \
plural form header on all POs (I'd simply kill that).<br> <br>
Hi Chusslove,<br>
<br>
Thanks for all the useful info! As I have understood we have two options:<br>
1. Have KI18n-style plurals in all translation files under l10n-kf5<br>
and convert plurals just before running lconvert for *_qt.po files.<br>
This will required changes to<br>
extra-cmake-modules/modules/ECMCreateQmFromPoFiles.cmake.<br>
Pro: translators are not confused with two different plural formulas.<br>
Cons: msgstr[3] in *_qt.po need translations which will be<br>
truncated at lconvert stage and never be used.<br>
2. Have Qt-style plurals in *_qt.po and KI18n-style plurals in other<br>
.po files. This can be done as easy as changing plural headers of<br>
_qt.po files in SVN.<br>
Pro: translators see in .po files what exactly will be in the<br>
resulting binary files (.qm and .mo).<br>
Cons: it takes some brainpower from translators to remember what<br>
each msgstr[i] stands for in two plural formulas.<br>
<br>
I suggest we use the second option - to have different plural headers<br>
in different files. The reason I think of as most impotant is full<br>
translator's control of what will be in the resulting .qm and .mo<br>
files.<br>
<br>
== Forcing plural headers in Scripty ==<br>
<br>
Now will talk about Scripty forcing plural form header on all POs. It<br>
does not do that currently since scripts/check_po_files can force<br>
plural header only when a kdelibs4.po exists, and it does not exist<br>
anymore in l10n-kf5.<br>
<br>
But still I would like to have plural header adjustment done by<br>
Scripty. Many translators don't pay attention to plural headers and<br>
therefore don't change it before committing files to SVN or forget to<br>
do that (including me) or just rely on Scripty.<br>
<br>
I'm going to modify l10n-kf5/scripts/check_po_files (will make a<br>
patch) in a way that it grabs the plural header<br>
1. from kcoreaddons5_qt.po for all *_qt.po files,<br>
2. from ki18n5.po for all other .po files.<br>
<br>
Does this plan sound good?<br>
<br>
--<br>
Alexander Potashev<br>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic