<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
	xmlns:atom="http://www.w3.org/2005/Atom" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/" 
	xmlns:dc="http://purl.org/dc/elements/1.1/" 
	xmlns:georss="http://www.georss.org/georss" 
	xmlns:icbm="http://postneo.com/icbm" 
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/" 
	xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" 
	xmlns:wfw="http://wellformedweb.org/CommentAPI/" >

<channel>
	<title>Translator handbook</title>
	<link>https://yacs.fr/section-194-translator-handbook</link>
	<atom:link href="https://yacs.fr/section-feed/194?id=194"  rel="self" type="application/rss+xml" />
	<description></description>
	<language>fr</language>
	<copyright>Yacs - Actupro</copyright>
	<managingEditor>christian@actupro.fr</managingEditor>
	<lastBuildDate>Sat, 30 May 2026 11:38:24 GMT</lastBuildDate>
	<generator>yacs</generator>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>70</ttl>

 <item>
		<title>i18n and l10n</title>
		<link>https://yacs.fr/article-2360-i18n-and-l10n</link>
		<guid isPermaLink="true">https://yacs.fr/article-2360-i18n-and-l10n</guid>
		<description> Internationalization and localization are terms used to describe the effort to make YACS (and other such projects) available in languages other than English, for people from different locales, who use different dialects and local preferences. 

The process of localizing a program is two-fold. It begins on the developer's end, where the developers provide a mechanism and method for the eventual translation of the program and it's interface to suit local preferences and languages for users worldwide. This step is called internationalization, abbreviated as i18n. 

Then comes the localization or l10n, the process by which the software is translated and ... suite
 </description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Tue, 22 Jan 2008 23:39:02 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2360</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2360</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2360</trackback:ping>
	</item>

 <item>
		<title>Are you the first?</title>
		<link>https://yacs.fr/article-2361-are-you-the-first</link>
		<guid isPermaLink="true">https://yacs.fr/article-2361-are-you-the-first</guid>
		<description> YACS is an open source project, and this means that translators are encouraged to contribute and to provide sets of translated strings.

Therefore, before engaging in translation, you should check the localization factory and look for the language that interests you. Also visit the localization repository for past versions of YACS.

At this step you would either join an existing group of translators for some language, or decide to support a new language. In both cases, follow instructions to ensure that other translators know about your work</description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Sun, 18 Nov 2007 11:49:14 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2361</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2361</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2361</trackback:ping>
	</item>

 <item>
		<title>Are you qualified?</title>
		<link>https://yacs.fr/article-2362-are-you-qualified</link>
		<guid isPermaLink="true">https://yacs.fr/article-2362-are-you-qualified</guid>
		<description> YACS is entirely written in English, and you need to be fluent in this language and, of course, in the language you will be translating to. Casual knowledge of either one will make translating difficult for you, or make the localization you create confusing to native speakers.

You need to be familiar with PHP, as you will sometimes need to read through the YACS code to figure out the best way to translate messages.

You should be familiar with human language constructs: nouns, verbs, articles, etc., different types of each, and be able to identify variations of their contexts ... suite
 </description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Sat, 17 Feb 2007 17:09:15 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2362</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2362</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2362</trackback:ping>
	</item>

 <item>
		<title>Understanding gettext files</title>
		<link>https://yacs.fr/article-2363-understanding-gettext-files</link>
		<guid isPermaLink="true">https://yacs.fr/article-2363-understanding-gettext-files</guid>
		<description> YACS uses the GNU Gettext localization framework. Gettext is a mature, widely used framework for modular translation of software. It is the de facto standard for localization in the open source/free software realm.

There are three types of files used in the Gettext translation framework. Depending on the tool you use to translate, you will need to be familiar with some or all of these files.

 POT (Portable Object Template) files  The first step in the localization process. A program is used to search through the YACS source code and pick out every string passed to i18n::s() or i18n::c() ... suite
 </description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Tue, 23 Mar 2010 23:38:05 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2363</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2363</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2363</trackback:ping>
	</item>

 <item>
		<title>Where can I find template files?</title>
		<link>https://yacs.fr/article-2364-where-can-i-find-template-files</link>
		<guid isPermaLink="true">https://yacs.fr/article-2364-where-can-i-find-template-files</guid>
		<description> YACS is a friendly software, but the drawback of this is that there are many strings to translate. To ease the job of translators all native strings have been spread in different files, each file having a reasonable size. 

