<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Translating with the New Madcap Lingo V2</title>
	<atom:link href="http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/feed/" rel="self" type="application/rss+xml" />
	<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/</link>
	<description>The Latest Trends in Technical Communication</description>
	<lastBuildDate>Mon, 13 Feb 2012 21:02:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ima Translator</title>
		<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/comment-page-1/#comment-147533</link>
		<dc:creator>Ima Translator</dc:creator>
		<pubDate>Sat, 26 Dec 2009 09:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3030#comment-147533</guid>
		<description>Thank you for your post. It was quite informative. 
Translation tools are still limited in capacity and cannot handle large projects as of yet. Breaking down the language barrier is vital in today&#039;s global economy.</description>
		<content:encoded><![CDATA[<p>Thank you for your post. It was quite informative.<br />
Translation tools are still limited in capacity and cannot handle large projects as of yet. Breaking down the language barrier is vital in today&#8217;s global economy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/comment-page-1/#comment-143915</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 15 Sep 2009 13:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3030#comment-143915</guid>
		<description>Ivan, thanks for the update. I assume you&#039;re a translator, or that you do translation. When I looked into Lingo, I realized that it was really set up for a team that handles its own translation rather than writers who outsource translation to other groups that use their own set of translation tools.</description>
		<content:encoded><![CDATA[<p>Ivan, thanks for the update. I assume you&#8217;re a translator, or that you do translation. When I looked into Lingo, I realized that it was really set up for a team that handles its own translation rather than writers who outsource translation to other groups that use their own set of translation tools.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Walsh</title>
		<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/comment-page-1/#comment-143904</link>
		<dc:creator>Ivan Walsh</dc:creator>
		<pubDate>Tue, 15 Sep 2009 09:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3030#comment-143904</guid>
		<description>Hi Folks, 

Version 3.0 is now out which comes with many new features. 

New to me is the TermBase Editor.

This &quot;also allows the import and export of Term Base eXchange (TBX) files. TBX is an open, XML-based standard used for exchanging structured terminological data. 

TBX files offer a clear advantage in that they can handle multiple languages versus TMX files, which can only handle two languages.&quot;

http://technicalwriter.ivanwalsh.com/2009/09/18/madcap-lingo-3-0-helps-technical-writers-and-translators-reduce-projects-costs/

Regards, 

Ivan</description>
		<content:encoded><![CDATA[<p>Hi Folks, </p>
<p>Version 3.0 is now out which comes with many new features. </p>
<p>New to me is the TermBase Editor.</p>
<p>This &#8220;also allows the import and export of Term Base eXchange (TBX) files. TBX is an open, XML-based standard used for exchanging structured terminological data. </p>
<p>TBX files offer a clear advantage in that they can handle multiple languages versus TMX files, which can only handle two languages.&#8221;</p>
<p><a href="http://technicalwriter.ivanwalsh.com/2009/09/18/madcap-lingo-3-0-helps-technical-writers-and-translators-reduce-projects-costs/" rel="nofollow">http://technicalwriter.ivanwalsh.com/2009/09/18/madcap-lingo-3-0-helps-technical-writers-and-translators-reduce-projects-costs/</a></p>
<p>Regards, </p>
<p>Ivan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dan</title>
		<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/comment-page-1/#comment-139923</link>
		<dc:creator>dan</dc:creator>
		<pubDate>Sun, 03 May 2009 17:30:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3030#comment-139923</guid>
		<description>Daniel Green,
I am assuming your subcontractor has mixed your project with the translation of others as well, so a clean export and import is not viable.

Well in Lingo v2, if you have the source project and translated project outputs, you could try the new Alignment feature. it should try to help you fuzzy match the source-translated language pairs you need...then once they match up, you can upload them to your new translation memory database...the clean start you require.</description>
		<content:encoded><![CDATA[<p>Daniel Green,<br />
I am assuming your subcontractor has mixed your project with the translation of others as well, so a clean export and import is not viable.</p>
<p>Well in Lingo v2, if you have the source project and translated project outputs, you could try the new Alignment feature. it should try to help you fuzzy match the source-translated language pairs you need&#8230;then once they match up, you can upload them to your new translation memory database&#8230;the clean start you require.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dan</title>
		<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/comment-page-1/#comment-139922</link>
		<dc:creator>dan</dc:creator>
		<pubDate>Sun, 03 May 2009 17:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3030#comment-139922</guid>
		<description>Daniel Green,
Get your contractor to export the embedded data in their Trados system to a TMX file. Then you can use your copy of Madcap Lingo to import the TMX file standard into your own translation memory/database. TMX is an open file standard and should be compatible with pretty much any other translation memory tool worth its salt. 

The TMX file should retain the segments of source language and translated language pairs that you require of your contractor.</description>
		<content:encoded><![CDATA[<p>Daniel Green,<br />
Get your contractor to export the embedded data in their Trados system to a TMX file. Then you can use your copy of Madcap Lingo to import the TMX file standard into your own translation memory/database. TMX is an open file standard and should be compatible with pretty much any other translation memory tool worth its salt. </p>
<p>The TMX file should retain the segments of source language and translated language pairs that you require of your contractor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Green</title>
		<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/comment-page-1/#comment-138568</link>
		<dc:creator>Daniel Green</dc:creator>
		<pubDate>Thu, 19 Mar 2009 18:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3030#comment-138568</guid>
		<description>Hello, Daniel.

When I first encountered this tool, we were cost-stumped by the &#039;translation database&#039; requirement. Is it possible now, with this version, to construct our TM from source or output files from our most recent localized Flare deliverables? Just curious; our TM history has been embedded into a subcontractor&#039;s Trados system, commingled with everything else they&#039;ve done, with everyone else unfortunately. It would be a clean &amp; smarter start if we could construct our own TM DB using our source/output files. Thanks, =dg= Fox Racing Shox, Watsonville, CA</description>
		<content:encoded><![CDATA[<p>Hello, Daniel.</p>
<p>When I first encountered this tool, we were cost-stumped by the &#8216;translation database&#8217; requirement. Is it possible now, with this version, to construct our TM from source or output files from our most recent localized Flare deliverables? Just curious; our TM history has been embedded into a subcontractor&#8217;s Trados system, commingled with everything else they&#8217;ve done, with everyone else unfortunately. It would be a clean &amp; smarter start if we could construct our own TM DB using our source/output files. Thanks, =dg= Fox Racing Shox, Watsonville, CA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MadCap Lingo 2 - new features &#124; Translator's Shack</title>
		<link>http://idratherbewriting.com/2009/02/24/translating-with-the-new-madcap-lingo-v2/comment-page-1/#comment-137895</link>
		<dc:creator>MadCap Lingo 2 - new features &#124; Translator's Shack</dc:creator>
		<pubDate>Wed, 25 Feb 2009 07:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3030#comment-137895</guid>
		<description>[...] Update: The I&#8217;d Rather Be Writing blog has a review about MadCap Lingo 2. [...]</description>
		<content:encoded><![CDATA[<p>[...] Update: The I&#8217;d Rather Be Writing blog has a review about MadCap Lingo 2. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

