Pedro Mendonça

<p>Adds the CSV format to GlotPress to export/import translations and originals.</p>
<p>This allows you to export a translation set to a CSV file, and use this to import the translations or originals into the project.</p>
<p>This plugin is properly prepared for localization.</p>
<h3>The CSV Format</h3>
<p>The CSV output has values separated by <code>,</code> and enclosured by <code>" "</code>.</p>
<p>The total number of columns depends on the number of Plural Forms of the exported Locale.</p>
<p>For an sample file, please check out <a href="https://github.com/pedro-mendonca/GP-Format-CSV/blob/main/example.csv" rel="nofollow ugc">example.csv</a>.</p>
<p>The header columns for the different translations have the <code>Translation (<plural-form>)</code> naming convention, being the Plural Forms depending on each exported Locale.</p>
<p>See the example below for a <strong>Portuguese</strong> CSV export, which has <code>2</code> plural forms.</p>
<h4>The exported CSV in plain text</h4>
<pre><code>"Context","Singular","Plural","Comments","References","Translation (Singular)","Translation (Plural)"
"","Singular in English.","","Comment 1.\nComment 2.","","Singular em Português.",""
</code></pre>
<h4>The main columns</h4>
<p>The 5 main columns are <code>Context</code>, <code>Singular</code>, <code>Plural</code>, <code>Comments</code> and <code>References</code>.</p>
<h4>The Plural Forms variable columns</h4>
<p>The number of Plural Forms columns may vary depending on each Locale setting.</p>
<p>Check the below table for examples of <a href="https://github.com/GlotPress/GlotPress/blob/develop/locales/locales.php" rel="nofollow ugc">GlotPress Locales</a> from 1 to 6 Plural Forms.</p>
<h3>Included filters</h3>
<p>The <code>gp_format_csv_header</code> allows you to add, remove or customize items from the CSV header.</p>
<p>The <code>gp_format_csv_row</code> allows you to add, remove or customize items from the CSV row.</p>
<h3>Usage</h3>
<h4>Export translations to CSV</h4>
<ol>
<li>Go to the bottom of the translation table.</li>
<li>Select <code>CSV (.csv)</code>.</li>
<li>Click on the <code>Export</code> link to download the CSV file.</li>
</ol>
<h4>Import translations from CSV</h4>
<ol>
<li>Go to the bottom of the translation table.</li>
<li>Click on the <code>Import Translations</code> link.</li>
<li>Select the CSV file to upload, the <code>Format</code> is <em>Auto Detected</em>.</li>
<li>Click on the <code>Import</code> button.</li>
</ol>
<h4>Import originals from CSV</h4>
<ol>
<li>Go to the project page.</li>
<li>On the project actions click on the <code>Import Originals</code> link.</li>
<li>Select the CSV file to upload, the <code>Format</code> is <em>Auto Detected</em>.</li>
<li>Click on the <code>Import</code> button.</li>
</ol>


CSV Format for GlotPress

Adds the CSV format to GlotPress to export/import translations and originals.

