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:
>>>
>>> For historic scripts, the variation
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:
For historic scripts, the variation sequence provides a useful tool,
because it can show mistaken or nonce
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
> base character. It
Janusz S. Bien wrote:
> You seem to assume that my concern is only rendering.
Well my thinking is that what you are wanting is a way to accurately transcribe
documents and maybe printed books from Old Polish into a Unicode-based
electronic format so that the information can be more readily
On 7/17/2018 8:56 PM, Janusz S. "Bień" wrote:
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
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 time being a kind of
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 time being a kind of Private Use variation database seems
WJGO >> My suggestion is to use for each desired glyph a sequence consisting of
three characters, and then have an OpenType font decode them so that the glyph
can be displayed.
JSB >This is a prohibitive requirement, because for years there is the lack of
font creators interested in old
Janusz S. Bien wrote:
> I understand there is no sufficient demand for the Unicode Consortium
> maintaining a supplementary non-ideographic variation database. Hence for the
> time being a kind of Private Use variation database seems to be the only
> solution - am I right?
Well, with the
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
>>
On Mon, Jul 16 2018 at 1:08 -0700, unicode@unicode.org writes:
> The use case would seem to be more properly served by some form of
> registration mechanism, like the one IVD represents for ideographs.
I agree.
>
> The use of "standardized" variation sequences with the understanding
> that
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 in the FAQ.
I wonder if you could say please what are the "kind of fall-back
The use case would seem to be more
properly served by some form of registration mechanism, like the
one IVD represents for ideographs.
The use of "standardized" variation sequences with the
understanding that those would be (fairly) widely implemented
13 matches
Mail list logo
