describe-char-fold-equivalences

describe-char-fold-equivalences

[T.V Raman]

Calling describe-char-fold-equivalences and specifying "'"
displays the following --- could we get rid of the '\n'    that
appears on every line as a field delimiter?

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮


': ?\N{APOSTROPHE}
❟: ?\N{HEAVY LOW SINGLE COMMA QUOTATION MARK ORNAMENT}
❛: ?\N{HEAVY SINGLE TURNED COMMA QUOTATION MARK ORNAMENT}
❜: ?\N{HEAVY SINGLE COMMA QUOTATION MARK ORNAMENT}
‘: ?\N{LEFT SINGLE QUOTATION MARK}
’: ?\N{RIGHT SINGLE QUOTATION MARK}
‚: ?\N{SINGLE LOW-9 QUOTATION MARK}
‛: ?\N{SINGLE HIGH-REVERSED-9 QUOTATION MARK}
‚: ?\N{SINGLE LOW-9 QUOTATION MARK}
󠀢: ?\N{TAG QUOTATION MARK}
❮: ?\N{HEAVY LEFT-POINTING ANGLE QUOTATION MARK ORNAMENT}
❯: ?\N{HEAVY RIGHT-POINTING ANGLE QUOTATION MARK ORNAMENT}
‹: ?\N{SINGLE LEFT-POINTING ANGLE QUOTATION MARK}
›: ?\N{SINGLE RIGHT-POINTING ANGLE QUOTATION MARK}
＇: ?\N{FULLWIDTH APOSTROPHE}

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

Re: describe-char-fold-equivalences

[Eli Zaretskii]

> Date: Sat, 07 Jan 2023 20:26:44 -0800
> From: "T.V Raman" <raman@google.com>
> 
> Calling describe-char-fold-equivalences and specifying "'"
> displays the following --- could we get rid of the '\n'    that
> appears on every line as a field delimiter?

Which newlines do you want to get rid of?

If those are the newlines between the individual characters, then
removing the newlines will produce a single very long line, which will
be harder to read.

Re: describe-char-fold-equivalences

[Ruijie Yu via Emacs development discussions.]

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sat, 07 Jan 2023 20:26:44 -0800
>> From: "T.V Raman" <raman@google.com>
>>
>> Calling describe-char-fold-equivalences and specifying "'"
>> displays the following --- could we get rid of the '\n'    that
>> appears on every line as a field delimiter?
>
> Which newlines do you want to get rid of?
>
> If those are the newlines between the individual characters, then
> removing the newlines will produce a single very long line, which will
> be harder to read.

I think they mean for each line, instead of saying "?\N{DESCRIPTION}",
just say "DESCRIPTION".

Best,


RY

Re: describe-char-fold-equivalences

[Yuri Khan]

On Sun, 8 Jan 2023 at 11:27, T.V Raman <raman@google.com> wrote:

> Calling describe-char-fold-equivalences and specifying "'"
> displays the following --- could we get rid of the '\n'    that
> appears on every line as a field delimiter?

Those are not newlines (backslash small letter en) but syntax for
specifying a character by its Unicode name (question mark backslash
capital en). Maybe your screen reader does not make that obvious.

> ': ?\N{APOSTROPHE}

Re: describe-char-fold-equivalences

[T.V Raman]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 786 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

I meant the verbatim '\n' that appears between the displayed char and
its unicode name -- it's a literal '\n' at least that's what I see in
what I pasted.
>> Date: Sat, 07 Jan 2023 20:26:44 -0800
>> From: "T.V Raman" <raman@google.com>
>> 
>> Calling describe-char-fold-equivalences and specifying "'"
>> displays the following --- could we get rid of the '\n'    that
>> appears on every line as a field delimiter?
>
> Which newlines do you want to get rid of?
>
> If those are the newlines between the individual characters, then
> removing the newlines will produce a single very long line, which will
> be harder to read.

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8

Re: describe-char-fold-equivalences

[T.V Raman]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 876 bytes --]

Ruijie Yu <ruijie@netyu.xyz> writes:


correct:-)
Thanks for confirming that that '\n' exists:-)

  > Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Date: Sat, 07 Jan 2023 20:26:44 -0800
>>> From: "T.V Raman" <raman@google.com>
>>>
>>> Calling describe-char-fold-equivalences and specifying "'"
>>> displays the following --- could we get rid of the '\n'    that
>>> appears on every line as a field delimiter?
>>
>> Which newlines do you want to get rid of?
>>
>> If those are the newlines between the individual characters, then
>> removing the newlines will produce a single very long line, which will
>> be harder to read.
>
> I think they mean for each line, instead of saying "?\N{DESCRIPTION}",
> just say "DESCRIPTION".
>
> Best,
>
>
> RY

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8

Re: describe-char-fold-equivalences

[T.V Raman]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 747 bytes --]

