Add translation to constants.py

[Toff]

It will be great if you can add translation to DEFAULT_TAGS in constant.py,
so we can have a translation of 'info', 'warning', etc in templates by using {{message.tags}}

[alasdair]

message.tags is used for CSS - if you translated the DEFAULT_TAGS you would break the styling.

For example, in django/contrib/admin/templates/admin/base.py

{% if messages %}
<ul class="messagelist">{% for message in messages %}
<li{% if message.tags %} class="{{ message.tags }}"{% endif %}>{{ message|capfirst }}</li>
{% endfor %}</ul>
{% endif %}

I understand that you might want to display the translations of "info", "warning" etc to the user, but this would have to be a different attribute than message.tags.

[Claude Paroz]

IMHO, message tags are not meant as user-visible strings as their first role.
You can always mark those strings as translatable in your own project (i.e. ugettext_noop('debug'), etc.), then create your own template filter or tag to get translated tags.

[Aymeric Augustin]

Claude, would you consider an API like message.get_tags_display to provide human-readable versions of the levels?

[Claude Paroz]

I don't really see the use case of message.get_tags_display in the sense that there may be multiple space-separated tags returned. Maybe a message.get_level_display (which wouldn't consider extra_tags)? But once again, mixing tag and display roles with the same string doesn't seem very clean to me.
In any case, we would then need a use case common enough to justify it (considering that a custom template tag/filter can easily fill the "gap").

[Toff]

You're right, i haven't seen this CSS breakdown.
message.tags is not intented for a direct text rendering.

I'll try an another way, like ugettext_noop as suggest claudep.

Thanks for your rapid answers and all your work.