On 11/9/2012 1:26 AM, Jean-François Colson wrote:
For a five level rating, ○ ◔ ◑ ◕ ● could do the job.
Yes it's possible to use other sets of symbols to indicate rating, but
when it comes to such use of symbols Unicode would not encode the
semantic of rating but that of star. The deeper
On 11/9/2012 5:53 PM, Philippe Verdy wrote:
Why then stars ? Any symbol, even any Unicode letter could be repeated
and half-filled.
There's nothing magical about limiting the half-filled geometrical
shapes to the current (haphazard) set. If half-filled stars can be
documented, they are
On 11/9/2012 7:14 PM, Philippe Verdy wrote:
2012/11/9 Asmus Freytag asm...@ix.netcom.com:
Actually, there are certain instances where characters are encoded based on
expected usage. Currency symbols are a well known case for that, but there have
been instances of phonetic characters encoded
On 11/11/2012 2:08 PM, Doug Ewell wrote:
Personal opinions follow.
It looks like the only actual use case we have, exemplified by the
xkcd strip, is for a star with the left half black and the right half
white. There *might* also be a case for the left-white, right-black star.
Precedent is
On 11/11/2012 3:01 PM, Asmus Freytag wrote:
On 11/11/2012 2:08 PM, Doug Ewell wrote:
Personal opinions follow.
It looks like the only actual use case we have, exemplified by the
xkcd strip, is for a star with the left half black and the right half
white. There *might* also be a case
On 11/11/2012 4:50 PM, Philippe Verdy wrote:
2012/11/12 Kent Karlsson kent.karlsso...@telia.com
mailto:kent.karlsso...@telia.com
rendering tomatoes or doughnuts or film reels as glyph variants of
stars,
They should certainly **NOT** be treated as glyph variants of
stars!
On 11/11/2012 8:47 PM, Philippe Verdy wrote:
No, I was clear throughout, using the same arguments, that encoding
things for the purpose of representing empty, full, half filled
like if it was a nuemric gauge was a bad idea.
Trying to encode a gauge is indeed a losing proposition.
When I
On 11/11/2012 9:26 PM, Philippe Verdy wrote:
2012/11/12 Asmus Freytag asm...@ix.netcom.com
mailto:asm...@ix.netcom.com
However, the half-filled, five pointed stars are garden-variety
type symbols, and, as I keep pointing out, they absolutely fall
within the scope
On 11/12/2012 10:13 AM, Philippe Verdy wrote:
2012/11/12 Asmus Freytag asm...@ix.netcom.com
mailto:asm...@ix.netcom.com
On 11/11/2012 9:26 PM, Philippe Verdy wrote:
2012/11/12 Asmus Freytag asm...@ix.netcom.com
mailto:asm...@ix.netcom.com
However, the half-filled, five
On 11/12/2012 1:27 PM, Khaled Hosny wrote:
I’m not sure from where you are getting your statistics, but I’ve to
deal with all those “rare” and “extremely rare” situations all the day.
Khaled, don't mind Philippe - his experience is a bit on the
theoretical end.
A./
On 11/12/2012 7:13 AM, David Starner wrote:
On Mon, Nov 12, 2012 at 4:39 AM, Julian Bradfield
jcb+unic...@inf.ed.ac.uk wrote:
Again, it depends. A user-oriented editor will treat é as a single
unit anyway, for text manipulations. In my programmer-oriented editor,
when the cursor is on e or ́,
In the business of character encoding, it's not helpful to try to
construct algorithmic rules that lead from one set of conditions to the
state of encoded. It just doesn't work that way.
What does work is to think of factors, or criteria, that you can use in
weighing a question. Certain
On 11/27/2012 5:39 AM, Masatoshi Kimura wrote:
(2012/11/27 20:27), Philippe Verdy wrote:
Could you please stop spreading an unfounded rumor such as Firefox is
wrong because it ignores the lacking of HTML5 prolog?
Getting Philippe to stop spreading unfounded anything is a near
impossible
On 12/11/2012 11:50 AM, vanis...@boil.afraid.org wrote:
From: James Lin James_Lin_at_symantec.com
Hi
Does anyone know why ill-form occurred on the UTF-8? besides it doesn't follow
the pattern of UTF-8 byte-sequences, i just wondering how or why?
If i have a code point: U+4E8C or 二
In UTF-8,
In relating the size of different series of geometric shapes with each
other, the relevant aspect is not the height of the ink but the area, in
my opinion.
I'm currently not able to take the time to sift through various
documents and propose any resolution, but I would like to make sure that
element for this, but perhaps not the only one - if
you know you are using the STIX fonts you can adjust your styles or
glyph (character) selection to tweak the outcome, something that isn't
an option for a generic prescription.
A./
Michel
*From:*Asmus Freytag [mailto:asm...@ix.netcom.com]
*Sent
On 12/20/2012 2:52 AM, Martinho Fernandes wrote:
Hello,
I was wondering if there is a list of character names translated into
other languages somewhere. Is there?
A French list was created, and for a while maintained with funding from
the Canadian government. It covered the complete list
On 12/20/2012 7:26 AM, Leif Halvard Silli wrote:
Andreas Prilop, Thu, 20 Dec 2012 15:41:28 +0100 (CET):
On Thu, 20 Dec 2012, Jukka K. Korpela wrote:
http://www.ling.helsinki.fi/filt/info/mes2/
Unicode names have certain restrictions (capital ASCII letters, etc).
This Finnish list even uses
On 12/20/2012 2:36 PM, Jukka K. Korpela wrote:
2012-12-20 14:13, David Starner wrote:
It may be useful to try to agree on official or semi-official names for
characters in a language. Such a list hardly needs to cover all of
the over
100,000 Unicode characters.
Why not? Why should an
On 12/20/2012 5:12 PM, Philippe Verdy wrote:
Given the form of these names in the UCD, most of them could be
translated automatically using a common dictionnary and resolving some
terminologies that are approximative in Unicode.
If you mean by that: can usefully be done with a translation
On 12/23/2012 3:55 PM, Joó Ádám wrote:
Roger, thank you for sharing this excerpt, I truly enjoyed it. You
drew my attention to a book I should definitely have a look at.
It's definitely a nice way to introduce people or remind them of this
book. I'm sure, some misguided publishers would like
On 12/23/2012 10:58 PM, Asmus Freytag wrote:
It's definitely a nice way to introduce people or remind them of this
book.
There's a word missing in that sentence.
On 12/30/2012 1:22 PM, Costello, Roger L. wrote:
Hi Folks,
I have heard it stated that, in the context of character encoding and decoding:
Interoperability is getting better.
Do you have data to back up the assertion that interoperability is getting
better?
The number of times that I
On 12/30/2012 3:19 PM, Leif Halvard Silli wrote:
My feeling is that interoperability is getting better everywhere. But one
field which lags behind is e-mail. Especially Web archives of
e-mail (for instance, take the WHATwg.org’s web archive). And also some e-mail
programs fail to default to
On 12/31/2012 3:27 AM, Leif Halvard Silli wrote:
Asmus Freytag, Sun, 30 Dec 2012 17:05:56 -0800:
The Web archive for this very list, needs a fix as well …
The way to formally request any action by the Unicode Consortium is via
the contact form (found on the home page).
A./
On 1/1/2013 3:53 PM, Naena Guru wrote:
(By the way, Unicode is quietly suppressing Basic Latin block by
removing it from the Latin group at top of the code block page
(http://www.unicode.org/charts/) and hiding it under different names
in the lower part of the page.)
I don't know what you
On 1/1/2013 12:43 PM, Costello, Roger L. wrote:
Hi Folks,
Does the term codepoint apply to non-Unicode character sets?
For example, are there codepoints in iso-8859-1? In Windows-1252?
/Roger
The short answer is yes.
The term code point was in use for locations in IBM code pages long
From: Asmus Freytag mailto:asm...@ix.netcom.com
Sent: 1/1/2013 23:43
To: Costello, Roger L. mailto:coste...@mitre.org
Cc: unicode@unicode.org mailto:unicode@unicode.org
Subject: Re: Terminology: does the term codepoint apply to
non-Unicode character sets?
On 1/1
On 1/2/2013 3:26 PM, Jukka K. Korpela wrote:
2013-01-03 0:22, Markus Scherer wrote:
The page has been modified to add an alias for Basic Latin (ASCII) under
the Latin heading.
I can see that, but I don’t think it’s an improvement. It puts the
Latin script in a special status.
The
On 1/4/2013 2:36 AM, Stephan Stiller wrote:
All,
There are plenty of unassigned code points within blocks that are in
use; these often come at the end of a block but there are plenty of
holes as well.
I have a cluster of interrelated questions:
1. What sorts of reasons are there (or have
On 1/10/2013 2:08 AM, Otto Stolz wrote:
Hello,
le 09/01/2013 18:07, Frédéric Grosshans a écrit :
Yes, but I actually don't know. I'd really like to have some idea on
those old
printing techniques, but I fear we're drifting to off topic subjects...
Am 2013-01-09 um 18:16 schrieb Frédéric
On 1/10/2013 5:21 AM, Frédéric Grosshans wrote:
Le 10/01/2013 11:08, Otto Stolz a écrit :
Hello,
le 09/01/2013 18:07, Frédéric Grosshans a écrit :
Yes, but I actually don't know. I'd really like to have some idea on
those old
printing techniques, but I fear we're drifting to off topic
http://ts2.mm.bing.net/th?id=H.4791646751032057pid=1.7w=176h=155c=7rs=1
??
Relation? Visual or otherwise. Pun?
(Note the similarity :widder: :wider:)
Just thinking out loud.
A./
On 1/16/2013 5:35 PM, Philippe Verdy wrote:
Fair enough. It's not a problem to ask the question, Is this a candidate for
encoding? It becomes a problem when the poster assumes, because thet blob appeared
in such-and-so location, that it MUST be a candidate for encoding, and no level of
On 1/21/2013 4:11 PM, Andrés Sanhueza wrote:
Hello.
I have wondered if it may be a good idea to make a proposal to an
spiral character, basically because I believe is the only mayor
symbol recurrently used for represent swearing in comics that's
missing from Unicode.
If it should come to a
On Thu, 24 Jan 2013 20:05:41 -0300
Andrés Sanhueza peroyomasli...@gmail.com wrote:
Do you think that a end of story symbol may be feasible/useful?
My position is that the attempt to encode such semantics that are
defined on the whole text level is a mistake. In fact, it is a common
On 1/25/2013 6:52 AM, Joó Ádám wrote:
Asmus, I would be happy to hear your opinion on my question, in
context of which I may not have been clear on that my intent is not to
propose a general character for all uses as end-of-story sign but a
well-defined symbol based on both shape and usage
On 1/25/2013 7:44 AM, Mark E. Shoulson wrote:
On 01/25/2013 08:12 AM, Joó Ádám wrote:
I don’t know of its use outside of Hungary, but here, as the quote of
Halmos suggests, the tombstone is traditionally used in print
magazines as end of story. We have adopted it to the web on the
Weblabor
On 1/28/2013 5:12 AM, Martinho Fernandes wrote:
Similarly, there could be a type of pdf document where the text within the pdf
document were stored in UTF-64 format.
FWIW, there is already a PDF variant designed for long-term archiving
known as PDF/A. You may want to look into that.
Good
On 1/28/2013 5:12 AM, Martinho Fernandes wrote:
Similarly, there could be a type of pdf document where the text within the pdf
document were stored in UTF-64 format.
FWIW, there is already a PDF variant designed for long-term archiving
known as PDF/A. You may want to look into that.
Good
On 1/28/2013 4:30 AM, William_J_G Overington wrote:
The idea is that there would be an additional UTF format, perhaps UTF-64, so
that each character would be expressed in UTF-64 notation using 64 bits, thus
providing error checking and correction facilities at a character level.
I think this
Mark,
in my view, the key aspect of the notice cited by Debbie, is the
rejection of an external link semantic, which would act as a kind of
generic code and could be rendered in many different ways.
Instead, the notice leaves open a request to standardize a particular
shape, which then
On 1/31/2013 5:55 PM, Mark E. Shoulson wrote:
So if a generic external link symbol isn't acceptable, I definitely
see reason for at least the adoption of box-with-arrow, possibly
*called* EXTERNAL LINK or something.
Make that: possibly aliased or annotated as one of the symbols used
to
How come I'm not surprised to see the problem traced to an RTF format
incompatibility. Trying to figure out which parts of the RTF spec to
support when is nearly impossible...
A./
On 2/7/2013 8:08 AM, Murray Sargent wrote:
If you include a {\fonttbl...} entry that defines \f0 as an Arabic
On 2/13/2013 1:59 PM, Andries Brouwer wrote:
[Concerning the g-slash, r-slash, eth-slash symbols,
they can be coded using U+0337 as g̷ r̷ ð̷.
Unicode generally does not decompose slashed symbols - so for example,
o-slash does not have a decomposition using U+0337. The UTC may not
feel bound
On 2/13/2013 1:24 PM, Stephan Stiller wrote:
It looks like something that has not been encoded.
What is the reason for not having a true combining grapheme joiner,
one that overlays graphemes? Or a code point that instructs that the
preceding (or following, I guess) code point should be
On 2/13/2013 2:58 PM, Buck Golemon wrote:
On Wed, Feb 13, 2013 at 2:30 PM, Asmus Freytag asm...@ix.netcom.com wrote:
On 2/13/2013 1:24 PM, Stephan Stiller wrote:
It looks like something that has not been encoded.
What is the reason for not having a true combining grapheme joiner, one
On 2/13/2013 2:56 PM, Leo Broukhis wrote:
On Wed, Feb 13, 2013 at 11:31 AM, Andries Brouwer a...@win.tue.nl wrote:
I wondered how to code an s-j overstrike combination in Unicode.
I'd write s ZWJ j and use a font that has the appropriate ligature.
These features in Unicode aren't intended
On 2/13/2013 6:00 PM, Leo Broukhis wrote:
Everything dialectology-related is a fancy presentation of the
phoneme attribute markup.
Well, that's one view.
A./
Leo
On Wed, Feb 13, 2013 at 5:51 PM, Asmus Freytag asm...@ix.netcom.com wrote:
On 2/13/2013 2:56 PM, Leo Broukhis wrote:
On Wed
require to resubmit the
sections from 3555 that contain them and restart the discussion in UTC
and WG2.
But I'm sure you'll eventually hear from a direct participant.
On Wed, Feb 13, 2013 at 02:24:12PM -0800, Asmus Freytag wrote:
On 2/13/2013 1:59 PM, Andries Brouwer wrote:
[Concerning the g
On 2/15/2013 11:59 PM, Andries Brouwer wrote:
On Fri, Feb 15, 2013 at 10:56:17PM -0600, Ben Scarborough wrote:
On Feb 16, 2013 02:13, Andries Brouwer wrote:
The fragment of text I showed
was not from dialectology, but just from a novel written in Elfdalian.
The symbols are meant to be those of
On 2/16/2013 1:38 AM, Stephan Stiller wrote:
That would make it analogous in a way to German ß.
The minute things show up in real orthographies the pressure to
handle ALL CAPS exists.
The question then is whether you'll find SJ or overlaid S/J. Or
how a Swede would instinctively handle
On 2/16/2013 7:04 AM, Andries Brouwer wrote:
[BTW Is the fact that o-slash is not decomposed not entirely
analogous to the fact that i is not decomposed? I would say
that neither gives an indication of how symbols involving
a combining dot or combining slash are handled in general.]
Why don't
On 2/16/2013 7:04 AM, Andries Brouwer wrote:
I found Diauni.ttf at
http://www.thesauruslex.com/typo/dialekt.htm (swedish)
http://www.thesauruslex.com/typo/engdial.htm (english)
It has landmålsalfabetet at E100-E197 (lower case only)
and s-j at E19F, S-J at E1A5, with Y-ogonek, Å-ogonek,
On 2/16/2013 10:48 AM, Stephan Stiller wrote:
the issue is a bit different, as not focused on one letter
While we're splitting hairs: Word- or larger-level all-caps /does/
normally make a one-letter difference. When we undo all-caps, one can
/normally/ lowercase everything of the word except
On 2/16/2013 10:48 AM, Stephan Stiller wrote:
the issue is a bit different, as not focused on one letter
While we're splitting hairs: Word- or larger-level all-caps /does/
normally make a one-letter difference. When we undo all-caps, one can
/normally/ lowercase everything of the word except
On 2/16/2013 12:06 PM, Philippe Verdy wrote:
2013/2/16 Stephan Stiller stephan.stil...@gmail.com:
Of course in my worldview, all-caps writing is deprecated :-)
This is a presentation style which makes words more readable in some
conditions, notably on plates displayed on roads (cities are
On 2/16/2013 9:55 PM, Stephan Stiller wrote:
from earlier:
Otto Scholz
Oops, sorry. Otto Stolz.
And usually not totally sense-destroying to a human reader with
context available. But these fallbacks allow clear misspelled words
to appear, not just miscapitalized ones. That's huge.
I'm all
On 2/17/2013 12:30 AM, Stephan Stiller wrote:
But I have to ask one more thing:
Since the latter is expected to be rare, I personally would be
comfortable with making a code point for it, so that fonts like this,
which are actually used, can be mapped to Unicode w/o forcing people
into
On 2/16/2013 11:19 PM, Julian Bradfield wrote:
On 2013-02-17, Philippe Verdy verd...@wanadoo.fr wrote:
True lowercase letters are causing problems on road sign indicators on
roads with high speed : they are hard to read and if the driver has to
look at them for one more second, he does not look
On 2/17/2013 8:20 AM, Richard Wordingham wrote:
Is there any guarantee that U+E4567 will not have a
canonical decomposition mapping to U+0F73 TIBETAN VOWEL SIGN II,
U+E4568? If so, where is it published? I thought we had guarantees
that new canonical decompositions to non-starters would not be
Nice collection of links, here, Neil.
A./
On 2/17/2013 10:52 AM, Neil Harris wrote:
On 17/02/13 10:48, Philippe Verdy wrote:
I was not citing empirical results but things that are regulated by
legislation.
And your existing empirical results are just nfomal tests ignoring
important parts of
On 2/18/2013 5:43 AM, Erkki I Kolehmainen wrote:
This looks quite clear to me. If I create something and somebody else uses my
creation in the intended context, he agrees to my definition. his agreement is
private, outside the standard, since the same code points may represent a
multitude of
Toll, eine dreisprachige Nachricht! Wer macht weiter?
A./
On 2/18/2013 10:25 PM, Charlie Ruland wrote:
Ne vous moquez pas de monsieur Verdy: il s’ agit là du dernier des
Mohicans polymathes ! ☺
Charlie
Op zondag 17 februari 2013 schreef Asmus Freytag:
Would not be the first time that Mr
On 2/19/2013 9:35 AM, Leif Halvard Silli wrote:
Werner LEMBERG, Tue, 19 Feb 2013 10:48:52 +0100 (CET):
Otto Stoltz wrote:
Here is a minimal pair to illustrate that point:
Er hat in Moskau liebe Genossen.
Er hat in Moskau Liebe genossen.
which translates to:
At Moskow, he’s got
On 2/19/2013 2:26 PM, Andries Brouwer wrote:
On Tue, Feb 19, 2013 at 09:55:09AM +0100, Elbrecht wrote:
The academical TITUS project occupied U+E000 thru U+EFFF
of the Private Use Area ...
The primary Private Use Area is U+E000 .. U+F8FF today.
However, Unicode 1.0 defined a Private Use Area
Richard,
the situation with the raised decimal point is a mess in Unicode.
I know that Mark thinks we have too many dots, but the reason this case
is a mess is because the unification with U+002E is both non-workable in
practice and runs counter to precedent.
The precedent in Unicode is to
On 3/9/2013 1:51 PM, Jukka K. Korpela wrote:
2013-03-09 21:30, Asmus Freytag wrote:
I believe the Unicode Standard should be fixed by explicitly removing
all suggestions in the text that the raised decimal point is unified
with 002E.
That would be a good move if agreement can be found
On 3/9/2013 3:41 PM, Philippe Verdy wrote:
2013/3/9 Asmus Freytag asm...@ix.netcom.com:
This appears to be another possible mistake. However, the Greek script does
provide a context which could be used to select the ano teleia appearance
and properties (unless you tell me that the character
On 3/9/2013 5:30 PM, Richard Wordingham wrote:
On Sat, 09 Mar 2013 14:41:11 -0800
Asmus Freytag asm...@ix.netcom.com wrote:
On 3/9/2013 1:51 PM, Jukka K. Korpela wrote:
2013-03-09 21:30, Asmus Freytag wrote:
I wonder what character and techniques British publishers use to
produce notations
Richard has given some cogent arguments below.
Another counter example is the use of : to form abbreviations in
Swedish. (It's inserted in the word to replace the elided part). In that
use, this punctuation character is suddenly part of a word.
To handle the full set of general case, word
On 3/9/2013 6:01 PM, Stephan Stiller wrote:
'The Lancet' reportedly insists on the use of the raised decimal point
(http://www.download.thelancet.com/flatcontentassets/authors/artwork-guidelines.pdf)
and gives the instructions 'Type decimal points midline (ie, 23·4, not
23.4). To create a
On 3/9/2013 5:47 PM, Philippe Verdy wrote:
2013/3/10 Asmus Freytag asm...@ix.netcom.com:
On 3/9/2013 3:41 PM, Philippe Verdy wrote:
2013/3/9 Asmus Freytag asm...@ix.netcom.com:
This appears to be another possible mistake. However, the Greek script
does
provide a context which could be used
On 3/13/2013 10:25 PM, Peter Constable wrote:
I would be inclined to assume that there are Unicode 1.1 apps loitering about.
What marks an implementation as version X.y ?
If the implementation doesn't support any processing of characters for
which there is a mandatory conformance
On the basis of security considerations, it might be necessary to not
allow variation selectors to salt strings for parsing. If the string
cannot be rejected, then the proper thing might be to parse it as if the
variation selectors were not present (on the basis that they do not
affect
On 3/21/2013 4:22 PM, Philippe Verdy wrote:
2013/3/21 Richard Wordingham richard.wording...@ntlworld.com:
Further, the code chart glyphs for the ANO TELEIA and the MIDDLE DOT
differ, see attachment. If they are canonically equivalent, and one
is a mandatory decomposition of the other, why do
On 3/22/2013 4:02 AM, Philippe Verdy wrote:
2013/3/22 Asmus Freytag asm...@ix.netcom.com:
Semantic selectors are pure pseudo-coding, because if the semantic
differentiation is needed it is needed in plain text - and then it should be
expressible in plain character codes.
We don't disagree
On 3/22/2013 4:08 AM, Philippe Verdy wrote:
2013/3/22 Asmus Freytag asm...@ix.netcom.com:
If you need to annotate text with the results of semantic analysis as
performed by a human reader, then you either need XML, or some other format
that can express that particular intent.
Absolutely
On 3/22/2013 4:16 AM, Philippe Verdy wrote:
2013/3/22 Asmus Freytag asm...@ix.netcom.com:
The number of conventions that can be applicable to certain punctuation
characters is truly staggering, and it seems unlikely that Unicode is the
right place to
a) discover all of them or
b) standardize
On 3/22/2013 12:08 PM, Karl Williamson wrote:
On 03/21/2013 04:48 PM, Richard Wordingham wrote:
For linguistic analysis, you need the normalisation appropriate to the
task.
Linguistic analysis (in general) being a hugely complex undertaking,
mere normalization pales in comparison, so
On 3/22/2013 6:17 PM, Richard Wordingham wrote:
On Fri, 22 Mar 2013 18:01:14 -0700
Asmus Freytag asm...@ix.netcom.com wrote:
On 03/21/2013 04:48 PM, Richard Wordingham wrote:
However, distinguishing U+00B7 and U+0387 would fail spectacularly
of the text had been converted to form NFC before
On 3/23/2013 4:55 AM, Michael Everson wrote:
On 23 Mar 2013, at 01:01, Asmus Freytag asm...@ix.netcom.com wrote:
Let's get back to the interesting question:
Is it possible to correctly process text that uses 00B7 for ANO TELEIA, or is
this fundamentally impossible? If so, under what scenario
The question is who would be able to take on the drafting of a document
that explains the recommended usage of 00B7 for the various purposes
(including recommended ways of getting the correct rendering and
processing).
ONLY by having such a document, is it possible to be certain that the
On 3/27/2013 12:07 PM, Philippe Verdy wrote:
2013/3/27 Asmus Freytag asm...@ix.netcom.com:
At the moment, the statement that the existing encoding is actually
implementable is something that must be considered unproven (enough issues
have been pointed out for various elements of the unification
On 4/1/2013 12:19 PM, Buck Golemon wrote:
The only remaining question is whether the colors should be
represented in the HSL or HSV color space.
Go HSV http://www.hsv.de/news/!
On 4/22/2013 4:27 AM, Charlie Ruland ☘ wrote:
* William_J_G Overington [2013/4/22]:
[...]
If the scope of Unicode becomes widened in this way, this will provide a basis
upon which those people who so choose may research and develop localizable
sentence technology with the knowledge that such
On 4/22/2013 12:35 PM, Stephan Stiller wrote:
[Charlie Ruland:]
The Unicode Consortium is prepared to encode all characters that can
be shown to be in actual use.
Are you sure there is a precedent for what is essentially markup for a
system of (alpha)numerical IDs?
You don't even have to
On 4/23/2013 3:00 AM, Philippe Verdy wrote:
Do you realize the operating cost of any international standard
comittee or for the maintenance ans securization of an international
registry ? Who will pay ?
Currently we all are paying by having interminable discussions of
half-baked ideas
On 4/23/2013 2:01 AM, William_J_G Overington wrote:
On Monday 22 April 2013, Asmus Freytag asm...@ix.netcom.com wrote:
I'm always suspicious if someone wants to discuss scope of the standard before
demonstrating a compelling case on the merits of wide-spread actual use.
The reason that I
On 5/26/2013 3:15 PM, David Starner wrote:
On Sun, May 26, 2013 at 12:40 PM, Andreas Stötzner a...@signographie.de wrote:
One of the bodies in the world still ignorant of this fact to the very day
is Unicode. Which I feel is a mess.
Problems from Unicode generally come from of two places;
On 5/29/2013 1:39 AM, Andreas Stötzner wrote:
Am 29.05.2013 um 01:06 schrieb David Starner:
And what you'll run into is the fact that people don't agree that that
belongs in Unicode.
What Andreas was suggesting is rigorous study. I think that is a
commendable suggestion.
The more
On 5/29/2013 8:39 AM, Leo Broukhis wrote:
I'd like to ask: what is supposed to be the trigger condition for the
UTC to consider changing the representative glyph of
your favorate symbol here to a novel design?
The answer: the purpose of the representative glyph is not to track
fashions
On 5/29/2013 9:38 AM, Leo Broukhis wrote:
On Wed, May 29, 2013 at 9:35 AM, Asmus Freytag asm...@ix.netcom.com
mailto:asm...@ix.netcom.com wrote:
In the case you give, the new design is clearly not the
canonical shape, because it deliberately innovates. If it ever
replaces
On 5/29/2013 9:53 AM, Manuel Strehl wrote:
Out of curiosity, has it happened before, that a glyph was updated
(i.e., substantially changed) in the standard?
Yes, Philippe gives some examples of typical situations.
Representative glyphs are not immutable - what is immutable is the
identity
On 6/19/2013 6:36 AM, Michael Everson wrote:
Only in text which has been decomposed. Not all text gets decomposed.
All text may get decomposed without warning.
As data is shipped around and processed in various parts of a
distributed system, nobody can make any safe assumptions on the
On 6/19/2013 6:36 AM, Michael Everson wrote:
The issue of cedilla can easily be solved at a higher level, font technologies
like OpenType can easily display glyphs in Latvian or Livonia and different
glyphs for Marshallese.
Only in environments which permit language tagging. I'd like
On 7/3/2013 2:04 AM, Michael Everson wrote:
On 3 Jul 2013, at 09:52, Martin J. Dürst due...@it.aoyama.ac.jp wrote:
Quite a few people might expect their Japanese filenames to appear with a
Japanese font/with Japanese glyph variants, and their Chinese filenames to
appear with a Chinese
On 7/8/2013 1:35 PM, Whistler, Ken wrote:
A much more productive approach, it seems to me, would be instead to
try to establish information about various, identifiable typographical
traditions for use of punctuation around the world, and then associate
exemplar sets of punctuation used with
On 7/8/2013 8:15 PM, Richard Wordingham wrote:
On Mon, 08 Jul 2013 14:42:15 -0700
Asmus Freytag asm...@ix.netcom.com wrote:
We are stuck with a format that seemingly assumes that all characters
are treated individually. However, I agree with you, that this is not
the case, but instead
What is wrong with using DIAMOND OPERATOR?
A./
On 7/18/2013 8:27 PM, Stephan Stiller wrote:
Hi all,
Modal logic uses a box and a diamond (this is how they're
informally called) as operators (accepting one formula and returning
another) to denote necessity and possibility, resp. Older texts
601 - 700 of 1250 matches
Mail list logo
