From: jsbien@mimuw.edu.pl (Janusz S. Bień)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32599@debbugs.gnu.org
Subject: bug#32599: 25.2; Feature request: input PUA characters by name
Date: Mon, 27 May 2019 19:39:50 +0200 [thread overview]
Message-ID: <86muj7u789.fsf@mimuw.edu.pl> (raw)
In-Reply-To: <868t4n3wbt.fsf@mimuw.edu.pl>
On Mon, May 27 2019 at 20:11 +03, Eli Zaretskii wrote:
>> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
>> Cc: 32599@debbugs.gnu.org
>> Date: Mon, 27 May 2019 07:48:38 +0200
>>
>> On Sun, May 26 2019 at 21:52 +03, Eli Zaretskii wrote:
>>
>> [...]
>>
>> > Personally, I'm surprised people use PUA for
>> > these purposes,
>>
>> Which purposes?
>
> The purposes of mainstream text editing. Are there other comparable
> applications that let users define fonts for PUA codepoints, define
> their attributes, and then manipulate those characters as any other?
I don't know and don't care, as I use only Emacs for editing.
>> > and even more surprised they expect Emacs to support
>> > this. But that's me.
>>
>> PUA characters, especially MUFI, are needed to typeset some
>> texts. (XeLa)TeX is still a very good typesetting system and Emacs-based
>> AUCTeX is still a very good tool to use TeX.
>
> Those are separate projects. If they need to use non-standard
> characters with corresponding non-standard fonts, they could maintain
> some add-on packages for Emacs to do that.
Thanks for the suggestion. I will contact AUCTeX people and see what thay
think about it.
>
> Asking Emacs to maintain compatibility to various ad-hoc registries
> outside of Unicode is not really reasonable.
Yes, but it is not what I propose. I just would the user to be able to
use his own definition of PUA provided in the form of an additional
UnicodeData.txt (not necessarily as a part of Unicode, it can be perhaps
a different coding system).
[...]
> I guess what I'm saying is that without a dedicated volunteer who
> would take care of this issue we can only wish such support will be
> added, but we have no real hope it will materialize, except by some
> enormous luck.
As I said, we have different things in mind, so I'm not sure the above
statement really applies to my proposal.
> Of course, if you know someone who could be persuaded to come on board
> and work on this now and in the future, I think the feature will be
> welcome.
I don't know such a person now, but this can of course change in the
future.
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
next prev parent reply other threads:[~2019-05-27 17:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86sh30fg4q.fsf@mimuw.edu.pl>
2018-08-31 6:05 ` bug#32599: 25.2; Feature request: input PUA characters by name Janusz S. Bień
2018-08-31 8:05 ` Robert Pluim
2018-08-31 9:09 ` Janusz S. Bień
2018-08-31 12:34 ` Robert Pluim
2018-08-31 12:54 ` Janusz S. Bień
2019-05-26 8:10 ` Janusz S. Bień
2019-05-26 14:45 ` Eli Zaretskii
2019-05-26 15:18 ` Janusz S. Bień
2019-05-26 15:48 ` Janusz S. Bień
2019-05-26 16:51 ` Eli Zaretskii
2019-05-26 16:56 ` Eli Zaretskii
2019-05-26 17:33 ` Janusz S. Bień
2019-05-26 18:52 ` Eli Zaretskii
2019-05-27 5:48 ` Janusz S. Bień
2019-05-27 17:11 ` Eli Zaretskii
2019-05-27 17:39 ` Janusz S. Bień [this message]
2019-05-27 18:45 ` Eli Zaretskii
2019-05-28 5:18 ` Janusz S. Bień
2019-05-28 5:34 ` Eli Zaretskii
2019-05-28 5:39 ` Janusz S. Bień
2020-12-30 17:49 ` Janusz S. Bień
2020-12-30 20:52 ` Eli Zaretskii
2020-12-31 6:39 ` Janusz S. Bień
2020-12-31 7:49 ` Eli Zaretskii
2020-12-31 8:14 ` Janusz S. Bień
2020-12-31 9:06 ` Eli Zaretskii
2020-12-31 9:31 ` Janusz S. Bień
2020-12-31 10:31 ` Eli Zaretskii
2022-04-26 13:09 ` Lars Ingebrigtsen
2022-04-26 13:30 ` Janusz S. Bień
2022-04-26 13:37 ` Lars Ingebrigtsen
2022-04-26 13:44 ` Janusz S. Bień
2022-04-26 13:45 ` Lars Ingebrigtsen
2022-04-26 15:33 ` Janusz S. Bień
2022-04-26 15:49 ` Robert Pluim
2022-04-26 16:09 ` Janusz S. Bień
2022-04-26 16:44 ` Eli Zaretskii
2022-04-26 18:22 ` Janusz S. Bień
2022-04-27 11:51 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86muj7u789.fsf@mimuw.edu.pl \
--to=jsbien@mimuw.edu.pl \
--cc=32599@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).