UnicodeData.txt was devised long before any of the other UCD data files. Though
it might seem like a simple enhancement to us, adding a header block, or even a
single line, would break a lot of existing processes that were built long ago
to parse this file.
So Unicode can't add a header to this
Welel an alternative to XML is JSON which is more compact and
faster/simpler to process; however JSON has no explicit schema, unless the
schema is being made part of the data itself, complicating its structure
(with many levels of arrays of arrays, in which case it becomes less easy
to read by huma
Thank you for looking into this. First, I’m unable to retrieve the publication
you are citing,
but a February thread had nearly the same subject, referring to Vol. 50. How
did you
compute these figures? Is that a code phrase to say: “The same questions over
and
over again; let’s settle this o
On 30/08/18 23:34 Philippe Verdy via Unicode wrote:
>
> Welel an alternative to XML is JSON which is more compact and faster/simpler
> to process;
Thanks for pointing the problem and the solution alike. Indeed the main
drawback of the XML
format of UCD is that it results in an “insane” filesize
A good compromise between human readability, machine processability and
filesize would be using YAML.
Unlike JSON, YAML supports comments, anchors and references, multiple
documents in a file and several other features.
Regards,
Marius Spix
On Fri, 31 Aug 2018 06:58:37 +0200 (CEST) Marcel Schn
To handle the UCD XML file a streaming parser like Expat is necessary.
For codepoints.net I use that data to stuff everything in a MySQL
database. If anyone is interested, the code for that is Open Source:
https://github.com/Codepoints/unicode2mysql/
The example for handling the large XML file c
On 31/08/18 08:25 Marius Spix via Unicode wrote:
>
> A good compromise between human readability, machine processability and
> filesize would be using YAML.
>
> Unlike JSON, YAML supports comments, anchors and references, multiple
> documents in a file and several other features.
Thanks for advi
Hello Marcel,
YAML supports references, so you can refer to another character’s
properties.
Example:
repertoire:
char:
-
name_alias:
- [NUL,abbreviation]
- ["NULL",control]
cp:
na1: "NULL"
props: &
age: "1.1"
na: ""
JSN: ""
gc: Cc
ccc: 0
8 matches
Mail list logo
