From: Dan Davison <dandavison7@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: "Sébastien Mengin" <sebastien-listes@edilibre.net>,
emacs-orgmode@gnu.org
Subject: Re: markup for small caps ?
Date: Sun, 31 Oct 2010 19:53:46 +0000 [thread overview]
Message-ID: <87d3qqf8ad.fsf@gmail.com> (raw)
In-Reply-To: <373F2343-91D3-435C-B447-E5548E2C865C@tsdye.com> (Thomas S. Dye's message of "Sun, 31 Oct 2010 09:08:48 -1000")
"Thomas S. Dye" <tsd@tsdye.com> writes:
> On Oct 31, 2010, at 7:43 AM, Dan Davison wrote:
>
>> "Thomas S. Dye" <tsd@tsdye.com> writes:
>>
>>> Aloha Sebastien,
>>>
>>> Arbitrary markup is possible, see http://orgmode.org/worg/org-tutorials/org-latex-export.php#sec-12
>>>
>>> Using this approach [[latex:textsc][My small caps]] would export to
>>> LaTeX as \textsc{My small caps}.
>>
>> In the Org-buffer I see "My small caps" with a special underlined
>> face. This is standard for links with a non-missing display part,
>> but in
>> the case of non-standard link types such as this I'm not sure it's
>> helpful. I think I'd like to see in my Org buffer what markup is being
>> applied.[1]
>>
>> (Related question -- is there a command I can enter with point on a
>> link
>> which displays the raw text of the link? (temporarily remove
>> overlays at
>> point?))
>>
>> Thanks,
>>
>> Dan
>>
>>
>> Footnotes:
>> [1] Maybe add an optional display argument to org-add-link-type
>> which would be a function used by the org-activate-*-link function??
>>
>
> Hi Dan,
>
> I agree that it would be good to generalize the Org-mode link syntax
> so that it doesn't assume a link representation in the Org-mode buffer
> and in HTML export. If a link representation was one possibility
> among others, then this syntax would be that much more useful.
>
> As for showing small caps, say, in the Org-mode buffer, I agree that
> this would be nice in this instance.
Hi Tom,
Sorry, I didn't express myself clearly. I didn't mean that I'd like to
see small caps in the org buffer. What I meant is that I'd prefer to see
something like [[latex:textsc][My small caps]], as opposed to it all
magically being covered up with an overlay displaying "My small
caps". With the overlay, I've no idea that it is a special markup, and
not some form of link.
Dan
next prev parent reply other threads:[~2010-10-31 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 14:37 markup for small caps ? Sébastien Mengin
2010-10-31 16:11 ` Thomas S. Dye
2010-10-31 16:45 ` Sébastien Mengin
2010-10-31 17:05 ` Bernt Hansen
2010-11-01 12:22 ` Sébastien Mengin
2010-10-31 17:43 ` Dan Davison
2010-10-31 19:08 ` Thomas S. Dye
2010-10-31 19:53 ` Dan Davison [this message]
2010-10-31 20:13 ` Thomas S. Dye
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3qqf8ad.fsf@gmail.com \
--to=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebastien-listes@edilibre.net \
--cc=tsd@tsdye.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).