Translation

Allows a complete uninstall and cleanup of qTranslate X meta-tags or importing translations into WPML

This plugin can either cleanup the qTranslate X meta-HTML tags from your site and leave just one 'clean' language, or migrate all languages to WPML's format. Very important: This plugin will modify the entire content of your database. You must backup your database before attempting to use it. For complete documentation, please refer to the qTranslate uninstall and WPML importer documentation. qTranslate X uninstall and cleanup mode Notice: this mode is temporary not supported. We are working to reintroduce this feature. This mode is intended if you just want to keep one language in your site and you want to clean up the language meta-tags that qTranslate added. For this mode, you don't need WPML. Instructions: Save all qTranslate X settings Go to the Plugins admin page and de-activate qTranslate X Install & activate QT Importer Go to Options -> QT Importer, select language to keep and click Start. Migrate all languages from qTranslate X to WPML In this mode, the QT import plugin will convert the language information from qTranslate's language tags format to WPML's post-per-language format. For this to work, you must have WPML active in the site (but not necessarily configured). Instructions: Save all qTranslate settings Go to the Plugins admin page and de-activate qTranslate X Have WPML activated, but not yet configured (just activated) Install & activate QT Importer Go to Options -> QT Importer and click Start Add redirects from old URLs to new URLs The import runs in small batches so it doesn't have timeout issues with large databases. You can run it on sites of any size. During the import process, the plugin generates a set of URL redirect rules. These rules tell visitors and search engines that the URLs in your site have changed (from qTranslate's format to WPML's format). When the import completes, you'll be able to export these rules either as rewrite directives for your .htaccess file or as a PHP file to add to the theme. You can skip the redirect rules, but then, incoming links to internal pages may lead to 404 pages. The import tool converts posts, meta data and taxonomy. We tried to take every possible scenario in mind, but there's no alternative to manual testing. Please consider spending time reviewing the final result and possible doing some last touch-ups before relaunching the site with WPML.

qTranslate X

3.4.6.8

248

433709

Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=QEXEK3HX8AR6U Adds a user-friendly multilingual dynamic conten

