[Bugs] #622 HIGH: not all translations working (sugar-jhbuild)

SugarLabs Bugs bugtracker-noreply at sugarlabs.org
Tue Mar 24 13:06:21 EDT 2009


#622: not all translations working (sugar-jhbuild)
------------------------------+---------------------------------------------
    Reporter:  erikos         |          Owner:  sascha_silbe     
        Type:  defect         |         Status:  accepted         
    Priority:  High           |      Milestone:  0.86             
   Component:  sugar-jhbuild  |        Version:  Git as of bugdate
    Severity:  Major          |     Resolution:                   
    Keywords:                 |   Distribution:  Unspecified      
Status_field:  New            |  
------------------------------+---------------------------------------------

Comment(by sascha_silbe):

 OK, that exercise was a waste of time (though I now know how to actually
 add patches - the docs are incorrect).
 The python gettext module determines the path independently from the GNU
 gettext library:

 {{{
 sascha.silbe at twin:~$ grep prefix /usr/lib/python2.5/gettext.py
 _default_localedir = os.path.join(sys.prefix, 'share', 'locale')
 }}}


 So now we've got three to four options:

 a) Build (full) Python inside sugar-jhbuild.
 b) Add a small module that ships a hacked gettext.py.
 c) Set the locale path in each and every process using gettext.
 d) File an RFE upstream to add support for supplying the path in an env
 var or using the Python module search path.


 a) would mean we have to closely watch Python for security updates, like
 we already have to for xulrunner. Doesn't scale very well.
 b) is a hack and might cause problems with future Python versions, but is
 easiest to implement and the security implications are minimal.
 c) would require changes to a lot of different modules, though mostly one-
 time fixes (i.e. no maintainance required).
 d) is the most general solution (would help other projects as well), but
 won't help in the short run.


 While the computer science guy in me prefers c), b) + d) are probably more
 practical (though I'm not sure how upstream will handle our request -
 after all, for any single module it's easy to override the default).

-- 
Ticket URL: <http://dev.sugarlabs.org/ticket/622#comment:2>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system


More information about the Bugs mailing list