No, there were no problems at all, at least not from my point of view. I'm using the substitutions for the Romanian and Hungarian characters, but at least those are perfectly alright. They are working so far, so I'm gonna use the substitutions given by your code.Yincognito wrote: ↑July 30th, 2020, 6:50 pm No problem - I'm glad it worked. Put it to the test as many times as you want, as this will no doubt lead to a better implementation, if by any chance there are still issues with the approach. There shouldn't be however, unlike the V1 code, which indeed worked only for small Unicode intervals.
Excelent work. I'm amazed by it.
Many - many congratulations again.
Don't worry. Better later, than never, I suppose.Yincognito wrote: ↑July 30th, 2020, 6:50 pm Too bad I didn't come up with this automated code a couple of years earlier though, when I built my own "decoder substitute" that handled multiple encodings in HTML (something that DecodeCharacterReference doesn't handle), but then, it's not like I manually built that one either - I just used some Notepad++ regex replacements on a wiki list of Unicode characters instead.
This is not a problem. It has to be done only once, so it's alright.Yincognito wrote: ↑July 30th, 2020, 6:50 pm P.S. Don't forget to delete the last comma from the sustitute, when using it - I could have bothered with doing that automatically as well, but didn't.