Home Forums Landing Pages [Landing Pages] Multilingual compatibility

This topic contains 5 replies, has 2 voices, and was last updated by  Hudson Atwell 2 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #131204

    MSC-Marketing
    Participant

    Hi,

    I shall be installing InboundNow later on today and woonder if there are know compatibility issues with either of the following;
    1. WPML (WordPress Multilingual Plugin) https://wpml.org/
    2. Loco Translate https://wordpress.org/plugins/loco-translate/

    I did find a post relating but that was from 2014 so unsure

    Alternatively I read you use Transifex, similar to our companies use of Crowdin, we have an inhouse translation team, so please suggest which plugin would be best for use with InboundNow to have everything working multilingual

    Thank you
    Erik

    #131209

    Hudson Atwell
    Keymaster

    Hi Erik,

    We do use Transifex and our translations are slowly improving. I cannot account for their quality as at first we used machine translate and to be honest that messed things up.

    But for the last year translators have been singing up and making imporvements here and there.

    WPML and Loco translate will not work with our plugin. We’re 100% transifex custom solution.

    Translations are set disabled to start and can be enabled manually.

    Kind regards,
    Hudson Atwell

    #131212

    MSC-Marketing
    Participant

    Hi Hudson,

    Thank you for the response, hope the hurricane is not affecting work too much.

    So if we have to make use of Transifex, can we still manually make language changes should we not agree with what comes from Transifex?

    From the looks of it we want to use InboundNow company wide, we’re starting with 2 domains now but there will be more to follow and with an inhouse translator team we do require correct translations

    #131217

    Hudson Atwell
    Keymaster

    Yes you’ll have the option to edit all current strings. Translation files are updated every new Inbound Pro update. If you would like to expedite this process just let me know when you are ready to make the updates go live.

    It wasn’t that bad for us. Minor cleanup. Lost a mailbox.

    Kind regards,
    Hudson Atwell

    #131259

    MSC-Marketing
    Participant

    Would there be an option to send our existing translation strings (We’re working in Crowdin) over for import?
    If so what is the preferred format?

    #131266

    Hudson Atwell
    Keymaster

    I could work with a po file. You are welcome to do a pull request. https://github.com/inboundnow/translations/tree/master/lang

    And here’s our source file:
    https://github.com/inboundnow/translations/blob/master/lang/en.po

    I would have to prevent the language from being overwritten by Transifex. As it stands now I’ve no system to merge translations outside of Transifex. I’d just have to preserve the one you preferred. A completed asset is preferable to an unfinished one. I could drop support for the language on transifex. All should be good as long as it works.

Viewing 6 posts - 1 through 6 (of 6 total)

The topic ‘[Landing Pages] Multilingual compatibility’ is closed to new replies.