Manuel Strehl

Yes, thanks for bringing this to my attention again! In principle the fix is ready but I wasn’t able to test it appropriately (and generalize it as much as I...

A bit off-topic, but we could piggy-back [RFC 6901 (JSON Pointer)](http://tools.ietf.org/html/rfc6901), where a grammar comes delivered free. The syntax would be a bit different. And I seem to remember, that...

Another problem that I pointed out at the list right now: ``` ``` creates a huge response. Combined with CSRF that would mean DDoS with minimal scripting afford.

@macek To cite #15: “This has been pointed out before[...]” Yep, that was me here :-) Anyway, thanks for the cross-link!

Apparently, browsers do not yet (as of 2016-03) feature a security guard against massive sparse arrays: http://codingsight.com/how-to-hang-chrome-firefox-and-node-js-inside-native-func/

Yes, that basically sums up my uncertainty on how to implement that. On top, I think it a nice feature, that the current alphabet adds some "optical feedback" in the...

Yes, I deduced that from various clues. This issue is more meant as a documentation bug.

Apparently the Consortium itself has some data on this subject: http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/ Also the IANA: http://www.iana.org/assignments/charset-reg/charset-reg.xhtml

We already include some representations now, but by far not as succinct and complete as fileformat.info. Still work to do here.

This concretely is fixed now but superseded by basically the same bug on the home page. Some characters get cut off at strange places, e.g. https://codepoints.net/U+FFFC Compare OTOH #127 where...