WordPress.org

Ready to get started?Download WordPress

Forums

Flexo Archives
internationalization (5 posts)

  1. christian_feldbauer
    Member
    Posted 3 years ago #

    Hi again,
    I've discovered another issue (probably). For proper internationalization, so it seems to me, you should define an individual textdomain using 'load_plugin_textdomain' in your 'flexo_widget_register' function.
    Correct me, if I am mistaken...
    Cheers,
    Christian

    http://wordpress.org/extend/plugins/flexo-archives-widget/

  2. Heath Harrelson
    Member
    Plugin Author

    Posted 3 years ago #

    You are correct. The i18n support is currently in an incomplete state, but I will be doing a release with full support very soon. If you have translation experience, your help would be greatly appreciated at that time.

  3. christian_feldbauer
    Member
    Posted 3 years ago #

    Sure. Good thing there aren't many strings to be considered. So it's easy for the users to provide their own .mo files. But important is that all your strings use the '__('string','yourtextdomain')' function to enable translation (I discovered one hard-coded string for the title attribute of the year links).
    cheers,
    Christian

  4. Heath Harrelson
    Member
    Plugin Author

    Posted 3 years ago #

    I discovered one hard-coded string for the title attribute of the year links

    Thanks for pointing that out. I somehow missed it on the branch where I'm making the i18n changes, which does use a unique text domain.

    I have the new branch mostly sorted out, so I'm planning on releasing the new version with proper i18n on Thursday or Friday.

  5. Heath Harrelson
    Member
    Plugin Author

    Posted 3 years ago #

    I have added the appropriate changes and a POT file to version 2.1.0.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic