On 19 Aug 2015 at 20:59, I wrote:
On 19 Aug 2015 at 17:18, William_J_G Overington wrote:
I suggest to Emma the contacting of Unicode Inc. using the following form.
http://www.unicode.org/reporting.html
William is right. I strongly recommend you to first use the Contact form, as
I did
I'm trying to work out the meaning of TUS 8.0 Section 23.2.
To do Thai word breaking properly, one needs to do a semantic analysis
of the text to do the equivalent of resolving the equivalent of
'humanevents' into 'human events' rather than 'humane vents'. One also
needs to cope with unknown and
On Sat, 22 Aug 2015 14:08:14 -0600
Karl Williamson pub...@khwilliamson.com wrote:
But it isn't such a replacement, creating some consternation, and the
main reason is that, unlike \b, it treats the boundary between white
space characters as a breaking opportunity, so that it doesn't create
On Sat, 22 Aug 2015 10:32:45 -0700
Asmus Freytag (t) asmus-...@ix.netcom.com wrote:
On 8/22/2015 9:35 AM, Julian Bradfield wrote:
There is no inherent meaning to the
order of codepoints, it's just convenience.
And for that reason, we have property files to explicitly give the
properties
The concept of \b in a regular expression meaning to match the boundary
between a word and non-word was invented by Larry Wall, for the Perl
programming language. This was before Unicode, and a word was defined
as alphanumerics plus the underscore, which fit well with how
identifiers in that
On 8/22/2015 2:47 PM, Richard
Wordingham wrote:
But codepoints are normally orderly until they enter the ISO approval
process. Thereafter, disorder creeps in, and becomes ever more likely
as blocks fill up
Haha, good one.
. The
On 8/22/2015 9:35 AM, Julian Bradfield
wrote:
There is no inherent meaning to the
order of codepoints, it's just convenience.
And for that reason, we have property files to
explicitly give the properties rather than asking the user to "glean"
Hi all
I am looking for clarification on an aspect of Unicode bracket pairing,
specifically in relation to the following four characters:
298D; 2990; o # LEFT SQUARE BRACKET WITH TICK IN TOP CORNER
298E; 298F; c # RIGHT SQUARE BRACKET WITH TICK IN BOTTOM CORNER
298F; 298E; o # LEFT SQUARE
From: Nigel Small ni...@nigelsmall.com
Date: Sat, 22 Aug 2015 17:08:48 +0100
I am looking for clarification on an aspect of Unicode bracket pairing,
specifically in relation to the following four characters:
298D; 2990; o # LEFT SQUARE BRACKET WITH TICK IN TOP CORNER
298E; 298F; c #
On 2015-08-22, Nigel Small ni...@nigelsmall.com wrote:
298D; 2990; o # LEFT SQUARE BRACKET WITH TICK IN TOP CORNER
298E; 298F; c # RIGHT SQUARE BRACKET WITH TICK IN BOTTOM CORNER
298F; 298E; o # LEFT SQUARE BRACKET WITH TICK IN BOTTOM CORNER
2990; 298D; c # RIGHT SQUARE BRACKET WITH TICK IN
10 matches
Mail list logo
