string 13 is not translatable
Bug #792364 reported by
serfus
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Lernid |
Fix Released
|
Medium
|
John S. Gruber |
Bug Description
I have encountered an error when trying to translate string 13[1].
Error is: "Error in Translation:
'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The character that terminates the directive number 1 is not a valid conversion specifier."
I have been told that gettext does not yet support the new style of python string formatters
[1] https:/
Related branches
lp://staging/~jsjgruber/lernid/lernid-proposed
- John S. Gruber: Pending requested
-
Diff: 2983 lines (+636/-637)50 files modifiedbin/lernid (+7/-9)
debian/changelog (+22/-0)
etc/lernid-classrooms.d/ubuntu-classroom (+1/-1)
lernid.1 (+0/-3)
lernid/Sessions.py (+6/-7)
lernid/lernidconfig.py (+1/-1)
lernid/widgets/Browser.py (+225/-182)
lernid/widgets/Schedule.py (+1/-1)
lernid/widgets/WebChatroom.py (+0/-61)
lernid/widgets/__init__.py (+0/-1)
po/af.po (+8/-8)
po/ar.po (+10/-11)
po/ast.po (+8/-8)
po/ca.po (+9/-9)
po/cs.po (+8/-8)
po/da.po (+8/-8)
po/de.po (+11/-11)
po/el.po (+9/-9)
po/en_AU.po (+10/-10)
po/en_CA.po (+10/-10)
po/en_GB.po (+12/-11)
po/eo.po (+9/-9)
po/es.po (+13/-13)
po/es_AR.po (+8/-8)
po/eu.po (+9/-9)
po/fi.po (+8/-8)
po/fil.po (+12/-11)
po/fr.po (+12/-12)
po/he.po (+9/-9)
po/hr.po (+9/-9)
po/hu.po (+9/-9)
po/id.po (+8/-8)
po/it.po (+10/-10)
po/jbo.po (+8/-8)
po/ms.po (+10/-10)
po/nb.po (+8/-8)
po/nl.po (+12/-12)
po/oc.po (+9/-9)
po/pl.po (+11/-11)
po/pt.po (+8/-8)
po/pt_BR.po (+10/-10)
po/ro.po (+8/-8)
po/ru.po (+9/-9)
po/sl.po (+10/-10)
po/sv.po (+11/-11)
po/te.po (+8/-8)
po/tr.po (+9/-9)
po/uk.po (+10/-10)
po/zh_CN.po (+12/-11)
setup.py (+1/-1)
Changed in lernid: | |
assignee: | John S. Gruber (jsjgruber) → nobody |
Changed in lernid: | |
status: | Triaged → In Progress |
assignee: | nobody → John S. Gruber (jsjgruber) |
Changed in lernid: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Yeah, it seems gettext is choking on {1:.1}, so I think the solution here would simply to change that string to use the deprecated (but still valid) _('blah blah %d' % (number)) string formatting specifiers