You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, you are correct.
What you have is somewhat edge, but problematic nonetheless.
I think that "declarative mark" should not take over like that. But I am new to this encoding world....
Not entirely true, it's more complicated than that.
Fortunately, I know how to fix this. I don't know exactly when, but soon.
The idea is to do a preg replace within the normalizer CLI if there is a declarative mark.
Provide the file
110-original.zip
Verbose output
Using the CLI, run
normalizer -v ./my-file.txt
and past the result in here.enca
will however detect UTF-8 as it shouldExpected encoding
Expected normalizer to show UTF-8 encoding after conversion to UTF-8.
Am I wrong here?
Desktop (please complete the following information):
Additional context
I know. Html is not the same as text.
But I will document this here.
I think that "declarative mark" should not take over like that. But I am new to this encoding world....
The text was updated successfully, but these errors were encountered: