Bug 505842 - smoltSendProfile doesn't work on Swedish locale
Summary: smoltSendProfile doesn't work on Swedish locale
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: smolt
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Mike McGrath
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-14 09:49 UTC by Fredrik Duprez
Modified: 2009-06-22 20:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-22 20:32:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fredrik Duprez 2009-06-14 09:49:24 UTC
Description of problem:

Try to run smoltSendProfile and an error occurs

Version-Release number of selected component (if applicable):

smolt-1.2-4.2.fc11.noarch

How reproducible:

run smoltSendProfile

Steps to Reproduce:
1. smoltSendProfile
2.
3.
  
Actual results:

Traceback (most recent call last):
  File "/usr/bin/smoltSendProfile", line 31, in <module>
    from i18n import _
  File "/usr/share/smolt/client/i18n.py", line 36, in <module>
    t = gettext.translation('smolt', '/usr/share/locale/', fallback = True)
  File "/usr/lib/python2.6/gettext.py", line 480, in translation
    t = _translations.setdefault(key, class_(open(mofile, 'rb')))
  File "/usr/lib/python2.6/gettext.py", line 180, in __init__
    self._parse(fp)
  File "/usr/lib/python2.6/gettext.py", line 316, in _parse
    plural = v[1].split('plural=')[1]


Expected results:


Additional info:

It looks like this has been filed against F7-10 as well. Is there a workaround?

Comment 1 Fredrik Duprez 2009-06-14 14:25:20 UTC
Found a workaround:

LANG=en_US.utf8
followed by smoltSendProfile works.

Smolt should behave more gracefully if a translation doesn't exist.

http://www.smolts.org/client/show/pub_df7ce2df-1372-463f-b30d-5d63c2b477ae

Comment 2 Mike McGrath 2009-06-22 20:32:45 UTC
This should be handled a bit better in the next release.


Note You need to log in before you can comment on or make changes to this bug.