[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:       Albert Astals Cid <aacid () kde ! org>
Date:       2014-04-08 22:16:52
Message-ID: 2624345.bD9uAB8XQz () xps
[Download RAW message or body]

El Dimarts, 8 d'abril de 2014, a les 12:26:47, Alexander Potashev va escriure:
> В письме от 8 апреля 2014 07:52:08 пользователь Yuri \
> Chornoivan написал:
> > Guessing from Trojita ans Kst translations, lconvert just skip the whole
> > translation and left the messages untranslated.
> > 
> > The error message is:
> > 
> > "Removed plural forms as the target language has less forms.
> > If this sounds wrong, possibly the target language is not set or
> > recognized."
> > 
> > > 2. In the case there is a problem, what options may there be to
> > > 
> > > overcome it?
> > 
> > It thought that some addition of sed magic to lconvert wrapper may help.
> 
> Good morning Yuri,
> 
> Thanks for the clarification!
> 
> By having plans for changes in lconvert wrapper you make an assumption that
> one can clearly say what i18n system a .po file uses. But it can use both,
> kcoreaddons is an example.
> 
> Mixing i18n() in tr() in one .po sounds wrong conceptually, not only at the
> level of our problems with plurals.

This should not happen and if it's happening it should be fixed.

At most it's happening in Summit, Chusslove is the guy that cares about it.

Cheers,
  Albert

> 
> Then, in the case we start using separate translation catalogs for KF's and
> Qt's i18n system-based messages, like kcoreaddons.po and kcoreaddons_qt.po,
> we can also modify scripty in the way that it forces different plural
> formulas on different files - say, 3-form plurals for files with "_qt.po"
> in the filename and 4-form plurals for the others.
> 
> However, if such a sed-like tool you mentioned will be necessary, I
> volunteer to write a C program doing manipulations with plurals using the
> official libgettextpo library. It would be faster, more stable and easier
> to write than sed, if you meant that standard tool literally. The also was
> a Pology sieve written by Chusslove, but it's too slow for daily use.


[prev in list] [next in list] [prev in thread] [next in thread]