• Resolved BenM

    (@alysko)


    Hi,

    I sent you the french translation few month ago but I can’t integrate it in Glotpress because your plugin

    This plugin is not properly prepared for localization

    .

    You just have to put your header (comment with Plugin Name, Plugin URI, Text Domain, Domain Path, etc.) in simple-ajax-chat.php (not -core.php) and change text-domain with the slug of your plugin, namely ‘simple-ajax-chat’, not ‘sac’.

    More details here.

    Thanks.

    https://www.ads-software.com/plugins/simple-ajax-chat/

Viewing 15 replies - 1 through 15 (of 23 total)
  • Plugin Author Jeff Starr

    (@specialk)

    Thanks for the feedback. Currently the plugin has three working translations, which you can verify using the plugin Loco Translate (and others). Not sure what’s up with Glotpress, but I will try to make any necessary changes in the upcoming new version. FYI, the text-domain works fine with sac; using the plugin slug is a recommendation only. Thanks.

    Thread Starter BenM

    (@alysko)

    GlotPress is the official way to translate plugins ! It’s very handy, ok, but it’s the official way. So, everybody could easily traduct your plugin in all languages.

    Check the sidebar on your www.ads-software.com plugin home : The “Translate Simple Ajax Chat” button lead to your Glotpress page.

    April 24th, there is the GTD, Global Translation Day, an opportunity for you to be translate in many languages. If your plugin is not translation ready for WP, you’ll miss the boat.

    Bye.

    Plugin Author Jeff Starr

    (@specialk)

    Thanks for the info, but you don’t have to use Glotpress, in fact many plugins are translated using all sorts of other tools, including Loco Translate and other free plugins. It’s just a matter of preference, and the www.ads-software.com site happens to use Glotpress. Even so, translations are important to the plugin and I will try to make any necessary changes to make it even more compatible than it already is (and it is compatible, as evidenced by the other working translations already included with the plugin). See ya.

    Thread Starter BenM

    (@alysko)

    I see you made some works on your plugin last weeks, it’s cool, thanks.

    Could you just think to change Text Domain to simple-ajax-chat please ?

    PS : And, yes, I know I don’t have to use Glotpress as I use POEdit but, generally, GlotPress translations are better because there are supervisors who check translations before validating it.

    Plugin Author Jeff Starr

    (@specialk)

    Yes, I did make some changes to improve the quality of the plugin, thanks for the feedback. A couple of reasons why I am hesitant to change the text domain:

    1. Doing so would break existing translations
    2. The text-domain string “simple-ajax-chat” is much longer, more cumbersome, and greatly would clutter up the source code

    Plus it takes more time, which is in short supply these days.

    I totally understand that you don’t want to use a different translation tool to translate the plugin, but doing so remains a possible solution.

    Either way, thanks again for the feedback.

    Thread Starter BenM

    (@alysko)

    A very very good reason to use the GlotPress system : I (we) don’t need to contact you for updating translations !

    Moreover, you don’t need to publish an update to add/correct translation.

    Translations updates are made separetly.

    Here is a problem on your text : in function sac_time_since(), you declare some arrays for time (year, month, etc.) and you decide to add a ‘s’ on plural. It’s ok in english and it’s sometimes ok in french, but not all the time and not for all languages.

    For example, month in french is “mois” in singular AND plural. So, we have “Il y a 2 moiss”.

    Thread Starter BenM

    (@alysko)

    PS : all good translation tools have a “translation memory”. Even if you change text domain, we keep our translation.

    PS2 : if you make a search&replace on “, ‘sac’)” -> “, ‘simple-ajax-chat’), it should be ok.

    PS3 : Yes, I do all my best to convince you ??

    Plugin Author Jeff Starr

    (@specialk)

    Yeah it’s borderline annoying, but all valid points. I will think about changing the text domain for the next plugin update. Thanks for your feedback and concern.

    Plugin Author Jeff Starr

    (@specialk)

    Just to follow up with this thread, I went ahead and changed the text-domain for SAC. Should be Glotpress ready as of version 20160811. Thanks for the encouragement ??

    Thread Starter BenM

    (@alysko)

    Great, thanks !

    Thread Starter BenM

    (@alysko)

    Hey ! Me again ??

    Are you intentionally limit trad to trunk ?

    In your header, you have Stable tag: trunk. If you want traduction to be possible in current version, you had to specify version number after Stable tag.

    So, Stable tag: 20160811 for the current.

    Thanks.

    Plugin Author Jeff Starr

    (@specialk)

    Trunk always has meant current version, but sure whatever I will make the change next update. Thanks so much ??

    Thread Starter BenM

    (@alysko)

    Hi Jeff,

    You published an update 3 months ago but translation is still only available for dev, not stable. Could you update this please ?

    Thanks.

    Plugin Author Jeff Starr

    (@specialk)

    Hey Benjamin,

    Thanks for the encouragement, but please understand that this is a free plugin, so has to wait until I’ve paid the bills with actual paying work. Will definitely be updating the plugin again when time allows. Gotta feed the kids first, then will have time to play with the freebies. Thank you for your kind understanding.

    Thread Starter BenM

    (@alysko)

    Hey Jeff,

    Sorry to give the impression of urging you but I think it’s just a one-line modification. Your sons will not be starved ??

    But, whatever, translation into french is now finished and validated. This is the first translation completed on Glotpress ??

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘not (glotpress) translation ready’ is closed to new replies.