From kde-i18n-doc Mon Apr 07 23:32:29 2008 From: "Nicolas Ternisien" Date: Mon, 07 Apr 2008 23:32:29 +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=120761121310787 Yes, it's right, I will submit this to the Kwest developer. Thanks ! Nicolas On Mon, Apr 7, 2008 at 8:37 PM, Albert Astals Cid wrote: > A Divendres 28 Març 2008, Nicolas Ternisien va escriure: > > > 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 ? > > Why add a context if you don't want it translated at all? Just > X-KDE-KWest-Query and that's all no? > > Albert > > > > > > > On Thu, Mar 27, 2008 at 10:15 PM, Albert Astals Cid wrote: > > > A Dimarts 25 Març 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 always 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=playgroun > > >d- > > > > > > >ioslaves&filename=desktop_playground- > > > > > > ioslaves.po&compare=rekwest%3A%2Fbeagle > > > > > > >%3Fquery%3D\\\\{%40} > > > > > > > > On Tue, Mar 25, 2008 at 8:07 PM, Albert Astals Cid > > > > > > wrote: > > > > > A Dimarts 25 Març 2008, Nicolas Ternisien va escriure: > > > > > > Hi, > > > > > > > > > > > > I would like to know how > > > > > > > > > > How = as anything else that we translate, editing the suitable .po > > > > > > file > > > > > > > > > and why the Query value could be translated, > > > > > > > > > > Why = 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=markup > > > > > > http://websvn.kde.org/trunk/playground/ioslaves/kwest/kio_kwest/kclucene_ > > > > > > > >co > > > > > > > > > > >ntent.desktop?view=markup > > > > > > http://websvn.kde.org/trunk/playground/ioslaves/kwest/kio_kwest/beagle_de > > > > > > > >fa > > > > > > > > > > >ult.desktop?view=markup > > > > > > > > > > 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 > > >