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
On 7/16/2018 8:30 PM, Richard
Wordingham via Unicode wrote:
On Mon, 16 Jul 2018 10:53:03 +0300
Shai Berger via Unicode wrote:
What I'm not OK with is:
!Hello, World
Which is what you'll see if your editor decides to use RTL
directionality for
On Mon, 16 Jul 2018 10:53:03 +0300
Shai Berger via Unicode wrote:
> What I'm not OK with is:
>
> !Hello, World
>
> Which is what you'll see if your editor decides to use RTL
> directionality for this file, as the FAQ says it may.
Using 'left aligned' for RTL and 'right aligned' for LTR are
On 7/16/2018 3:51 PM, Shai Berger via Unicode wrote:
And I should add, in response to the other points raised in this
thread, from the same page in the core standard: "If the same plain text
sequence is given to disparate rendering processes, there is no
expectation that rendered text in each
Hi Eli and all,
On Sat, 14 Jul 2018 14:07:50 +0300
Eli Zaretskii via Unicode wrote:
> From: Shai Berger
> >
> > I have no argument with this, but I do think that in such cases it
> > is wrong for the app to pretend that it is still treating the text
> > as plain.
>
> What is "plain text"
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
On Sat, 14 Jul 2018 12:14:35 -0700
Asmus Freytag via Unicode wrote:
> I would say the problem lies in the attempt to exchange arbitrary raw
> data and expect perfectly compatible rendering [...] Editors for
> plain text will wrap or not wrap lines on presentation [...] The bidi
> case is just
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
10 matches
Mail list logo
