From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: starback@stp.lingfil.uu.se, 13745@debbugs.gnu.org
Subject: bug#13745: c1-acronyms
Date: Wed, 24 Feb 2016 19:21:24 +0200 [thread overview]
Message-ID: <834mcyhvmz.fsf@gnu.org> (raw)
In-Reply-To: <877fhufyko.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 24 Feb 2016 16:48:39 +1100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 24 Feb 2016 16:48:39 +1100
> Cc: 13745@debbugs.gnu.org
>
> starback@stp.lingfil.uu.se (Per Starbäck) writes:
>
> > In GNU Emacs 24.2.93.1.
> >
> > char-acronym-table has three entries with "XXX". They are from
> > lisp/international/characters.el :
> >
> >> (let ((c1-acronyms '("XXX" "XXX" "BPH" "NBH" "IND" "NEL" "SSA" "ESA"
> >> "HTS" "HTJ" "VTS" "PLD" "PLU" "R1" "SS2" "SS1"
> >> "DCS" "PU1" "PU2" "STS" "CCH" "MW" "SPA" "EPA"
> >> "SOS" "XXX" "SC1" "CSI" "ST" "OSC" "PM" "APC")))
> >
> > These are the three C1 control characters that are listed with no name
> > in Unicode and that aren't part of ISO/IEC 6429.
> >
> > These had the acros PAD, HOP, SGCI in draft DIS 10646, but weren't
> > standardized (not accepted to ISO 10646).
> >
> > http://en.wikipedia.org/wiki/C0_and_C1_control_codes#C1_set
> > http://www.aivosto.com/vbtips/control-characters.html
> >
> > I don't like the acronym feature showing different characters the same,
> > so I suggest that "XXX" is replaced by the inofficial PAD, HOP, SGCI
> > here.
>
> If this list is automatically generated from the C1 control code list,
> then perhaps that generating function should be removed?
>
> If not, I think your patch is OK, if I understand what it's doing here.
> (I may very well be not.)
I'm okay with applying this, thanks.
next prev parent reply other threads:[~2016-02-24 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 17:00 bug#13745: c1-acronyms Per Starbäck
2016-02-24 5:48 ` Lars Ingebrigtsen
2016-02-24 17:21 ` Eli Zaretskii [this message]
2016-02-25 5:52 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834mcyhvmz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13745@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=starback@stp.lingfil.uu.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.