Modify ↓
Opened 17 years ago
Closed 17 years ago
#1691 closed defect (fixed)
Translation of log(...) messages may be a bad idea
Reported by: | jmt4b04d4v | Owned by: | jmt4b04d4v |
---|---|---|---|
Priority: | normal | Component: | TracSpanishTranslation |
Severity: | normal | Keywords: | log messages |
Cc: | Trac Release: | 0.10 |
Description
As noticed by cboss?, translation of log(...) messages may be a bad idea:
If I may, it's not a good idea to translate the various log(...) messages. Imagine that you get in trouble and trigger a Trac bug (unlikely, but not impossible :-) ). Then we ask for the log to understand what happened and ... we get in trouble! -- cboos
Get info about which messages shouldn't be translated (besides log(...)
messages), and correct patch for Trac engine translation.
Attachments (0)
Change History (3)
comment:1 Changed 17 years ago by
Status: | new → assigned |
---|
comment:2 Changed 17 years ago by
trac-users
gave feedback about this. Translation of log()
messages must be dropped.
comment:3 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
- Undo translation of
log()
messages. - Updated to Trac 0.10.5dev r5758 (changes in 0.10-stable branch up to rev5644)
Note: See
TracTickets for help on using
tickets.
Maybe http://trac.edgewall.org/ticket/5469 its a good place to discuss which messages shouldn't be translated, besides
log(...)
messages.In any case, use this ticket to discuss about it.