Re: Missing file in libxklavier CVS

[Jody Goldberg <jody gnome org>]

On Mon, Nov 10, 2003 at 09:06:30AM +0000, Sergey V. Oudaltsov wrote:
> 
> > no upgrades sounds fine.
> > no translations is not a good idea.
> Well, I intentionally said: no translations. Even the xfree86.xml itself
> (head version, actually used in XFree) it not properly translated. And I
> surely would like it to be translated (and for this reason I am ready to
> move it from sf to gnome CVS). But this "fallback" file 

My thought was that because intltool nicely splits the translations
out into po files then remerges things it would be very easy to
generate patches that could be fed upstream.
 
> do you really
> think it would make sense to put a lot of GTP efforts into the file
> which people should virtually never see (and the more people move to
> XFree 4.3 - the less people will notice this file)? I'm afraid this
> would be real waste of such a valuable resource as GTP.

These are user visible strings in an area that intl users are fairly
likely to look.  Proper translation is a very high priority.

> So, what we could do - move xfree86.xml module into GNOME CVS - so at
> least the version in XFree would be properly translated (and the faster
> we do it - the better - the version 4.4 is going to be released soon).

We could put the actual upstream version in GNOME CVS.  Fantastic.
That would make would ideal from a translation perspective.

> Surely, this is only possible if GTP does not mind helping XFree. And I
> would keep the fallback version untranslated. Just for the simplicity
> sake. Sure, I could create special branch for the version related to
> XFree 4.2 - so translators could work with it etc. But this would return
> me to the point where I don't want to be - _maintaining_ this file in
> libxklavier. Which I don't want. I just want to put it there - and
> forget:)

Why not keep the fallback in sync, even if it is only updating it at
release time as you do now ?