You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading an MO file, the message context is kept as bytes unlike the msgid and msgstr which are decoded to utf8. This is surprising because in order to use for example Catalog.get, one must pass the context encoded as bytes. I wonder if this is intentional or just an omission?
Example:
When I read an MO file compiled from this PO file:
msgctxt"fooctxt"msgid"foo"msgstr"bar"
The message key is ('foo', b'fooctxt') (notice the that fooctxt is a bytes object):
When reading an MO file, the message context is kept as bytes unlike the
msgid
andmsgstr
which are decoded to utf8. This is surprising because in order to use for exampleCatalog.get
, one must pass the context encoded as bytes. I wonder if this is intentional or just an omission?Example:
When I read an MO file compiled from this PO file:
The message key is
('foo', b'fooctxt')
(notice the thatfooctxt
is a bytes object):The text was updated successfully, but these errors were encountered: