Current behavior:
When using HTML subfilter with e.g. JSON files, & and < are always exported as
When using HTML subfilter with e.g. JSON files, & and < are always exported as
& and < where these are parts of the strings. This is not optional.Available workaround (if any):
Converting
<[^>]+?> to tags is not a valid workaround because it cannot handle entities such as & or ", or paired tags, let alone more complex HTML elements/attributes for translation, e.g. an alt attribute for animg element.
Requested behavior:
Customizable HTML entity "Reader" and "Writer" settings (in all filetypes where applicable).
Customizable HTML entity "Reader" and "Writer" settings (in all filetypes where applicable).
Use case:
"The automatic escaping behavior is very abrupt as the source json file (without escaping) is valid per se, it’s also causing more issues, e.g. the & symbol in translation changes to &".
"The automatic escaping behavior is very abrupt as the source json file (without escaping) is valid per se, it’s also causing more issues, e.g. the & symbol in translation changes to &".
0 comments
Please sign in to leave a comment.