<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Localization Project Management Log &#187; localization kit</title>
	<atom:link href="http://ventajamarketing.com/l10nblog/category/localization-kit/feed/" rel="self" type="application/rss+xml" />
	<link>http://ventajamarketing.com/l10nblog</link>
	<description>Tips, tricks, traps, trivia and trophies for localization project managers in the trenches.</description>
	<lastBuildDate>Tue, 01 May 2012 03:18:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>What&#8217;s in Your Localization Kit?</title>
		<link>http://ventajamarketing.com/l10nblog/2009/01/whats-in-your-localization-kit/</link>
		<comments>http://ventajamarketing.com/l10nblog/2009/01/whats-in-your-localization-kit/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 01:01:00 +0000</pubDate>
		<dc:creator>John White</dc:creator>
				<category><![CDATA[localization kit]]></category>
		<category><![CDATA[localization process improvement]]></category>
		<category><![CDATA[new to localization]]></category>
		<category><![CDATA[translation project]]></category>

		<guid isPermaLink="false">http://ventajamarketing.com/l10nblog/?p=137</guid>
		<description><![CDATA[A localization kit &#8211; as I&#8217;ve come to use the term &#8211; is the 5-kilo bag of items you hand off to a vendor for localization. When properly assembled and used, the kit contains everything needed to localize and test software/documentation/Web site/etc. The quality of the loc kit is a barometer of the client&#8217;s sophistication [...]]]></description>
			<content:encoded><![CDATA[<p>A localization kit &#8211; as I&#8217;ve come to use the term &#8211; is the 5-kilo bag of items you hand off to a vendor for localization. When properly assembled and used, the kit contains everything needed to localize and test software/documentation/Web site/etc.</p>
<p>The quality of the loc kit is a barometer of the client&#8217;s sophistication in and regard for the localization process.</p>
<p><span style="font-weight: bold;">The Best</span><br />Have you ever received or sent a loc kit of which you were proud? What did you put into it? How long did it take you to put it together?
<ul>
<li>Software &#8211; resource files/bundles, object code, source graphics, installer scripts, start menu items and all libraries in the correct file structure required to build binaries</li>
<li>Documentation &#8211; source files for text, source files for graphics in text, build structure for online help systems, list of preferred tools and authoring applications</li>
<li>Web &#8211; files in correct structure, access to stage site to test translation (especially for .php/.jsp/.asp/.do- based Web content), clear guidelines about how far to translate and what to do about references to untranslated content</li>
<li>Sales/marketing materials &#8211; source files (InDesign, Quark, Creative Suite), access to the printing company for proper preparation</li>
<li>Multimedia &#8211; source files for Flash and movies, scripts, uncompressed QuickTime files</li>
<li>Glossaries and existing TMs &#8211; assets from previous translation efforts, or at least previously translated materials (even sales collateral) whether authorized or not</li>
<li>Instructions &#8211; what to translate, what not to translate, how to build the product, encodings to use, special notes for translators</li>
<li>Request for Proposal/Quotation (RFP/RFQ) &#8211; target languages, timelines, expectations for the quotation</li>
</ul>
<p>&#8230;and all of it properly internationalized.<br /><span style="font-weight: bold;"><br />The Worst</span><br />If a client sends a vendor a handful of PDFs and asks for the translations &#8220;as soon as possible&#8221; (most people&#8217;s favorite deadline), they probably don&#8217;t have much regard for the work involved. Most vendors can do the job from PDFs, of course, but they&#8217;re a pain in the neck (the PDFs, not the vendors) because it&#8217;s very hard to do a <span style="font-style: italic;">good</span> job from PDFs. Without the source files from which the PDFs were made, the vendor has to create from scratch most of the things the client takes for granted in the PDFs: formatting, spacing, layout, typeface, page setup, headers, footers, margins&#8230;</p>
<p><span style="font-weight: bold;">Wiggle Room</span><br />Of course, perfection is not in human nature. The handful-of-PDF&#8217;ers aren&#8217;t being malicious; they&#8217;re just doing as they&#8217;re told. Over time, the patient vendor may build a relationship with these people such that their interest in localization rises and their kits improve.</p>
<p>And even the best of loc kits does not answer every question. We&#8217;ve been running projects from the client-side with the same vendor for years, and questions still arise. I look forward to the questions, because we can improve the loc kit based on them. In fact, I get nervous when there are no questions: I suspect that somebody is doing something wrong and is afraid to check with me.</p>
<p>What have I left out? Do you have a secret weapon that you put into your loc kits?</p>
]]></content:encoded>
			<wfw:commentRss>http://ventajamarketing.com/l10nblog/2009/01/whats-in-your-localization-kit/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

