From kde-i18n-doc Fri Mar 28 00:21:33 2008 From: "Nicolas Ternisien" Date: Fri, 28 Mar 2008 00:21:33 +0000 To: kde-i18n-doc Subject: Re: desktop_playground-ioslaves.po with translatable Query keyword Message-Id: X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=120666373200583 MIME-Version: 1 Content-Type: multipart/mixed; boundary="------=_Part_17071_15823737.1206663693495" ------=_Part_17071_15823737.1206663693495 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Yes, you're right about crazy translation which could also totally broke an application. So, maybe we could add a QueryContext keyword, that scripty will add as a "msgctxt" in PO file ? On Thu, Mar 27, 2008 at 10:15 PM, Albert Astals Cid wrote: > A Dimarts 25 Mar=E7 2008, Nicolas Ternisien va escriure: > > Alright, but is there any reason, apart wp keyword, to make a Query > > translatable ? My problem is that a Query is a technical information, > not a > > translatable string, and most l10n teams does not know what to do with > > this. The other problem is that a bad translation can prevent the apps > to > > work... > > > > So, a workaround could be the adding of a context string to explain and > > describe Query keyword in KBabel/Lokalize/Whatever, the other solution > > could be the externalization of wikipedia localized URL, to make it > > translatable, and the Query untranslatable. > > So having a look at the desktop file specification at > > http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-la= test.html > you can see that Query is not part of the standard, so it does not have a > defined meaning, so someone is using in KDE as something that needs to be > translated, as said, if you want something not translatable you can alway= s > use X-KDE-KWest-Query instead of Query > > Besides translators can ALWAYS screw up things, just imagine they > translate "Do you want to remove this file" as "Do you want to keep this > file" and voila, all files removed when the user wanted otherwise. > > Albert > > > > > Example for Bulgarian translation : > > > > > http://l10n.kde.org/dictionary/compare-translations.php?package=3Dplaygro= und- > >ioslaves&filename=3Ddesktop_playground- > ioslaves.po&compare=3Drekwest%3A%2Fbeagle > >%3Fquery%3D\\\\{%40} > > > > On Tue, Mar 25, 2008 at 8:07 PM, Albert Astals Cid > wrote: > > > A Dimarts 25 Mar=E7 2008, Nicolas Ternisien va escriure: > > > > Hi, > > > > > > > > I would like to know how > > > > > > How =3D as anything else that we translate, editing the suitable .po > file > > > > > > > and why the Query value could be translated, > > > > > > Why =3D because i don't want the wp: konqueror Query to go to > > > en.wikipedia.org > > > but to ca.wikipedia.org > > > > > > > and if this could be prevented in those files : > > > > > > > http://websvn.kde.org/trunk/playground/ioslaves/kwest/kio_kwest/kclucene_ > > >an > > > > > > >y.desktop?view=3Dmarkup > > > > > > > http://websvn.kde.org/trunk/playground/ioslaves/kwest/kio_kwest/kclucene_ > > >co > > > > > > >ntent.desktop?view=3Dmarkup > > > > > > > http://websvn.kde.org/trunk/playground/ioslaves/kwest/kio_kwest/beagle_de > > >fa > > > > > > >ult.desktop?view=3Dmarkup > > > > > > You can always use a keyword that is not translated like > > > X-KDE-KWest-Query. > > > > > > P.S: Translatable entries are Name, Comment, Language, Keywords, > About, > > > Description, GenericName, Query, ExtraNames and X-KDE-Submenu > > > > > > Albert > > > > > > > Thanks > > > > > > > > Nicolas Ternisien > > > ------=_Part_17071_15823737.1206663693495 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Yes, you're right about crazy translation which could also totally brok= e an application.

So, maybe we could add a QueryContext keyword, tha= t scripty will add as a "msgctxt" in PO file ?


On Thu, Mar 27, 2008 at 10:15 PM, Albert Astals Cid <aacid@kde.org> wrote:
A Dimarts 25 Mar=E7 2008, Nicolas Ternisien va escriu= re:
> Alright, but is there any reason, apart wp= keyword, to make a Query
> translatable ? My problem is that a Query is a technical information, = not a
> translatable string, and most l10n teams does not know what to do with=
> this. The other problem is that a bad translation can prevent the apps= to
> work...
>
> So, a workaround could be the adding of a context string to explain an= d
> describe Query keyword in KBabel/Lokalize/Whatever, the other solution=
> could be the externalization of wikipedia localized URL, to make it > translatable, and the Query untranslatable.

So having a look at the desktop file specification at
http://standards.freedesktop.org/desk= top-entry-spec/desktop-entry-spec-latest.html
you can see that Query is not part of the standard, so it does not have a defined meaning, so someone is using in KDE as something that needs to be translated, as said, if you want something not translatable you can always<= br> use X-KDE-KWest-Query instead of Query

Besides translators can ALWAYS screw up things, just imagine they
translate "Do you want to remove this file" as "Do you want = to keep this
file" and voila, all files removed when the user wanted otherwise.

Albert

>
> Example for Bulgarian translation :
>
> http://l10n.kde.org/dictionary/compar= e-translations.php?package=3Dplayground-
>ioslaves&filename=3Ddesktop_playground-ioslaves.po&compare=3Dre= kwest%3A%2Fbeagle
>%3Fquery%3D\\\\{%40}
>
> On Tue, Mar 25, 2008 at 8:07 PM, Albert Astals Cid <aacid@kde.org> wrote:
> > A Dimarts 25 Mar=E7 2008, Nicolas Ternisien va escriure:
> > > Hi,
> > >
> > > I would like to know how
> >
> > How =3D as anything else that we translate, editing the suitable = .po file
> >
> > > and why the Query value could be translated,
> >
> > Why =3D because i don't want the wp: konqueror Query to go to=
> > en.wikipedi= a.org
> > but to ca.w= ikipedia.org
> >
> > > and if this could be prevented in those files :
> >
> > http://websvn.kde.org/trunk/playgrou= nd/ioslaves/kwest/kio_kwest/kclucene_
> >an
> >
> > >y.desktop?view=3Dmarkup
> >
> > http://websvn.kde.org/trunk/playgrou= nd/ioslaves/kwest/kio_kwest/kclucene_
> >co
> >
> > >ntent.desktop?view=3Dmarkup
> >
> > http://websvn.kde.org/trunk/playgrou= nd/ioslaves/kwest/kio_kwest/beagle_de
> >fa
> >
> > >ult.desktop?view=3Dmarkup
> >
> > You can always use a keyword that is not translated like
> > X-KDE-KWest-Query.
> >
> > P.S: Translatable entries are Name, Comment, Language, Keywords, = About,
> > Description, GenericName, Query, ExtraNames and X-KDE-Submenu
> >
> > Albert
> >
> > > Thanks
> > >
> > > Nicolas Ternisien



------=_Part_17071_15823737.1206663693495--