maximeschoeni

<p>Sublanguage is a multilanguage plugin for wordpress.</p>
<h4>Concept</h4>
<ul>
<li>no duplicated content (untranslated or untranslatable data inherits main language value)</li>
<li>no additional database table (translation data is stored in post_meta)</li>
<li>no markup added into content (unlike q-translate)</li>
<li>no cookies (language is defined solely by URLs, better for SEO)</li>
</ul>
<h4>Features</h4>
<ul>
<li>[NEW] support for Gutenberg (beta feature)</li>
<li>translation UI for posts content, title, permalink, excerpt and meta (for posts, pages and custom posts)</li>
<li>translation UI for terms name, slug and description</li>
<li>translation UI for attachments title, caption, description, alt and meta</li>
<li>translation UI for nav menus</li>
<li>translate localized text</li>
<li>translate login, password change, etc.</li>
<li>translatability: define which content is translatable or not</li>
<li>URL rewrite: translate posts and terms permalinks and child pages path</li>
<li>support revisions</li>
<li>support multisite</li>
<li>extendable</li>
</ul>
<h4>Notes</h4>
<p>In version 2.9, a security vulnerability (“The plugin settings can be executed by lower privilleged (sic) user”) was reported for Sublanguage. In order to ease the fixing, we chose to permanently remove a few under-used features concerned by this exploit in v 2.10. Please write in the forum if you disagree with this choice.</p>
<ul>
<li>remove automatic upgrade from version 1.x (version 2.0 is now about 10 years old).</li>
<li>remove a quick edit button in classic editor that was available width Tinymce Advanced plugin.</li>
<li>remove the possibility to translate options (Options translated so far will still works as usual in the front-end, you just no longer can edit translations in the back-end).</li>
</ul>
<h4>Documentation</h4>
<p>Plugin documentation is available on <a href="https://github.com/maximeschoeni/sublanguage" rel="nofollow ugc">github</a></p>
<h4>Extensions</h4>
<ul>
<li><a href="https://wordpress.org/plugins/sublanguage-switcher-widget/" rel="ugc">Sublanguage Switcher Widget</a> by <a href="https://profiles.wordpress.org/geschke" rel="nofollow ugc">Ralf Geschke</a></li>
</ul>
<h4>Thanks</h4>
<ul>
<li><a href="https://profiles.wordpress.org/uggur" rel="nofollow ugc">uggur</a> for Turkish translation</li>
</ul>


Sublanguage

Sublanguage is a lightweight multilanguage plugin for wordpress.

livewords1

