Re: Variation Sequences (and L2-11/059)

On Wed, Mar 13 2019 at 9:48 -07, Ken Whistler wrote: > On 3/13/2019 2:42 AM, Janusz S. Bień via Unicode wrote: >> Hi! >> >> On Mon, Jul 16 2018 at 7:07 +02, Janusz S. Bień via Unicode wrote: >>> FAQ (http://unicode.org/faq/vs.html) states: >>> >&

Re: Variation Sequences (and L2-11/059)

Hi! On Mon, Jul 16 2018 at 7:07 +02, Janusz S. Bień via Unicode wrote: > FAQ (http://unicode.org/faq/vs.html) states: > > For historic scripts, the variation sequence provides a useful tool, > because it can show mistaken or nonce glyphs and relate them to the >

Update to the second question summary (was: A sign/abbreviation for "magister")

On Sun, Dec 02 2018 at 10:33 +0100, Hans Åberg via Unicode wrote: >> On 30 Oct 2018, at 22:50, Ken Whistler via Unicode >> wrote: >> >> On 10/30/2018 2:32 PM, James Kass via Unicode wrote: >>> but we can't seem to agree on how to encode its abbreviation. >> >> For what it's worth, "mgr" seems

A sign/abbreviation for "magister" - third question summary

On Sat, Oct 27 2018 at 14:10 +0200, Janusz S. Bień via Unicode wrote: > Hi! > > On the over 100 years old postcard > > https://photos.app.goo.gl/GbwNwYbEQMjZaFgE6 > > you can see 2 occurences of a symbol which is explicitely explained (in > Polish) as meaning "Mag

A sign/abbreviation for "magister" - second question summary

On Sat, Oct 27 2018 at 14:10 +0200, Janusz S. Bień via Unicode wrote: > Hi! > > On the over 100 years old postcard > > https://photos.app.goo.gl/GbwNwYbEQMjZaFgE6 > > you can see 2 occurences of a symbol which is explicitely explained (in > Polish) as meaning "Ma

A sign/abbreviation for "magister" - first question summary

On Sat, Oct 27 2018 at 14:10 +0200, Janusz S. Bień via Unicode wrote: > Hi! > > On the over 100 years old postcard > > https://photos.app.goo.gl/GbwNwYbEQMjZaFgE6 > > you can see 2 occurences of a symbol which is explicitely explained (in > Polish) as meaning "Magister

Re: A sign/abbreviation for "magister"

On Fri, Nov 02 2018 at 5:09 -0700, Asmus Freytag via Unicode wrote: [...] > To transcribe the postcard would mean selecting the characters > appropriate for the printed equivalent of the text. You seem to make implicit assumptions which are not necessarily true. For me to transcribe the

mail attribution (was: A sign/abbreviation for "magister")

On Thu, Nov 01 2018 at 6:43 -0700, Asmus Freytag via Unicode wrote: > On 11/1/2018 12:52 AM, Richard Wordingham via Unicode wrote: > > On Wed, 31 Oct 2018 11:35:19 -0700 > Asmus Freytag via Unicode wrote: [...] > Unfortunately, your emails are extremely hard to read in plain text. > It is

Re: A sign/abbreviation for "magister"

On Thu, Nov 01 2018 at 13:34 -0700, Asmus Freytag via Unicode wrote: > On 11/1/2018 10:23 AM, Janusz S. Bień via Unicode wrote: [...] > Looks like you completely missed my point. Nobody ever claimed that > reproducing all variations in manuscripts is in scope of Unicode, so > whom

Re: A sign/abbreviation for "magister"

On Thu, Nov 01 2018 at 8:43 -0700, Asmus Freytag via Unicode wrote: > On 11/1/2018 12:33 AM, Janusz S. Bień via Unicode wrote: > > On Wed, Oct 31 2018 at 12:14 -0700, Ken Whistler via Unicode wrote: > > On 10/31/2018 11:27 AM, Asmus Freytag via Unicode wrote: > >

Re: A sign/abbreviation for "magister"

On Wed, Oct 31 2018 at 12:14 -0700, Ken Whistler via Unicode wrote: > On 10/31/2018 11:27 AM, Asmus Freytag via Unicode wrote: >> >> but we don't have an agreement that reproducing all variations in >> manuscripts is in scope. > > In fact, I would say that in the UTC, at least, we have an

use vs mention (was: second attempt)

On Wed, Oct 31 2018 at 9:38 GMT, Julian Bradfield via Unicode wrote: > On 2018-10-31, Janusz S. =?utf-8?Q?Bie=C5=84?= via Unicode > wrote: [...] >> The relevant fragment of the postcard in a loose translation is >> >> Use the following address: ... >> is the abbreviation of

Re: second attempt

On Wed, Oct 31 2018 at 9:38 GMT, Julian Bradfield via Unicode wrote: > On 2018-10-31, Janusz S. =?utf-8?Q?Bie=C5=84?= via Unicode > wrote: >> On Mon, Oct 29 2018 at 12:20 -0700, Doug Ewell via Unicode wrote: > > [ as did I in private mail ] > >>> The abbreviation in the postcard, rendered in

second attempt (was: A sign/abbreviation for "magister")

My previous attempt to send this mail was rejected by the list as spam. If this one will not appear on the list, would you be so kind to forward it to the list and the listmaster? On Mon, Oct 29 2018 at 12:20 -0700, Doug Ewell via Unicode wrote: [...] > The abbreviation in the postcard,

Re: A sign/abbreviation for "magister"

On Mon, Oct 29 2018 at 7:57 GMT, James Kass wrote: > Janusz S. Bień asked, > >> Do you claim that in the ground-truth for HWR the >> squiggle and raising doesn't matter? > > Not me! I know, sorry if my previous mail was confusing. > "McCoy", "M=ͨC

Re: A sign/abbreviation for "magister"

On Sun, Oct 28 2018 at 20:42 GMT, Michael Everson wrote: > This is no different the Irish name McCoy which can be written MᶜCoy > where the raising of the c is actually just decorative, though perhaps > it was once an abbreviation for Mac. In some styles you can see a line > or a dot under the

Re: A sign/abbreviation for "magister"

On Sun, Oct 28 2018 at 15:19 +0100, Philippe Verdy via Unicode wrote: > Given the "squiggle" below letters are actually gien distinctive > semantics, I think it should be encoded a combining character (to be > written not after a "superscript" but after any normal base letter, > possibly with

Re: A sign/abbreviation for "magister"

On Sat, Oct 27 2018 at 5:58 -0700, Asmus Freytag via Unicode wrote: [...] > My suspicion would be that the small "z" is rather a "=" that acquired > a connecting stroke as part of quick handwriting. You must be right. In the meantime I looked up some other postcards written by the same person

Re: A sign/abbreviation for "magister"

On Sat, Oct 27 2018 at 16:32 +0200, rein wrote: > Janusz, > > "wszystkimi m(oj)ami rączki" some sort of plural instrumentalis :) Rather "moimi", although still the phrase sounds strange. > "embracing you with all my hands/arms" Now "kiss" (całować) and "embrace" (obejmować) are strictly

Re: A sign/abbreviation for "magister"

tkiem I read this "wszystkiemi". >Mami I can't guess a word which would make sense of this phrase... > rączki Twój Kochający Włodek 12/9 917 > > pozdrawiam, Rein Nawzajem :-) > > Sat, 27 Oct 2018 13:10:20 +0200 schreef Janusz S. Bień via Unicode > : [...] >&

A sign/abbreviation for "magister"

Hi! On the over 100 years old postcard https://photos.app.goo.gl/GbwNwYbEQMjZaFgE6 you can see 2 occurences of a symbol which is explicitely explained (in Polish) as meaning "Magister". First question is: how do you interpret the symbol? For me it is definitely the capital M followed by the

Re: Unicode String Models

On Sat, Sep 08 2018 at 18:36 +0200, Mark Davis ☕️ via Unicode wrote: > I recently did some extensive revisions of a paper on Unicode string models > (APIs). Comments are welcome. > > https://docs.google.com/document/d/1wuzzMOvKOJw93SWZAqoim1VUl9mloUxE0W6Ki_G23tw/edit# It's a good opportunity to

Re: CLDR

some time ago. On Fri, Aug 31 2018 at 12:17 +0200, Marcel Schneider via Unicode wrote: > On 31/08/18 07:27 Janusz S. Bień via Unicode wrote: > […] >> > Given NamesList.txt / Code Charts comments are kept minimal by design, >> > one couldn’t simply pop them into XML

Re: UCD in XML or in CSV? (is: UCD data consumption)

On Sun, Sep 02 2018 at 4:16 +0200, [...] > So you can understand that I’m not unaware of the complexity of UCD. Though > I don’t think that this could be an argument for not publishing a medium-size > CSV file with scalar values listed as in UnicodeData.txt. For a non-programmer like me CVS

CLDR (was: Private Use areas)

On Thu, Aug 30 2018 at 2:27 +0200, unicode@unicode.org writes: [...] > Given NamesList.txt / Code Charts comments are kept minimal by design, > one couldn’t simply pop them into XML or whatever, as the result would be > disappointing and call for completion in the aftermath. Yet another task

Re: Private Use areas

On Tue, Aug 28 2018 at 9:43 -0700, unicode@unicode.org writes: > On August 23, 2011, Asmus Freytag wrote: > >> On 8/23/2011 7:22 AM, Doug Ewell wrote: >>> Of all applications, a word processor or DTP application would want >>> to know more about the properties of characters than just whether >>>

Re: Emacs Verbose Character Entry (was Private Use Areas)

On Thu, Aug 23 2018 at 22:15 +0100, unicode@unicode.org writes: > On Thu, 23 Aug 2018 21:47:03 +0200 > "Janusz S. Bień via Unicode" wrote: > >> My needs are very simple, for example C-x 8 Return LATIN CAPITAL >> LETTER A WITH MACRON AND BREVE [MUFI] should yield

Re: Private Use areas

On Fri, Aug 24 2018 at 16:12 +0300, e...@gnu.org writes: >> From: jsb...@mimuw.edu.pl (Janusz S. Bień) >> Cc: unicode@unicode.org, richard.wording...@ntlworld.com >> Date: Thu, 23 Aug 2018 21:47:03 +0200 >> >> I'm very glad you join the discussion. > > I'm

Re: Private Use areas

On Thu, Aug 23 2018 at 11:49 -0700, beckie...@gmail.com writes: > On Thu, Aug 23, 2018 at 5:10 AM, Janusz S. Bień wrote: > > > I already provide this myself for my uses of the PUA as well as the > > CSUR and any vendor-specific agreements I can find: > > > &g

Re: Private Use areas

On Thu, Aug 23 2018 at 22:17 +0300, e...@gnu.org writes: >> Date: Thu, 23 Aug 2018 20:30:52 +0200 >> Cc: Richard Wordingham >> From: "Janusz S. Bień via Unicode" >> >> >> and in Emacs - to my disappointed it looks like the Unicode data are >&

Re: Private Use areas

On Thu, Aug 23 2018 at 17:26 +0100, unicode@unicode.org writes: > On Thu, 23 Aug 2018 17:39:15 +0200 > Philippe Verdy via Unicode wrote: > >> You make a confusion: I do not propose "hacking" existing codes, but >> instead adding new codes for private variations. It's then up to PUV >> sequence

Re: Private Use areas

On Thu, Aug 23 2018 at 17:11 +0100, unicode@unicode.org writes: > On Thu, 23 Aug 2018 14:10:35 +0200 > "Janusz S. Bień via Unicode" wrote: > >> What kind of software do you have in mind? >> >> I'm primarily interested in the locally developed program

Re: Private Use areas

On Tue, Aug 21 2018 at 11:23 -0700, unicode@unicode.org writes: > On Tue, Aug 21, 2018 at 10:21 AM, Janusz S. Bień via Unicode > wrote: > > I think PUA users should provide the > properties of the characters used in a form analogical to the Unicode > itself, and the softw

Re: Private Use areas

On Tue, Aug 21 2018 at 16:56 +0200, unicode@unicode.org writes: > On Mon, Aug 20, 2018 at 05:17:21PM -0700, Ken Whistler via Unicode wrote: >> On 8/20/2018 5:04 PM, Mark E. Shoulson via Unicode wrote: >> > Is there a block of RTL PUA also? >> >> No. > > Perhaps there should be? > > What about

L2-11/059 and L2/13‐153 (was: Variation Sequences (and L2-11/059))

On Mon, Jul 16 2018 at 7:07 +0200, jsb...@mimuw.edu.pl writes: [...] > To the best of my knowledge, the only attempt to introduce additional > variation sequences was the strongly criticised Karl Pentzlin's proposal > L2-11/059 > > http://www.unicode.org/L2/L2011/11059-latin-cyr-var.pdf > >

old Polish and Unicode (was: Variation Sequences (and L2-11/059))

I apologize for sending by mistake the previous post with no new content. On Thu, Jul 19 2018 at 17:47 +0100, wjgo_10...@btinternet.com writes: [...] > I found the following. > > https://en.wikipedia.org/wiki/Old_Polish_language Thanks again for your interest in Polish language. There is

Re: Variation Sequences (and L2-11/059)

On Tue, Jul 17 2018 at 8:34 -0700, Asmus Freytag writes: > On 7/16/2018 10:04 PM, Janusz S. Bień via Unicode wrote: > > I understand there is no sufficient demand for the Unicode Consortium > maintaining a supplementary non-ideographic variation database. Hence > for the tim

Re: Variation Sequences (and L2-11/059)

On Mon, Jul 16 2018 at 19:00 +0100, wjgo_10...@btinternet.com writes: > Hi > >> I ask the question because there are now several historical corpora >> of Polish under development, which use at present a kind of fall-back >> or some other ad hoc solutions for "nonce glyphs", as they are called >>

Re: Variation Sequences (and L2-11/059)

ternate to be > selected. I agree. [...] > On 7/15/2018 10:07 PM, Janusz S. Bień via Unicode wrote: > > > FAQ (http://unicode.org/faq/vs.html) states: > > For historic scripts, the variation sequence provides a useful tool, > because it can show mistaken or nonce glyph

Variation Sequences (and L2-11/059)

FAQ (http://unicode.org/faq/vs.html) states: For historic scripts, the variation sequence provides a useful tool, because it can show mistaken or nonce glyphs and relate them to the base character. It can also be used to reflect the views of scholars, who may see the relation

Re: Unicode Emoji 11.0 characters now ready for adoption!

; wrote: > > On 2018/02/28 19:38, Janusz S. Bień via Unicode wrote: > > On Tue, Feb 27 2018 at 13:45 -0800, announceme...@unicode.org writes: > > The 157 new Emoji are now available for adoption, to help the Unicode > Consortium’s work on digitally disadvantaged language

Re: Unicode Emoji 11.0 characters now ready for adoption!

On Tue, Feb 27 2018 at 13:45 -0800, announceme...@unicode.org writes: > The 157 new Emoji are now available for adoption, to help the Unicode > Consortium’s work on digitally disadvantaged languages. I'm quite curious what it the relation between the new emojis and the digitally disadvantages

Re: Unicode Digest, Vol 50, Issue 13

On Sun, Feb 18 2018 at 18:03 CET, kilob...@angband.pl writes: > On Sun, Feb 18, 2018 at 02:35:00PM +0100, Janusz S. Bień via Unicode wrote: >> On Sun, Feb 18 2018 at 14:06 CET, unicode@unicode.org writes: >> > Subject: metric for block coverage >> > >> > Hi!

Re: metric for block coverage

On Sun, Feb 18 2018 at 17:33 CET, e...@gnu.org writes: >> Cc: unicode-requ...@unicode.org >> Date: Sun, 18 Feb 2018 14:35:00 +0100 >> From: "Janusz S. Bień via Unicode" <unicode@unicode.org> >> >> As a Debian user using some rare characters for

Re: Unicode Digest, Vol 50, Issue 13

On Sun, Feb 18 2018 at 14:06 CET, unicode@unicode.org writes: [...] > From: Adam Borowski via Unicode > Subject: metric for block coverage > To: unicode@unicode.org > Date: Sat, 17 Feb 2018 23:18:25 +0100 > Reply-To: Adam Borowski > Date: Sat, 17 Feb

Re: TIRONIAN SIGN ET

On Sat, Jan 27 2018 at 21:59 CET, davidj_fau...@yahoo.ca writes: [...] > As far as I can tell, it was originally proposed in the document n1747 > 'Contraction mark characters for the UCS’ by Everson. However, I > cannot find that document anywhere. Thank you very much for the reference. On

Re: TIRONIAN SIGN ET

On Sat, Jan 27 2018 at 20:53 CET, r...@unicode.org writes: > Hello Janusz -- > > Try this: http://www.unicode.org/L2/L2017/17300-n4841-tironian-et.pdf > > Regards, > > On 1/27/2018 11:40 AM, Janusz S. Bień via Unicode wrote: >> Hi! >> >> I try to find

TIRONIAN SIGN ET

Hi! I try to find in UTC Document Register the proposals for characters which interest me for some reasons. I'm usually rather successful, but I'm unable to find the proposal for TIRONIAN SIGN ET. Any hints? Best regards Janusz -- , Prof. dr hab. Janusz S. Bien

Unicode vs. Unikod

This is a long overdue issue, but better late than never. To make a long story short, I think that the word "Unikod" should not be used in the Polish translation of "What is Unicode": http://www.unicode.org/standard/translations/polish.html The word "Unikod", to the best of my knowledge, has

Re: "A Programmer's Introduction to Unicode"

On Fri, Mar 10 2017 at 19:55 CET, man...@mozilla.com writes: > I recently wrote > http://manishearth.github.io/blog/2017/01/14/stop-ascribing-meaning-to-unicode-code-points/ > , which sort of addresses the whole hangup programmers have with > treating code points as "characters". [...] This is

Re: a character for an unknown character

On Sun, Dec 25 2016 at 18:31 CET, jkorp...@cs.tut.fi writes: > 21.12.2016, 4:29, Martin Mueller wrote: > >> Is there a Unicode character that says “I represent an alphanumerical >> character, but I don’t know which”. > > I think including such a “character” in Unicode would not fit into the > the

Re: The usage of Z WITH STROKE

On Fri, Nov 25 2016 at 15:38 CET, jsb...@mimuw.edu.pl writes: > Hi! > > There are two comments to the character(s) in the U0180 chart: > > 1. Pan-Turkic Latin orthography [...] On Mon, Nov 28 2016 at 16:48 CET, kenwhist...@att.net writes: > On 11/25/2016 10:20 PM, Ja

Re: The usage of Z WITH STROKE

Thanks for all the interesting asnwers. I will focus now on my first question. On Fri, Nov 25 2016 at 15:38 CET, jsb...@mimuw.edu.pl writes: > Hi! > > There are two comments to the character(s) in the U0180 chart: > > 1. Pan-Turkic Latin orthography > 2. handwritten variant of Latin “z” > > Ad

The usage of Z WITH STROKE

Hi! There are two comments to the character(s) in the U0180 chart: 1. Pan-Turkic Latin orthography 2. handwritten variant of Latin “z” Ad 1. Do I understand correctly that the Pan-Turkic Latin ortography refers to the initiative described in the post to the Linguist list:

Re: graphemes

016 at 16:28 CEST, christoph.pae...@crissov.de writes: > Janusz S. Bień <jsb...@mimuw.edu.pl>: > > On Sun, Sep 18 2016 at 12:26 CEST, jsb...@mimuw.edu.pl writes: > > Quote/Cytat - Christoph Päper <christoph.pae...@crissov.de> (pią, >

Re: graphemes

ften work reasonably well to > separate clear cases from questionable ones which are likely to be > treated differently by different scholars. Let me remind the issues which started the thread: On Sun, Sep 18 2016 at 12:26 CEST, jsb...@mimuw.edu.pl writes: > Quote/Cytat - Christoph Päper

Re: "textels"

On Tue, Sep 20 2016 at 18:09 CEST, d...@ewellic.org writes: > Janusz Bień wrote: > >> For me it means that Swift's characters are equivalence classes of the >> set of extended grapheme clusters by canonical equivalence relation. > > I still hope we can come to some conclusion on the correct

graphemes (was: "textels")

On Sun, Sep 18 2016 at 21:40 CEST, christoph.pae...@crissov.de writes: > Janusz S. Bien : >> >> From the Unicode glossary: >> >>> Grapheme. (1) A minimally distinctive unit of writing in the context of a >>> particular writing system.[...] (2) What a user thinks of as a

User-perceived character (was: "textels")

On Sun, Sep 18 2016 at 22:02 CEST, asm...@ix.netcom.com writes: > On 9/18/2016 3:26 AM, Janusz S. Bien wrote: [...] >> From the Unicode glossary: >> >> Grapheme. (1) A minimally distinctive unit of writing in the context >> of a particular writing system.[...] (2) What a user thinks of as a >>

Re: "textels"

On Thu, Sep 15 2016 at 21:56 CEST, jsb...@mimuw.edu.pl writes: [...] > 1. Graphemes, if I understand correctly, are language dependent, textels > are not. > > 2. Textel "ń" means both U+0144 and , so it is a notion > on a higher abstraction level then a grapheme cluster. In other

Re: "textels"

On Thu, Sep 15 2016 at 21:27 CEST, e...@gnu.org writes: [...] > Isn't "grapheme cluster" the definition you are looking for? I don't think so. On Thu, Sep 15 2016 at 21:27 CEST, leobo...@namakajiri.net writes: > Isn't the Swift "character" and the "textel" merely the same thing as > what

"textels" (was: Default character encoding for each operating system?)

On Thu, Sep 15 2016 at 16:36 CEST, john.w.kenn...@gmail.com writes: [...] > In the new Swift programming language, which is white-hot in the Apple > community, Apple is moving toward a model of a transparent, generic > Unicode that can be “viewed” as UTF-8, UTF-16, or UTF-32 if necessary, > but

Re: Character Index

On Tue, Mar 29 2016 at 20:56 CEST, asm...@ix.netcom.com writes: > On 3/29/2016 11:24 AM, Ken Whistler wrote: > > On 3/29/2016 12:16 AM, Janusz S. Bień wrote: > > What about a simpler and more technical approach, like a character > index > with

Re: NamesList.txt as data source

On Tue, Mar 29 2016 at 10:40 CEST, andrewcw...@gmail.com writes: > On 29 March 2016 at 06:15, Asmus Freytag (c) wrote: >> >> What is the copyright status of the >> document? >> [...] > All documents submitted to WG2 and to L2 by individuals are copyright > of the author(s)

Re: NamesList.txt as data source

On Tue, Mar 29 2016 at 9:54 CEST, asm...@ix.netcom.com writes: > On 3/29/2016 12:16 AM, Janusz S. "Bień" wrote: > > The document I refer to is a ISO/IEC document. As far as I know, ISO is > quite crazy about copyright. Does the Unicode Consortium policy apply to

Re: NamesList.txt as data source

On Tue, Mar 29 2016 at 7:15 CEST, asm...@ix.netcom.com writes: > On 3/28/2016 9:40 PM, Janusz S. "Bień" wrote: [...] > The terms of use (ostensibly for the entire site) are defined here: > > http://www.unicode.org/copyright.html > > The document archive has not b

Re: NamesList.txt as data source

don't have access to those "other sources," See below. > then as far as I > can tell, yes, it's available only in NamesList.txt. > > -- > Doug Ewell | http://ewellic.org | Thornton, CO  > > On Sun, Mar 27 2016 at 6:38 CEST, asmus-...@ix.netcom.com writes: &

Re: NamesList.txt as data source

On Thu, Mar 10 2016 at 22:40 CET, kenwhist...@att.net writes: [...] > The *reason* that NamesList.txt exists at all is to drive the tool, unibook, > that formats the full Unicode code charts for posting. It is only > posted in the Unicode Character Database at all as a matter of > convenience,

annotations (was: NamesList.txt as data source)

On Thu, Mar 10 2016 at 22:40 CET, kenwhist...@att.net writes: > The *reason* that NamesList.txt exists at all is to drive the tool, > unibook, that formats the full Unicode code charts for posting. [...] On Fri, Mar 11 2016 at 3:13 CET, asm...@ix.netcom.com writes: > On 3/10/2016 5:49 PM, "J.

free download of ISO/IEC 10646 (was: Accessing the WG2 document register)

On Thu, Jun 11 2015 at 10:49 CEST, andrewcw...@gmail.com writes: [...] The latest version of ISO/IEC 10646 is not inaccessible to most people, as it is (and has been since 2006) available for free download from ISO at http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html. The

reversed Polish-hook o

I've just noticed the comment quoted in the subject in the description of 'LATIN SMALL LETTER TURNED DELTA' (U+018D) and I'm intrigued how it got into the standard. On Sun, May 31 2015 at 18:20 CEST, frederic.grossh...@gmail.com writes: [...] The upper case was introduces for

Sencoten and Unicode policy (was: the usage of LATIN SMALL LETTER A WITH STROKE)

On Mon, Jun 01 2015 at 3:29 CEST, prosfil...@gmail.com writes: On Sun, May 31, 2015 at 11:09 AM Janusz S. Bien jsb...@mimuw.edu.pl wrote: The proposal makes me curious about past and present Unicode policy, e.g. would it be accepted if submitted now. Why wouldn't it?

the usage of LATIN SMALL LETTER A WITH STROKE

I'm curious what was the motivation for adding the character to Unicode. I understand the proposal is somewhere in the archives, perhaps it is available on the Internet? The only usage I'm aware of (with the exception of my own for historical Polish) is that found in Wiktionary: ⱥ is also

Re: Proposed new characters updated in Pipeline Table

Where the details of the proposed characters are available? I'm especially interested in Old Hungarian. Regards JSB On Thu, 11 Aug 2011 announceme...@unicode.org wrote: The Pipeline Table for proposed new characters has been updated to reflect recent decisions by the UTC. Changes include

Re: Proposed new characters updated in Pipeline Table

On Fri, 12 Aug 2011 Michael Everson ever...@evertype.com wrote: On 12 Aug 2011, at 08:13, Janusz S. Bień wrote: Where the details of the proposed characters are available? I'm especially interested in Old Hungarian. See http://std.dkuug.dk/JTC1/SC2/WG2/docs/n4110.pdf Thank you very much

Re: Definition of character

On Tue, 12 Jul 2011 Asmus Freytag asm...@ix.netcom.com wrote: [...] Let's look at the putative benefit of a better definition. I think such a benefit has implicitly been claimed to exist, but I would ask for a demonstration in this case. My positon formulated already in 2004:

Re: statistics

On Mon, 11 Oct 2010 Asmus Freytag asm...@ix.netcom.com wrote: On 10/11/2010 9:49 PM, Janusz S. Bień wrote: On Mon, 11 Oct 2010 announceme...@unicode.org wrote: The newly finalized Unicode Version 6.0 adds 2,088 characters, What is the current total? Are other statistic informations

statistics (was: Unicode Version 6.0: Support for Popular Symbols in Asia)

On Mon, 11 Oct 2010 announceme...@unicode.org wrote: The newly finalized Unicode Version 6.0 adds 2,088 characters, What is the current total? Are other statistic informations available somewhere? Best regards JSB -- , dr hab. Janusz S. Bien, prof. UW -

Re: Solved (was: [OT]: a strange language name abbreviation)

On Sat, 18 Sep 2010 André Szabolcs Szelp a.sz.sz...@gmail.com wrote: 1. (*) text/plain ( ) text/html Given the complete parallels heard here earlier, shouldn't it really be Crimean Gothic? Rather not. [...] On Fri, 06 Aug 2010 jsb...@mimuw.edu.pl (Janusz S. Bień

Solved (was: [OT]: a strange language name abbreviation)

On Mon, 09 Aug 2010 jsb...@mimuw.edu.pl (Janusz S. Bień) wrote: Thanks for all the comments. For the time being the puzzle remains unsolved. Perhaps in the future somebody will dig through the sources used by the author of the dictionary and will find an explanation... Dr Marian Ptaszyk

Re: ,,semi-virgula''

Thanks for all the comments. On Tue, 31 Aug 2010 jsb...@mimuw.edu.pl (Janusz S. Bień) wrote: [...] First, is semivirgula a good name? Google shows that it often refers to semicolon. Caudatum seems to me even more misleading because it should refer simply to ogonek (to the best of my

Re: [OT]: a strange language name abbreviation

Thanks for all the comments. For the time being the puzzle remains unsolved. Perhaps in the future somebody will dig through the sources used by the author of the dictionary and will find an explanation... Best regards Janusz -- , dr hab. Janusz S. Bien, prof. UW -

How to encode reversed section sign?

An important 19th century dictionary of Polish uses two kinds of section sign, illustrated in the attachment, there is over 5000 occurrences of the characters. Dirty OCR interpreted both of them as the letter g, so you can see most of them visiting

Re: How to encode reversed section sign?

On Fri, 6 Aug 2010 Joó Ádám cer...@gmail.com wrote: Nevertheless, our typesetter had those types for some reason. Or do you think that – given its different style – it was only a glyph variant of some other font? That's what André suggested and it might be true. Looks like nobody was

[OT]: a strange language name abbreviation (was: How to encode reversed section sign?)

On Fri, 06 Aug 2010 jsb...@mimuw.edu.pl (Janusz S. Bień) wrote: An important 19th century dictionary of Polish uses two kinds of section sign, illustrated in the attachment, there is over 5000 occurrences of the characters. Dirty OCR interpreted both of them as the letter g, so you can see

Re: long s

On Wed, 4 Aug 2010 Karl Pentzlin karl-pentz...@acssoft.de wrote: Am Dienstag, 3. August 2010 um 19:11 schrieb Janusz S. Bień: JJSB I see no reason why, if I understand correctly, the long s variant is JSB to be limited to Fraktur-like styles. The *variant* is applicable to situations where