On Tue, 23 May 2017 17:44:49 -0700
Ken Whistler via Unicode wrote:
> Ah, but keep in mind, if projecting out to Version 23.0 (in the year
> 2030, by our current schedule), there is a significant chance that
> particular UCD data files may have morphed into something entirely
> different. Reca
Richard
On 5/23/2017 1:48 PM, Richard Wordingham via Unicode wrote:
The object is to generate code*now* that, up to say Unicode Version 23.0,
can work out, from the UCD files DerivedAge.txt and
PropertyValueAliases.txt, whether an arbitrary code point was included
by some Unicode version ident
On Tue, 23 May 2017 05:29:33 -0700
Asmus Freytag via Unicode wrote:
> On 5/23/2017 4:04 AM, Janusz S. Bien via Unicode wrote:
> > Quote/Cytat - Manuel Strehl via Unicode (Tue
> > 23 May 2017 11:33:24 AM CEST):
> >
> >> The rising standard in the world of web development (and others)
> >> is ca
2017-05-23 8:43 GMT+02:00 Asmus Freytag via Unicode :
> On 5/22/2017 3:49 PM, Richard Wordingham via Unicode wrote:
>
>> One of the objectives is to use a current version of the UCD to
>> determine, for example, which characters were in Version x.y. One
>> needs that for a regular expression such
On 5/23/2017 4:04 AM, Janusz S. Bien via Unicode wrote:
Quote/Cytat - Manuel Strehl via Unicode (Tue 23
May 2017 11:33:24 AM CEST):
The rising standard in the world of web development (and others) is
called
»Semantic Versioning« [1], that many projects adhere to or sometimes
must
actively e
Quote/Cytat - Manuel Strehl via Unicode (Tue 23
May 2017 11:33:24 AM CEST):
The rising standard in the world of web development (and others) is called
»Semantic Versioning« [1], that many projects adhere to or sometimes must
actively explain, why they don't.
The structure of a »semantic vers
The rising standard in the world of web development (and others) is called
»Semantic Versioning« [1], that many projects adhere to or sometimes must
actively explain, why they don't.
The structure of a »semantic version« string is a set of three integers,
MAJOR.MINOR.PATCH, where the »sematics« pa
On 5/22/2017 3:49 PM, Richard Wordingham via Unicode wrote:
One of the objectives is to use a current version of the UCD to
determine, for example, which characters were in Version x.y. One
needs that for a regular expression such as [:Age=3.0:], which
also matches all characters that have survi
On Mon, 22 May 2017 17:19:08 -0500
Anshuman Pandey wrote:
> I performed several operations on DerivedAge.txt a few months ago.
> One basic example here:
>
> https://pandey.github.io/posts/unicode-growth-UCD-python.html
So what happens if you apply it to Unicode Version 10.0? Are the
versions s
On Mon, 22 May 2017 15:10:02 -0700
Markus Scherer via Unicode wrote:
> On Mon, May 22, 2017 at 2:44 PM, Richard Wordingham via Unicode <
> unicode@unicode.org> wrote:
>
> > Given two raw values of the Age property, defined in UCD file
> > DerivedAge.txt, how is a computer program supposed to c
I performed several operations on DerivedAge.txt a few months ago. One basic
example here:
https://pandey.github.io/posts/unicode-growth-UCD-python.html
If you provide some more insight into your objective, I might be able to help.
I would recommend against relying on the order of the data, and
On Mon, May 22, 2017 at 2:44 PM, Richard Wordingham via Unicode <
unicode@unicode.org> wrote:
> Given two raw values of the Age property, defined in UCD file
> DerivedAge.txt, how is a computer program supposed to compare them?
> Apart from special handling for the value "Unassigned" and its short
Given two raw values of the Age property, defined in UCD file
DerivedAge.txt, how is a computer program supposed to compare them?
Apart from special handling for the value "Unassigned" and its short
alias "NA", one used to be able to compare short values against short
values and long values against
13 matches
Mail list logo
