User contributions
Jump to navigation
Jump to search
- 14:33, 30 September 2014 diff hist +22 m LlJsonValueType "rope" added to show position
- 14:25, 30 September 2014 diff hist +52 m LlJsonValueType at least SOME output would be good.
- 14:22, 30 September 2014 diff hist +2 m LlJsonValueType small bugs
- 14:02, 29 September 2014 diff hist −3,547 m Talk:Combined Library false alert. it was just a bug in my debugger. current
- 13:52, 29 September 2014 diff hist −251 m Combined Library →Unicode Integer to UTF8: sad undo
- 13:52, 29 September 2014 diff hist −33 m Combined Library →Unicode Integer to UTF8
- 13:52, 29 September 2014 diff hist 0 m Combined Library →Unicode Integer to UTF8: nah wrong alert. could not reproduce results. possibly confused something else
- 12:46, 29 September 2014 diff hist +3,547 Talk:Combined Library →CombinedLibrary.zip: and it did it. I fixed 7 year old "unnoticed" bug in UnicodeIntegerToUTF8().
- 12:12, 29 September 2014 diff hist +289 Combined Library →Unicode Integer to UTF8: guess whop just fixed a bug that went unnoticed for 7 years and that was falely blamed on utf8 representations... OLLJ OH, thats me, YAY
- 10:52, 29 September 2014 diff hist +150 m UTF-8 →Limits: HAH that solves one conundrum! . i almost missed it... stupud hexadecimal representation always confuses me unneccessarily. function is simply poorly defuined for high ranges
- 10:48, 29 September 2014 diff hist +10 m UTF-8 →Limits: 2^20+2^16... but why does it start to fail at this value and not earlier (except for the simpler ealier ranges)
- 10:39, 29 September 2014 diff hist +53 m UTF-8 U+FFFE detailing
- 10:32, 29 September 2014 diff hist +12 m UTF-8 →Limits: i think i might "solve" these, except for U+FFFE, which is "broken by design" and has to be skipped, i think i can fix this.... 2^11 and 1114112 are just too strange to be coincidence
- 10:25, 29 September 2014 diff hist −1 m UTF-8 →Limits: syntax fix
- 10:24, 29 September 2014 diff hist +91 m UTF-8 →Limits: + wikipedia link about U+FFFE (and U+FFFF)
- 10:17, 29 September 2014 diff hist +183 m UTF-8 →Limits: tested 2x times, [65534..65535] was a false alert, while [65534] persists as "INVALID CHARACTER"
- 09:41, 29 September 2014 diff hist +62 m UTF-8 i dont think this is due to special utf8 characters. i think one case of one of these functions may simply be wrong!
- 00:27, 29 September 2014 diff hist +1 m LlJsonGetValue confused left and right
- 01:30, 27 September 2014 diff hist +36 m UTF-8 →General Use: the => These
- 01:29, 27 September 2014 diff hist +19 UTF-8 oh this was supposed to go into the == General Use== section...