11 Responses

  1. Gregory Karpinsky
    Gregory Karpinsky September 16, 2016 at 06:09 | | Reply

    Hi Nagdy,

    1.3 Media Translation – may be convenient but not really necessary. The ALT is editable when you add media to the post. Caption – too. And of course, you can use different images for each language.

    6. Translate Different Slugs – it’s funny, but specifically in WC, their own translation of ‘product’ to ‘produit’, ‘produkt’, etc. may conflict with a multilingual plugin :). Otherwise – yes, it’s nice to have.

    11. Right To Left Language (RTL) Support – it should be a theme’s business. The multilingual plugin just switches locale. The theme should load RTL. No?

    15. Automatic Machine Translation – well, if you are running a joke site, that’s an option. For anything serious, you do not even start with an automatic translation. IMHO.

    Integration with other plugins, themes – that’s the largest pain. In our case, (WPGlobus), if a theme does echo $post->post_title, we cannot do anything.

    And the main point is Support. The biggest “PITA”, especially when your model is “freemium”.

    Thank you!

  2. Andrew Traub
    Andrew Traub September 19, 2016 at 07:36 | | Reply

    Nice article – but it’s missing a comparison table showing how the existing translation plug-ins meet or do not meet your checklist.

  3. Joel Fisher
    Joel Fisher September 20, 2016 at 06:53 | | Reply

    So what plugin is recommended?

    1. Jean Galea
      Jean Galea September 20, 2016 at 09:05 | | Reply

      WPML is what I use and recommend.

    2. Augustin
      Augustin September 22, 2016 at 01:14 | | Reply

      You could also try Weglot (https://wordpress.org/plugins/weglot/).

  4. Gregory Karpinsky
    Gregory Karpinsky September 21, 2016 at 05:51 | | Reply

    @Andrew:

    To help Nagdy with the comparison table:

    WPGlobus does NOT do (see my comment above for a partial “why”):

    – translate media
    – translate taxonomy slugs (only translates post/page slugs)
    – support (sub)domains (only the domain.com/xx/ format is supported)
    – automatic translation
    – anything special for RTL (themes do that, and everything works as far as we know)
    – translation of themes and plugins texts (not our business; use Loco Translate / POEdit)
    – custom (?) language switchers (though we have a menu-based switcher and we have a configurable switcher widget, which could be placed anywhere)

    All the rest IS supported by WPGlobus. Mostly in the free version. WooCommerce and slug translation – in premium add-ons.

    In addition to the Nagdy’s list, WPGlobus can turn on and off any elements of the menus and even can assign completely different menus for each language. Same – for widgets.

  5. Luca
    Luca December 17, 2016 at 11:08 | | Reply

    I don’t agree with the author of the plugin about the minor importance of translating the URL slugs.

    Sorry to say but this is a very important SEO practice.

    I was ready to buy Wp Glbus Plus but the lack of this important feature stopped me from doing it.

    Hope the author will consider to add this function in future updates.

    Cheers

    1. Gregory Karpinsky
      Gregory Karpinsky December 17, 2016 at 11:42 | | Reply

      @Luca WPGlobus Plus can translate slugs. Read the description.

Leave a Reply