<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bill Swallow on Medium]]></title>
        <description><![CDATA[Stories by Bill Swallow on Medium]]></description>
        <link>https://medium.com/@billswallow?source=rss-43836508dbcd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xeXnoNcGY2MmyJ3Wc_ZwrQ.jpeg</url>
            <title>Stories by Bill Swallow on Medium</title>
            <link>https://medium.com/@billswallow?source=rss-43836508dbcd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:43:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@billswallow/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Translation and the complexity of simple content]]></title>
            <link>https://medium.com/@billswallow/translation-and-the-complexity-of-simple-content-64dc102540c?source=rss-43836508dbcd------2</link>
            <guid isPermaLink="false">https://medium.com/p/64dc102540c</guid>
            <category><![CDATA[translation]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[localization]]></category>
            <dc:creator><![CDATA[Bill Swallow]]></dc:creator>
            <pubDate>Mon, 07 Mar 2016 08:45:20 GMT</pubDate>
            <atom:updated>2016-03-07T14:54:36.329Z</atom:updated>
            <content:encoded><![CDATA[<p>Translating content for foreign markets can be an expensive and time-consuming endeavor. While it’s important to keep costs in check, the critical element to watch is quality. The only sure-fire way to ensure quality in translation is to build it into your source.</p><h3>GIGO: Garbage in, garbage out</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*dvQmOYhZSRsMrDff.jpg" /><figcaption>That’s not what we meant! (flickr: JD Hancock)</figcaption></figure><p>Developing content is often seen as a necessary evil. It’s easy to justify cutting corners to deliver it quickly or create it using fewer resources. After all, it’s just content, right?</p><p>Not quite.</p><p>More often than not, even technical content is being used in the pre-sales cycle. People want to evaluate a product or service before purchasing, and one of the easiest ways to do that is by searching for information online. Content quality in this case might make or break a sale.</p><p>Content quality is also a major factor in retaining existing customers. People are extremely happy when they can easily find answers to their questions without having to call support. Likewise, the easier the answer is to understand, the better.</p><p>So there’s a logical fallacy that content is a necessary evil. It plays a critical role in attracting and retaining happy customers. It is a business cornerstone. This is true in all markets. Despite your translators’ best efforts, the quality of their translation work is a direct reflection on the quality of your source content. And to keep translation costs down, you need to make that effort simple.</p><h3>The complexity of simple content</h3><p>Simple content does not mean dumbed-down or bare bones. In this context, simple content means streamlined content.</p><ul><li>Messaging is clear and concise</li><li>Words are carefully chosen</li><li>Content is written in discrete chunks (topics)</li><li>Those chunks are written once and reused wherever appropriate</li><li>Content is consistently formatted (or better, tagged in XML)</li></ul><p>In short, the entirety of content development is closely monitored and skillfully performed.</p><p>The effort involved is anything but simple, but the benefits far outweigh the work. All of the heavy lifting is done on the source content side, simplifying the translation process.</p><p>When your source content is clear, concise, and complete, it can be translated easily. When content is written once and reused, translators only need to translate it once. When content is consistently tagged, formatting translated content becomes automatic.</p><p>As a result, your content quality is consistent across all languages, your translation costs are reduced, and the translation work is completed quicker, allowing you to accelerate your time to market.</p><p><em>Originally published at </em><a href="http://www.scriptorium.com/2016/03/translation-and-the-complexity-of-simple-content/"><em>www.scriptorium.com</em></a><em> on March 7, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64dc102540c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Has your localization service provider (LSP) been naughty or nice?]]></title>
            <link>https://medium.com/@billswallow/has-your-localization-service-provider-lsp-been-naughty-or-nice-4fbeed408d?source=rss-43836508dbcd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fbeed408d</guid>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[translation]]></category>
            <dc:creator><![CDATA[Bill Swallow]]></dc:creator>
            <pubDate>Wed, 11 Dec 2013 09:00:45 GMT</pubDate>
            <atom:updated>2015-12-22T19:41:58.924Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A festive piece from two years ago that’s still relevant today.</em></p><p>Last month I posted about the <a href="http://www.scriptorium.com/2013/11/five-gotchas-that-will-affect-your-translation-turnaround-time/">five gotchas that will affect your translation turnaround time</a>. That post focused on content quality, but I’d also mentioned how “a good LSP” would handle things. This month, let’s take a step back and look at five things that separate the <em>nice</em> LSPs from the <em>naughty</em> ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/214/0*rhieUWXPlLb4YVsb.jpg" /></figure><p>Santa Claus By Jonathan G Meath (Jonathan G Meath) [CC-BY-SA-2.5 (http://creativecommons.org/licenses/by-sa/2.5)], via Wikimedia Commons</p><p><strong>1. Questions</strong></p><p><strong>Naughty:</strong> A naughty LSP will more often than not skip over all of the pesky project details to get to the word count and source file formats so they can turn around a quick quote. They’ll likely respond to your questions with hollow assurances that everything will be fine, and that they’ll follow up with any questions, if they have them, after receiving your files. The false confidence they exhibit usually masks problems until it’s too late in the project to properly correct them.</p><p><strong>Nice:</strong> When first engaging a client or beginning a new project, a nice LSP will ask you informed, pertinent questions about your content, your audience, and the purpose of the project. They will ask about technology, workflow, review, and other aspects of the project. Their goal is to understand all aspects of the project so they can deliver the best translations possible.</p><p><strong>2. Advice</strong></p><p><strong>Naughty:</strong> You might not think it’s naughty behavior, but a naughty LSP will translate your files just as they are, whether it’s an easy or complex process for them. Why is this naughty? If they are encountering issues, they are not alerting you and explaining better ways of doing things, which could mean that you are paying more in project setup or DTP fees than you ideally should be.</p><p><strong>Nice:</strong> Nice LSPs are open, honest, and helpful. They will point out issues in files, offer solutions, and often offer several options for their clients to choose from in correcting issues or in avoiding potential problems. Nice LSPs understand that helpful advice fosters collaboration and constructively builds long-term partnerships.</p><p><strong>3. Workflow</strong></p><p><strong>Naughty:</strong> A naughty LSP has their own way of doing things, and will often strongly suggest you conform to their preferred workflow (or face possible additional charges). This may be because of their own technology investments (or lack thereof), or because they have no control over how their translators work. Worse, they may mandate that you conform to their workflow if you want to use them at all.</p><p><strong>Nice:</strong> A nice LSP realizes that their clients may have spent considerable time and money on implementing technologies and training staff to create content in a certain way. They work to integrate into your workflow, or at least work to meet you part of the way so you can realize the ROI from your chosen workflow.</p><p><strong>4. Pricing</strong></p><p><strong>Naughty:</strong> Naughty LSPs can be sneaky about their service pricing. Their terms may be unclear, and what you may save from a low price per word might be lost many times over via pricey DTP, project management, or file prep charges. Always make sure you have a complete pricing breakdown for your project and be aware of inflated pricing or effort estimates.</p><p><strong>Nice:</strong> Nice LSPs are completely up-front with their pricing models and explain every line item in their quotes. They explain how various approaches to a project, and how potential issues, will affect the pricing. Nice LSPs understand the value of transparency in process and in pricing, and they also understand that clear and honest pricing helps establish long-term business partnerships.</p><p><strong>5. Translation Memory Ownership</strong></p><p><strong>Naughty:</strong> A naughty LSP may have no up front policy about translation memory (TM) ownership, or might either avoid or downplay any conversation about TM ownership. Worse, they might claim outright ownership of it or withhold it! In this case, forget the coal in the stocking and call the <a href="http://www.ajc.com/news/news/world/krampus-story-austrias-terrifying-christmas-tradit/ncFSX/">Krampus</a>!</p><p><strong>Nice:</strong> A nice LSP acknowledges up front and in writing that you own your TM and are entitled to receive a copy of it whenever you request one. They understand that they are providing you a service involving your intellectual property.</p><p><em>Originally published at </em><a href="http://www.scriptorium.com/2013/12/has-your-localization-service-provider-lsp-been-naughty-or-nice/"><em>www.scriptorium.com</em></a><em> on December 11, 2013.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fbeed408d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five gotchas that will affect your translation turnaround time]]></title>
            <link>https://medium.com/@billswallow/five-gotchas-that-will-affect-your-translation-turnaround-time-22ddc8d6b6?source=rss-43836508dbcd------2</link>
            <guid isPermaLink="false">https://medium.com/p/22ddc8d6b6</guid>
            <category><![CDATA[translation]]></category>
            <category><![CDATA[localization]]></category>
            <dc:creator><![CDATA[Bill Swallow]]></dc:creator>
            <pubDate>Mon, 25 Nov 2013 08:15:08 GMT</pubDate>
            <atom:updated>2015-12-08T18:36:10.477Z</atom:updated>
            <content:encoded><![CDATA[<p>Having worked at two translation companies and on many projects requiring localization, I appreciate just how nimble LSPs (language service providers) can be. Their ability to track down translators with the necessary subject matter expertise and handle a vast array of file formats is truly remarkable. That said, localization efficiency is dependent on you, the content provider.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/0*xvwAm_eR2pJetvqB.jpg" /></figure><blockquote>flickr: Robyn Jay</blockquote><p>Although a good LSP can work with any type of content you might throw at them, their efficiency (and therefore your costs) depend on the source files. From the simplest looking Word file to the most robust XML solution, what’s lurking beneath the surface of these files could make or break your translation deadlines.</p><p><strong>1. Frankenfiles</strong></p><p>A “Frankenfile” is a term of endearment used to describe a file with absolutely no rhyme or reason behind its formatting (often, it was quite literally hacked and stitched together). When a file is full of style overrides, inconsistent style use, unconventional or inconsistent spacing, hard returns for line wrapping, and other visual formatting “hacks,” it is incredibly difficult and time consuming to properly translate the content and deliver it with the same look and feel. As a Frankenfile is updated, new hacks (or fixes) are likely to be introduced that reduce translation memory leverage. (Leverage is a measurement of how much previous translation can be reused in a translation update. It is far cheaper to use translation memory than it is to retranslate content.)</p><p>The best advice, regardless of what tool you are using, is to strictly adhere to a template or standardized style. Do not use formatting overrides to achieve a specific visual result, and do not create stylistic exceptions for “unique” content unless absolutely necessary AND unless you are committing those styles to the core template used by all files. Consistency is extremely important, particularly if the LSP needs to create custom filters to handle your style conventions in their tools. They can then create the filters once and reuse them as needed, saving precious turnaround time.</p><p><strong>2. CMS output</strong></p><p>A content management system is a wonderful thing. It keeps your content neat and tidy in a centralized location, allows you to reuse portions as needed, and likely supports a plethora of workflow automation out of the box. One of these workflows may be translation, but it may not be the workflow that your LSP had in mind. Some CMS have built-in translation UIs, some provide XML output, and others even go so far to supply XLIFF output (often considered a translation-friendly format).</p><p>All of these options are valid for a translation workflow, but do not assume that your LSP is ready and able to work in the manner your CMS dictates. You may find that what sounded good on paper doesn’t in fact work very efficiently in practice. Before approaching a localization project, and ideally before selecting a CMS, talk with your LSP to see what workflows might be more optimal than others. Conduct a trial/pilot translation using your chosen workflow to ensure that content can not only be exported, translated, and imported, but can be done so several times as revisions are introduced into the source after each translation cycle.</p><p><strong>3. Excessive wordsmithing</strong></p><p>Your content will most likely need to be updated over time. Sometimes new information is added, outdated information is removed, and incorrect information is corrected. When you edit content that has previously been translated, every edit comes at a cost; rewritten text, changes in punctuation, and even changes in spacing require a translator’s eye, and will lessen your translation memory leverage.</p><p>A best practice within a translation workflow is to only modify what absolutely needs to be updated from release to release. If you missed an Oxford comma or an a/an distinction, stop and consider whether there is value in correcting it, as these seemingly innocent edits can add up over time. Peppering these changes through a document can add an hour or more (I’ve seen cases where an entire day or more was lost to vetting fuzzy matches in a translation memory) to turnaround time.</p><p><strong>4. Graphics</strong></p><p>Graphics are a tricky beast in the localization world. Two key issues with regard to graphics are 1) translatable text within the graphics, and 2) cultural appropriateness of the images themselves.</p><p>The argument against using text in graphics has pretty much been beaten to death, but I mention it now because — believe it or not — it’s still common practice. It could be out of convenience (for either the illustrator or the reader), or habit, or not knowing. If you choose to use text in your graphics, you should plan to keep the editable unflattened source image (the raw Photoshop, Illustrator, or other image application source file), all fonts used, and keep a text/Word/Excel file with it that contains all of the text used in the graphic. This way the translator has everything needed to produce the translation. This will take some time to do, depending on how intricate your images are, but will take much less time than trying to hack translated text into a flattened JPG.</p><p>Cultural appropriateness of imagery is something that is less often considered. Sometimes the most innocent of images can come across as offensive in other cultures. Little things like gestures, fine details, and colors can make the difference between a non-issue and a dead stop when preparing content for varied cultural markets. The time spent researching and proofing for these issues before sending the files for translation pales in comparison to the time and effort spent searching for a replacement at the 11th hour, particularly when the replacement influences design changes.</p><p><strong>5. Translating deliverable files</strong></p><p>Often, we use content either from a variety of sources or from a greater pool of information when creating documentation. When readying for translation, it’s common to send out for translation only the documents that are being delivered in English. This can complicate the translation process. Specifications used for products shipped to one region may not be compatible with the needs of another region. Wording or specific types of information might also not be appropriate in another region. Finally, any changes influenced by related products — which may or may not have been available in other regions prior — may also impact translation.</p><p>It is important to consider translation at the source level to avoid these risks and ensure that your information is ready to be deployed anywhere in any language at any time. This will decrease any rework from last minute issues found by translators, allow you to build consistency into your wording choices up front, and help you realize a greater return from translation memory leverage over time.</p><p><strong>Do you have other suggestions for producing localization-friendly files? Please share them in the comments!</strong></p><p><em>And one last note about those “Frankenfiles”… Beware!</em></p><p><em>Originally published at </em><a href="http://www.scriptorium.com/2013/11/five-gotchas-that-will-affect-your-translation-turnaround-time/"><em>www.scriptorium.com</em></a><em> on November 25, 2013.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22ddc8d6b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>