#136 Localization bug in plugins avelsieve, quota_usage, useracl

open
nobody
None
5
2006-03-01
2006-03-01
No

Localization files dont loading...
Solution:
change strings from:
bindtextdomain('plugin_name', SM_PATH .
'plugin/plugin_name/locale')
to:
bindtextdomain('plugin_name', SM_PATH . 'locale')

everywhere you'll find them in this plugins dirs...

Discussion

  • Tomas Kuliavas

    Tomas Kuliavas - 2006-03-06

    Logged In: YES
    user_id=225877

    this is not a bug. Plugin developers can distribute
    translations with their packages.

    Translation policies don't enforce use of squirrelmail
    locale directory and plugin developers decide which location
    is used in their plugins.

     
  • Santyaga_ru_RU

    Santyaga_ru_RU - 2006-03-07

    Logged In: YES
    user_id=1456625

    I found this some later ;(
    IMHO all localization in one folder is more convenient than
    some in one some in other... ;) May be suggest configurable
    folder for localization (in plugin dir, in global locale
    dir, in global locale plugin dir) for plugin writer?

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks