<?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>Software localization blog Archives - Ciklopea</title>
	<atom:link href="https://ciklopea.com/tag/software-localization-blog/feed/" rel="self" type="application/rss+xml" />
	<link>https://ciklopea.com/tag/software-localization-blog/</link>
	<description>Approccio individuale.Soluzioni personalizzate.</description>
	<lastBuildDate>Thu, 25 Aug 2022 12:57:31 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Successful Agile Localization of ESET Antivirus Software to Croatian</title>
		<link>https://ciklopea.com/blog/success-stories/successful-agile-localization-eset-antivirus-software-croatian/</link>
					<comments>https://ciklopea.com/blog/success-stories/successful-agile-localization-eset-antivirus-software-croatian/#respond</comments>
		
		<dc:creator><![CDATA[Zana Čizmin]]></dc:creator>
		<pubDate>Thu, 10 May 2018 14:42:59 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Success Stories]]></category>
		<category><![CDATA[Agile Localization]]></category>
		<category><![CDATA[Client Interview]]></category>
		<category><![CDATA[ESET]]></category>
		<category><![CDATA[Interview]]></category>
		<category><![CDATA[IT security solutions]]></category>
		<category><![CDATA[L10n]]></category>
		<category><![CDATA[Localization]]></category>
		<category><![CDATA[localized software]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Software localization blog]]></category>
		<category><![CDATA[Successful Agile Localization of ESET Antivirus Software to Croatian]]></category>
		<guid isPermaLink="false">https://ciklopea.com/?p=12207</guid>

					<description><![CDATA[<p><em>We had a chat with Mr. Miroslav Nikolac, Business Development Manager at Nort Ltd, exclusive representative of ESET for seven countries in Southeast Europe, who was kind enough to share with us a unique insight into localization from the client’s</em><em> side.</em></p>
<p>The post <a href="https://ciklopea.com/blog/success-stories/successful-agile-localization-eset-antivirus-software-croatian/">Successful Agile Localization of ESET Antivirus Software to Croatian</a> appeared first on <a href="https://ciklopea.com">Ciklopea</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>As the exclusive regional representative for <a href="http://www.eset.com">ESET</a>, one of the world&#8217;s largest vendors of IT security solutions, <a href="https://www.nod32.com.hr">Nort Ltd.</a> covers the territories of Croatia, Bosnia and Herzegovina, Serbia, Montenegro, Kosovo, Republic of Macedonia and Albania. Nort Ltd. introduced ESET products to these markets in 2000, and the first localized version of ESET&#8217;s software became available very soon after that.</p>
<p>Our localization requirements have been steadily increasing since the early days and currently include translation of several home and business products, as well as the accompanying documentation and help resources. Since ESET upgrades its products to new versions once a year and performs minor tweaks throughout the products&#8217; lifetime, localization is performed in short, irregular cycles that can last anywhere between a week and a few months.</p>
<p>Localization of ESET software is performed as a part of the software development process, i.e. the new strings are localized as soon as they are updated. It is a typical agile localization workflow that requires fast response, good coordination and short turnaround times.</p>
<p>Translation and proofreading are performed by the linguist team in specific CAT tools (SDL Pasolo, SDL Trados Studio and/or MemoQ, depending on the type of documentation), in accordance with the previously translated and approved elements that are used as the master translation memory (TM).</p>
<p>In addition to the TM, the client-approved Termbase and Style Guide are consulted during all translation projects. The translated and proofread files are then sent to the local distributor (Nort ltd.) for review and approval.</p>
<p>Client review is an essential part of the localization process, one of the reasons being that our technical support experts are in a better position to determine whether a highly specific term requires translation, which often comes across as awkward, or should be left alone. Every time a new localized build &#8211; software version &#8211; becomes available, our technical support experts perform thorough tests on multiple operating systems and make sure that the translation is in order. Any errors or omissions are immediately reported and corrected.</p>
<p>This process is now streamlined and the application of corrections to the localized software takes up a couple of days at the most.</p>
<p>Our clients have a say in the matter as well – if we learn that the users aren’t quite clear about what a certain program function does or how to interpret our localized help resources, we take steps to clarify the translation.</p>
<p>IT security is a sensitive matter, and users certainly don’t want to see a localized IT security product with an interface that is difficult to understand. The same goes for all communication in local language with the clients, including license e-mails, program installation and setup instructions, and renewal reminders.</p>
<p>In addition to enabling the clients who feel more comfortable with their native tongue to use our products, localization does one more important thing: it demonstrates our willingness to allocate resources in order to make the products more accessible to the end user. This goes a long way towards building client confidence in the product.</p>
<p>The post <a href="https://ciklopea.com/blog/success-stories/successful-agile-localization-eset-antivirus-software-croatian/">Successful Agile Localization of ESET Antivirus Software to Croatian</a> appeared first on <a href="https://ciklopea.com">Ciklopea</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ciklopea.com/blog/success-stories/successful-agile-localization-eset-antivirus-software-croatian/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Science or Fiction: Computer-Assisted Translation Explained</title>
		<link>https://ciklopea.com/blog/translation/science-fiction-computer-assisted-translation-explained/</link>
					<comments>https://ciklopea.com/blog/translation/science-fiction-computer-assisted-translation-explained/#respond</comments>
		
		<dc:creator><![CDATA[Ciklopea]]></dc:creator>
		<pubDate>Wed, 29 Nov 2017 12:18:02 +0000</pubDate>
				<category><![CDATA[Translation]]></category>
		<category><![CDATA[CAT]]></category>
		<category><![CDATA[Computer Assisted Translation]]></category>
		<category><![CDATA[Machine Translation]]></category>
		<category><![CDATA[MT]]></category>
		<category><![CDATA[Software localization blog]]></category>
		<category><![CDATA[spell checkers]]></category>
		<guid isPermaLink="false">https://ciklopea.com/?p=10016/</guid>

					<description><![CDATA[<p>Hot on the heels of our article on <a href="https://ciklopea.com/translation/science-or-fiction-machine-translation-explained/">machine translation</a>, it’s now time to discuss <strong>computer-assisted translation</strong> or <strong>CAT</strong>.</p>
<p>The post <a href="https://ciklopea.com/blog/translation/science-fiction-computer-assisted-translation-explained/">Science or Fiction: Computer-Assisted Translation Explained</a> appeared first on <a href="https://ciklopea.com">Ciklopea</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Even though computer-assisted translation or <strong>computer-aided translation</strong> may sound like an offshoot of machine translation, it actually represents a completely different technology. It is a form of translation in which a <strong>professional</strong> <strong>human translator</strong> uses a computer software <strong>to support</strong> and <strong>facilitate</strong> the translation process, meaning it requires even more human input than MT, because translation is performed manually, but with a little help from computer science.</p>
<p>First, what you need is a software that includes a translation interface such as <strong>SDL Trados Studio</strong>, <strong>Across</strong>, <strong>memoQ</strong> or <strong>Memsource</strong>. Of course, software itself is useless without its not-so-additional “equipment”.</p>
<p>That <em>equipment</em> is what really helps you get the best of translation and it includes the following:</p>
<h3>Translation Memories (TM)</h3>
<p>The subject of translation memories could take an article for itself, but I will try to make it as short and clear as possible. <strong>Translation memories</strong> are databases containing the previously translated segments of the source texts and their equivalents in the target language that can be retrieved, used, reused or updated via CAT software during the translation process.</p>
<h3>Terminology Managers</h3>
<p>Terminology management software, or what we like to call it &#8211; <strong>termbases</strong> &#8211; are manually created bilingual or multilingual lists of specific terms relating to specific topic or field. This can be really helpful when the right term is just at the tip of your tongue, but your brain gets stuck on the thought whether or not you should have that third coffee. And it is also a great tool that enables accurate and consistent translation of specific terms.</p>
<h3>Concordancers</h3>
<p>These are the programs that look for the context of the text in monolingual, bilingual or multilingual corpus. Their outputs may serve as input to a translation memory system or as an early step in machine translation.</p>
<h3>Spell Checkers</h3>
<p>Those short deadlines got us type fast like crazy, which is why we’re in desperate need of spell checkers to make sure there aren’t any typing mistakes in our translation.</p>
<h3>Grammar Checkers</h3>
<p>In the day and age when people still have difficulties figuring out the difference between <em>their</em> and <em>they’re</em>, grammar checkers are definitely a must-have accessory. They can be either built into word processing software or used as standalone or add-on programs.</p>
<p>Of course, there are many more tools that serve as the backbone for computer-assisted translation, but it would be too extensive to fit all of them into one blog post.</p>
<p>However, this short dichotomy should be enough to clear any possible confusions regarding the machine translation and the computer-assisted translation.</p>
<p>I feel the need to say once again that there is no need for panic, since we’re not living in a science fiction movie where we’re completely replaced by robots and smart technology. Our jobs are still safe because no other creature, living or artificial, is better in word manipulation than us humans. And there will probably never be one.</p>
<p>The post <a href="https://ciklopea.com/blog/translation/science-fiction-computer-assisted-translation-explained/">Science or Fiction: Computer-Assisted Translation Explained</a> appeared first on <a href="https://ciklopea.com">Ciklopea</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ciklopea.com/blog/translation/science-fiction-computer-assisted-translation-explained/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Make Your Software Localization Project Run Smoothly – A Quick Guide</title>
		<link>https://ciklopea.com/blog/localization/make-software-localization-project-run-smoothly-quick-guide/</link>
					<comments>https://ciklopea.com/blog/localization/make-software-localization-project-run-smoothly-quick-guide/#respond</comments>
		
		<dc:creator><![CDATA[Ciklopea]]></dc:creator>
		<pubDate>Wed, 11 Oct 2017 10:54:29 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Localization]]></category>
		<category><![CDATA[L10n]]></category>
		<category><![CDATA[Software Localization]]></category>
		<category><![CDATA[Software localization blog]]></category>
		<guid isPermaLink="false">https://ciklopea.com/?p=8520/</guid>

					<description><![CDATA[<p>Many software developers are confronted with certain challenges in the software localization department that they might have trouble overcoming. Instead of trying to find an adequate solution to their problem, they just leave it as it is and hope for the best, which often results in a product that is full of bugs and glitches. It should not be forgotten that the process of localization is a complex one and requires a great deal of planning, patience and coordination, so we’ve made a list of things that should help you with L10n of your product.</p>
<p>The post <a href="https://ciklopea.com/blog/localization/make-software-localization-project-run-smoothly-quick-guide/">How to Make Your Software Localization Project Run Smoothly – A Quick Guide</a> appeared first on <a href="https://ciklopea.com">Ciklopea</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>1. Planning is everything</h2>
<p>As every software developer knows, not everything goes as planned and it is necessary to think ahead and consider possible difficulties before they occur. First and foremost, <a href="https://ciklopea.com/industries/it-and-software/">software localization </a>is not something that can be done last minute. It needs to be planned in advance, along with translation, compatibility and regression testing and other crucial stages of software development. It has been shown time and again that localization process runs the best when it is integrated into the software development process from day one. Finding a <a href="https://ciklopea.com/solutions/localization/">localization </a>partner who can integrate the language solutions into software development and work with you on agile localization projects can save you a lot of headache.</p>
<h2>2. Cutting the code</h2>
<p>It’s always a good idea to separate the main code from translatable strings and keep those strings in their own document. This helps translators focus on actual translation instead on finding what needs to be translated. It also doesn’t hurt to identify those strings and describe them as precisely as possible (i.e. title, button, image, etc.) Doing this at the very beginning makes job a lot easier and saves a lot of time and resources in advance.</p>
<h2>3. Expanding the space for translatable strings</h2>
<p>Some languages require more space than English &#8211; some of them even up to 30% more!</p>
<p>However, simply leaving extra space after each label might cause them to appear far apart from each other in compact languages. To avoid that, it is possible to align labels to the right or even place them above the controls. Other solution would be to use layout managers that understand how <em>locale</em> affects user interface.</p>
<h2>4. Avoiding concatenated strings</h2>
<p>Simplifying code by using placeholders in software development is nothing unusual, but when it comes to translation and localization, concatenated strings are better left behind. It just presumes grammar and sentence structure, which makes order of words and phrases in some way hard-coded. Obviously, that’s not the most wanted case so maybe it would be better to break sentences up into several smaller pieces.</p>
<h2>5. Rooting out hard-coded text</h2>
<p>Dates, time, currencies and other culturally specific features should definitely not be hard-coded since their format and use varies from culture to culture. Instead, it is better to have localizable strings and let translators decide what would be the best choice for their language. Also, it’s a smart move to store this type of data in a standard ISO format and use a library to format them for the given <em>locale</em>.</p>
<h2>6. Encoding the data</h2>
<p>It’s not a secret that different languages use different encoding system, but it is often hard to decide which one to use, since choosing wrong character encoding may cause translation to break, which leaves you with extra work to fix it. To avoid confusions and complications, use UTF-8 whenever possible. Ideally, every part of your project should use UTF-8, from HTML and HTTP server to database and the application itself.</p>
<h2>7. Testing the software</h2>
<p>Of course this is the logical and obligatory step in software localization so skipping it would be a terrible decision. Localized software versions should be tested as rigorously as the original one. Seeing a foreign language in context within your software might be an eye-opener for overlooked details and possible mistakes.</p>
<h2>8. Localizing documentation</h2>
<p>Every software comes hand in hand with its documentation so it’s very important to localize it as well. Users will eventually experience some problems when using your software and will probably try to find a solution under Help or User’s guide documents. Having that in mind, try to be as consistent as possible with usage of terminology and localization in general.</p>
<h2>Wrap-up</h2>
<p>Software localization is a seemingly never-ending process. Each new project comes with new challenges and problems that require unique solutions and this short guide surely can’t predict every single one of them. However, it should serve you as a good springboard for getting to know the whole process and a guiding light through the chaotic world of background code.</p>
<p>The post <a href="https://ciklopea.com/blog/localization/make-software-localization-project-run-smoothly-quick-guide/">How to Make Your Software Localization Project Run Smoothly – A Quick Guide</a> appeared first on <a href="https://ciklopea.com">Ciklopea</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ciklopea.com/blog/localization/make-software-localization-project-run-smoothly-quick-guide/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
