Edgewall Software

Changes between Initial Version and Version 1 of Ticket #8055


Ignore:
Timestamp:
Feb 14, 2009, 12:33:23 PM (15 years ago)
Author:
Christian Boos
Comment:

Replying to kabuchan@…:

Can not extract and translate like this.

trac/ticket/templates/ticket.html line 312

<label for="field-${field.name}" py:if="field"

py:strip="field.type == 'radio'">${field.edit_label or field.label or field.name}:</label>

Type:,Priority:,Milestone:,Milestone:,Version:,Severity: ,Keywords:,Cc:

Yes, translation of ticket field names is still an open point. Let's use this ticket as a reminder for this.

Note also that in general, when there's something written "<some text>:", then the ':' must be part of the string to be translated, as different languages have different typographic rule (e.g. in French that would be translated to "<un texte> :").

<input type="submit" name="preview" value="${_('Preview')}" accesskey="r" />&nbsp;

  • <input type="submit" name="submit" value="${ticket.exists and 'Submit changes' or 'Create ticket'}" />

+ <input type="submit" name="submit" value="${ticket.exists and _('Submit changes') or _('Create ticket')}" />

…just an example among many :-) Thanks. There's still an awful lot of places where messages should be recomposed in order to lead to meaningful translations.

and can not translate messages including tag.

#: trac/admin/templates/admin_components.html:42 msgid "" "Description (you may use\n" " [1:WikiFormatting]\n" " here):"

I don't understand what you mean. Are you saying that those messages don't get translated? If so, are you using the proper versions of the supporting packages, i.e. Genshi advanced-i18n branch and Babel 0.9.4? (see TracL10N#GettingtheToolChain for pointers).

Legend:

Unmodified
Added
Removed
Modified