On 9 Dec 2015, at 23:32, Martin J. Dürst wrote:
On 2015/12/10 09:30, Mark E. Shoulson wrote:
I remember when we went through all this the first time around,
encoding
ẞ in the first place. People were saying "But the Duden says
no!!!" And
someone then pointed out, "Please close your Duden
On 2015/12/10 09:30, Mark E. Shoulson wrote:
I remember when we went through all this the first time around, encoding
ẞ in the first place. People were saying "But the Duden says no!!!" And
someone then pointed out, "Please close your Duden and cast your gaze
upon ITS FRONT COVER, where you wil
On 12/9/2015 3:49 PM, Hans Meiser
wrote:
Yes, they do it wrong because (1) they don't know better and (2) they let their software convert lower case text into upper case (a feature nearly every typographic software provides).
Yet, if we let the majority of illitera
On 12/09/2015 06:49 PM, Hans Meiser wrote:
Yes, they do it wrong because (1) they don't know better and (2) they let their
software convert lower case text into upper case (a feature nearly every
typographic software provides).
Yet, if we let the majority of illiterate people decide what's rig
On 9 Dec 2015, at 22:57, Asmus Freytag (t) wrote:
>
>> In my new edition of the first German translation of “Alice’s Adventures in
>> Wonderland”, the editor and I made sure that the cakes said “Iẞ MICH!” and
>> not “Iß MICH!”. :-)
>
> And the correct spelling (modern) would have been "Iss mi
Yes, they do it wrong because (1) they don't know better and (2) they let their
software convert lower case text into upper case (a feature nearly every
typographic software provides).
Yet, if we let the majority of illiterate people decide what's right and what's
wrong we could as easily decid
On 12/9/2015 1:11 PM, Michael Everson
wrote:
On 9 Dec 2015, at 20:57, Gerrit Ansmann wrote:
Proposal: Shouldn't the glyph be amended to match the natural language?
Nothing of this is really natural. If you go by what m
2015-12-09 22:45 GMT+01:00 Richard Wordingham <
richard.wording...@ntlworld.com>:
> On Wed, 9 Dec 2015 19:55:24 +
> Hans Meiser wrote:
>
> > I see.
> >
> > Yet, the u+1E9E doesn't quite look like two capital "S". So any
> > program implementing a conversion conforming to Unicode will
> > curr
On Wed, 9 Dec 2015 19:55:24 +
Hans Meiser wrote:
> I see.
>
> Yet, the u+1E9E doesn't quite look like two capital "S". So any
> program implementing a conversion conforming to Unicode will
> currently display/print in a wrong result: "MAßE" instead of the
> correctly converted result "MASSE"
On 9 Dec 2015, at 20:57, Gerrit Ansmann wrote:
>> Proposal: Shouldn't the glyph be amended to match the natural language?
>
> Nothing of this is really natural. If you go by what most people do, you
> would have to write FUßBALL.
In my new edition of the first German translation of “Alice’s Ad
On Wed, 09 Dec 2015 20:55:24 +0100, Hans Meiser wrote:
Yet, AFAIK, the current glyph would currently be considered an error.
See it like this: The point of spelling rules is to easy reading. However, the
use of SS for capital ß is rather obstrusive, as it is not exactly frequent in
everyday
I see.
Yet, the u+1E9E doesn't quite look like two capital "S". So any program
implementing a conversion conforming to Unicode will currently display/print in
a wrong result: "MAßE" instead of the correctly converted result "MASSE". Both
would be correctly encoded as u+004D u+0041 u+1E9E u+0045
On Wed, Dec 09, 2015 at 06:16:35PM +0100, Frédéric Grosshans wrote:
> * use your own casing rule and add a ZWNJ (zero width non joiner character)
> such that ss↔SS and ß↔S+ZWNJ + S.
Wouldn’t ZWJ be a more logical choice given that he wants to “join” both
S’s into a single character.
Regards,
Khal
On 12/9/2015 9:52 AM, Gerrit Ansmann
wrote:
After
the German spelling reform in 1996, "ß" then became a letter of
its own, and words containing the letter "ß" are no longer
equivalent to words containing an "ss" combination instead of
My proposal is to introduce a capital letter equivalent of "ß" that's resembling two capital
"S" letters: "SS".
Actually, the capital ß is already included in Unicode (ẞ) because it was and
is used as a separate letter (not looking like SS), though only rarely. It is
now realised as a proper
For more information on the capital sharp s (ẞ) (converting Maße to
MAẞE), you can also look at Wikipedia
https://en.wikipedia.org/wiki/Capital_%E1%BA%9E (more details in the
german version https://en.wikipedia.org/wiki/Capital_%E1%BA%9E ) and
Andreas Stötzner 2004 proposal to Unicode
http://s
I comment as a western Japanologist who teaches and researches using
hentaigana. I have published with hentaigana using image files (resulting
in two publisher errors) and will publish next year with hentaigana using
the Koin Hentaigana font (Koin変体仮名外字明朝.tte), and anticipate typesetting
problems.
Just have a look at
U+1E9E LATIN CAPITAL LETTER SHARP S
in the block Latin Extended Additional
http://www.unicode.org/charts/PDF/U1E00.pdf
Kind regards
Von: Unicode [mailto:unicode-boun...@unicode.org] Im Auftrag von Hans Meiser
Gesendet: Mittwoch, 9. Dezember 2015 13:26
An: unicode@unicode.org
Currently there is a vast problem trying to determine the lower case equivalent
of a capitalized German word like "MASSE".
This is due to the fact that an orthographic rule exists to convert lower case
letter "ß" to upper case letters "SS". So after converting a word from lower
case to upper c
19 matches
Mail list logo
