For web searching, using the math-string 푀푎푦푛푎푟푑 퐾푒푦푛푒푠 as
the keywords finds John Maynard Keynes in web pages. Tested this in
both Google and DuckDuckGo. Seems like search engines are accomodating
actual user practices. This suggests that social media data is possibly
already being
I’m implementing a Unicode names library. I’m confused about loose
character-name matching, even after rereading The Unicode Standard § 4.8, UAX
#34 § 4, #44 § 5.9.2 – as well as
[L2/13-142](http://www.unicode.org/L2/L2013/13142-name-match.txt
On Thu, 17 Jan 2019 18:35:49 +0100
Marcel Schneider via Unicode wrote:
> Among the grievances, Unicode is blamed for confusing Greek psili and
> dasia with comma shapes, and for misinterpreting Latin letter forms
> such as the u with descender taken for a turned h, and double u
> mistaken for a
[Just a quick note to everyone that, I’ve just subscribed to this public list,
and will look into this ongoing Mongolian-related discussion once I’ve mentally
recovered from this week’s UTC stress. :)]
Best,
梁海 Liang Hai
https://lianghai.github.io
> On Jan 17, 2019, at 11:06, Asmus Freytag via
On 1/17/2019 9:35 AM, Marcel Schneider
via Unicode wrote:
[quoted mail]
But the French "espace fine insécable" was requested
long long before Mongolian was discussed for encodinc in
Thanks for this nice website !
Some feedback:
Given the number of scripts in this period, I think that
splitting 10c-19c in two (or even three) would be a good idea
A finer unicode status would be nice
On 17/01/2019 12:21, Philippe Verdy via Unicode wrote:
[quoted mail]
But the French "espace fine insécable" was requested long long before Mongolian
was discussed for encodinc in the UCS. The problem is that the initial rush for French
was made in a period where Unicode and ISO were
On 17/01/2019 14:36, I wrote:
[…]
The only thing that searches have brought up
It was actually the best thing. Here’s an even more surprising hit:
B. In the rules, allow these characters to bridge both
alphabetic and numeric words, with:
* Replace MidLetter
If encoding italics means reencoding the normal linguistic usage, it is no
! We already have the nightmares caused by partial encoding of Latin and
Greek (als a few Hebrew characters) for maths notations or IPA notations,
but they are restricted to a well delimited scope of use and subset, and at
On 17/01/2019 12:21, Philippe Verdy via Unicode wrote:
[quoted mail]
But the French "espace fine insécable" was requested long long before Mongolian
was discussed for encodinc in the UCS.
Then we should be able to read its encoding proposal in the UTC document
registry, but Google Search
On 2019-01-17 11:50 AM, Martin J. Dürst wrote:
> Most probably not. I think Asmus has already alluded to it, but in good
> typography, roman and italic fonts are considered separate.
So are Latin and Cyrillic fonts. So are American English and Polish
fonts, for that matter, even though
On 2019/01/17 17:51, James Kass via Unicode wrote:
>
> On 2019-01-17 6:27 AM, Martin J. Dürst replied:
> > ...
> > Based by these data points, and knowing many of the people involved, my
> > description would be that decisions about what to encode as characters
> > (plain text) and what to
On 17/01/2019 09:58, Richard Wordingham wrote:
On Thu, 17 Jan 2019 04:51:57 +0100
Marcel Schneider via Unicode wrote:
Also, at least one French typographer was extremely upset
about Unicode not gathering feedback from typographers.
That blame is partly wrong since at least one typographer
Le jeu. 17 janv. 2019 à 05:01, Marcel Schneider via Unicode <
unicode@unicode.org> a écrit :
> On 16/01/2019 21:53, Richard Wordingham via Unicode wrote:
> >
> > On Tue, 15 Jan 2019 13:25:06 +0100
> > Philippe Verdy via Unicode wrote:
> >
> >> If your fonts behave incorrectly on your system
Andrew Cunningham wrote:
Underlying, bold text, interletter spacing, colour change, font style
change all are used to apply meaning in various ways. Not sure why
italic is special in this sense.
Italic is uniquely different from these in that the meaning has been
well-established in our
( I appreciate that UTC meetings are going on - I too will be traveling
a bit over the next couple of weeks, so may not respond quickly. )
Support for marking 'italic' in plain text - however it's done - would
certainly require changes in text processing. That would also be the
case for some
Courier New was lacking NNBSP on Windows 7. It is including it on
Windows 10. The tests I referred to were made 2 years ago. I
confess that I was so disappointed to see Courier New unsupporting
NNBSP a decade after encoding, while many relevant people in the
industry were surely aware of its role
On Thu, 17 Jan 2019 04:51:57 +0100
Marcel Schneider via Unicode wrote:
> Also, at least one French typographer was extremely upset
> about Unicode not gathering feedback from typographers.
> That blame is partly wrong since at least one typographer
> was and still is present in WG2, and even if
On 2019-01-17 6:27 AM, Martin J. Dürst replied:
> ...
> So even if you can find examples where the presence or absence of
> styling clearly makes a semantic difference, this may or will not be
> enough. It's only when it's often or overwhelmingly (as opposed to
> occasionally) the case that a
19 matches
Mail list logo
