312709 - Localization - presentation layer / Template for severity, status and resolution

Status: RESOLVED DUPLICATE of bug 512623

(Bugzilla :: Bugzilla-General, enhancement)

Description

[David KELLER]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.7.12) Gecko/20050919 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.7.12) Gecko/20050919 Firefox/1.0.7

Is it possible to distinct presentation and data layer ?

For example, to improve the localisation template I need to perform this action.
For french localization :
<select > 
<option value="NEW" >Nouveau</option> 
<option value="ASSIGNED" >Assigné</option> 
<option value="RESOLVED" >Résolu</option> 
<option value="CLOSED" >Clos/option> 
</select> 

And the same for the bug list or reports.

Is it possible with Template Toolkit (TT) ?

Best Regards,
David



Reproducible: Always

Steps to Reproduce:
1. create a NEW bug
Actual Results:  
no localization in the presentation layer

Expected Results:  
localization in the presentation layer

Comment 1

[Emmanuel Seyman]

(In reply to comment #0)
> 
> Is it possible to distinct presentation and data layer ?

With regards to statuses and resolutions, this is possible in 2.20 by editing
the global/field-descs.none.tmpl file and rename statuses and resolutions to
whatever you see fit.
Severities are in the database and you can name them however you want.

If you feel this can be improved, please feel free to make suggestions.

Comment 2

[Frédéric Buclin]

for severity and priority, for instance, we could imagine that we look into
field-descs.html.tmpl and we cannot find the corresponding entry, we fall back
to the value given by the DB.

Comment 3

[Emmanuel Seyman]

(In reply to comment #2)
> for severity and priority, for instance, we could imagine that we look into
> field-descs.html.tmpl and we cannot find the corresponding entry, we fall back
> to the value given by the DB.

The more I think about it, the more this sounds feasible.
These could go in a severity_descs hash in global/field-descs.none.tmpl.

Can we include the Hardware and OS fields in this? I've always been annoyed
by the 'All' and 'Others' choices which I've always found jarring when
everything else on the page is in another language than english.

Comment 4

[Max Kanat-Alexander]

If you do this though, I think we should make a FILTER called translate_severity
or something. Otherwise, we get a *lot* of difficult-to-maintain code, like we
did for the Resolution and Status fields.

Comment 5

[Emmanuel Seyman]

(In reply to comment #4)
> If you do this though, I think we should make a FILTER called
> translate_severity
> or something. Otherwise, we get a *lot* of difficult-to-maintain code, like we
> did for the Resolution and Status fields.

Wouldn't it make more sense to have a translate FILTER that
translates everything including resolutions and statuses?

Comment 6

[Frédéric Buclin]

something like that?

[% my_status = 'NEW' %]
The actual status is <b>[% my_status FILTER translate('status') FILTER html %]</b>

Comment 7

[Marc Schumann [:Wurblzap]]

Bug 218746 is related.