The current policy is that each module of YACS has its own .pot file. A module is either a directory of scripts (e.g., articles, sections, ...) or the installation directory itself (the root module).

All template files are available in stable releases of YACS in the directory i18n/templates and you can use these as a starting point for translations ... suite
 </description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Fri, 06 Apr 2007 20:27:38 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2364</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2364</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2364</trackback:ping>
	</item>

 <item>
		<title>What tools to use?</title>
		<link>https://yacs.fr/article-2365-what-tools-to-use</link>
		<guid isPermaLink="true">https://yacs.fr/article-2365-what-tools-to-use</guid>
		<description> We recommend you to install translation tools at your personal workstation, since this has been proven more powerful than on-line translation services.

There are various tools available to aid in translating. Ultimately .pot and .po are plain text files, and any text editor can be used to change them. However, your work will be more efficient with dedicated tools, and you will need one at least to compile strings and generate .mo files.

poEdit An open source program for Windows and UNIX/Linux which provides an easy-to-use GUI for editing PO files and generate MO files.

KBabel Another open source ... suite
 </description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Wed, 02 May 2007 11:41:59 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2365</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2365</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2365</trackback:ping>
	</item>

 <item>
		<title>How to preserve placeholders?</title>
		<link>https://yacs.fr/article-2366-how-to-preserve-placeholders</link>
		<guid isPermaLink="true">https://yacs.fr/article-2366-how-to-preserve-placeholders</guid>
		<description> Many messages contain special PHP formatting placeholders, which allow the insertion of side strings that are either untranslatable dynamic content (e.g. a number), or complementary translated information (e.g. the label of a web link). The PHP placeholders come in two different formats:

 %s  When only one placeholder is present, this marker is used.
 %1$s, %2$s, %3$s, …  Numbered placeholders, which allow translations to rearrange the order of the placeholders in the string while maintaining the information each is replaced with.


The important thing is that you have to preserve placeholders in translated strings. And it may be ... suite
 </description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Sat, 17 Feb 2007 17:11:49 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2366</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2366</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2366</trackback:ping>
	</item>

 <item>
		<title>Tips for Good Translations</title>
		<link>https://yacs.fr/article-2367-tips-for-good-translations</link>
		<guid isPermaLink="true">https://yacs.fr/article-2367-tips-for-good-translations</guid>
		<description> Take care of spammersSince e-mail addresses of translators are featured in  .po and .mo files, translators are advised these will be used by spammers. Please ensure you are driving people to a place that is safe for you.
Don't translate literally, translate organically Being bi- or multi-lingual, you undoubtedly know that the languages you speak have different structures, rhythms, tones, and inflections. Translated messages don't need to be structured the same way as the English ones: take the ideas that are presented and come up with a message that expresses the same thing in a natural way for the ... suite
 </description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Sat, 17 Feb 2007 17:12:18 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2367</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2367</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2367</trackback:ping>
	</item>

 <item>
		<title>Where can I share new translations?</title>
		<link>https://yacs.fr/article-2368-where-can-i-share-new-translations</link>
		<guid isPermaLink="true">https://yacs.fr/article-2368-where-can-i-share-new-translations</guid>
		<description> Visit the translation factory, and create a thread with updated files there. These will be processed by the development team afterwards, and released either in a next official YACS version (for French and English), or as a separate language pack</description>
		<dc:creator>Bernard</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Sat, 17 Feb 2007 17:24:29 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2368</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2368</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2368</trackback:ping>
	</item>

 <item>
		<title>Poedit Tips for new Translators</title>
		<link>https://yacs.fr/article-2937-poedit-tips-for-new-translators</link>
		<guid isPermaLink="true">https://yacs.fr/article-2937-poedit-tips-for-new-translators</guid>
		<description> Introduction and tips for new translators working with PoEdit</description>
		<dc:creator>William Koch</dc:creator>
		<category>Translator handbook</category>
		<pubDate>Tue, 12 Jan 2016 09:59:21 GMT</pubDate>
		<comments>https://yacs.fr/section-194-translator-handbook#comments</comments>
		<slash:comments>1</slash:comments>
		<wfw:comment>https://yacs.fr/comments/post.php/article/2937</wfw:comment>
		<wfw:commentRss>https://yacs.fr/comments/feed.php/article/2937</wfw:commentRss>
		<trackback:ping>https://yacs.fr/links/trackback.php?anchor=article%3A2937</trackback:ping>
	</item>

</channel>
</rss>