[Bug 27478] Serializing JSON: \t, \r, Unicode sequences

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27478

Jim Melton <jim.melton@acm.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |jim.melton@acm.org
         Resolution|---                         |FIXED

--- Comment #3 from Jim Melton <jim.melton@acm.org> ---
I'm not Mike but I'll take a stab at answering the question anyway. 

I do NOT believe that the use of "HHHH" (as opposed to "hhhh", "Hhhh", "hHhh,
etc.) was intended to imply that the hexadecimal digits must be output in upper
case.  In fact, it is rather more common for lowercase to be used.  I don't
believe that it is useful for our specs to prescribe one or the other, so I
think implementation-dependent (not -defined!) is most appropriate.  And that
probably is worth an entry into the appendix. 

I'm re-marking the bug RESOLVED/FIXED. If you agree that this is the
appropriate response, please mark the bug CLOSED.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 5 December 2014 20:28:37 UTC