As noted by Owen on the listserv, there are times where translators inject double quotes: #: koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/itemsearch.tt:379 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:100 #, c-format msgid "Not for loan status" msgstr "Статус \"на дом не выдается\"" Which leads to this: + ' <th id="items_status" data-colname="notforloan_status">' + _("Статус "на дом не выдается"") + '</th>' But really those backslash escapes should've been preserved or during the text replacement process they should've been escaped again. -- Personally, I don't know enough about the translation mechanisms to know the finer details, but I suspect that would be the answer.
Related to commit 6757cd5f861e6f2972b48f669750003195e67304 Bug 35043: Use Locale::PO->quote And koha-i18n's commit 2460c96ab283407f9729f9a925129823b9012a8b Do not use Locale::PO to quote Looks like an historical behaviour. Will need more thoughts to know if it can be fixed (easily).
(In reply to Jonathan Druart from comment #3) > Related to > commit 6757cd5f861e6f2972b48f669750003195e67304 > Bug 35043: Use Locale::PO->quote > > And > koha-i18n's commit 2460c96ab283407f9729f9a925129823b9012a8b > Do not use Locale::PO to quote > > Looks like an historical behaviour. Will need more thoughts to know if it > can be fixed (easily). Hmmm interesting. Looks like I have more to learn here about the translation process. I had hoped we'd be able to just deal with the Javascript tokens specifically, but looks like we might not be quite so lucky. In the case of itemsearch.tt and itemslost.tt, I think we could avoid needing _() if we used <template> instead, but I imagine there may be times it's difficult to avoid the _(). (I was looking a bit at the Vue.js and I think we're still using _() there a swell?)
(In reply to David Cook from comment #4) > (In reply to Jonathan Druart from comment #3) > > Related to > > commit 6757cd5f861e6f2972b48f669750003195e67304 > > Bug 35043: Use Locale::PO->quote > > > > And > > koha-i18n's commit 2460c96ab283407f9729f9a925129823b9012a8b > > Do not use Locale::PO to quote > > > > Looks like an historical behaviour. Will need more thoughts to know if it > > can be fixed (easily). > > Hmmm interesting. Looks like I have more to learn here about the translation > process. > > I had hoped we'd be able to just deal with the Javascript tokens > specifically, but looks like we might not be quite so lucky. > > In the case of itemsearch.tt and itemslost.tt, I think we could avoid > needing _() if we used <template> instead, but I imagine there may be times > it's difficult to avoid the _(). (I was looking a bit at the Vue.js and I > think we're still using _() there a swell?) We are using __() in vue components.
I don't think I will spend time on this soon if there is only one single occurrence of the problem. It can still be worked around using single quote.
(In reply to Jonathan Druart from comment #5) > We are using __() in vue components. It's a shame we didn't go with something like the Vue i18n plugin but I can understand wanting to be consistently. (In reply to Jonathan Druart from comment #6) > I don't think I will spend time on this soon if there is only one single > occurrence of the problem. > > It can still be worked around using single quote. It could happen in lots of other cases, but it seems to me like something that could also be caught in translation approval/review instead/as well. After looking at the Koha translation code, I can understand not wanting to make changes to it.