Localization

Viewing 4 replies - 1 through 4 (of 4 total)

  • Got this added to the queue for the next release https://github.com/BeardedGinger/admin-page-notes/issues/2

    I just updated to Version 1.1.0 which includes your suggestions for localization.

    I did some tests but would love your feedback when you get a chance to test it.

    Thanks!

    Thread Starter Knut Sparhell

    (@knutsp)

    When changing the textdomain, be sure to change all occurrences. Now it’s a mix of gb-page-notes and admin-page-notes. This is confusing and makes plugins like Code Styling Localization not work for the other textdomain.

    It seems the translations are loaded from the plugin root folder, not the languages folder. I use

    load_plugin_textdomain( 'gb-page-notes', false, dirname( plugin_basename( __FILE__ ) ) . '/languages/' );

    in my plugins (from codex example).

    There is also a locale-less .mo file in the languages dir.

    Anyway, it still works for nb_NO with the old gb-page-notes-nb_NO.mo in the root, but that is a bit unexpected.

    Thanks! I really appreciate the input.

    Looks like I botched the localization :).

    I’ll give it another go and test with the Code Styling Localization plugin. Should have it updated before next week.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Localization’ is closed to new replies.