[Kbabel] Full Gettext support in KBabel

[Stanislav Visnovsky]

Dňa Štvrtok 20 Október 2005 20:00 Nicolas Goutte napísal:
> On Thursday 20 October 2005 15:04, Stanislav Visnovsky wrote:
> > Dňa Štvrtok 20 Október 2005 14:43 Nicolas Goutte napísal:
> > > On Thursday 20 October 2005 13:24, Chusslove Illich wrote:
> > > > Hi,
> > > >
> > > >
> > > > What would it take for KBabel to fully support Gettext PO features?
> > >
> > > Well, it is quite (too) late now, as KDE 3.5 is in message freeze.
> > > Therefore KBabel cannot be changed where it would matter.
> > >
> > > (KDE 4 will not be translated with its own KBabel but with the KBabel
> > > of KDE 3.5. We had that experience already with KDE2 to KDE3 switch.)
> > >
> > > > Since
> > > > few days ago, Gettext has full support for what we need in KDE:
> > > > formal contexts (new msgctxt field) and xgettext extractor updated
> > > > accordingly (will also work for overloaded ordinary, context and
> > > > plural calls). So I think there is no reason to fiddle with custom
> > > > stuff for KDE 4, providing that all tools are updated to handle
> > > > standard Gettext POs, KBabel being primary.
> > >
> > > Well, it also depends how fast such a Gettext is officially released,
> > > so that it can be really used.
> > >
> > > (Do not forget! KBabel is a tool for translators. That are not people
> > > that can jump on every new software tool, either because they do not
> > > have the knowledge how to compile or because downloading is
> > > cost-intensive (not to say prohibitive). You can look at how many
> > > people we have lost with the change from CVS to SVN.)
> > >
> > > > I've browsed a bit through KBabel's Gettext import/export code, and
> > > > couldn't find anything explicitly left to be done, but I've been said
> > > > that
> > >
> > > msgid_plural and msgstr_plural are not correctly handled
> > > (only loaded as far as I understand the code).
> >
> > They are fully supported. Try one, for example gettext.po ;-)
>
> In that case, I probably misunderstood something that you have written. :-(
>
> So I am going to revert the KDE 3.5 feature plan on this point.
>
> So we would need to introduce the new context in a (rather) transparent
> way. (Not sure if somebpody can do that until KDE 3.5).

We could silently ignore it for now - just to make sure we can open the files.
Adapting the code to properly handle this would be tricky - we could probably 
map the new PO syntax to the old KDE context syntax - that should work

Stano