The plugin offers a way to maintain dynamic multilingual content on a WordPress site. While static localization is already excellently implemented and offered by WordPress framework through po/mo file framework, it is still impossible to maintain dynamic multilingual content without an additional specialized plugin, a kind of which qTranslate-X belongs to. For example, what if you need to make title, content and excerpt of a page to be multilingual? In theory, it could be handled by po/mo files, but in an insanely inconvenient way. To deal with dynamic content, qTranslate-X provides language switching buttons on applicable admin editing pages, which, once pressed, make all the text of multilingual fields to be filled with the language chosen. The instant language change happens locally in your browser without sending an additional request to the server, which makes it most convenient for bi-lingual or few-lingual sites, for example, owners of which perform the translation of content on their own. qTranslate-X does not provide a way to translate static strings, assuming that this part is already implemented and handled by the WordPress localization framework. The plugin provides a way to designate which fields on a page or post are to be multilingual. Once a field is declared multilingual, it will be distinguishably highlighted (in a customizable way) on admin side. At frontend, the value of active language, as defined by a page viewer, is extracted from multilingual field to be displayed within HTML context. Thus, a concept of multilingual field is in use here, as opposite to a concept of whole separate page or separate site for each language, as it is done in a number of other multilingual content management plugins, see, for example, free Polylang or paid WPML. Each plugin has its own pros and cons, please, choose carefully the one which suits your needs the best. Plugin qTranslate-X provides a convenient way to describe which fields need to be multilingual through a JSON-encoded configuration file as described in Integration Guide. It makes it easy to integrate your theme or other plugins with qTranslate-X. A JSON-encoded file, named i18n-config.json, such as the one used by qTranslate-X itself, may be provided by themes and plugins within their distribution. Plugin qTranslate-X picks up and load those configuration files on activation of a plugin or on the switch of a theme. Such a configuration file can potentially be employed by any other multilingual plugin. The developers are encouraged to contact us to discuss a common standard for the i18n-config.json configuration file. The plugin does not currently offer any kind of translation services. The team has conducted an online survey to find out how people translate their content. You are welcome to make your entry too. It appears so far, that translation service is not an immediate need. Administrators normally have their ways to translate the content, but they need a convenient way to enter translated content into an appropriate place, which this plugin is designed to help for. Translation services might still be provided in the future releases as a paid feature. Plugin qTranslate-X makes creation of multilingual content as easy as working with a single language. Here are some features: One-click local switching between the languages - Changing the language as easy as switching between Visual and HTML. Comes with a number of languages already built-in - English, German, Simplified Chinese, for example, and many more. Language customizations without changing the .po/mo files - It stores all the translations in the same post fields, while shows it to user for editing one by one depending on the language to edit chosen. In-line syntax '[:en]English Text[:de]Deutsch[:]' or 'English TextDeutsch' for theme-custom fields gets them translated - See FAQ for more information. Language tag encoding allows strings like this '[:en]English Text[:]<html-language-neutral-code>[:de]Deutsch[:]<another-html-language-neutral-code>', with language-neutral text embedded. Multilingual dates out of the box - translates dates and time for you. Theme custom fields can be configured to be translatable too. Choose one of a few modes to make your URLs look pretty and SEO-friendly, for example, the simple and beautiful /en/foo/, or nice and neat en.yoursite.com, or everywhere compatible ?lang=en. One language for each URL - Users and SEO will thank you for not mixing multilingual content. qTranslate-X supports unlimited number of languages, which can be easily added/modified/deleted via a comfortable Configuration Page at Settings->Languages. Custom CSS for "qTranslate Language Chooser" widget configurable via its properties. Menu item "Language Switcher" to enable language choosing from a menu. To generate language-specific sitemaps for better SEO support, use Google XML Sitemaps or 'XML Sitemaps' under Yoast SEO. Please, report a successful use of other sitemap plugins. The website qTranslate-X explained provides and keeps updated a few useful listings: The list of plugins, which provide integration of qTranslate-X with other popular plugins. The list of some plugins reported to be compatible with qTranslate-X without an additional integrating plugin. The list of some plugins reported not to be currently compatible with qTranslate-X. The list of Know Issues. If you encounter a conflicting plugin, please let us know, and meanwhile try to use other plugin of similar functionality, if possible. This plugin has started as a descendant of qTranslate, which has apparently been abandoned by the original author, Qian Qin. At this point, qTranslate-X has many new features and hardly resembles its ancestor. Neither it is a straightforward compatible with older plugin. One will need to carefully read Migration Guide in order to switch a site from old qTranslate to qTranslate-X. You may still find some useful information through reading qTranslate's original documentation, which is not duplicated here in full. There are also other plugins, which offer multilingual support, but it seems that Qian Qin has a very good original back-end design, and many people have been pleasantly using his plugin ever since. It stores all translations in the same single post, which makes it easy to maintain and to use it with other plugins. However, the user interface of former qTranslate got out of sync with the recent versions of Wordpress, especially after WP went to TinyMCE 4. There is a number of forks of qTranslate, see for example, mqTranslate, qTranslate Plus and zTranslate. They all try to fix qTranslate's user interface preserving its original back-end, which is what this plugin does too. This plugin is a hybrid of all of them and fixes a few bugs in each of them. It also has many new features too, like theme custom translatable fields, for example. We hope that this plugin is the most complete working version which combines the best features of qTranslate, mqTranslate, qTranslate Plus and zTranslate. We organized an anonymous entity qTranslate Team to maintain a joint authority of all qTranslate-ish plugins. Anyone is welcome to join with a contribution. Participating plugin authors should share the support efforts for each other. GitHub repository is available: https://github.com/qTranslate-Team/qtranslate-x.git. We thank our sponsors for persistent help and support: Citizens Law Group Gunu (Marius Siroen) Lightbulb Web Agency OptimWise Pedro Mendonça pictibe Werbeagentur This plugin is not free in terms of money, the users, who start using it on permanent basis, should signup for DONATION PLAN.

Multi-Language Framework

0.1

8709

Handles creation of multilingual content.

