<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Re: Silly translations</title>
	<atom:link href="http://blog.incase.de/index.php/2008/11/29/re-silly-translations/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.incase.de/index.php/2008/11/29/re-silly-translations/</link>
	<description>Sven's occasional log</description>
	<lastBuildDate>Mon, 23 Aug 2010 22:28:38 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sven</title>
		<link>http://blog.incase.de/index.php/2008/11/29/re-silly-translations/comment-page-1/#comment-2500</link>
		<dc:creator>sven</dc:creator>
		<pubDate>Mon, 22 Dec 2008 22:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=52#comment-2500</guid>
		<description>Henning:
The problem in this case was that Ubuntu specifically threw away existing translations from (KDE) upstream. So Ubuntu does NOT only translate what is specific to Ubuntu. This might not be the sole mistake of Ubuntu, but also partly caused by KDE upstream, but in general, your tools should report problems when an import fails due to file format changes. And more specifically, there should be a few regression tests at least, which detect when previously existing translations are seemingly dropped by upstream (which was not the case here anyway).

I generally welcome the effort Ubuntu puts into translations, but some of them seem slightly misguided.

Sven</description>
		<content:encoded><![CDATA[<p>Henning:<br />
The problem in this case was that Ubuntu specifically threw away existing translations from (KDE) upstream. So Ubuntu does NOT only translate what is specific to Ubuntu. This might not be the sole mistake of Ubuntu, but also partly caused by KDE upstream, but in general, your tools should report problems when an import fails due to file format changes. And more specifically, there should be a few regression tests at least, which detect when previously existing translations are seemingly dropped by upstream (which was not the case here anyway).</p>
<p>I generally welcome the effort Ubuntu puts into translations, but some of them seem slightly misguided.</p>
<p>Sven</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henning Eggers</title>
		<link>http://blog.incase.de/index.php/2008/11/29/re-silly-translations/comment-page-1/#comment-2499</link>
		<dc:creator>Henning Eggers</dc:creator>
		<pubDate>Mon, 22 Dec 2008 12:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=52#comment-2499</guid>
		<description>The import of translations for Ubuntu 8.10 were indeed problematic, which happened because of a shift in responsibilities. This has been discussed during UDS and will run much more smoothly for Jaunty so you will see more complete translations there. Also, the next language pack is due in January, so Intrepid will improve, too.

Much has been done to improve translations in Launchpad and it is not possible for random translations ending up in Ubuntu. Ubuntu mostly uses translations from upstream and the Ubuntu community only translates what is specific to Ubuntu. We are currently in the process of implementing the export of these changes to be used by upstream, if desired.

KDE translations are a special case because they use a non-standard file structure. Rosetta has special code to treat these imports but the structure changed again for the last import - so Kubuntu will lack behind, we can only do so much.

Henning</description>
		<content:encoded><![CDATA[<p>The import of translations for Ubuntu 8.10 were indeed problematic, which happened because of a shift in responsibilities. This has been discussed during UDS and will run much more smoothly for Jaunty so you will see more complete translations there. Also, the next language pack is due in January, so Intrepid will improve, too.</p>
<p>Much has been done to improve translations in Launchpad and it is not possible for random translations ending up in Ubuntu. Ubuntu mostly uses translations from upstream and the Ubuntu community only translates what is specific to Ubuntu. We are currently in the process of implementing the export of these changes to be used by upstream, if desired.</p>
<p>KDE translations are a special case because they use a non-standard file structure. Rosetta has special code to treat these imports but the structure changed again for the last import &#8211; so Kubuntu will lack behind, we can only do so much.</p>
<p>Henning</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jure Repinc</title>
		<link>http://blog.incase.de/index.php/2008/11/29/re-silly-translations/comment-page-1/#comment-2494</link>
		<dc:creator>Jure Repinc</dc:creator>
		<pubDate>Mon, 01 Dec 2008 06:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=52#comment-2494</guid>
		<description>We have the same problems with *buntu and Slovenian translations. Some are missing completely although the upstream is translated just fine and a lot of them are completely broken. And again if you check out upstream all is fine. Canonical should just close down this Roseta and let upstream do their job properly and with high quality. Roseta should only be used for translations specific to *buntu and only for projects who explicitly want to use Roseta. Current situation only harms Free/Open Source Software and Linux (users getting bad product, translators getting mad and even stoping with translation work), even more so because *buntu is so popular now.</description>
		<content:encoded><![CDATA[<p>We have the same problems with *buntu and Slovenian translations. Some are missing completely although the upstream is translated just fine and a lot of them are completely broken. And again if you check out upstream all is fine. Canonical should just close down this Roseta and let upstream do their job properly and with high quality. Roseta should only be used for translations specific to *buntu and only for projects who explicitly want to use Roseta. Current situation only harms Free/Open Source Software and Linux (users getting bad product, translators getting mad and even stoping with translation work), even more so because *buntu is so popular now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sven</title>
		<link>http://blog.incase.de/index.php/2008/11/29/re-silly-translations/comment-page-1/#comment-2492</link>
		<dc:creator>sven</dc:creator>
		<pubDate>Sat, 29 Nov 2008 21:18:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=52#comment-2492</guid>
		<description>Frederik: You are right, this is definitely NOT the fault of the KDE team, which I already knew when writing the blog entry. I shall really update my post and make that clear.</description>
		<content:encoded><![CDATA[<p>Frederik: You are right, this is definitely NOT the fault of the KDE team, which I already knew when writing the blog entry. I shall really update my post and make that clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://blog.incase.de/index.php/2008/11/29/re-silly-translations/comment-page-1/#comment-2491</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sat, 29 Nov 2008 17:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=52#comment-2491</guid>
		<description>That&#039;s what happens when random strings from random translators are taken from roseta/launchpad....</description>
		<content:encoded><![CDATA[<p>That&#8217;s what happens when random strings from random translators are taken from roseta/launchpad&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederik</title>
		<link>http://blog.incase.de/index.php/2008/11/29/re-silly-translations/comment-page-1/#comment-2490</link>
		<dc:creator>Frederik</dc:creator>
		<pubDate>Sat, 29 Nov 2008 17:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=52#comment-2490</guid>
		<description>Hi,

Kubuntu has a bug in the translation import stuff for their rosetta translation tool for years now that leads to improperly imported oficial translations for KDE. Since their copy of the KDE translation is incomplete, they fill the gaps with user contributed translations.

The translation you mentioned does not come from the official german KDE team.

It is sad that the reputation of ther german KDE team and KDE as a whole has to suffer from that. The Cannonical guys did not really care for the last years. Last week they allegedly fixed one of the bigger importing problems. Let&#039;s see if things become better now.

Regards</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Kubuntu has a bug in the translation import stuff for their rosetta translation tool for years now that leads to improperly imported oficial translations for KDE. Since their copy of the KDE translation is incomplete, they fill the gaps with user contributed translations.</p>
<p>The translation you mentioned does not come from the official german KDE team.</p>
<p>It is sad that the reputation of ther german KDE team and KDE as a whole has to suffer from that. The Cannonical guys did not really care for the last years. Last week they allegedly fixed one of the bigger importing problems. Let&#8217;s see if things become better now.</p>
<p>Regards</p>
]]></content:encoded>
	</item>
</channel>
</rss>
