On Thu, Jan 31, 2019 at 11:17:19PM +, Richard Wordingham via Unicode wrote:
> On Thu, 31 Jan 2019 12:46:48 +0100
> Egmont Koblinger wrote:
>
> No. How many cells do CJK ideographs occupy? We've had a strong hint
> that a medial BEH should occupy one cell, while an isolated BEH should
>
On 2019-01-31 3:18 PM, Adam Borowski via Unicode wrote:
> They're only from a spammer's point of view.
Spammers need love, too. They’re just not entitled to any.
Hi Eli,
> Arabic presentation forms are more like an exception than a rule, I
> hope you understand this by now. Most languages/scripts don't have
> such forms, and even for Arabic they cover only a part of what needs
> to be done to present correctly shaped text. Complex script shaping
> is
> From: Egmont Koblinger
> Date: Fri, 1 Feb 2019 13:54:02 +0100
> Cc: Adam Borowski , unicode@unicode.org
>
> For this behavior, the only feature you need from a terminal emulator
> is to have a mode where it doesn't shuffle the characters. Currently
> every emulator I'm aware of has such a
Hi,
On Thu, Jan 31, 2019 at 4:14 PM Eli Zaretskii wrote:>
> I suggest that you show the result to someone who does read Arabic.
I contacted one guy who is pretty knowledgeable in Arabic scripts, as
well as terminal emulation, I sent out an early unpublished version of
the proposal to him, but
> From: Egmont Koblinger
> Date: Fri, 1 Feb 2019 14:35:35 +0100
> Cc: Frédéric Grosshans ,
> unicode@unicode.org
>
> > You could do that, but it will require a lot of non-trivial processing
> > from the applications. Text-mode applications don't want any complex
> > tinkering, they want
Hi Richard,
On Fri, Feb 1, 2019 at 12:19 AM Richard Wordingham via Unicode
wrote:
> Cropped why? If the problem is the truncation of lines, one can simple
> store the next character.
Yup, trancation of line for example.
I agree that one could "store the next character". We could extend the
Hi,
On Thu, Jan 31, 2019 at 4:10 PM Eli Zaretskii wrote:
> The reordering happens before TABs are converted to cursor motion,
> does it not?
No, not at all.
You cannot "mix" handling the input and reordering, since the input is
not available as a single step but arrives continuously in a
> From: Egmont Koblinger
> Date: Fri, 1 Feb 2019 13:40:48 +0100
> Cc: unicode@unicode.org
>
> I now understand that presentation forms isn't an ideal possible
> approach, and the recommendation should be improved here.
>
> Until it happens, I'm uncertain whether using presentation form
>
Hi Ken,
> [language tag]
> That is a complete non-starter for the Unicode Standard.
Thanks for your input!
(I hope it was clear that I just started throwing in random ideas, as
in a brainstorming session. This one is ruled out, then.)
cheers,
egmont
Hi Eli,
> So we will some day have one such terminal emulator. That's good, but
> a text-mode application that needs to support bidi cannot rely on its
> users all having access to that single terminal.
No. A text-mode application that needs to support BiDi must do the
BiDi itself and pass
> From: Egmont Koblinger
> Date: Fri, 1 Feb 2019 14:16:03 +0100
> Cc: Adam Borowski , unicode@unicode.org
>
> There's absolutely no way we could reorder first, and then handle
> TAB's cursor movement. TAB's cursor movement happens in the lower
> layer, reordering happens in the upper one.
But
On Thu, Jan 31, 2019 at 4:26 PM Eli Zaretskii wrote:
> > Yes, I do argue that emacs will need to print a new escape sequence.
> > Which is much-much-much-much-much better than having to tell users to
> > go into the settings of their macOS Terminal / Konsole /
> > gnome-terminal etc. and disable
Hi,
I'm trying to respond to every question, but I'm having a hard time
keeping up :-)
Thanks a lot for all the precious input about shaping!
Here's my suggestion, for version 0.2 of the recommendation:
- No longer encourage any use of presentation form characters.
- State that it's the
Richard Wordingham wrote:
> Language tagging is already available in Unicode, via the tag
> characters in the deprecated plane.
Plane 14 isn't deprecated -- that isn't a property of planes -- and the
tag characters U+E0020 through U+E007E have been un-deprecated for use
with emoji flags. Only
On Fri, 1 Feb 2019 13:02:45 +0200
Khaled Hosny via Unicode wrote:
> On Thu, Jan 31, 2019 at 11:17:19PM +, Richard Wordingham via
> Unicode wrote:
> > On Thu, 31 Jan 2019 12:46:48 +0100
> > Egmont Koblinger wrote:
> >
> > No. How many cells do CJK ideographs occupy? We've had a strong
> >
On Fri, 1 Feb 2019 14:47:22 +0100
Egmont Koblinger via Unicode wrote:
> Hi Ken,
>
> > [language tag]
> > That is a complete non-starter for the Unicode Standard.
>
> Thanks for your input!
>
> (I hope it was clear that I just started throwing in random ideas, as
> in a brainstorming
Richard,
On 2/1/2019 1:30 PM, Richard Wordingham via Unicode wrote:
Language tagging is already available in Unicode, via the tag characters
in the deprecated plane.
Recte:
1. Plane 14 is not a "deprecated plane".
2. The tag characters in Tag Character block (U+E..U+E007F) are not
On Fri, 1 Feb 2019 at 22:20, Doug Ewell via Unicode wrote:
>
> Richard Wordingham wrote:
>
> > Language tagging is already available in Unicode, via the tag
> > characters in the deprecated plane.
>
> Plane 14 isn't deprecated -- that isn't a property of planes -- and the
> tag characters U+E0020
the proposal would contradict the goals of variation selectors and would
pollute ther variation sequences registry (possibly even creating
conflicts). And if we admit it for italics, than another VSn will be
dedicated to bold, and another for monospace, and finally many would follow
for various
On Fri, Feb 01, 2019 at 06:57:43PM +, Richard Wordingham via Unicode wrote:
> On Fri, 1 Feb 2019 13:02:45 +0200
> Khaled Hosny via Unicode wrote:
>
> > On Thu, Jan 31, 2019 at 11:17:19PM +, Richard Wordingham via
> > Unicode wrote:
> > > On Thu, 31 Jan 2019 12:46:48 +0100
> > > Egmont
On Sat, 02 Feb 2019 00:38:04 +0100
Kent Karlsson via Unicode wrote:
> Den 2019-02-01 19:57, skrev "Richard Wordingham via Unicode"
> :
> "Monospaced font" is really a concept with modification. Even for
> "plain old ASCII" there are two advance widths, not just one: 0 for
> control characters
On Fri, 01 Feb 2019 15:18:13 -0700
Doug Ewell via Unicode wrote:
> Richard Wordingham wrote:
>
> > Language tagging is already available in Unicode, via the tag
> > characters in the deprecated plane.
>
> Plane 14 isn't deprecated -- that isn't a property of planes -- and
> the tag
On Fri, 1 Feb 2019 15:15:53 +0100
Egmont Koblinger via Unicode wrote:
> Hi Richard,
>
> On Fri, Feb 1, 2019 at 12:19 AM Richard Wordingham via Unicode
> wrote:
>
> > Cropped why? If the problem is the truncation of lines, one can
> > simple store the next character.
>
> Yup, trancation of
Den 2019-02-01 19:57, skrev "Richard Wordingham via Unicode"
:
> On Fri, 1 Feb 2019 13:02:45 +0200
> Khaled Hosny via Unicode wrote:
>
>> On Thu, Jan 31, 2019 at 11:17:19PM +, Richard Wordingham via
>> Unicode wrote:
>>> On Thu, 31 Jan 2019 12:46:48 +0100
>>> Egmont Koblinger wrote:
>>>
25 matches
Mail list logo