Even though the text "please note your reason here..." (in suggestion.tt) will get picked up into the po-files, it is never actually translated in the templates when you install the language.
Created attachment 25057 [details] [review] Bug 11686 - "please note your reason here..." does not get translated Through some quirk of the translation script a predefined value on a text input is not properly translated even though the string appears in the po file. On the suggestions form the problem can be solved by using the HTML5 placeholder attribute. To test you must have existing suggestions to manage. Apply the patch and: - Update a translation by running tranlsate update [language code] - Install/reinstall the translation by running translate install [language code] - In the English templates: - Navigate to Acquisitions -> Suggestions and find the "Mark selected as:" section below the table of existing suggestions. - Select "Other" from the "choose a reason" field. A text input field should appear with the placeholder text "please note your reason here." - In the templates you updated and installed, follow the same procedure above. The placeholder text should now appear with the correct translation. - In both English and translated templates using this bulk-status option should save your chosen status correctly with the correct reason, whether that reason be predefined or manually entered.
Created attachment 25737 [details] [review] Bug 11686 - "please note your reason here..." does not get translated Through some quirk of the translation script a predefined value on a text input is not properly translated even though the string appears in the po file. On the suggestions form the problem can be solved by using the HTML5 placeholder attribute. To test you must have existing suggestions to manage. Apply the patch and: - Update a translation by running tranlsate update [language code] - Install/reinstall the translation by running translate install [language code] - In the English templates: - Navigate to Acquisitions -> Suggestions and find the "Mark selected as:" section below the table of existing suggestions. - Select "Other" from the "choose a reason" field. A text input field should appear with the placeholder text "please note your reason here." - In the templates you updated and installed, follow the same procedure above. The placeholder text should now appear with the correct translation. - In both English and translated templates using this bulk-status option should save your chosen status correctly with the correct reason, whether that reason be predefined or manually entered. Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Created attachment 26157 [details] [review] [PASSED QA] Bug 11686 - "please note your reason here..." does not get translated Through some quirk of the translation script a predefined value on a text input is not properly translated even though the string appears in the po file. On the suggestions form the problem can be solved by using the HTML5 placeholder attribute. To test you must have existing suggestions to manage. Apply the patch and: - Update a translation by running tranlsate update [language code] - Install/reinstall the translation by running translate install [language code] - In the English templates: - Navigate to Acquisitions -> Suggestions and find the "Mark selected as:" section below the table of existing suggestions. - Select "Other" from the "choose a reason" field. A text input field should appear with the placeholder text "please note your reason here." - In the templates you updated and installed, follow the same procedure above. The placeholder text should now appear with the correct translation. - In both English and translated templates using this bulk-status option should save your chosen status correctly with the correct reason, whether that reason be predefined or manually entered. Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> Signed-off-by: Katrin Fischer <Katrin.Fischer.83@web.de> Passes tests and QA script. Tested successfully with German - nice to see this fixed!
Pushed to master. Thanks, Owen!
Pushed to 3.14.x, will be in 3.14.08