Support » Plugin: Requirements Checklist » translation

Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Author dauidus

    (@dauidus)

    Oh, goodness me… you’re right. This will be remedied in the next release, scheduled for next week.

    Thanks for the catch, and thanks for the translation!

    -Dave

    OK 🙂 Good to know.

    Plugin Author dauidus

    (@dauidus)

    I have added a working language file… at least, I think I have. Sorry about the long wait on that. 🙂

    Please let me know if this is what you need for a translation. And, as always, thank you for contributing!

    -D

    It seems you forgot to add text domain:

    load_plugin_textdomain('yourplugin', false, basename( dirname( __FILE__ ) ) . '/languages' );

    Plugin Author dauidus

    (@dauidus)

    OK, I think I finally have this figured out. It (might) be fixed in 2.3.1?

    Thanks for sticking with me on this!

    -D

    OK, I will give you the mo and po file when I’m sure it works 🙂

    Hi dauidus,
    I also made a translation with CodeStyling Localization plugin, made a PO file and generated translated MO but it seems it’s not working.

    Could you please let me know how can I force this translation to work?

    Thanks for this great plugin by the way, it’s very helpful!

    Same problem here. It misses (?) the second line here

    * Text Domain: 	  post-type-requirements-checklist
    * Domain Path: /languages

    but even adding this one, it does not work…

    I’ve read a lot of things on the Web to try to fix this but did not manage to to it 🙁

    Plugin Author dauidus

    (@dauidus)

    Barth7 and Li-An,

    Could one of you please send me your po and mo files for this plugin? That way, I can change my language, do some testing on my end and avoid continuing to guess at a solution for this.

    It seems every localization tutorial out there does this all differently. So, I’ll stick to my original code. (all the localization stuff is in public/class-post-type-requirements-checklist.php)

    I have a feeling my text-domain should be aptrc, as that’s what the plugin_slug is. I’ll keep digging.

    Thanks for all your help on this! 🙂

    -D

    Plugin Author dauidus

    (@dauidus)

    OK, think I got this figured out… at least, some language files worked for me in a dev environment. I have changed the text domain to ‘aptrc’, in order to keep it consistent with the text domain. So, you’ll need to rename your po and mo files to aptrc-(lang).mo.

    Again, sorry about all the confusion here. The codex had incorrect/incomplete information and other tutorials led me on an online goose chase.

    Thanks again and Cheers!
    -D

    Plugin Author dauidus

    (@dauidus)

    EDIT:

    The po and mo files need the entire locale string, ex aptrc-de_DE.mo (for German).

    It’s OK now, you can grab the french translation here: http://www.echodesplugins.li-an.fr/mes-traductions-wp/#require

    But in 2.4 version there is no po or pot file in language directory ???

    Plugin Author dauidus

    (@dauidus)

    Thanks for that translation – but your filenames are aptcr…. they should be aptrc…

    🙂

    -D

    It worked ?!? Maybe I changed the name meanwhile… I know where it came from: I have different versions of the files and must haved missed the good name in the uploaded files.

    Plugin Author dauidus

    (@dauidus)

    That’s ok… seems to be my problem, too (at least, mixing up the files before upload).

    Just one question… when the plugin is updated with new functionality and the line numbers change, will you need to provide a new translation file each time? Seems tedious.

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