Comment 2 for bug 1710512

I originally added that string when my intent for bug 1098685 was to be able to just use html5 form validation, and only fallback to this basic plain-vanilla JS for older browsers that did not support it.
But it was decided to just keep it plain vanilla js for validation in the OPAC.

Currently, I am not aware of the method that EG is using to I18n-ize any string that's part of a separate js file used on the OPAC.

However, from what I've gathered a solution would be to have perhaps a i18n_js_strings.tt2 file and inline a <script> tag with a global js blob and push i18n'd string values into the JS of the OPAC, so these translations can take place. Similar to how Open-ILS/src/templates/staff/base_js.tt2 works for the webstaff client.

Not sure how optimal this solution is, but I'm open to any ideas...