Am Montag, den 30.04.2012, 09:09 -0700 schrieb David Starner:
I think there's exactly zero chance that Unicode will separate two
characters that have been unified for the entire history of Unicode
and used for terabytes, possibly petabytes, of data. Like many of the
things inherited from
Am Sonntag, den 29.04.2012, 23:43 -0700 schrieb Asmus Freytag:
Even if some minutiae of glyph selection are left to a font, the
problem is often that there's no specification as to what certain
languages need, so that fonts cannot be expected to provide the
correct implementation.
Strange as
Sometimes you are not free to choose what you would like.
One thing that's off the table is a new character code.
The reason for that categorical statement is that there is too much data
and software out that uses the existing character codes. Throwing a new
character into the mix will just
Am Donnerstag, 3. Mai 2012 um 10:03 schrieb Asmus Freytag:
AF ... The time to
AF create a special character code for German quotation marks is passed.
This is especially true as other standards refer to the way the quotes
are encoded now.
For instance, the new German keyboard standard DIN
Thanks to everybody commented about the effect of the rotation
for Canadian syllabics. Yet I've not understood fully about
how small superscriptic characters are drawn (or expected to be
drawn) in vertical writing mode.
I attached a picture. In my understanding, when aamuu is written
in vertical
Am Mittwoch, den 02.05.2012, 13:46 -0700 schrieb Doug Ewell:
Werner LEMBERG wl at gnu dot org wrote:
So if two glyphs have enough visual character to be used in one
document to express two different meanings, then they should be
encoded as different characters?
Yes, more or less.
I
I am forwarding this query to my colleagues in Nunavut.
Michael Everson * http://www.evertype.com/
Thanks!
Michael Everson wrote:
I am forwarding this query to my colleagues in Nunavut.
Michael Everson * http://www.evertype.com/
On 5/3/2012 5:50 AM, suzuki toshiya wrote:
Thanks!
Michael Everson wrote:
I am forwarding this query to my colleagues in Nunavut.
Well, it's an incomplete query and because of that, you will get an
incomplete result.
It may give an answer on what the preference would be in handling small
On Wed, 2 May 2012, Asmus Freytag wrote:
a document that not only describes the issues
but provides a suggested solution.
Suggested solution:
Correct the typefaces Comic Sans MS, Tahoma, Verdana
in the same way as the typeface Trebuchet MS has been corrected:
Make U+2018 a rotational image of
On 3 May 2012, at 17:35, Asmus Freytag wrote:
Well, it's an incomplete query and because of that, you will get an
incomplete result.
Oh, give over.
It may give an answer on what the preference would be in handling small marks
- under the assumption that characters were to be written
On 3 May 2012, at 17:53, Andreas Prilop wrote:
Suggested solution:
Correct the typefaces Comic Sans MS, Tahoma, Verdana
in the same way as the typeface Trebuchet MS has been corrected:
Make U+2018 a rotational image of U+2019.
Make U+201B a mirrored image of U+2019.
Make a clear
Le 01/05/12 20:19, Michael Everson a écrit :
On 1 May 2012, at 17:05, Julian Bradfield wrote:
On 2012-05-01, Michael Eversonever...@evertype.com wrote:
than it is in English, except in neon). The examples you showed were made by
people who hadn't thought about what they were doing. Since
Andreas Prilop wrote:
Suggested solution:
Correct the typefaces Comic Sans MS, Tahoma, Verdana
in the same way as the typeface Trebuchet MS has been corrected:
Make U+2018 a rotational image of U+2019.
Make U+201B a mirrored image of U+2019.
Make a clear statement in the Unicode standard:
14 matches
Mail list logo
