Not “Translation Ready”

  • Resolved jomo

    (@jonathanmoorebcsorg)


    7 years, 1 month ago

    WPML, Polylang and others support additional string translation of admin-configurable strings for multi-language sites by using a string translation table.
    [the main tools also use an api compatibility layer so it doesn’t matter which one you implement].

    The ti-woocommerce-wishlist gets all the button labels using this type of code:
    tinv_get_option( ‘table’, ‘text_add_all_to_cart’ )
    This gets the custom text in the admin language but does not allow for any standard hook for WPML or other string translation into the current language when running a multi-language site.

    It is possible to implement string translation table at a lower level by hooking WordPress option hooks as: add_filter(‘option_tinvwl-table.text_add_all_to_cart’, …
    etc for each string to translate, but requires debugging the code and is not as convenient as the plugin being WPML ready, as in:

    “TRANSLATION READY
    You can easily translate WooCommerce Wishlist Plugin to any language. Simply choose the most convenient way for you: using poEdit tool, Loco Translate or WPML.”
    Well no, you can’t translate the button labels with Loco Translate or WPML.

Viewing 1 replies (of 1 total)
  • Thread Starter jomo

    (@jonathanmoorebcsorg)

    This is incorrect, please ignore.

    Polylang reads the wpml-config.xml and registers the
    <wpml-config>
    <admin-texts>
    for translation.

    However, due to a separate compatibility issue reported separately, Polylang was not working once the wishlist was activated.

Viewing 1 replies (of 1 total)
  • The topic ‘Not “Translation Ready”’ is closed to new replies.