From: Stefan Monnier <monnier@iro.umontreal.ca>
To: 15703@debbugs.gnu.org
Subject: bug#15703: [PATCH 1/8] EWW: Support user defined representation for checkbox.
Date: Sun, 03 Nov 2013 20:50:56 -0500 [thread overview]
Message-ID: <jwvy555lyvo.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <8738ndu31a.fsf@flea.lifelogs.com> (Ted Zlatanov's message of "Sun, 03 Nov 2013 06:40:17 -0500")
>>> Ah, OK, I see. But it seems like kind of the same ideas, so maybe a
>>> generic facility would be useful... not a font-lock interaction, but for
>>> keeping the record of "this string maps to this Unicode symbol"?
>>> Basically a big hashtable with some user control. Then
>>> `prettify-symbols-mode' could use that facility too.
SM> I think it'd be easier to go the other way around: provide an
SM> replacement to use if/when the display font doesn't provide a glyph for
SM> that characters.
> That doesn't help with drawing trees in Unicode, for example.
I think this case is quite different: none of the proposals so far can
handle it. And I don't think it can be handled purely locally
(i.e. without knowing that those chars are put together to represent
a tree).
Stefan
next prev parent reply other threads:[~2013-11-04 1:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1382658061.git.ruediger@c-plusplus.de>
2013-10-24 23:43 ` bug#15703: [PATCH 1/8] EWW: Support user defined representation for checkbox Rüdiger Sonderfeld
2013-10-25 15:00 ` Ted Zlatanov
2013-10-25 17:39 ` Rüdiger Sonderfeld
2013-10-25 18:04 ` Ted Zlatanov
2013-10-26 1:54 ` Stefan Monnier
2013-11-03 11:40 ` Ted Zlatanov
2013-11-04 1:50 ` Stefan Monnier [this message]
2013-11-04 16:23 ` Ted Zlatanov
2013-11-04 17:51 ` Stefan Monnier
2013-12-01 15:53 ` Lars Magne Ingebrigtsen
2013-10-24 23:43 ` bug#15704: [PATCH 2/8] EWW: Handle HTML5 input types as text input Rüdiger Sonderfeld
2013-12-01 15:38 ` Lars Magne Ingebrigtsen
2013-10-24 23:43 ` bug#15705: [PATCH 3/8] shr: Display content for video if no poster is available Rüdiger Sonderfeld
2013-12-01 15:46 ` bug#15708: " Lars Magne Ingebrigtsen
2013-10-24 23:43 ` bug#15706: [PATCH 4/8] shr: Add support for <audio> tag Rüdiger Sonderfeld
2013-12-01 15:46 ` bug#15708: " Lars Magne Ingebrigtsen
2013-10-24 23:44 ` bug#15707: [PATCH 5/8] EWW: Option to always use external-browser for certain content Rüdiger Sonderfeld
2013-12-01 15:44 ` Lars Magne Ingebrigtsen
2013-10-24 23:44 ` bug#15708: [PATCH 6/8] EWW: Erase old title Rüdiger Sonderfeld
2013-10-26 1:17 ` Rüdiger Sonderfeld
2013-10-26 11:04 ` bug#15708: [PATCH] " Rüdiger Sonderfeld
2013-12-01 15:47 ` bug#15708: [PATCH 6/8] " Lars Magne Ingebrigtsen
2013-10-24 23:44 ` bug#15709: [PATCH 7/8] shr: Handle <source> tag for video/audio elements Rüdiger Sonderfeld
2013-10-24 23:44 ` bug#15710: [PATCH 8/8] * lisp/net/shr.el: Fix typo Rüdiger Sonderfeld
2013-12-01 15:36 ` bug#15708: " Lars Magne 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=jwvy555lyvo.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=15703@debbugs.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).