[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: using gettext for .desktop translations
From: Jonathan Riddell <jriddell () ubuntu ! com>
Date: 2009-12-12 1:36:31
Message-ID: 20091212013630.GI32356 () muse ! 19inch ! net
[Download RAW message or body]
On Sat, Dec 12, 2009 at 01:30:13AM +0100, Chusslove Illich wrote:
> > [: Jonathan Riddell :]
> > There was a posting about this to the xdg list once upon a time but \
> > since the maintainers of the .desktop spec have long since fallen off \
> > the internet it didn't go anywhere. So the process has to start here.
>
> This would be great. But it should produce an update to .desktop spec
> document *before* we change anything in translation system on KDE's side. \
> So that when someone comes in complaining about broken .desktop files
> translation-wise, he can be pointed to the updated spec.
>
> Do you already have a proposal (given experience in Ubuntu)?
The original proposal is in the attachment at
http://lists.freedesktop.org/archives/xdg/2005-June/005344.html
Our patch is at
http://bazaar.launchpad.net/%7Ekubuntu-members/kdelibs/ubuntu/annotate/head%3A/debian/patches/kubuntu_56_langpacks_desktop_files.diff
Here's SuSE's patch
http://people.canonical.com/~jriddell/desktop-translations.diff
This is the discussion over there
https://bugzilla.gnome.org/show_bug.cgi?id=569829
> You probably haven't deliberated about disambiguation contexts so far, \
> and neither have I in this sense (my internal solution in KDE was a \
> comment in
> .desktop file, but this is not acceptable for dynamic translation). How
> about having a *-Context counterpart to every translatable field (as they
> are currently listed in the spec)?
I don't believe we have. Could the name of the .desktop file be used
as a context?
> Another thing is that I don't see how to define this without linking the
> .desktop spec to a particular runtime translation system, here Gettext. \
> To me this is just fine because I hold Gettext to be the superior \
> solution, but I expect it not to be fine with everyone. E.g. a pure Qt \
> application, using Qt's native runtime translation system, would have to \
> provide and install PO files merely for the sake of its .desktop files.
Pure Qt apps already have to use a second translation system merely
for the sake of .desktop files. At least we can stop KDE from having
to do so.
Jonathan
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic