<?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: Translation glossary for all project types</title>
	<atom:link href="http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/</link>
	<description>Hire expert translators, manage projects yourself</description>
	<lastBuildDate>Tue, 31 Jan 2012 16:19:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Silvia</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-21</link>
		<dc:creator>Silvia</dc:creator>
		<pubDate>Tue, 08 Dec 2009 21:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-21</guid>
		<description>Thanks Amir, for your feedback.

@Steffan: I agree with you, nevertheless I would like to comment on your post above, where you say &quot;There simply is only ONE translation and that’s it&quot;. It&#039;s all fine when the translation is good, but when you find out that a translation is not so good or there&#039;s room for improvement, I think that adjustments are in your own interest, especially in the long term. About menus, you&#039;re completely right. A guide or reference is required.</description>
		<content:encoded><![CDATA[<p>Thanks Amir, for your feedback.</p>
<p>@Steffan: I agree with you, nevertheless I would like to comment on your post above, where you say &#8220;There simply is only ONE translation and that’s it&#8221;. It&#8217;s all fine when the translation is good, but when you find out that a translation is not so good or there&#8217;s room for improvement, I think that adjustments are in your own interest, especially in the long term. About menus, you&#8217;re completely right. A guide or reference is required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amir</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-20</link>
		<dc:creator>Amir</dc:creator>
		<pubDate>Mon, 07 Dec 2009 11:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-20</guid>
		<description>Yup, that&#039;s what we&#039;re going to implement. And like you&#039;re suggesting, we&#039;ll start with very basic functionality and then build it from there.</description>
		<content:encoded><![CDATA[<p>Yup, that&#8217;s what we&#8217;re going to implement. And like you&#8217;re suggesting, we&#8217;ll start with very basic functionality and then build it from there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steffan</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-19</link>
		<dc:creator>Steffan</dc:creator>
		<pubDate>Mon, 07 Dec 2009 02:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-19</guid>
		<description>Great idea. Start with a simple solution and work from there. 

As a client I don&#039;t want heaven - I just want what you offered in your newsletter. 

My biggest problem is that translators translate the same glossary word across different texts and come up with different translations for the same terms and words. 

This gets worse if multiple translators are involved. Especially when creating software and help files and FAQs this is a huge problem: Menu items always have to have the same translation for example, as users can otherwise not understand how the text ralates to their software.

There is no grading involved. There simply is only ONE translation and that&#039;s it. 

I don&#039;t know why an early version - or any version - would need a grading system. If I as a client want a translation of a word or term in the glossary fixed, so that it always is translated in the same way, then that&#039;s what I want. That&#039;s why I place it in the glossary. I do this to take away ANY options from the translators to get the translation wrong.

If you can deliver what you are suggesting in the newsletter, you would provide a great solution. 

From the comments I can see above it appears you have translators responding who want a grat Glossry for entirely different reasons than suggested by you. Stick with what you suggested, and you will make many of your clients happy who want to get better quality and more consistent translations across multiple documents.

I do NOT want a glossary such as 
&quot;trainer -&gt; (sport) istruttore, allenatore, trainer, mister&quot;
That already exists in translation software. There is no need to reinvent this.

I want a glossary that takes away options from translators and forces them to always translate

X with Y.

This is what I understand you are planning - and this would be a great solution.
:)</description>
		<content:encoded><![CDATA[<p>Great idea. Start with a simple solution and work from there. </p>
<p>As a client I don&#8217;t want heaven &#8211; I just want what you offered in your newsletter. </p>
<p>My biggest problem is that translators translate the same glossary word across different texts and come up with different translations for the same terms and words. </p>
<p>This gets worse if multiple translators are involved. Especially when creating software and help files and FAQs this is a huge problem: Menu items always have to have the same translation for example, as users can otherwise not understand how the text ralates to their software.</p>
<p>There is no grading involved. There simply is only ONE translation and that&#8217;s it. </p>
<p>I don&#8217;t know why an early version &#8211; or any version &#8211; would need a grading system. If I as a client want a translation of a word or term in the glossary fixed, so that it always is translated in the same way, then that&#8217;s what I want. That&#8217;s why I place it in the glossary. I do this to take away ANY options from the translators to get the translation wrong.</p>
<p>If you can deliver what you are suggesting in the newsletter, you would provide a great solution. </p>
<p>From the comments I can see above it appears you have translators responding who want a grat Glossry for entirely different reasons than suggested by you. Stick with what you suggested, and you will make many of your clients happy who want to get better quality and more consistent translations across multiple documents.</p>
<p>I do NOT want a glossary such as<br />
&#8220;trainer -&gt; (sport) istruttore, allenatore, trainer, mister&#8221;<br />
That already exists in translation software. There is no need to reinvent this.</p>
<p>I want a glossary that takes away options from translators and forces them to always translate</p>
<p>X with Y.</p>
<p>This is what I understand you are planning &#8211; and this would be a great solution.<br />
 <img src='http://www.icanlocalize.com/site/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silvia</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-17</link>
		<dc:creator>Silvia</dc:creator>
		<pubDate>Sun, 06 Dec 2009 13:00:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-17</guid>
		<description>&quot;have worked on a client&#039;s project&quot;! Sorry :-)</description>
		<content:encoded><![CDATA[<p>&#8220;have worked on a client&#8217;s project&#8221;! Sorry <img src='http://www.icanlocalize.com/site/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silvia</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-16</link>
		<dc:creator>Silvia</dc:creator>
		<pubDate>Sun, 06 Dec 2009 12:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-16</guid>
		<description>LIKES:
- translation glossary per client
- client glossary accessible to any translator working on that client&#039;s project
- clients create their glossary
- translators can add entries and their translation
- integrated into all ICL tools (Translation Assistant, text resources, instant translations)
- automatic highlighted terms/phrases that can be found in the glossary

DISLIKES:
- &#039;small&#039; translations that follow and glossary given to whomever is free (so called small translations can take up to 450 source words or so, full of technical terms, if say 5 translators have work on a client&#039;s project, priority for instant translations should be given to them, this will also prevent ICL&#039;s risk/fear of abandoned projects)
- SEO done by translators (as a translator, I may suggest terms, but a) terms should be paid, this cannot be done for free and b) I cannot check what people are looking for, this should be done by the client)
- list of the main phrases made manually by the translator (this would take up more time)

&quot;Tell us how you&#039;d like it to work and what you think it should include.&quot;

Desired features:

1. An option to switch the glossary language, from ALL to single language (as an example, suppose some software has been around in Spanish, German and English for 5 years and, at a given point, the client decides to have it translated into Italian too, I would like to see how some terms have been translated in Spanish or German and have the chance to choose the type of display: any translation, or just Spanish, German etc.)

2. The term should be shown in context (to see how it was used: noun, verb, etc.)

3. A button to highlight a term or phrase that will be added to the glossary automatically (but translation to be added manually, so that it can be more accurate, please have a look at mymemory and see for yourself what automatic alignments do, most of the time they are unreliable).

4. Space for translators&#039; comments/explanations

My two cents:-)

I&#039;m not sure you can do all that, but you asked for my ideas and opinions, so there you are!</description>
		<content:encoded><![CDATA[<p>LIKES:<br />
- translation glossary per client<br />
- client glossary accessible to any translator working on that client&#8217;s project<br />
- clients create their glossary<br />
- translators can add entries and their translation<br />
- integrated into all ICL tools (Translation Assistant, text resources, instant translations)<br />
- automatic highlighted terms/phrases that can be found in the glossary</p>
<p>DISLIKES:<br />
- &#8216;small&#8217; translations that follow and glossary given to whomever is free (so called small translations can take up to 450 source words or so, full of technical terms, if say 5 translators have work on a client&#8217;s project, priority for instant translations should be given to them, this will also prevent ICL&#8217;s risk/fear of abandoned projects)<br />
- SEO done by translators (as a translator, I may suggest terms, but a) terms should be paid, this cannot be done for free and b) I cannot check what people are looking for, this should be done by the client)<br />
- list of the main phrases made manually by the translator (this would take up more time)</p>
<p>&#8220;Tell us how you&#8217;d like it to work and what you think it should include.&#8221;</p>
<p>Desired features:</p>
<p>1. An option to switch the glossary language, from ALL to single language (as an example, suppose some software has been around in Spanish, German and English for 5 years and, at a given point, the client decides to have it translated into Italian too, I would like to see how some terms have been translated in Spanish or German and have the chance to choose the type of display: any translation, or just Spanish, German etc.)</p>
<p>2. The term should be shown in context (to see how it was used: noun, verb, etc.)</p>
<p>3. A button to highlight a term or phrase that will be added to the glossary automatically (but translation to be added manually, so that it can be more accurate, please have a look at mymemory and see for yourself what automatic alignments do, most of the time they are unreliable).</p>
<p>4. Space for translators&#8217; comments/explanations</p>
<p>My two cents:-)</p>
<p>I&#8217;m not sure you can do all that, but you asked for my ideas and opinions, so there you are!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silvia Astengo</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-13</link>
		<dc:creator>Silvia Astengo</dc:creator>
		<pubDate>Sat, 28 Nov 2009 09:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-13</guid>
		<description>Yes,
it&#039;s a good idea. I think we can creat a glossary like that (I translat from English to Italian):

trainer -&gt; (sport) istruttore, allenatore, trainer, mister

There are many possibilities and we have to explain -maybe with an example- when one word is better than an other! 
My little contribute
Regards</description>
		<content:encoded><![CDATA[<p>Yes,<br />
it&#8217;s a good idea. I think we can creat a glossary like that (I translat from English to Italian):</p>
<p>trainer -&gt; (sport) istruttore, allenatore, trainer, mister</p>
<p>There are many possibilities and we have to explain -maybe with an example- when one word is better than an other!<br />
My little contribute<br />
Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miriam Moreno</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-12</link>
		<dc:creator>Miriam Moreno</dc:creator>
		<pubDate>Thu, 26 Nov 2009 18:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-12</guid>
		<description>This is a great idea. It will really make things a lot easier for us.</description>
		<content:encoded><![CDATA[<p>This is a great idea. It will really make things a lot easier for us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rafael Bordabehere</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-11</link>
		<dc:creator>Rafael Bordabehere</dc:creator>
		<pubDate>Thu, 26 Nov 2009 10:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-11</guid>
		<description>I expect my glossaries to:
- let me find individual words (like &#039;look&#039;) or compound phrases (like &#039;look forward´),
- identify clearly the field each word is applied to,
- copy and paste from &#039;suggested source&#039; to &#039;target&#039;,
- in-the-spot editing capability to correct mistakes,
- show synonyms (if applicable)
- and direct link to the text it was used in to verify context.

I know it is like asking for heaven but they are ideas. Good luck with glossaries.</description>
		<content:encoded><![CDATA[<p>I expect my glossaries to:<br />
- let me find individual words (like &#8216;look&#8217;) or compound phrases (like &#8216;look forward´),<br />
- identify clearly the field each word is applied to,<br />
- copy and paste from &#8216;suggested source&#8217; to &#8216;target&#8217;,<br />
- in-the-spot editing capability to correct mistakes,<br />
- show synonyms (if applicable)<br />
- and direct link to the text it was used in to verify context.</p>
<p>I know it is like asking for heaven but they are ideas. Good luck with glossaries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexandru Asmarandei</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-10</link>
		<dc:creator>Alexandru Asmarandei</dc:creator>
		<pubDate>Thu, 26 Nov 2009 10:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-10</guid>
		<description>I incline to agree with DrLofthouse. And a little bit with the first two commenters. This will create frictions between translators, for this will be more than a guideline for many of them. It will also look like a translation machine (you just take the word and replace it). This is very dangerous for this tend to make a translation rigid, which should never happen. Different people have different ways to tell things and, from my point of view, this is what makes a difference between translators. It is close to writers.</description>
		<content:encoded><![CDATA[<p>I incline to agree with DrLofthouse. And a little bit with the first two commenters. This will create frictions between translators, for this will be more than a guideline for many of them. It will also look like a translation machine (you just take the word and replace it). This is very dangerous for this tend to make a translation rigid, which should never happen. Different people have different ways to tell things and, from my point of view, this is what makes a difference between translators. It is close to writers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cyril</title>
		<link>http://www.icanlocalize.com/site/2009/11/translation-glossary-for-all-project-types/comment-page-1/#comment-9</link>
		<dc:creator>Cyril</dc:creator>
		<pubDate>Thu, 26 Nov 2009 09:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.icanlocalize.com/site/?p=1185#comment-9</guid>
		<description>A great idea! I&#039;m looking forward to use this glossary and anyway we will have the choice to use the glossary answer or not... The best would be like in Trados a one word auto search when we enlight the word and click somewhere for instance it would display the occurence in all the IcanLocalize translations in the language. A field separator would be important too as has said ejtrans100. It would be a great tool!
:)</description>
		<content:encoded><![CDATA[<p>A great idea! I&#8217;m looking forward to use this glossary and anyway we will have the choice to use the glossary answer or not&#8230; The best would be like in Trados a one word auto search when we enlight the word and click somewhere for instance it would display the occurence in all the IcanLocalize translations in the language. A field separator would be important too as has said ejtrans100. It would be a great tool!<br />
 <img src='http://www.icanlocalize.com/site/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