Yuri Khan <yuri.v.khan@gmail.com> writes:


It did make it obvious, the me the user still got confused -- I wasn't
aware of that particular usage 

> On Sun, 8 Jan 2023 at 11:27, T.V Raman <raman@google.com> wrote:
>
>> Calling describe-char-fold-equivalences and specifying "'"
>> displays the following --- could we get rid of the '\n'    that
>> appears on every line as a field delimiter?
>
> Those are not newlines (backslash small letter en) but syntax for
> specifying a character by its Unicode name (question mark backslash
> capital en). Maybe your screen reader does not make that obvious.
>
>> ': ?\N{APOSTROPHE}

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8

Re: describe-char-fold-equivalences

[Robert Pluim]

>>>>> On Sun, 08 Jan 2023 06:57:53 -0800, "T.V Raman" <raman@google.com> said:

    TVR> Yuri Khan <yuri.v.khan@gmail.com> writes:
    TVR> It did make it obvious, the me the user still got confused -- I wasn't
    TVR> aware of that particular usage 

See (info "(elisp) General Escape Syntax")

The idea was to produce something that people could copy and use,
without having the unicode codepoint numbers appearing.

Robert
-- 

Re: describe-char-fold-equivalences

[T.V Raman]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 264 bytes --]

thanks for the explanation.

Perhaps we could make that more discoverable when reading the output of
that function ie the doc string I complained about?


-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8

Re: describe-char-fold-equivalences

[Robert Pluim]

>>>>> On Mon, 09 Jan 2023 07:31:17 -0800, "T.V Raman" <raman@google.com> said:

    T> thanks for the explanation.
    T> Perhaps we could make that more discoverable when reading the output of
    T> that function ie the doc string I complained about?

Yes. Something like this for emacs-29?

diff --git a/lisp/char-fold.el b/lisp/char-fold.el
index eff2f5558b3..f1da7997407 100644
--- a/lisp/char-fold.el
+++ b/lisp/char-fold.el
@@ -436,7 +436,24 @@ describe-char-fold-equivalences
 describe all available character equivalences of `char-fold-to-regexp'.
 Optional argument LAX (interactively, the prefix argument), if
 non-nil, means also include partially matching ligatures and
-non-canonical equivalences."
+non-canonical equivalences.
+
+Each line of the display shows the equivalences in two different
+ways separated by a colon:
+
+    - as the literal character or sequence
+    - using an ASCII-only escape syntax
+
+For example, for the letter 'r', the first line is
+
+    r: ?\N{LATIN SMALL LETTER R}
+
+which is for the requested character itself, and a later line has
+
+    ṟ: ?\N{LATIN SMALL LETTER R}?\N{COMBINING MACRON BELOW}
+
+which clearly shows what the constituent characters are."
   (interactive (list (ignore-errors
                        (read-char-by-name
                         (format-prompt "Unicode name, single char, or hex"

Re: describe-char-fold-equivalences

[T.V Raman]

yes, this LGTM!

Robert Pluim writes:
 > >>>>> On Mon, 09 Jan 2023 07:31:17 -0800, "T.V Raman" <raman@google.com> said:
 > 
 >     T> thanks for the explanation.
 >     T> Perhaps we could make that more discoverable when reading the output of
 >     T> that function ie the doc string I complained about?
 > 
 > Yes. Something like this for emacs-29?
 > 
 > diff --git a/lisp/char-fold.el b/lisp/char-fold.el
 > index eff2f5558b3..f1da7997407 100644
 > --- a/lisp/char-fold.el
 > +++ b/lisp/char-fold.el
 > @@ -436,7 +436,24 @@ describe-char-fold-equivalences
 >  describe all available character equivalences of `char-fold-to-regexp'.
 >  Optional argument LAX (interactively, the prefix argument), if
 >  non-nil, means also include partially matching ligatures and
 > -non-canonical equivalences."
 > +non-canonical equivalences.
 > +
 > +Each line of the display shows the equivalences in two different
 > +ways separated by a colon:
 > +
 > +    - as the literal character or sequence
 > +    - using an ASCII-only escape syntax
 > +
 > +For example, for the letter 'r', the first line is
 > +
 > +    r: ?\N{LATIN SMALL LETTER R}
 > +
 > +which is for the requested character itself, and a later line has
 > +
 > +    ṟ: ?\N{LATIN SMALL LETTER R}?\N{COMBINING MACRON BELOW}
 > +
 > +which clearly shows what the constituent characters are."
 >    (interactive (list (ignore-errors
 >                         (read-char-by-name
 >                          (format-prompt "Unicode name, single char, or hex"

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

Re: describe-char-fold-equivalences

[Robert Pluim]

>>>>> On Mon, 9 Jan 2023 10:31:47 -0800, "T.V Raman" <raman@google.com> said:

    TVR> yes, this LGTM!

Now done on the emacs-29 branch.

Robert
--