Roundup Tracker - Issues

Issue 1429669

classification
"issue" not translated
Type: Severity: normal
Components: Web interface Versions:
process
Status: closed fixed
:
: richard : a1s, nerijus, richard
Priority: normal :

Created on 2006-02-11 12:10 by nerijus, last changed 2006-02-12 12:01 by a1s.

Messages
msg2155 Author: [hidden] (nerijus) Date: 2006-02-11 12:10
On line 512 of form_parser.py:
'Required %(class)s property %(property)s not supplied'

When I enter a new issue, the word "issue" (from
%(class)) is not translated.
%(property) is translated correctly.
msg2156 Author: [hidden] (a1s) Date: 2006-02-12 12:01
Logged In: YES 
user_id=8719

i have added gettext call for the class name.

however, class names are not in the roundup message file. 
you'll need to put class name translations in your tracker's
message file to have them translated.
msg2157 Author: [hidden] (nerijus) Date: 2006-02-12 12:11
Logged In: YES 
user_id=3416

Could you please put them in roundup.pot, so that they could
be translated?
msg2158 Author: [hidden] (a1s) Date: 2006-02-12 12:17
Logged In: YES 
user_id=8719

no.

roundup.pot is built automatically and contains strings
marked for translation in roundup sources.

since class names do not belong to roundup sources (they're
tracker-specific), there is no place in the sources where
these names could be marked as translatable.
History
Date User Action Args
2006-02-11 12:10:23nerijuscreate