But CSV is only fine for pure tabular data, and the UCD or CDLR data is has
a more complex structure than a simple 2D table. In addition, the schema is
evolving, with new kind of datas added everytime; you cannot keep that
compatibility by adding more empty columns to a single table; adding new
sem
On Mon, Sep 03, 2018 at 08:24:06AM +0200, Janusz S. Bień via Unicode wrote:
> For a non-programmer like me CVS is much more convenient form than XML -
> I can use it not only with a spreadsheet, but also import directly into
> a database and analyse with various queries. XML is politically correct,
On Sun, Sep 02 2018 at 4:16 +0200,
[...]
> So you can understand that I’m not unaware of the complexity of UCD. Though
> I don’t think that this could be an argument for not publishing a medium-size
> CSV file with scalar values listed as in UnicodeData.txt.
For a non-programmer like me CVS i
I’m not responding without thinking, as I was blamed of when I did,
but it is painful for me to dig into what Ken explained about how
we should be consuming UCD data. I’ll now try to get some more clarity
into the topic.
> On 31/08/18 19:59 Ken Whistler via Unicode wrote:
> […]
> >
> > Third, pl
4 matches
Mail list logo
