• Resolved MarioVisie

    (@mariovisie)


    I have added the Dutch translation (informal)
    There are 2 problems with Dutch:

    2 strings are not translated due to below ..

    Soms translations are not nice toe make: Example:
    Newsletter(s) Wil be in dutch: Nieuwsbrief/Nieuwsbrieven (to long or does not cause good running sentences)
    And second, In dutch we have formal and informal language use
    U (formal) and Je/jij are both in English: YOU

    Yet it is a big difference:
    Business is formal
    Not businesslike, or less distant informal

    Another point: I have at several points that should be given to the Dutch legislation Opt-in is almost mandatory for almost all only ordered one may put a checkbox “on”. Lik e on this:

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 20 total)
  • I get the “Empty PO data” error as well. Why can’t this be added to the plugin so that anyone can loco-translate this plugin to suit their own needs?

    Plugin Author ehsantikweb

    (@ehsantikweb)

    Hi all,
    There are two ways can translate plugin, either you have to add string your local language in the WordPress Translating page,

    WordPress Translating Page

    Or you can upload “.po” file to this location “/wp-content/languages/plugins”

    You may use Loco Translate Loco Translate Plugin

    The Loco Translate plugin itself generate a .po file in the languages/plugins folder, You don’t need to upload any .po file manually. However, I’m sharing a .po file with the google doc. Here is the Link

    Hope this will help you guys.

    Thanks
    Ehsan

    Plugin Author ehsantikweb

    (@ehsantikweb)

    Hi @mariovisie,
    Thanks for your feedback. I have re-read my own answer, and we have instead changed the code for pluralization text, and we have released a new version 1.0.4. Please update the plugin and check.

    Regarding the second issue about formal and informal language, for example: use for YOU

    You can export the normal dutch, then import it into the formal version – and then change the texts that are different. If you look at the page with all the languages, you will see that for dutch, there are 3 different languages. Look at:
    https://translate.wordpress.org/projects/wp-plugins/add-on-woocommerce-mailpoet/dev

    There is: “Dutch” + “Dutch (Belgium)” + “Dutch → Dutch (Formal)”
    1. Click “Dutch”, then at the bottom click “Export”, and export your dutch translation to a .po file.
    2. Then click into the formal version, and use the import link at the bottom.
    3. Finally, edit the fields that needs to be changed for formal language.

    Automatic translations need 2 more things to work:
    1. You have only translated the texts, but WordPress will not generate the language files for the websites, before you have also translated most of the readme. See: https://translate.wordpress.org/locale/nl/default/wp-plugins/add-on-woocommerce-mailpoet

    “Development (trunk)” have 0% translated and 49 texts waiting for approval.
    “Development Readme (trunk)” have 0% translated and 0 texts waiting for approval.

    Click the readme and also translate all the texts here.
    2. A translation editor for the specific language, needs to approve the translations for our plugin. And currently there are no approved translation editors for dutch for our plugin.

    You may be the first dutch editor 🙂
    Only the WordPress polyglots team can approve translation editors for plugins – you can request to become translation editor for dutch, by making a request on https://make.wordpress.org/polyglots/ – you can see examples by scrolling down on that forum/page. Here is what we suggest you write:

    —beginning of forum post—

    Hello Polyglots, I have added translations for Add-on WooCommerce – MailPoet 3 and would like to become the translation editor for my language.
    Please add my WordPress.org user as Project Translation Editor (PTE) for the respective locales:

    o #nl – @mariovisie
    o #nl_BE – @mariovisie
    o #nl/formal – @mariovisie

    If you have any questions, just comment here. Thank you!
    #editor-requests

    —end of forum post—

    • This reply was modified 1 year, 4 months ago by  ehsantikweb.
    • This reply was modified 1 year, 4 months ago by  ehsantikweb.

    Hi,

    nl_BE done @mariovisie

    Jeroen

    @ehsantikweb, the example you give for the forum post is almost perfect. Just one minor thing: instead of a bullet point, please make it a small letter o followed by a space.

    So for the correct formatting:
    o #nl – @mariovisie
    o #nl_BE – @mariovisie

    etc.

    It will help us in following the requests automatically 🙂

    I have manually uploaded the .po and .mo files, but Loco Translate still gives the “Empty PO data” error… Anyone?

    Plugin Author ehsantikweb

    (@ehsantikweb)

    Hi @miezz81,
    Regarding the “Loco Translate” plugin issue, there are two things very important that you must follow, the .po/.mo file name and the language file location,

    For the Dutch language, the .po/.mo file name should like “add-on-woocommerce-mailpoet-nl_NL.po” and “add-on-woocommerce-mailpoet-nl_NL.mo”

    Second, where you will upload the .po/.mo files. The location should be here, “/wp-content/languages/plugins”

    If you need any further information, please comment here.

    Plugin Author ehsantikweb

    (@ehsantikweb)

    Hi @casiepa,

    Thank you for your nice feedback, I understand what you wanted to say. thanks again.

    Reviewed nl_NL. However strings are only for development. Stable strings are missing on translate.wordpress.org. Don’t know if they will be available using WordPress Updates.

    Plugin Author Kasper Tikjøb

    (@kasperta)

    They will when the translation editor approves them – current approved editors can be seen at: https://translate.wordpress.org/projects/wp-plugins/add-on-woocommerce-mailpoet/contributors

    When we are not using “stable” everything is read from “development”.

    Hi @ehsantikweb,

    I can confirm that both the location as the filenames are correct. Prove to me is that the correct translation is shown in the front-end.

    However, I would like to adjust the translation to suit the tone of voice just for my site. This is where Loco Translate gives the “Empty PO data” error.

    Help would be appreciated.

    Plugin Author ehsantikweb

    (@ehsantikweb)

    Hi @miezz81,

    I’ve installed and tested “Loco Translate” plugin in locally, the issue is that the .pot file in our plugin/language folder is empty now and “Loco translate” plugin always find the plugin/language/xxx.pot file first, that’s why the “Empty PO data” is showing there.

    Although the .pot file is not mandatory for the plugin translation because we are suggesting to get the translation from WordPress translation, we know well that it is better practice to put a .pot file in the language folder in the plugin, so that if want to add/edit any strings that do not exist in the WordPress language.

    We are now releasing new updated version soon, hope it will help you.

    Thanks

    Hi @ehsantikweb,

    Great, good to know. Is ‘soon’ a matter of days or weeks?

    Thanks!

    Plugin Author Kasper Tikjøb

    (@kasperta)

    We have now written a very thorough description on how to use the online translation system – or use local .po files.

    The file is named how-to-translate.txt and from the next version of our plugin (released later today) it will always be in languages/how-to-translate.txt

    You can also read the file here: https://plugins.trac.wordpress.org/browser/add-on-woocommerce-mailpoet/trunk/languages/how-to-translate.txt

    The same text is also added to the plugins main page here at wordpress.org – go to https://wordpress.org/plugins/add-on-woocommerce-mailpoet/ and scroll a bit down to “How to translate?”

    I hope this clears up everything for everyone 🙂

    Hi @kasperta and @ehsantikweb,

    Did you test this with Loco Translate? Because this still doesn’t work.

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