Hi again haukex and huck
I would agree in the suspicion that something else than Perl has changed, but I already dived fairly deep into this.
Java (that runs the JBoss server from which I get my input) hasn't been updated, because it is not a package available in my package manager, neither are the JBoss itself or the database host.
The Apache has been updated, but as I understand it, it would have interpreted double quotes wrongly regardless of its version, right?
That leaves Perl and my changes in the scripts as possible culprits. As I said, the update messed up the page encoding, because none of the scripts were explicitly using UTF-8 and most of them started the HTML page encoded as ISO-8859-1.
I can confirm with 100% certainty that saving and loading UTF-8 characters and double quotes worked before the update.
However, I do not know, if it didn't work at all after the update or if it started to malfunction this way after I enabled the scripts to use UTF-8 (though I think these errors are not necessarily connected).
I appreciate your answers a lot and I will definitely propose updating our infrastructure according to your advice.
In reply to Re^3: Escaping double quotes in complete document
by MeinName
in thread Escaping double quotes in complete document
by MeinName
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |