Language Translation Plugins

Home › Forums › Plugin or Theme Compatibility › Language Translation Plugins

NOTICE: We've Moved to a Ticket System for Support

As of August 31, 2017 (12am EST) our support forums will be retired (read-only), and we will be moving to a support ticket system.  This will allow us to better organize and answer support requests, and provide a more personalized experience as we assist our customers.

For the time being, we will leave our forums open for reading and learning while we work on creating a more robust Knowledge Base for everyone to use.

If you are a WC Vendors Pro customer please open a support ticket here. 

If you are a WC Vendors user please open a support ticket on the Wordpress.org forums.

The information on this forum is outdated and in most instances no longer relevant. Please be sure to check our documentation for the most up to date information.

https://docs.wcvendors.com/

Thank you to all of our customers!

 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • December 9, 2016 at 1:35 pm #49826
    Ben
    Participant

    Hello team,

    I would like your valuable advice, please.

    I saw different topics with different support questions about several translation plugins (like WPML, Polylang, Loco Translate, qTranslate…). Considering evolution of WCV Pro, I would like to know which ones could be appropriated/compatible to do that (2 hypotheses) :

    Hypothese 1 :
    1/ Translate the frontend vendor dashboard (through default .po and .mo files)
    2/ Create flag icons menu on frontend which permits users to switch language.

    Hypothese 2 :
    1/ Translate the frontend dashboard (through default .po and .mo files)
    2/ Create flag icons menu on frontend which permits users to switch language.
    3/ Allow vendors to translate on his dashboard the content he record (product description, product name). Probably requires some massive custom codes from what I read.

    On other sites I manage (without WCV) I use Loco Translate to do 1/ and Polylang to do 2/ and that’s working fine. The translation of default WordPress/Themes/Plugins languages works great with Loco. And it permits :
    – to keep custom languages files safe from updates
    – to synchronize .pot files and update new strings
    – to generate all language files even if the Theme/Plugin do not have one (with its default template).
    But I read that there could be somes issues with the slug with Polylang. Is it still relevant ?
    Also, I saw maybe qTranslate would not be maintained.

    So, before starting working on translation of a website with WCV. I search the best way to do what I need (probably Hypothese 1!)
    I know you would not promote one or another of your colleague, but just wanted to know, which ones would be more in phase with the way you code WCV, and I want to restart a clean installation with less plugins but most appropriated with WCV which is the main hinge of the structure 🙂

    Many thanks!

    December 17, 2016 at 7:50 pm #50695
    Anna
    Member

    Hello,
    I do not know exactly how you are going to configure various languages across your site.
    As far as we know, we are compatible with WPML and have had them look over our files to ensure that we are compatible.
    Language files can be submitted also to be included in future updates to improve our language translation capabilities.
    As far as changing the language on the front-end into various languages, I am not certain what works best.
    Anything that changes the URL by adding in /en/ or /fr/ will mess with the vendor dashboard pages, as these need to have the original URL to show properly.

    Reading through your scenarios, I think option 1 will work best; language translation using the .po and .mo files to configure the base language if it is not English. Then using some kind of language switcher on the front end for site visitors. However, I am not sure still if the dashboard pages will work in more than one language. Likely not.

    December 17, 2016 at 8:03 pm #50696
    WC Vendors Support
    Participant

    If I go to a Russian website to find myself a mail order bride, or if I want to read a French newspaper, Google Chrome already translates the entire page on the fly for you. What else is necessary? Why do I need a bloated translation plugin slowing down my entire website for every single visitor when every current webbrowser in the world does this for you?

    December 18, 2016 at 12:23 pm #50760
    Ben
    Participant

    Hey there !

    Sometimes integration, or simply translation, could be more adapted with a plugin we can control. But I have to say that, even if I mainly use Firefox on my desktop, I use Chrome on my smartphone and I have noticed that it purposes translation on the fly. And that is working pretty fine yes. This will certainly extend to other browsers in the near future hopefully.

    I take note of the /en /fr URL which will be not appropriate to the vendor dashboard page. Thank you for this reminder. So I will not use Polylang, even if I used it only as a switcher. Because I didn’t find a way to preserve the original URL. Would you have heared speaking about a simple switcher plugin ?

    Concerning Loco Translate, I will have a try with WC Vendors and will tell you what it gives. I really enjoy this plugin as it gives real satisfaction by editing .po .mo files of all themes and plugins. Never tried with WC Vendors but I don’t think it could not be possible if there is a language structure.

    Thanx for your precious advise

    Cheers

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • The forum ‘Plugin or Theme Compatibility’ is closed to new topics and replies.