User: jpmcc Date: 2010-06-19 11:00:52+0000 Modified: native-lang/www/planet/atom.xml native-lang/www/planet/index.html native-lang/www/planet/opml.xml native-lang/www/planet/rss10.xml native-lang/www/planet/rss20.xml
Log: Planet run at Sat Jun 19 13:00:39 CEST 2010 File Changes: Directory: /native-lang/www/planet/ =================================== File [changed]: atom.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/atom.xml?r1=1.3211&r2=1.3212 Delta lines: +50 -30 --------------------- --- atom.xml 2010-06-19 05:00:40+0000 1.3211 +++ atom.xml 2010-06-19 11:00:49+0000 1.3212 @@ -5,9 +5,49 @@ <link rel="self" href="http://native-lang.openoffice.org/planet/atom.xml"/> <link href="http://native-lang.openoffice.org/planet/"/> <id>http://native-lang.openoffice.org/planet/atom.xml</id> - <updated>2010-06-19T05:00:39+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> <generator uri="http://www.planetplanet.org/";>Planet/2.0 +http://www.planetplanet.org</generator> + <entry xml:lang="en"> + <title type="html">Emotions and localisation</title> + <link href="http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation"/> + <id>http://translate.org.za/blogs/86 at http://translate.org.za/blogs/friedel</id> + <updated>2010-06-19T08:02:38+00:00</updated> + <content type="html"><p>I recently had to do a slightly harder bit of translation work for <a href="http://pidgin.im">Pidgin</a>. Part of it was an extension for the XMPP protocol to <a href="http://xmpp.org/extensions/xep-0107.html">standardise emotions</a>. With this extension different chat programs can exchange information about the user's mood in a standard way. But the text shown to the user should of course be translated, and this ended up not being easy at all.</p> +<p>There are <a href="http://xmpp.org/extensions/xep-0107.html#moods">more than 80 emotions</a> described in the specification and it includes a few physical states (such as "cold" and "sick"). I got started to translate but quickly realised that this isn't all that easy. Firstly I don't know all the nuances of all the English terms well enough, but of course I just consulted dictionaries to solve that. Shortly, however, there were terms with multiple translations, some of which overlap with the translations of other terms. Some of these terms that I had some trouble with:</p> +<ul> +<li>Amazed, In awe</li> +<li>Thankful, Grateful</li> +<li>Amorous, In love, Aroused</li> +<li>Dismayed, Dejected</li> +<li>Contented, Satisfied</li> +<li>Humbled: It is ambiguous, in my opinion. It has meanings in the direction of "modest" and towards the direction of "abased" &mdash; quite a big difference. The intended meaning is given in the specification, but how will users know what is intended here?</li> +<li>Lucky en Happy: These two unfortunately both translate to "Gelukkig" in Afrikaans, and the difference is usually deduced from context. There is likely to be no context where the translations are used; maybe just a list of emotions to choose from.</li> +</ul> +<p>The goal is of course not just to get <em>some</em> translation, but something that is accurate, distinguishable from the others, and something that conveys the correct message to the person that you chat with &mdash; someone who likely uses a different chat program, maybe even in another language. It doesn't help if two terms are translated in the same way and you see something like "Gelukkig" twice in the list.</p> +<p>Although the specification gives the idea that the list of emotions is based on a bunch of good research about emotions (including cross-cultural studies of emotion), I wonder how useful this list is when it has terms that are so close to each other in meaning. Although some of the tricky bits specifically had to do with Afrikaans, it seems as if there are a few terms that can cause confusion for translators, and maybe even for users too.</p> +<p>Later in the same file I encountered stuff from the OSCAR protocol (used in ICQ and AIM) allowing users to indicate what they are busy with. Here are three of the strings: Surfing, Searching the web, Browsing the web &mdash; frustration! Then there are also a few in which I would have no interest to know that someone is busy with. Some of these didn't get my attention.</p> +<h3>Lessons learnt</h3> +<ul> +<li>Internationalisation is hard when it deals with emotions.</li> +<li>Programmers must give comments to explain things to translators in the best possible way.</li> +<li>These comments must be in the translation file. The link to the specification was only shared with translators later on the mailing list. Someone translating Pidgin in future will likely miss it.</li> +<li>Good dictionaries are amazing. This work would have taken significantly longer if I didn't get good starting points each time in the dictionaries.</li> +<li>A second opinion on my translations was a great help.</li> +<li>These words can't simply be put into a sentence. Different verbs are associated with these emotions. So while you in English might be able to say "I am ...." and fill in any of these emotions, this simply won't work in Afrikaans. (Mens <em>kry</em> warm, maar <em>voel</em> hartseer.) There are probably more reasons in other languages to never even try to squeeze these into a sentence.</li> +</ul></content> + <author> + <name>Friedel Wolff</name> + <uri>http://translate.org.za/blogs/friedel</uri> + </author> + <source> + <title type="html">Friedel en ander frappanthede</title> + <link rel="self" href="http://translate.org.za/blogs/friedel/en/rss.xml"/> + <id>http://translate.org.za/blogs/friedel/en/rss.xml</id> + <updated>2010-06-19T11:00:42+00:00</updated> + </source> + </entry> + <entry> <title type="html">ACTA restricts developing economies, India tells WTO ⢠The Register</title> <link href="http://ooo-speak.blogspot.com/2010/06/acta-restricts-developing-economies.html"/> @@ -202,7 +242,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -246,7 +286,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -290,7 +330,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -309,7 +349,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -332,7 +372,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -351,7 +391,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -375,7 +415,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -394,7 +434,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> @@ -467,27 +507,7 @@ <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> - </source> - </entry> - - <entry xml:lang="utf-8"> - <title type="html">#Traveling from #ichinoski to #tono #iwate</title> - <link href="http://openoffice.exblog.jp/10715067/"/> - <id>http://openoffice.exblog.jp/10715067/</id> - <updated>2010-05-30T06:49:38+00:00</updated> - <content type="html"><center><img class="IMAGE_MID" src="http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg" border="0" width="240" height="400" /></center><br /> -éã®é§ é é風ã®ä¸<br /></content> - <author> - <name>khparametric</name> - <uri>http://openoffice.exblog.jp</uri> - </author> - <source> - <title type="html">Hirano, Kazunari</title> - <subtitle type="html">Ichinoseki, Iwate, Japan</subtitle> - <link rel="self" href="http://openoffice.exblog.jp/atom.xml"/> - <id>http://openoffice.exblog.jp/atom.xml</id> - <updated>2010-06-19T05:00:38+00:00</updated> + <updated>2010-06-19T11:00:45+00:00</updated> </source> </entry> File [changed]: index.html Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/index.html?r1=1.3211&r2=1.3212 Delta lines: +38 -17 --------------------- --- index.html 2010-06-19 05:00:40+0000 1.3211 +++ index.html 2010-06-19 11:00:49+0000 1.3212 @@ -30,8 +30,45 @@ <a href="rss20.xml"><img src="rss2.gif" alt="Link to RSS 2 feed" /></a> </div> -<p><em>Bloggings on native language topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: June 19, 2010 05:00 AM CET</em></p> +<p><em>Bloggings on native language topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: June 19, 2010 11:00 AM CET</em></p> +<h2>June 19, 2010</h2> +<h3> +<a href="http://translate.org.za/blogs/friedel"; title="Friedel en ander frappanthede"> +Friedel Wolff</a> : +<a href="http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation";> +Emotions and localisation</a> +</h3> +<p> +<p>I recently had to do a slightly harder bit of translation work for <a href="http://pidgin.im";>Pidgin</a>. Part of it was an extension for the XMPP protocol to <a href="http://xmpp.org/extensions/xep-0107.html";>standardise emotions</a>. With this extension different chat programs can exchange information about the user's mood in a standard way. But the text shown to the user should of course be translated, and this ended up not being easy at all.</p> +<p>There are <a href="http://xmpp.org/extensions/xep-0107.html#moods";>more than 80 emotions</a> described in the specification and it includes a few physical states (such as "cold" and "sick"). I got started to translate but quickly realised that this isn't all that easy. Firstly I don't know all the nuances of all the English terms well enough, but of course I just consulted dictionaries to solve that. Shortly, however, there were terms with multiple translations, some of which overlap with the translations of other terms. Some of these terms that I had some trouble with:</p> +<ul> +<li>Amazed, In awe</li> +<li>Thankful, Grateful</li> +<li>Amorous, In love, Aroused</li> +<li>Dismayed, Dejected</li> +<li>Contented, Satisfied</li> +<li>Humbled: It is ambiguous, in my opinion. It has meanings in the direction of "modest" and towards the direction of "abased" — quite a big difference. The intended meaning is given in the specification, but how will users know what is intended here?</li> +<li>Lucky en Happy: These two unfortunately both translate to "Gelukkig" in Afrikaans, and the difference is usually deduced from context. There is likely to be no context where the translations are used; maybe just a list of emotions to choose from.</li> +</ul> +<p>The goal is of course not just to get <em>some</em> translation, but something that is accurate, distinguishable from the others, and something that conveys the correct message to the person that you chat with — someone who likely uses a different chat program, maybe even in another language. It doesn't help if two terms are translated in the same way and you see something like "Gelukkig" twice in the list.</p> +<p>Although the specification gives the idea that the list of emotions is based on a bunch of good research about emotions (including cross-cultural studies of emotion), I wonder how useful this list is when it has terms that are so close to each other in meaning. Although some of the tricky bits specifically had to do with Afrikaans, it seems as if there are a few terms that can cause confusion for translators, and maybe even for users too.</p> +<p>Later in the same file I encountered stuff from the OSCAR protocol (used in ICQ and AIM) allowing users to indicate what they are busy with. Here are three of the strings: Surfing, Searching the web, Browsing the web — frustration! Then there are also a few in which I would have no interest to know that someone is busy with. Some of these didn't get my attention.</p> +<h3>Lessons learnt</h3> +<ul> +<li>Internationalisation is hard when it deals with emotions.</li> +<li>Programmers must give comments to explain things to translators in the best possible way.</li> +<li>These comments must be in the translation file. The link to the specification was only shared with translators later on the mailing list. Someone translating Pidgin in future will likely miss it.</li> +<li>Good dictionaries are amazing. This work would have taken significantly longer if I didn't get good starting points each time in the dictionaries.</li> +<li>A second opinion on my translations was a great help.</li> +<li>These words can't simply be put into a sentence. Different verbs are associated with these emotions. So while you in English might be able to say "I am ...." and fill in any of these emotions, this simply won't work in Afrikaans. (Mens <em>kry</em> warm, maar <em>voel</em> hartseer.) There are probably more reasons in other languages to never even try to squeeze these into a sentence.</li> +</ul></p> +<p> +<em><a href="http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation";>by Friedel at June 19, 2010 08:02 AM CET</a></em> +</p> +<br /> +<hr /> +<br /> <h2>June 15, 2010</h2> <h3> <a href="http://ooo-speak.blogspot.com/"; title="ooo-speak"> @@ -398,22 +435,6 @@ <br /> <hr /> <br /> -<h2>May 30, 2010</h2> -<h3> -<a href="http://openoffice.exblog.jp"; title="Hirano, Kazunari"> -Kazunari Hirano</a> : -<a href="http://openoffice.exblog.jp/10715067/";> -#Traveling from #ichinoski to #tono #iwate</a> -</h3> -<p> -<center><img class="IMAGE_MID" src="http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg"; border="0" width="240" height="400" /></center><br /> -éã®é§ é é風ã®ä¸<br /></p> -<p> -<em><a href="http://openoffice.exblog.jp/10715067/";>by khparametric at May 30, 2010 06:49 AM CET</a></em> -</p> -<br /> -<hr /> -<br /> <a id="disclaimer" name="disclaimer"></a> <p><em>Disclaimer: all views expressed on this page are those of the individual contributors, and may not reflect the views of the File [changed]: opml.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/opml.xml?r1=1.3210&r2=1.3211 Delta lines: +1 -1 ------------------- --- opml.xml 2010-06-19 05:00:41+0000 1.3210 +++ opml.xml 2010-06-19 11:00:50+0000 1.3211 @@ -2,7 +2,7 @@ <opml version="1.1"> <head> <title>Native Language Confederation Planet</title> - <dateModified>Sat, 19 Jun 2010 05:00:39 +0000</dateModified> + <dateModified>Sat, 19 Jun 2010 11:00:46 +0000</dateModified> <ownerName>Native Language Confederation</ownerName> <ownerEmail>[email protected]</ownerEmail> </head> File [changed]: rss10.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/rss10.xml?r1=1.530&r2=1.531 Delta lines: +29 -9 -------------------- --- rss10.xml 2010-06-15 17:01:00+0000 1.530 +++ rss10.xml 2010-06-19 11:00:50+0000 1.531 @@ -13,6 +13,7 @@ <items> <rdf:Seq> + <rdf:li rdf:resource="http://translate.org.za/blogs/86 at http://translate.org.za/blogs/friedel"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4649039904546083564.post-610844788530949014" /> <rdf:li rdf:resource="http://standardsandfreedom.net/?p=190"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4649039904546083564.post-8509442990147931918" /> @@ -32,11 +33,38 @@ <rdf:li rdf:resource="http://standardsandfreedom.net/?p=186"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4649039904546083564.post-6475248512738668059" /> <rdf:li rdf:resource="http://openoffice.exblog.jp/10720159/"; /> - <rdf:li rdf:resource="http://openoffice.exblog.jp/10715067/"; /> </rdf:Seq> </items> </channel> +<item rdf:about="http://translate.org.za/blogs/86 at http://translate.org.za/blogs/friedel";> + <title>Friedel Wolff: Emotions and localisation</title> + <link>http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation</link> + <content:encoded><p>I recently had to do a slightly harder bit of translation work for <a href="http://pidgin.im">Pidgin</a>. Part of it was an extension for the XMPP protocol to <a href="http://xmpp.org/extensions/xep-0107.html">standardise emotions</a>. With this extension different chat programs can exchange information about the user's mood in a standard way. But the text shown to the user should of course be translated, and this ended up not being easy at all.</p> +<p>There are <a href="http://xmpp.org/extensions/xep-0107.html#moods">more than 80 emotions</a> described in the specification and it includes a few physical states (such as "cold" and "sick"). I got started to translate but quickly realised that this isn't all that easy. Firstly I don't know all the nuances of all the English terms well enough, but of course I just consulted dictionaries to solve that. Shortly, however, there were terms with multiple translations, some of which overlap with the translations of other terms. Some of these terms that I had some trouble with:</p> +<ul> +<li>Amazed, In awe</li> +<li>Thankful, Grateful</li> +<li>Amorous, In love, Aroused</li> +<li>Dismayed, Dejected</li> +<li>Contented, Satisfied</li> +<li>Humbled: It is ambiguous, in my opinion. It has meanings in the direction of "modest" and towards the direction of "abased" &mdash; quite a big difference. The intended meaning is given in the specification, but how will users know what is intended here?</li> +<li>Lucky en Happy: These two unfortunately both translate to "Gelukkig" in Afrikaans, and the difference is usually deduced from context. There is likely to be no context where the translations are used; maybe just a list of emotions to choose from.</li> +</ul> +<p>The goal is of course not just to get <em>some</em> translation, but something that is accurate, distinguishable from the others, and something that conveys the correct message to the person that you chat with &mdash; someone who likely uses a different chat program, maybe even in another language. It doesn't help if two terms are translated in the same way and you see something like "Gelukkig" twice in the list.</p> +<p>Although the specification gives the idea that the list of emotions is based on a bunch of good research about emotions (including cross-cultural studies of emotion), I wonder how useful this list is when it has terms that are so close to each other in meaning. Although some of the tricky bits specifically had to do with Afrikaans, it seems as if there are a few terms that can cause confusion for translators, and maybe even for users too.</p> +<p>Later in the same file I encountered stuff from the OSCAR protocol (used in ICQ and AIM) allowing users to indicate what they are busy with. Here are three of the strings: Surfing, Searching the web, Browsing the web &mdash; frustration! Then there are also a few in which I would have no interest to know that someone is busy with. Some of these didn't get my attention.</p> +<h3>Lessons learnt</h3> +<ul> +<li>Internationalisation is hard when it deals with emotions.</li> +<li>Programmers must give comments to explain things to translators in the best possible way.</li> +<li>These comments must be in the translation file. The link to the specification was only shared with translators later on the mailing list. Someone translating Pidgin in future will likely miss it.</li> +<li>Good dictionaries are amazing. This work would have taken significantly longer if I didn't get good starting points each time in the dictionaries.</li> +<li>A second opinion on my translations was a great help.</li> +<li>These words can't simply be put into a sentence. Different verbs are associated with these emotions. So while you in English might be able to say "I am ...." and fill in any of these emotions, this simply won't work in Afrikaans. (Mens <em>kry</em> warm, maar <em>voel</em> hartseer.) There are probably more reasons in other languages to never even try to squeeze these into a sentence.</li> +</ul></content:encoded> + <dc:date>2010-06-19T08:02:38+00:00</dc:date> +</item> <item rdf:about="tag:blogger.com,1999:blog-4649039904546083564.post-610844788530949014"> <title>Louis Suarez-Potts: ACTA restricts developing economies, India tells WTO ⢠The Register</title> <link>http://ooo-speak.blogspot.com/2010/06/acta-restricts-developing-economies.html</link> @@ -260,13 +288,5 @@ <dc:date>2010-05-31T02:30:24+00:00</dc:date> <dc:creator>khparametric</dc:creator> </item> -<item rdf:about="http://openoffice.exblog.jp/10715067/";> - <title>Kazunari Hirano: #Traveling from #ichinoski to #tono #iwate</title> - <link>http://openoffice.exblog.jp/10715067/</link> - <content:encoded><center><img class="IMAGE_MID" src="http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg" border="0" width="240" height="400" /></center><br /> -éã®é§ é é風ã®ä¸<br /></content:encoded> - <dc:date>2010-05-30T06:49:38+00:00</dc:date> - <dc:creator>khparametric</dc:creator> -</item> </rdf:RDF> File [changed]: rss20.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/rss20.xml?r1=1.531&r2=1.532 Delta lines: +29 -8 -------------------- --- rss20.xml 2010-06-15 17:01:00+0000 1.531 +++ rss20.xml 2010-06-19 11:00:50+0000 1.532 @@ -8,6 +8,35 @@ <description>Native Language Confederation Planet - http://native-lang.openoffice.org/planet/</description> <item> + <title>Friedel Wolff: Emotions and localisation</title> + <guid>http://translate.org.za/blogs/86 at http://translate.org.za/blogs/friedel</guid> + <link>http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation</link> + <description><p>I recently had to do a slightly harder bit of translation work for <a href="http://pidgin.im">Pidgin</a>. Part of it was an extension for the XMPP protocol to <a href="http://xmpp.org/extensions/xep-0107.html">standardise emotions</a>. With this extension different chat programs can exchange information about the user's mood in a standard way. But the text shown to the user should of course be translated, and this ended up not being easy at all.</p> +<p>There are <a href="http://xmpp.org/extensions/xep-0107.html#moods">more than 80 emotions</a> described in the specification and it includes a few physical states (such as "cold" and "sick"). I got started to translate but quickly realised that this isn't all that easy. Firstly I don't know all the nuances of all the English terms well enough, but of course I just consulted dictionaries to solve that. Shortly, however, there were terms with multiple translations, some of which overlap with the translations of other terms. Some of these terms that I had some trouble with:</p> +<ul> +<li>Amazed, In awe</li> +<li>Thankful, Grateful</li> +<li>Amorous, In love, Aroused</li> +<li>Dismayed, Dejected</li> +<li>Contented, Satisfied</li> +<li>Humbled: It is ambiguous, in my opinion. It has meanings in the direction of "modest" and towards the direction of "abased" &mdash; quite a big difference. The intended meaning is given in the specification, but how will users know what is intended here?</li> +<li>Lucky en Happy: These two unfortunately both translate to "Gelukkig" in Afrikaans, and the difference is usually deduced from context. There is likely to be no context where the translations are used; maybe just a list of emotions to choose from.</li> +</ul> +<p>The goal is of course not just to get <em>some</em> translation, but something that is accurate, distinguishable from the others, and something that conveys the correct message to the person that you chat with &mdash; someone who likely uses a different chat program, maybe even in another language. It doesn't help if two terms are translated in the same way and you see something like "Gelukkig" twice in the list.</p> +<p>Although the specification gives the idea that the list of emotions is based on a bunch of good research about emotions (including cross-cultural studies of emotion), I wonder how useful this list is when it has terms that are so close to each other in meaning. Although some of the tricky bits specifically had to do with Afrikaans, it seems as if there are a few terms that can cause confusion for translators, and maybe even for users too.</p> +<p>Later in the same file I encountered stuff from the OSCAR protocol (used in ICQ and AIM) allowing users to indicate what they are busy with. Here are three of the strings: Surfing, Searching the web, Browsing the web &mdash; frustration! Then there are also a few in which I would have no interest to know that someone is busy with. Some of these didn't get my attention.</p> +<h3>Lessons learnt</h3> +<ul> +<li>Internationalisation is hard when it deals with emotions.</li> +<li>Programmers must give comments to explain things to translators in the best possible way.</li> +<li>These comments must be in the translation file. The link to the specification was only shared with translators later on the mailing list. Someone translating Pidgin in future will likely miss it.</li> +<li>Good dictionaries are amazing. This work would have taken significantly longer if I didn't get good starting points each time in the dictionaries.</li> +<li>A second opinion on my translations was a great help.</li> +<li>These words can't simply be put into a sentence. Different verbs are associated with these emotions. So while you in English might be able to say "I am ...." and fill in any of these emotions, this simply won't work in Afrikaans. (Mens <em>kry</em> warm, maar <em>voel</em> hartseer.) There are probably more reasons in other languages to never even try to squeeze these into a sentence.</li> +</ul></description> + <pubDate>Sat, 19 Jun 2010 08:02:38 +0000</pubDate> +</item> +<item> <title>Louis Suarez-Potts: ACTA restricts developing economies, India tells WTO ⢠The Register</title> <guid>tag:blogger.com,1999:blog-4649039904546083564.post-610844788530949014</guid> <link>http://ooo-speak.blogspot.com/2010/06/acta-restricts-developing-economies.html</link> @@ -240,14 +269,6 @@ <br /></description> <pubDate>Mon, 31 May 2010 02:30:24 +0000</pubDate> </item> -<item> - <title>Kazunari Hirano: #Traveling from #ichinoski to #tono #iwate</title> - <guid>http://openoffice.exblog.jp/10715067/</guid> - <link>http://openoffice.exblog.jp/10715067/</link> - <description><center><img class="IMAGE_MID" src="http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg" border="0" width="240" height="400" /></center><br /> -éã®é§ é é風ã®ä¸<br /></description> - <pubDate>Sun, 30 May 2010 06:49:38 +0000</pubDate> -</item> </channel> </rss> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
![http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg"](http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg"){kind=link}
![http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg"](http://pds.exblog.jp/pds/1/201005/30/84/a0005484_15493860.jpg"){kind=link}