Michael,
I think using text rather than images is the right way to go. I have
another solution which may scale even better than unicode characters. In
the default stylesheet for Asciidoctor, I'm using CSS to circle the number
of a callout, effectively giving you the same presentation as either the
image or the unicode character. The benefit of this approach is that it
can accommodate any number.
Here's the CSS I use:
.conum {
display: inline-block;
color: white;
background-color: black;
border-radius: 100px;
text-align: center;
width: 18px;
height: 18px;
font-size: 12px;
font-weight: bold;
line-height: 18px;
font-family: Arial, sans-serif;
font-style: normal;
position: relative;
top: -1px;
}
Replace the backend template callout-inlinemacro with this one:
[callout-inlinemacro]
<i class="conum">{index}</i>
...and also in the callout list:
[listtags-callout]
...
item=<tr><td><i class="conum">{listindex}</i></td><td>|</td></tr>
(The HTML markup is inspired by the technique employed by Font Awesome).
Here's a preview of how it looks:
http://twitpic.com/cjewgb/full
What's nice about this approach is that if CSS is stripped away, the
callout number still renders.
-Dan
On Sun, Apr 14, 2013 at 12:03 PM, Michael Bishop <[email protected]> wrote:
> Hi Everyone,
>
> I'm new to this list and have only been using asciidoc for about a week so
> I apologize in advance if there are procedures and conventions I'm breaking.
>
> I have a feature request which is to be able to use Unicode characters for
> callouts in lieu of images. They will render with more fidelity in vector
> formats.
>
> Specifically, if you look in the Dingbats section of the Unicode charts,
> you'll see circled numbers that are rendered both in "positive" and
> "negative" presentations...
>
> http://en.wikipedia.org/wiki/List_of_Unicode_characters#Dingbats
>
> Characters U+2776...U+2793
>
> My feature request would be to specify a range of 10 unicode characters to
> be used for callouts instead of images.
>
> I have downloaded the code as well. If anyone can give me hints about
> where I should modify the code as a proof-of-concept, I'm all ears.
>
> Thanks!
>
> _ michael
>
> --
> You received this message because you are subscribed to the Google Groups
> "asciidoc" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/asciidoc?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
