[Plugin: Flexo Archives Widget] internationalization

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Heath Harrelson

    (@heathharrelson)

    13 years, 2 months 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.

    Thread Starter Christian Feldbauer

    (@christian_feldbauer)

    13 years, 2 months 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

    Plugin Author Heath Harrelson

    (@heathharrelson)

    13 years, 2 months 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.

    Plugin Author Heath Harrelson

    (@heathharrelson)

    13 years, 2 months ago

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: Flexo Archives Widget] internationalization’ is closed to new replies.