Release v1.6.55

Breakthrough on CSS encoding handling

While reading the MDN docs, I discovered that UltimaDark can safely ignore the original CSS charset (including charset attributes and @charset rules) and simply re-encode all CSS files as UTF-8, as long as a UTF-8 byte-order mark (BOM) is added at the start of the file.

This definitively resolves issues where CSS content values were being mis-decoded and incorrectly reflected in webpages — in a way that is both efficient and elegant.

HTML documents will still keep their original charset, so they continue loading their other resources (scripts, fetch calls, etc.) using the correct encoding.

Relevant MDN documentation:

https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/At-rules/@charset
Browsers determine stylesheet encoding in this order:
• UTF-8 BOM
• HTTP charset header
• @charset
• Referring document charset (obsolete)
• Otherwise assume UTF-8