[Nuxeo-localizer] Work-around for potentiall poEdit bug

[Johan Carlsson [EasyPublisher]]

Hi,
I have encountered a problem with .mo files created with poEdit.

It seams that poEdit creates .mo files containing null characters.

I'm not sure if this is disallowed or if it's a bug in poEdit.

After examining the gettext.py in Python, it opens .mo files binary,
so this should be considered a bug in Localizer.

Should I send the patch or can I get developer access Localizer and I'll 
commit it my self?
(My sourceforge id is: johanc)

DIFF:
   It's in row 58 of LocalFiles.py

    -            f = open(filename)
   +            f = open(filename, 'rb')

   I couldn't find any other files opening .mo files, but I might have 
missed it.


Regards,
Johan Carlsson










--
Torped Strategi och Kommunikation AB
Johan Carlsson
address@hidden

Mail:
Birkagatan 9
SE-113 36  Stockholm
Sweden

Visit:
Västmannagatan 67, Stockholm, Sweden

Phone +46-(0)8-32 31 23
Fax +46-(0)8-32 31 83
Mobil +46-(0)70-558 25 24
http://www.easypublisher.com
http://www.torped.se