On Tue, 5 Feb 2019 16:01:41 +
Andrew West via Unicode wrote:
> You would
> have to first convert any text to be italicized to NFD, then apply
> VS14 to each non-combining character. This alone would make a VS
> solution unacceptable in my opinion.
What is so unacceptable about having to do
I think that before making any decision we must make some decision about
what we mean by "newlines". There are in fact 3 different functions:
- (1) soft line breaks (which are used to enforce a maximum display width
between paragraph margins): these are equivalent to breakable and
compressible
> From: Egmont Koblinger
> Date: Tue, 5 Feb 2019 02:28:50 +0100
> Cc: unicode@unicode.org
>
> I have to admit, I'm not an Emacs user, I only have some vague ideas
> how powerful a tool it is. But in its very core I still believe it's a
> text editor – is it fair to say this? It could be used for
On Tue, 5 Feb 2019 at 15:34, wjgo_10...@btinternet.com via Unicode
wrote:
>
> italic version of a glyph in plain text, including a suggestion of to
> which characters it could apply, would test whether such a proposal
> would be accepted to go into the Document Register for the Unicode
>
> From: Egmont Koblinger
> Date: Tue, 5 Feb 2019 01:32:34 +0100
> Cc: unicode@unicode.org
>
> On the other hand, it's not unreasonable for higher level stuff (e.g.
> shell scripts, or tools like "zip") to use such control characters.
Yes, but most of them won't ever do that.
> > No, this
> Date: Tue, 5 Feb 2019 00:05:47 +
> From: Richard Wordingham via Unicode
>
> > > Actually, UAX#9 defines "paragraph" as the chunk of text delimited
> > > by paragraph separator characters. This means characters whose bidi
> > > category is B, which includes Newline, the CR-LF pair on
> From: Egmont Koblinger
> Date: Tue, 5 Feb 2019 00:08:10 +0100
> Cc: unicode@unicode.org
>
> every single newline character starts a new paragraph. The result of
> printf "Hello\nWorld\n" > world.txt
> is a text file consisting of two paragraphs, with 5 characters in each.
> Correct?
Yes.
>
James Kass wrote:
William’s suggestion of floating a proposal for handling italics with
VS14 might be an example of the old saying about “putting the cart
before the horse”.
Well, a proposal just about using VS14 to indicate a request for an
italic version of a glyph in plain text,
William Overington wrote,
> Well, a proposal just about using VS14 to indicate a request for an
> italic version of a glyph in plain text, including a suggestion of to
> which characters it could apply, would test whether such a proposal
> would be accepted to go into the Document Register for
On Tue, Feb 5, 2019 at 12:23 AM James Kass via Unicode
wrote:
> Text a man has JOINED together, let not algorithm put asunder.
>
I was hoping so much that ὃ οὖν ὁ θεὸς συνέζευξεν ἄνθρωπος μὴ χωριζέτω
would have an apostrophe but alas no.
10 matches
Mail list logo