<p>The Livewords Flow plugin connects a WordPress installation to Livewords Flow using the WPML plugin.</p>
<h4>Prerequisites</h4>
<ul>
<li>This plugin is dependent on WPML.
<ul>
<li>Minimum supported WPML version is 3.6.3</li>
<li>When WPML is not installed or if it is deactivated, the Livewords Flow plugin settings page shows a message saying that you should install WPML.</li>
</ul>
</li>
<li>API settings
<ul>
<li>You must provide an API URL (including protocol), Account domain and Livewords Flow API ID. These can be obtained from Livewords. After these settings are saved, you can use the ‘Test API connection’ button to see if you can connect successfully.</li>
</ul>
</li>
<li>WPML Settings
<ul>
<li>On the Livewords Flow plugin settings page there is a section called ‘WPML settings’.<br />
This is for information purposes only; WPML should be configured properly and be in working order before continuing with the Livewords Flow plugin.<br />
The settings display the default language and the target languages. You can edit these on the WPML settings page.</li>
</ul>
</li>
</ul>
<p>The Livewords Flow plugin fully follows the WPML workflow. It automates certain key actions of this flow, but every action can still be performed solely with the WPML plugin. Moreover, if the Livewords Flow plugin were to be uninstalled, the theme continues to function as a multi lingual website with all finished translations unaffected and functional.</p>
<p>More information on the WPML plugin can be found at <a href="https://wpml.org/documentation" rel="nofollow ugc">wpml.org/documentation</a></p>
<h4>Installation guide</h4>
<p>Before installing and activating this plugin, you should have an installed and working WPML configuration. Please refer to the <a href="https://wpml.org/documentation" rel="nofollow ugc">documentation</a>.<br />
Once everything is working properly, you can install and activate this plugin. After filling in the required API URL, Account domain and Livewords API ID, you can continue with the custom field section.</p>
<h4>Custom fields</h4>
<p>Post types can contain custom fields.<br />
These could be little pieces of information that do not belong to the body text of the post, or they can control the behaviour of your installed theme.<br />
There is a plethora of plugins that utilise these fields, either under the hood or as fields to be completed by the admin user.<br />
Many theme builders also use custom fields.</p>
<p>In this section, you can select which custom fields are to be sent to Livewords Flow for translation. All found custom fields are listed with a maximum of 5 value examples and a link to the post they belong to. This way, you can get a good idea of which fields contain translatable content and which fields do not.<br />
Once you have made your selection and saved it, you are good to go.</p>
<p>Next, it is time to test one or more posts, probably working together with the Livewords team to see if translations are received correctly. After everything has been set up, you can translate all existing content with the bulk translate functionality.</p>
<h4>Edit content manually</h4>
<p>You can use the WPML plugin and completely ignore the Livewords Flow plugin.<br />
Bear in mind however that manually performed translations will be overwritten by the Livewords Flow plugin whenever a translation is received.</p>
<h3>Making a post type translatable</h3>
<p>WordPress uses so-called post types to distinguish different kinds of posts, so technically, a ‘page’ is also a post.<br />
WordPress comes with a ‘post’ and a ‘page’ post type, but many WordPress implementations have more post types than these two.<br />
You can configure which post types should be translatable in the WPML settings page, or you can toggle this setting on the Edit page of a particular post type.</p>
<p>Once set for translation, the relevant post type is listed in the ‘Content’ section of the Livewords Flow plugin settings page with a ‘bulk translate’ button.<br />
A ‘Translate’ button and settings are also displayed on every Edit page of that particular post type.</p>
<h3>Single post settings</h3>
<p>Every translatable post will be requested in all available target languages by default.<br />
You can override this behaviour in the ‘Translate in the languages’ section on the Edit Post page.<br />
You can toggle individual target languages on and off, so a particular language will not be scheduled for translation either in a bulk translation request or in a single post translation request.<br />
Every change in the settings must be saved by hitting ‘Update’ in order for it to take effect.</p>
<h3>Single post translation</h3>
<p>On the Edit Post page you will see the Livewords Flow Translation box and the (WPML) Language box.<br />
This plugin follows the same paradigms as WPML. So every translation is also a (target) post, with a connection to the source post.<br />
On every Edit page of a <em>target</em> post you will see a message telling you that in order to use the Livewords Flow plugin, you have to navigate to the <em>source</em> post.<br />
We have added a link to the source post for your convenience.</p>
<p>You can check if a post already has translations (either created by Livewords Flow or manually) by looking at the ‘Translate this Document’ section.<br />
A plus sign at the target language indicates that there is no translation yet, a pencil sign indicates that there is a translation for this post in that language.<br />
The translation may be out of date, of course.</p>
<h4>Post status</h4>
<p>In WordPress, every post has a status such as ‘Draft’ or ‘Published’.<br />
All words newly translated using Livewords Flow (posts that have never been translated before) have a ‘Draft’ status and must be set to ‘Published’ manually.<br />
This can optionally be achieved by performing a ‘Bulk action’ in the WordPress post listing.</p>
<p>All existing translations will <em>keep</em> their post status after a translation update. The same goes for bulk translations.</p>
<p>New post</p>
<p>When creating a new post, the Livewords Flow Translation box will indicate that you first have to fill in all mandatory fields and save the post before you will be able to request translations.</p>
<p>After saving the post for the first time, the Translation status of the post will be <em>Untranslated</em>.<br />
This status only changes after a translate request and will never reoccur for that particular post.</p>
<p>After the translate request, the Translation status will read <em>In progress</em>.<br />
When a translation is received, a WPML-connected post will be created and updated with the translated information.<br />
The status reads <em>Incomplete</em> until all requested translations have been received, after which the status will read <em>Translated</em>.</p>
<p>Existing post</p>
<p>Translating an existing post is basically the same as translating a new post. This post can also have the status <em>Untranslated</em>, which means that the post already existed when the Livewords Flow plugin was installed. But all other statuses are possible as well.</p>
<p>Translation log</p>
<p>Every post has a translation log. This is a collapsible log, which shows the requests and responses received for each post. It is mainly used for debugging.</p>
<h3>Bulk translation</h3>
<p>Bulk translation can be performed for each post type. The bulk action will request a translation for every post that has the <em>Untranslated</em> or <em>Modified</em> status.<br />
The single post setting regarding target languages is applied in the request. The status of the translation request can be viewed in the same way as a single post translation request.</p>
<p>If there are no pending items left, you can execute a forced request for all posts of that post type by clicking ‘Translate anyway’.<br />
When performing this action, all translation statuses will be ignored, but the single post target languages setting is not.</p>
<h3>Taxonomies</h3>
<p>Only categories and tags are marked as translatable by WPML by default.<br />
If your theme utilises more taxonomies, you can enable them in the WPML settings page under Translation options > Custom taxonomies.<br />
The Livewords Flow plugin setting page has a ‘Translate taxonomies’ button. The plugin will request a translation for every translatable taxonomy.<br />
Taxonomies do not have status or language settings.</p>


Livewords Flow

The Livewords Flow plugin connects a Wordpress installation to Livewords Flow using the WPML plugin.

Sublanguage vs Livewords Flow