New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encode/decode JS entities works on one byte at a time and is not reversible #1
Comments
The decoding algorithm can only handle single-byte sequences. So, this works:
But this is broken:
A file in UTF-8 gives 2 bytes to each character, and the algorithm encodes each one separately. That's a limitation of the original author's design (based on pre-Unicode Notepad++). It affects both 32- and 64- bit versions. As I said in 82f9b0e,
Fixing this will be part of that overall task. |
If you're running at least Windows 10, here's a way to resolve this issue for the time being:
Here is N++ 8.3.3 (64-bit) on Windows 10 21H2, with the updated system encoding : The plugin is most likely calling a standard library function that uses the system's default encoding. What it should do is encode the document's text as Unicode every time, not rely on Windows. |
Original comment by Björn Klug (Bitbucket: [Björn Klug](https://bitbucket.org/Björn Klug/workspace/repositories)). I tried your workaround ("Beta: Use Unicode UTF-8 for worldwide language support” checkbox) but it broke all my MS Access 2010 applications, so that is not a viable solution for me. Since I’m using this plugin quite frequently I’d by very interested in your estimat when this bug will be fixed. [EDIT] Just found the download of version 1.2.2 at https://bitbucket.org/rdipardo/htmltag/downloads/ which works fine again. Thanks! |
Fixed in d2189a1 |
Original report by Anonymous.
Test:
Following characters require encoding: ä ö ü ß
After encoding:
Following characters require encoding: ä ö ü ß
After decoding encoded text:
Following characters require encoding: ä ö ü ß
The text was updated successfully, but these errors were encountered: