-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translation filter on select field #101
base: develop
Are you sure you want to change the base?
Conversation
I test more about selected fields to get label and not option. In some cases, key, value are not exactly and don't find all translated labels in translation_filter. For example:
I think a better option is clone select options in template and get it:
|
I improve values from selection fields use Model.fields_get. Get values from selection fields is more easy than add conditions or dict in jinja template (need afeter to translate). I don't know if "translation_filter" is the best name of this method/filter. Feedback? Details https://groups.google.com/d/msg/tryton-dev/JVCYVFlVtxs/GsZI-QGB810J |
@raimonesteve could you send the translation of select fields as a new patch please ? It is an important contribution which we could include before 3.2 release |
Hie Sharoon, I try to resend pull request but I get "Travis error field"... You could import/export commit raimonesteve@8537342 or copy code in main nereid project. You are free ;) |
Sure, we will try :) |
When render some fields in template, this fields is a option, not value (for example selected fields). Add new filter to translate values from ir.translations.