Re: [issue2551007] Selection fields are not translated

Ralf Schlatterbeck <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.devel
Message-ID <[email protected]>
On Wed, Oct 10, 2018 at 09:05:30PM -0400, John P. Rouillard wrote:
> 
> while search_select_translated does:
> 
...
>             i18n:translate=""></option>

> If I understand this, the 'i18n:translate=""' causes the templating
> engine to look up the content of the option tag (which I think is the
> displayed label) as a key in the translation table. Then it uses the
> result of that look up as the content.
> 
> If the content string of the option doesn't exist in the translation
> table the content is left untranslated.

Yes, that's correct.

> >From what info you have provided, I don't know if i18n:translate="" is
> missing from the template's options statement or if there is no
> translation for the option label. Either would result in what you see.

That would also be my first guess, on the other hand this can also
be a bug introduced with python3 support.
So if the same (unmodified) templates worked with an earlier version
of roundup and no longer works now, I would expect this.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.