emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: small caps
Date: Sat, 31 Oct 2015 12:16:15 -0400	[thread overview]
Message-ID: <CAN_Dec87UBhHuo25fUweVoFetNbMYQ=unb4UOmmqtcwgk+VAvQ@mail.gmail.com> (raw)
In-Reply-To: <m2pozwzell.fsf@christianmoe.com>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

On Oct 30, 2015 09:09, "Christian Moe" <mail@christianmoe.com> wrote:
>
>
> Thomas S. Dye writes:
>
> > Sorry, I forgot to give an example.  I use it like this [[sc:ad][AD]].
> >
> > The advantage of a link over a macro is that the link should export
> > correctly to both LaTeX and HTML.
> >
> > If you intend to export to a single backend, then Nicolas' suggestion to
> > use a macro is simpler.
>
> Though you could support multiple backends with a macro, too, you just
> need to use lots of @'s. E.g.:
>
>
> #+MACRO: sc @@latex:\textsc{$1}@@@@html:<span style="font-variant:
>  small-caps;">$1</span>@@
>
> Already in 400 {{{sc(bc)}}}, the Greeks...
>
>
> That's for a quick example; better to use <span class="smallcaps"> or
> something and put the CSS in a separate stylesheet, of couse

thanks everyone for all the suggestions, I will try out a few of them and
decide which seems most natural for me. But in any event I've learned a bit
about macros and custom links, which has been great.

Matt
>
> Yours,
> Christian

[-- Attachment #2: Type: text/html, Size: 1443 bytes --]

next prev parent reply	other threads:[~2015-10-31 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 16:39 small caps Matt Price
2015-10-29 16:47 ` Nicolas Goaziou
2015-10-29 16:55   ` Thomas S. Dye
2015-10-29 20:17     ` Matt Price
2015-10-29 20:42       ` Thomas S. Dye
2015-10-30 13:10         ` Christian Moe
2015-10-31 16:16           ` Matt Price [this message]
2015-10-29 17:25   ` Aaron Ecay
2015-10-29 17:39     ` Thomas S. Dye
2015-10-29 17:46       ` Nicolas Goaziou
2015-10-29 17:44     ` Nicolas Goaziou
2015-10-29 20:37 ` Rasmus
2015-10-29 21:18 ` Robert Klein

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='CAN_Dec87UBhHuo25fUweVoFetNbMYQ=unb4UOmmqtcwgk+VAvQ@mail.gmail.com' \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@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

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).