emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kodi Arfer <kodi@arfer.net>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-html: Allow "Figure %d:", etc. to be styled
Date: Tue, 09 Jul 2013 16:19:30 -0400	[thread overview]
Message-ID: <51DC7052.9070607@arfer.net> (raw)
In-Reply-To: <87bo6b1pe1.fsf@gmail.com>

On 2013 Jul 09 Tue 3:53:26 PM -0400, Nicolas Goaziou 
<n.goaziou@gmail.com> wrote:
> Kodi Arfer <kodi@arfer.net> writes:
>
>>  From a873d204b2c4f3facf2d8658f69764acbd063246 Mon Sep 17 00:00:00 2001
>> From: Kodi Arfer <git@arfer.net>
>> Date: Wed, 3 Jul 2013 17:51:56 -0400
>> Subject: [PATCH] ox-html: Allow "Figure %d:", etc. to be styled
>>
>> * lisp/ox-html.el (org-html-paragraph): Wrap "Figure %d:" in
>>    <span class="figure-number">.
>>    (org-html-list-of-tables, org-html-table): Wrap "Table %d:" in
>>     <span class="table-number">.
>>    (org-html-list-of-listings): Wrap "Listing %d:" in
>>    <span class="listing-number">.
>> * doc/org.text (CSS support): Mention .figure-number,
>>    .listing-number, and .table-number.
>
> Thank you for the patch.

De nada.

> Wouldn't it be more future-proof to wrap them within the same CSS entry?
> Otherwise, if we ever introduce other caption types, we'll need to
> remember to add another entry for it.
>
> Obviously, my question assume it is very unlikely that someone would
> want different styles for captions. But I may be wrong.

One case I know of is APA style. Here are some examples from the APA 
publication manual. "Figure 1" is supposed to be italicized and inline 
with the caption ( http://i.imgur.com/u6jsfJx.png ), whereas "Table 1" 
is supposed to be upright and on its own line ( 
http://i.imgur.com/3gvxEdd.png ). Admittedly, APA style is crazy, and 
you have to be additionally crazy to want APA style in HTML.

We could still use the same class and then expect people to use 
selectors to be as specific as they want (e.g., if the generic class is 
~.caption-number~, one could use the selector ~caption .caption-number~ 
for tables and ~figcaption .caption-number~ for figures, at least in 
HTML5). I think using different classes is actually simpler, though, 
because then we don't have to keep track of how selectable the different 
caption types are.

> BTW, do you have any news about your FSF papers?

I got an assignment form back from the FSF, and I returned scans of the 
signed form on July 1, but I haven't heard back since.

I guess there's not much of a hurry. I won't be firing off these little 
patches as much now that I've released http://arfer.net/daylight .

  reply	other threads:[~2013-07-09 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 22:19 [PATCH] ox-html: Allow "Figure %d:", etc. to be styled Kodi Arfer
2013-07-09 19:53 ` Nicolas Goaziou
2013-07-09 20:19   ` Kodi Arfer [this message]
2013-07-09 20:31     ` Nicolas Goaziou
2013-07-09 21:24     ` Bastien

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=51DC7052.9070607@arfer.net \
    --to=kodi@arfer.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.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).