[openbiblio-dev] Feedback on my BibJSON record

[Peter Murray-Rust]

On Thu, Feb 21, 2013 at 6:20 PM, Tom Morris <tfmorris at gmail.com> wrote:


> JSON supports full Unicode (UTF-8 by default) in strings, but it also
> allows (but does not require) the \uNNNN notation.  You can also see
> escaped newlines (\n) in the dc:publisher field.
>
>
> The use of \uNNNN is IMO more robust than the use of Unicode characters as
there are so many non-compliant tools at present. Although, in principle,
it should be possible to cut and paste Unicode , in practice it very
frequently gets corrupted. The use of ANSI characters is safe.
(the same thing is true in XML. I routinely output characters as &#dddd;
rather than the character. Of course I always declare UTF-8 as the
encoding.



-- 
Peter Murray-Rust
Reader in Molecular Informatics
Unilever Centre, Dep. Of Chemistry
University of Cambridge
CB2 1EW, UK
+44-1223-763069
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/openbiblio-dev/attachments/20130221/a31a245e/attachment.html>