Error messages not translatable

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author webaware

    (@webaware)

    G’day Uli,

    When writing this plugin, I chose not to localise it because its intended target is Australian websites (you need an Australian eWAY account to use this method of integration). My forthcoming Pro version is getting the full localisation treatment, however — it uses the Rapid 3.1 API and thus can be more international in its application.

    Out of interest, are you needing localisations because you’re selling to an international market from an Australian website?

    cheers,
    Ross

    Thread Starter _uli_

    (@_uli_)

    Hi Ross,

    that’s fair enough, I was just wondering if it is possible for completeness sake since most strings in the plugin did actually show up on the string translation.

    You are right, it’s an Australian site that also sells to overseas markets. We are using other payment gateways for the other countries however, so it’s really not a big deal. Would have been more of a nice to have for people like myself who are foreign language speakers living in Australia ??

    Thank you for your help!
    Uli

    Plugin Author webaware

    (@webaware)

    G’day Uli,

    Sounds like a fun project, I hope it goes well. I’d like to have a look at it (front end will do!) once it’s done, could you send me a link please?

    cheers,
    Ross

    [people tell me I speak in a foreign language too, but they just don’t understand Geek]

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error messages not translatable’ is closed to new replies.