On 17/06/12 23:07, Lex Trotman wrote:
[...]
This is probably a good reason to replace the obsolete<tt> tags
with<code>
tags in asciidoc. In the mean time you can put this workaround in your
AsciiDoc source file headers:
:listingblock.:<pre><code>|</code></pre>
Hi Stuart,
I just got around to running the manual through asciidoc to generate
the html to commit. Got a
asciidoc: WARNING: flexndex.asciidoc: line 5: missing configuration
section: listingblock
message (on 8.6.7 normal, not with your patch) maybe this is the
problem with github, but I don't understand whats causing it since
xhtml11.conf definitely has a listingblock section?
Cheers
Lex
Sigh, user error, I added the listingblock attribute so it was part of
the header, but of course backends havn't been loaded when header
attributes are processsed.
A blank line separating it from header fixed it.
Really weird though, yours
(https://github.com/elextr/flexndex/blob/master/flexndex.asciidoc) displays
listing blocks correctly, but mine does not
(https://github.com/srackham/clisms/blob/master/README.asciidoc).
The HTML source on both github pages has the listingblocks in
<pre><tt>|</tt></pre> but Chrome sees yours as <pre><code>|</code></pre> in the
DOM, but sees mine as <pre><tt>|</tt></pre> in the DOM.
Also I noticed no difference with or without the spacer line on my github page
(and it worked with and without the spacer compiled locally using the latest
asciidoc).
Cheers, Stuart
But the<code> sections show in a style without background or the
right font when shown in browsers, until you put<code> in the css I
guess. Since I don't like that I am having to comment out the
listingblock entry to make the .html then add it back in to commit.
Just watch me forget :)
Interestingly github renders<code> correctly, but maybe it has it in
the css for the overall page. And I notice it uses alternating
backgrounds for tables.
Cheers
Lex
done, I never thought to look at the github rendering of the manual.
Weird thing is that I tested this out with one of my github projects and it
worked, but when I pushed it a second time it had reverted to the old
behavior.
Cheers, Stuart
There's also a wee syntax error here:
simple-grouped::a simple built-in grouped style shows as a traditional
It should be:
simple-grouped:: a simple built-in grouped style shows as a traditional
thanks done
Will be pushed soon with other changes that are in progress.
Cheers
Lex
[...]
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
