(Notice the extra newline between "hey" and "lol" with the javascript extraction method).
I think it's most likely a bug, and the JavaScript should behave the same as the Python.
This is especially bad since the current behavior also differs from how the JavaScript parser interprets it:
const hey = _("hey \
lol"
);
The content of the variable is heylol, but the extracted source term is hey\nlol. The mismatch between the two will prevent the string from being translated by gettext at all.
Hello, the other day I noticed an inconsistent behavior between the python and javascript extraction methods:
(Notice the extra newline between "hey" and "lol" with the javascript extraction method).
I think it's most likely a bug, and the JavaScript should behave the same as the Python. This is especially bad since the current behavior also differs from how the JavaScript parser interprets it:
The content of the variable is
heylol
, but the extracted source term ishey\nlol
. The mismatch between the two will prevent the string from being translated by gettext at all.Could you take a look? Thanks in advance!