Bug#820119: restores original characters instead of taking care of every time numeric references coming up

2017-01-21 Thread victory
On Sat, 14 Jan 2017 13:55:16 +0100 Laura Arjona Reina wrote: > Victory is right no, i misinterpreted validate as tidy :p what the patch does: if both of (charset is "utf-8") and ([the last 56 chars of a error] is "is not a character number in the document character set\n")

Bug#820119: restores original characters instead of taking care of every time numeric references coming up

2017-01-14 Thread Laura Arjona Reina
Hi again. I think my conclusion is silly, I was considering encoding the whole string only. But we can encode the &000130 and leave the emoji in numeric entity. Victory is right, I'll try to think clearer later and merge the patch today. (Now afk, sorry). El 14 de enero de 2017 13:43:24 CET,

Bug#820119: restores original characters instead of taking care of every time numeric references coming up

2017-01-14 Thread Laura Arjona Reina
Hi El 13/01/17 a las 11:34, victory escribió: > > first, it is stupid to blame about names which are valid. > it is also stupid that taking care of each occurrences coming up. > as pages are all utf-8 now, no need to keep such references, > this patch restores original characters instead of

Bug#820119: restores original characters instead of taking care of every time numeric references coming up

2017-01-13 Thread victory
first, it is stupid to blame about names which are valid. it is also stupid that taking care of each occurrences coming up. as pages are all utf-8 now, no need to keep such references, this patch restores original characters instead of numeric references patch below: Index: