• Hi,

    We have several WordPress sites that we’re going to get translated, however after some research this doesn’t seem like an easy task.

    Preferred scenario

    1) Ability to export all strings from themes, plugins and content into one (or several) files (xml, json, whatever) with each string linked to an ID.

    2) These are provided to the translation company to translate into the given languages in the same format we provided.

    3) One (or several) click import of these files. WP will be told which files are which language.

    Unfortunately this doesn’t appear possible. Whilst researching I’ve found two promising plugins – WPML and qTranslate. Both of which feature easy enough multilingual support. The problem lies with the automation. The easy export/import is really rather important because the translation company will preferably not have direct access to the WP install and they also have no knowledge of WP itself.

    Has anyone tackled this issue before, or able to shed some light?

Viewing 1 replies (of 1 total)
  • With more than 6 years in multilingual plugin(s) as data-designer, I will try to bring some drafts:
    1) – If (translation ready) themes or plugins are developed according WP core rules, they contain .pot files with all translatable terms and author’s comments to help translators. (.pot files are text file usable with tools like poEdit – to become .po and finally .mo)
    2) – Good translators inc. are easy with tools like poEdit (desktop app. or online cloud app…) to share the work.
    3) – But some of plugins (free or commercial) are connected to companies via API – a way to capture customers offering translation services
    Automation ? Customization ? Process ? It depends on the organization of the development platform where WP tools are installed. (as presented in some WordCamp)
    M.

Viewing 1 replies (of 1 total)

The topic ‘Localization’ is closed to new replies.