<?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: Lessons learned in localization Part 1: Documentation pain</title>
	<atom:link href="http://www.klocwork.com/blog/2012/09/lessons-learned-in-localization-part-1-documentation-pain/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=lessons-learned-in-localization-part-1-documentation-pain</link>
	<description>&#62;kloctalk is a blog and a community for software development professionals who create and maintain mission-critical software and the challenges they face on a daily basis.</description>
	<lastBuildDate>Tue, 30 Apr 2013 13:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Samuel</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/comment-page-1/#comment-12816</link>
		<dc:creator>Samuel</dc:creator>
		<pubDate>Thu, 17 Jan 2013 20:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1517#comment-12816</guid>
		<description>Hi Patti and Kevin,

Great post on the pains of localization. An easier way of doing localization might be a using a localization platform. 
Instead of manually tracking strings with a spreadsheet, it acts like a version control system for your strings. 

You would essentially use a development framework to automatically extract translatable strings from your source code into what&#039;s called a plaintext file (e.g. .strings, .PO). That file is uploaded into the localization platform and from there, a lot of the work can be automated. For example, if you add a new string in English, it&#039;s automatically added to the Japanese language and your translators can be notified that a new string needs to be translated. Once the translations are done you can download the plaintext file for use when you deploy your software. And everything happens in the cloud so you Translation Memory, glossary, suggestions, etc. are always accessible. 

That was a very brief overview of what we (Transifex) do. Take a look at it (transifex.com) and let me know what you think. We would love to help make localization less painful for you guys. :)

I look forward to hearing from you.

Samuel</description>
		<content:encoded><![CDATA[<p>Hi Patti and Kevin,</p>
<p>Great post on the pains of localization. An easier way of doing localization might be a using a localization platform.<br />
Instead of manually tracking strings with a spreadsheet, it acts like a version control system for your strings. </p>
<p>You would essentially use a development framework to automatically extract translatable strings from your source code into what&#8217;s called a plaintext file (e.g. .strings, .PO). That file is uploaded into the localization platform and from there, a lot of the work can be automated. For example, if you add a new string in English, it&#8217;s automatically added to the Japanese language and your translators can be notified that a new string needs to be translated. Once the translations are done you can download the plaintext file for use when you deploy your software. And everything happens in the cloud so you Translation Memory, glossary, suggestions, etc. are always accessible. </p>
<p>That was a very brief overview of what we (Transifex) do. Take a look at it (transifex.com) and let me know what you think. We would love to help make localization less painful for you guys. :)</p>
<p>I look forward to hearing from you.</p>
<p>Samuel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirsty</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/comment-page-1/#comment-8753</link>
		<dc:creator>Kirsty</dc:creator>
		<pubDate>Fri, 12 Oct 2012 04:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1517#comment-8753</guid>
		<description>You might want to consider a form of translation memory tool to capture your translations. Then, even if you *have* to get a page retranslated for a few new sentences or changes to existing sentences, at least you can reuse the existing translations easily.</description>
		<content:encoded><![CDATA[<p>You might want to consider a form of translation memory tool to capture your translations. Then, even if you *have* to get a page retranslated for a few new sentences or changes to existing sentences, at least you can reuse the existing translations easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lessons learned from localization &#8211; software testing &#124; &#62;kloctalk</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/comment-page-1/#comment-8750</link>
		<dc:creator>Lessons learned from localization &#8211; software testing &#124; &#62;kloctalk</dc:creator>
		<pubDate>Thu, 11 Oct 2012 19:27:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1517#comment-8750</guid>
		<description>[...] needless pain, I launched this Lessons learned from localization series. In Part 1, we explored documentation pain and coping strategies. Part 2 was development discomfort and solutions. In this final installment, [...]</description>
		<content:encoded><![CDATA[<p>[...] needless pain, I launched this Lessons learned from localization series. In Part 1, we explored documentation pain and coping strategies. Part 2 was development discomfort and solutions. In this final installment, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lessons learned from localization Part 2: Development discomfort &#124; &#62;kloctalk</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/comment-page-1/#comment-8687</link>
		<dc:creator>Lessons learned from localization Part 2: Development discomfort &#124; &#62;kloctalk</dc:creator>
		<pubDate>Fri, 05 Oct 2012 14:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1517#comment-8687</guid>
		<description>[...] &#171; Lessons learned in localization Part 1: Documentation pain [...]</description>
		<content:encoded><![CDATA[<p>[...] &laquo; Lessons learned in localization Part 1: Documentation pain [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Welsh</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/comment-page-1/#comment-8678</link>
		<dc:creator>Kevin Welsh</dc:creator>
		<pubDate>Mon, 01 Oct 2012 14:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1517#comment-8678</guid>
		<description>I appreciate the tip, Amir. We will have to take a closer look at this and see if it&#039;s something we can use for a future release. Thanks!</description>
		<content:encoded><![CDATA[<p>I appreciate the tip, Amir. We will have to take a closer look at this and see if it&#8217;s something we can use for a future release. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amir E. Aharoni</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/comment-page-1/#comment-8660</link>
		<dc:creator>Amir E. Aharoni</dc:creator>
		<pubDate>Fri, 28 Sep 2012 06:20:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1517#comment-8660</guid>
		<description>You can use the Translate extension with MediaWiki. Its &quot;Page translation&quot; feature will help you translate documentation comfortable. Link:
https://www.mediawiki.org/wiki/Extension:Translate</description>
		<content:encoded><![CDATA[<p>You can use the Translate extension with MediaWiki. Its &#8220;Page translation&#8221; feature will help you translate documentation comfortable. Link:<br />
<a href="https://www.mediawiki.org/wiki/Extension:Translate" rel="nofollow">https://www.mediawiki.org/wiki/Extension:Translate</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Helen Abbott</title>
		<link>http://www.klocwork.com/blog/general-coding/lessons-learned-in-localization-part-1-documentation-pain/comment-page-1/#comment-8654</link>
		<dc:creator>Helen Abbott</dc:creator>
		<pubDate>Thu, 27 Sep 2012 15:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=1517#comment-8654</guid>
		<description>Great post. Kevin, you know I feel your pain. Despite my love for wikis, I&#039;m now using Help&amp;Manual. Within a day or so I could see that translation woes would be mucho reduced-o with a tool that has permanent topic IDs independent of topic titles. The original writer here had online help integrated with the software build within a week. And not expensive.</description>
		<content:encoded><![CDATA[<p>Great post. Kevin, you know I feel your pain. Despite my love for wikis, I&#8217;m now using Help&amp;Manual. Within a day or so I could see that translation woes would be mucho reduced-o with a tool that has permanent topic IDs independent of topic titles. The original writer here had online help integrated with the software build within a week. And not expensive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