Handles creation of multilingual content. This plugin is a work in progress and an effort to be an alternative for handling with multiple languages in a single WordPress translation. Here is a description of how it works: Current solutions and why I dont like them: Q-Translate -> saves the content of the post int the same post_content field of the database, separating the languages with html comments.. When the theme outputs the content of a post, it gets filtered and displays only one language. Appart from that, this is an excelent plugin. But I junt cant sleep well at night knowing my database is like this... WPML -> creates a lot of extra tables in a complex database structure and is associated with a translating service. In the top of that, the plugin does a lot more than juts adding the multi language support and claims itself as a cms solution for wordpress... I like plugin that do only one thing very well done. How do I think that can be done? 2.1 translating posts First, I think it can be done without adding any extra table or doing anything out of the database structure. The approach Im using is to treat translations as post types. So, for instance, if I would translate my posts to spanish, there would be the native "post" post type and the plugin would add the "post_translation_es" post type. In the edit posts screen, there would be an extra column called 'translations' that would show for each post if it already have the spanish translation. If it has, there is a button 'edit', if it dont, 'add'. If you go to the edit screen of the spanish posts, you would see the same thing, the other way round. This part is already coded and working fine. 2.2 translating everything else (appart from taxonomies) I think its nice to be able to translate everything on the site (The site title, te text of a text widget, etc). So what Im trying to do is to add a filter in get_option() and update/add_option() to allways check which language are we visiting right now (int the front end or the admin, does not matter) and allways look for a corresponding option in the current language. For instance.. if you do a get_option('option_name') and are visiting the spanish site, it will try to find an option called 'option_name_es'. If there is not, it will get the default. Same thing when saving.

PO/MO Editor

1.4.2

35005

POEditor

0.9.2

30717

This plugin will let you manage your POEditor translations directly from Wordpress via the POEditor API.

Multisite Language Switcher

1.0.8

225202

A simple, powerful and easy-to-use plugin that will help you to manage multilingual content in a multisite WordPress installation.

MultiLanguage Site

2.1

7700

Donate link: http://paypal.me/tazotodua Author URI: http://www.protectpages.com/profile Plugin URI: http://www.protectpages.com/ Multi-Language sit

qTranslate support for WooCommerce

1.1.0

16105

Qtranslate Slug

1.1.18

107099

Adds support for permalink translations to QTranslate-X

Plugin Name

Version

Rating

Reviews

Downloads

Flag

WPTB Language

1.1.0

27628

With this plugin you can easily switch the WordPress language. It will download and install the language files from the WP Repository as needed.

WordPress Language

1.2.1

147743

Integration: Yoast SEO & qTranslate-X

Run localized WordPress sites easily. Select the language and everything else happens automatically.

1.1.1

108242

Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=QEXEK3HX8AR6U Enables multilingual framework for plugin "

Enables qTranslate-X multilingual framework for plugin Yoast SEO. We appologize for the recent change of the plugin name from “Yoast SEO & qTranslate-X” due to WordPress request in the effort of cleaning up and enforcing plugin naming policies, especially with respect to trademark guideline #17: no plugin name should start with other plugin name. At least version 3.4.5 of qTranslate-X is required. This plugin is currently a work in progress, please review the Known Issues and report the features, which did not work for you. Please, do not contact Yoast SEO plugin developers asking to fix issues of this plugin, since they have their hands full with their own problems and they do not have neither time nor capability to consider and to work on the problems of this integration plugin. The biggest issue is that “Page Analysis” has not yet been fully integrated, and it is disabled unless Single Language Editor Mode is in use, which can be set on “Advanced” tab of “Languages” configuration page: /wp-admin/options-general.php?page=qtranslate-x#advanced. If you have time and resources, please feel free to submit pool request to the plugin repository at GitHub with the implementation of “Page Analysis” for other editor modes. However, it may not be possible without asking Yoast to put a few additional filters within “Yoast SEO” plugin code. Known Issues Yoast SEO “Page Analysis” is not yet integrated and is mostly disabled to prevent confusions. It is only experimentally enabled in Single Language Editor Mode, which can be set on “Advanced” tab of “Languages” configuration page, /wp-admin/options-general.php?page=qtranslate-x#advanced. If you have time and resources, please feel free to submit pool request to the plugin repository at GitHub with the implementation of “Page Analysis” for other editor modes. Unfortunately, it may not be possible without asking Yoast to put a few additional filters within “Yoast SEO” plugin code. [plugin Yoast SEO issue] When XML Sitemaps are enabled on Yoast configuration page /wp-admin/admin.php?page=wpseo_xml and Yoast plugin is deactivated, it clears rewrite rules needed for sitemap to function. On next activation of Yoast plugin, sitemaps no longer function until their functionality is deactivated and then activated again on Yoast configuration page “XML Sitemaps”. [Resolved in plugin version 1.0.2 under qTranslate-X 3.4.4] Field ‘Meta description’ is not coming back correctly after saving. In some configurations it works though. The nature of conflict is not yet known. You would need to keep this field empty, if you are affected. [not really an issue] Sitemaps do not work quite right in Query URL Modification Mode. Query Mode is not supposed to be used for SEO.

