From: Juri Linkov <juri@jurta.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ruediger@c-plusplus.de, 16439@debbugs.gnu.org, sva-news@mygooglest.com
Subject: bug#16439: [feature request] Highlighting of strings within Info buffers
Date: Wed, 22 Jan 2014 10:09:19 +0200 [thread overview]
Message-ID: <87r480zbdc.fsf@mail.jurta.org> (raw)
In-Reply-To: <83eh41gwlr.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 21 Jan 2014 17:53:20 +0200")
> I agree, and didn't say anything to the contrary. I told about the
> slant typeface as an evidence that what came out of @dfn should be
> emphasized in some way.
I don't understand the difference between using @dfn and double quotes,
e.g. why in the source of the chapter "The Organization of the Screen":
The main area of the frame, below the tool bar (if one exists) and
above the echo area, is called @dfn{the window}. Henceforth in this
manual, we will use the word ``window'' in this sense.
the different styles are used for @dfn{the window} and ``window''?
But if both were written in the Info output using DOUBLE QUOTATION MARK
as “window”, then in the Info browser we could emphasize such terms
using the slant typeface and put invisible properties on quote characters.
Then if code blocks such as e.g. in @code{("/foo" "/bar" @dots{})}
were written using simple quotation marks e.g. ("/foo" "/bar" …)
then it would make sense to highlight quoted strings in Info
in code samples using `font-lock-string-face'.
This problem doesn't exist in HTML output that keeps all different source
styles unambiguous, e.g.:
<p>The main area of the frame, below the tool bar (if one exists) and
above the echo area, is called <dfn>the window</dfn>. Henceforth in this
manual, we will use the word “window” in this sense.
<code>("/foo" "/bar" …)</code>
where only strings in " inside <code> makes sense
to highlight using `font-lock-string-face'.
next prev parent reply other threads:[~2014-01-22 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 10:15 bug#16439: [feature request] Highlighting of strings within Info buffers Sebastien Vauban
2014-01-14 14:34 ` Rüdiger Sonderfeld
2014-01-14 20:05 ` Drew Adams
2014-01-20 9:18 ` Juri Linkov
2014-01-20 14:10 ` Stefan Monnier
2020-09-18 14:03 ` Lars Ingebrigtsen
2014-01-20 15:17 ` Eli Zaretskii
2014-01-21 7:54 ` Juri Linkov
2014-01-21 15:53 ` Eli Zaretskii
2014-01-22 8:09 ` Juri Linkov [this message]
2014-01-22 15:42 ` Eli Zaretskii
2014-01-20 18:06 ` Drew Adams
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=87r480zbdc.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=16439@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ruediger@c-plusplus.de \
--cc=sva-news@mygooglest.com \
/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.