<p>If your want to present your blog in different languages (totally with title, rss, categories working, not just the post) and allows visitors to pick the language they want, this plugin is for you.</p>
<p>xLanguage is a full featured plugin allows you to blog in different language, and allows user to select which version to read.  It works for blog post, page, tags, categories.  The user language preferences will also select the right theme and plugins MO files.</p>
<p>Customization is the No. 1 design goal, after all that’s probably the reason why you want to setup a multilingual blog.   The language configuration combination is highly customizable to facilitate multiple fallbacks.  Every UI is extracted out, which could be optionally overridden by theme design without touching the plugin file at all.</p>
<p>The language preference is detected from browser’s preferences, as well as from Cookie if user visited before. Widget and template functions are also provided to allow user to switch the language easily. The presentation of the template functions can also be customized in your theme folder without touching the code in the plugins.</p>
<p>See <code>Other Notes</code> for the comparisons against similar plugins.</p>
<h4>Feature Highlights</h4>
<ul>
<li>Does not touch the WordPress database schema at all. All language text are stored in the same post and hence more friendly to other plugins.</li>
<li>For post that written in reader’s foreign language. You could hide them, or optionally show them with a notice prepended. Your choice!</li>
<li>Optionally present a total independent view to the search engine crawlers. So that you can have all languages text being crawled under a single URL. Think of SEO!</li>
<li>Each language can be presented in a different theme.</li>
<li>Language composing are done in inline instead of separated side by side posting, see Screenshot 1. The former is like Simplified/Traditional Chinese within Wikipedia-ZH, while latter is like Wikipedia-Zh and -EN version.</li>
<li>Many-to-many mappings between viewable language and authoring language is possible. Hong Kong-based reader could read Cantonese and Chinese, but average Chinese reader could only read Chinese, xLanguage specifically enables this scenario!</li>
</ul>
<h4>Usage Guide</h4>
<p>To fully enjoy the power of customization, please refer to the usage guide hosted on my <a href="http://hellosam.net/project/xlanguage" rel="nofollow ugc">blog project page</a>.  Also see my blog for live demostration.</p>
<p>There are some <a href="http://hellosam.net/project/xlanguage" rel="nofollow ugc">known problems and limitations</a>, please make sure you are aware of those.</p>
<h4>Change Log</h4>
<p>Please refer to my <a href="http://hellosam.net/project/xlanguage" rel="nofollow ugc">blog page</a> for recent changes.</p>
<h4>Upgrade Notice</h4>
<p>Permalinks <code>Postfix</code> appending position is known to be not working with WordPress 2.7 paged comments mode and potentially causing conflicts with many other plugins.  The mode will be changed to <code>Prefix</code> when you upgrade from v1.x. If you are using the <code>Postfix</code> mode and want to keep using it, please change the settings manually.</p>
<h3>Comparisons</h3>
<h4>Compare to qTranslate v2.0.2 (Jan 2009)</h4>
<p>The logic behind qTranslate is similar to that of xLanguage – both using HTML tag to differentiate the contents of languages and requires no database modification. qTranslate uses HTML comment tag while xLanguage uses the lang=”..” attribute.</p>
<p>The major differences lie within the admin interface, qTranslate provides strong Admin UI integration such that user enters the title, the category name and so on in independent textbox. The post is also to be post to an independent editor. While xLanguage, user enters the data in the same input box. For authoring in language that are very similar (like Cantonese and Written Chinese), and that cross-authoring is common, the method that xLanguage use will reduce much duplication work.</p>
<p>Due to the above restriction, qTranslate supports only one-to-one mapping between authoring and viewable lanugage. while xLanguage does not have this restriction. And hence, xLanguage allows all texts to be presented under one single URL for search engine to crawl with. (Think of SEO)</p>
<p>Feature-wise, xLanguage currently lacks of Pre-domain URL Permalinks mode, as well as automatic MO file download. (Note: MO does work in xLanguage but just have to be downloaded manually). Contribution would certainly help in accelerate these getting done :).</p>
<h4>Compare to Gengo v2.5.3 (Jan 2009)</h4>
<p>Gengo v2.5.3 is not tested with WordPress 2.7 according to the published plugin info.</p>
<p>In Gengo, each translations is a standalone post, linked to the original post.  It enables you to create maps between different content.  Think of different language version of Wikipedia, basically Gengo is the same – and it helps you to maintain such link table.</p>
<p>In xLanguage, everything is in the same post.  The xLanguage approaches make no structural changes to the WordPress itself, and hence should be easier maintain.  No extra magic in xLanguage is needed to keep the commenting, searching, popularity counter works.</p>
<h4>Compare to Language Switcher v1.11 (Jan 2008)</h4>
<p>This is actually the plugin that inspired me to build the xLanguage.  The Language Switcher and the xLanguage is working in a very similar way — Both enable multilingual post by tagging the it.  The Language Switcher uses square bracket instead of HTML tag, but have no assisting tools when composing the post.  The language code is limited to the length of 2, and offer no fallbacking and overlapping possibility.  The permalink url tag must be placed at the end.</p>
<p>Same as xLanguage, it allows user to enable multilingual functionality on single line content like tag, title and such.</p>
<h4>Compare to jLanguage v1.4 (Jan 2008)</h4>
<p>Almost the same as Language Switcher, both functionality and working principle.  However, jLanguage v1.4 does not have widget for user to select their favorite language.  In addition, It currently offer almost no customization, plus it does not work for single line content.  The language selection could not affect the MO file selection.</p>
<p>It enables the language tagging by using square brakets instead of standard tag, similar to that of Language Switcher.</p>
<h4>Compare to Multilingual post v0.2 (Jan 2008)</h4>
<p>Please be aware that Multilingual post v0.2 does not belong to this category at all.  It does not enable poster to publish mixed language in a post.  The user also cannot selectively view the post in a particular language.</p>
<p>It only does insert the lang=”..” tag at the HEAD such that browser can render the page better.  xLanguage also does this.</p>
<h4>Compare to Bunny’s Language Linker v0.2 (Jan 2008)</h4>
<p>Bunny’s Language Linker’s way to enable multilanguage blog is minimal and simple, yet the integration is very loose.  It works like Gengo, the pros and cons compare to xLanguage is very similar.</p>
<h4>Compare to Basic Bilingual v0.31 (Jan 2008)</h4>
<p>Basic Bilingual v0.31 allows you to insert a summaries in a different language.  It is yet another very simple plugin.</p>


xLanguage

Allows you to blog in multi-language, and users to select which to read.  Works on every blog UI elements, not just the post.

CSV Format for GlotPress vs xLanguage