WooCommerce & qTranslate-X

1.3

69654

Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=QEXEK3HX8AR6U Enables multilingual framework for plugin "

This plugin enables qTranslate-X multilingual framework (version 3.4.6.1 or later) for WordPress plugin WooCommerce – excelling eCommerce (version 2.3.5 or later). After the activation, depending on your theme, you may need to do the following additional step to finalize the configuration: In all customizable template files, replace calls to bloginfo('xxx') with bloginfo('xxx','display'), if you have any. You do not have to do this, if title of your blog appears correctly everywhere you can see it (especially in emails sent), or if you do not localize the name of your blog. This plugin is not supported by the authors on the WordPress forum due to its simplicity. If you find a field which is not translatable, follow the pattern how it is done in the code for other fields and make it translatable. Then submit a pull request at GitHub to enable your changes for everyone else. Is is a very good idea to review “Known Issues” in order to have right expectations. Known Issues Product Attribute may need to be re-saved (page /wp-admin/edit.php?post_type=product&page=product_attributes&edit=xxx) if they were created before installing this plugin: WP Topic. Product Attribute values are shown in admin language and do not respond to LSB. This is a convinience feature, which needs more work to be intergarated, but otherwise it is functional and usable. Custom Product Attributes (which are entered directly on product edit page /wp-admin/post.php?post=xxx&action=edit) have to be entered in raw multilingual text, with values like [:en]EN Val1[:de]DE Val1[:] | [:en]EN Val2[:de]DE Val2[:], leaving separator ‘|’ outside of language tags. This piece has not yet been integrated on admin side, but once all is entered in raw multilingual format, it should work well at front end. Delete and freshly re-create an attribte under this plugin, if it was created before installing this plugin and it misbehaves. Admin e-mails sent by pressing one of the buttons in column ‘Actions’ on order list page, /wp-admin/edit.php?post_type=shop_order, go in the original customer language used to submit the order. However, same e-mails sent using the “Resend order emails” option in order editor page, /wp-admin/post.php?post=nnn&action=edit, go in the mixed language of admin and customer. As a workaround, you can switch the admin language to the customer language before resending an e-mail (which shouldn’t happen too often). Use raw multilingual format with language tags [:en]...[:] or {:en}...{:} in any regualar field, which you wish to be multilingual. It most likely will be translated at front end appropriately. Report the field at GitHub if you found one that does not get translated at front end. Already known fileds: all fields on “Variable Product/Variations” section. Former Known Issues [Resolved in ver. 1.2] HTML header title on admin page /wp-admin/edit-tags.php?taxonomy=xxx&post_type=product displays raw multilingual values. [Resolved in ver. 1.2] Two buttons, “Add New XXX” and “Search XXX”, on attribute editor page, /wp-admin/edit-tags.php?taxonomy=xxx&post_type=product, are displayed with raw multilingual text. This should be fixed with a later

My WP Translate

1.0.2

100

34528

Google Translate WordPress » WP Translate

Simple yet powerful Translate plugin for WordPress. Can be used with most of the themes and plugins which support translation.

4.8.2

140005

Do you need to translate your WordPress content? WP Translate adds the multilingual power of Google Translate to your site. Allow your visitors to rea

Plugins Language Switcher

1.4.4

71284

It changes WordPress back-end language according to user selection.

xili-language

2.21.2

233133