ing set up) I thought I'd
at least point to it in case anyone was looking for ideas.
best
- thomas
On Thursday, 30 April 2020 00:02:24 UTC+1, Dan Allen wrote:
>
> thomas,
>
> That's great to hear. We welcome your participation!
>
> Both the charter for the working gr
idea or two.
- thomas
On Monday, 7 January 2019 21:36:20 UTC, Dan Allen wrote:
>
> I'm excited to share with you some much anticipated news.
>
> After numerous calls for an AsciiDoc specification over the past year,
> it's very clear the community is ready for Ascii
]
asciidoc: FAILED: incomplete configuration files
Regard's
Thomas
--
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 asciidoc+unsubscr...@googlegroups.com.
Having to worry about collisions like this is one of the minor drawbacks
> of using a lightweight markup language. That's why we try to provide
> alternate syntax choices.
>
> Cheers,
>
> -Dan
>
> On Thu, Sep 22, 2016 at 8:05 AM, Stéphane Thomas > wrote:
>
>
>
> The Asciidoctor implementation therefore requires that the closing and
> opening delimiters be the same length.
Yeah I saw that. That would be nice. I need to convert miscellanous files
(mostly program source but also plain text documentation, hence my problem)
but using a very long delim
Hi,
Let's say I have the following code :
[source,shell,numbered]
some source
code
yeah!
If my source code contains a line with only dashes (at least four) it will
prematurelly close my source block, this is not what I want…
I found the two following solutions :
1) Use an open block
For the record, we have exactly the same set of needs. A collapsing version
of the HMTL left-hand side TOC would replicate more or less what a PDF
reader does, and would make it much nicer.
- thomas
On Wednesday, October 28, 2015 at 5:49:15 AM UTC, Willem Ferguson wrote:
>
> I maintain
I have no affinity with Ruby or Python, and have no problem getting the
Ruby environment working, including doing a little bit of hacking with
Pygments to implement my own lexer for colourising a new language (and
Pygments BTW is in Python, so all this is via a Pygments-rb project that
bridges
Hello,
I tried this :
:toc-title: image::myimage.png[]
:toc-title: > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to asciidoc+u...@googlegroups.com .
> > To post to this group, send email to asci...@googlegroups.com
> .
> > Visit this group at
Hi,
I use the html5 backend, the toc2 and data-uri attributes.
I’d like to insert an image at the top of the TOC, how can I achieve that ?
asciidoc 8.6.9
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To unsubscribe from this group and stop rec
Thanks for these last two responses as well - good to get an idea of what
people do.
On Thursday, June 18, 2015 at 4:44:51 PM UTC+1, d...@wieers.com wrote:
>
> On Thu, 18 Jun 2015, Lex Trotman wrote:
>
> > If you don't care about portability you can embed some Python in an
> > eval attribute:
Thanks, this does work. Is there a way to embed the back-ticked command in
a source document?
--
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 asciidoc+unsubscr...@
Or how do Asciidoc authors obtain the current year?
thanks
--
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 asciidoc+unsubscr...@googlegroups.com.
To post to this gr
Ah! Perfect, this works. In my case I also wanted callouts to be replaced:
[subs="specialcharacters,attributes,callouts"]
Thanks,
Thomas
On Tue, Apr 28, 2015 at 1:36 AM, Dan Allen wrote:
> Thomas,
>
> AsciiDoc does have this feature, just not the shorthand syntax. You
On Wednesday, May 28, 2014 8:13:07 PM UTC-4, Lex Trotman wrote:
>
> On 29 May 2014 03:49, george thomas >
> wrote:
> >
> >
> > I encountered the originally reported problem a few days ago with
> asciidoc
> > 8.6.9 with Python 2.7.6 on 64-bit Wind
On Tuesday, April 1, 2014 8:09:00 AM UTC-4, Lex Trotman wrote:
>
> On 1 April 2014 20:51, > wrote:
> > Hi,
> > I am facing the same issue using asciidoc 8.6.9
>
> It doesn't appear to be similar. The problem referred to above is
> non-encoding, not incorrect encoding.
>
> > It is not a pyth
I'm doing a document which includes source code. I want to be able to show
the source code in various states of maturity and want to highlight the
parts that have been added or changed.
I've tried many different asciidoc markups including color, italics etc.
None seems to work, probably since t
idoc/dblatex/asciidoc-dblatex.sty"
"/home/thomasc/test.xml"Build the book set list...
Build the listings...
XSLT stylesheets DocBook - LaTeX 2e (0.3.4-1)
===
Build test.pdf
'test.pdf' successfully built
Hope this can shed some l
On Thursday, January 24, 2013 5:13:17 PM UTC+7, Lex Trotman wrote:
>
> Hi Thomas,
>
> Depends on what you actually want to do with that text. Did you want
> it literal? If so use and the [ is not processed. You could
> also look at the other pre-defined blocks i
On Thursday, January 24, 2013 3:45:51 PM UTC+7, Dan Allen wrote:
>
> You'll want to use the double dollar macro (i.e., $$text$$). This macro
> removes the text from the document while processing and reinserts it once
> all the parsing is done.
>
> Here's how that would look for your case:
>
> C
basic
form'> <'logical operator'> <'basic form'> [)
If have tried to escape it with \, but then \ just shows up in the final
document.
Sincerly
Thomas Christensen
--
You received this message because you are subscribed to the Google Groups
"asci
Hi there,
are there any PHP ports of AsciiDoc that you are aware of?
I'd like to run AsciiDoc on a machine where Python isn't available.
Many thanks in advance.
ps. I assume http://andrewk.webfactional.com/asciidoc.php is just a web
interface for the Python implementation...?
--
You received
relative paths.
My conclusion to avoid as many problems as possible: In Asciidoc, images
must always be included using relative paths which are interpretable as
relative URIs at the same time!
Am Dienstag, 17. Juli 2012 14:13:04 UTC+2 schrieb Lex Trotman:
>
> On 17 July 2012
round, though.
Thanks
Thomas
Am Dienstag, 17. Juli 2012 13:01:15 UTC+2 schrieb Lex Trotman:
>
> On 17 July 2012 20:00, Thomas K. wrote:
> > Hi,
> >
> > I am trying to use the {indir} attribute as part as a path when
> including
> > images, e.g.
>
works for all operating
systems. Or my problem actually related to dblatex, which should perform
this conversion instead?
Greetings
Thomas
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To view this discussion on the w
Thanks for helping.
It's a pitty that horizontal labels only usable in a small cases. I've
switched all to vertical labeled lists.
But good to know about the open block :)
cheers,
Thomas
On 26 Feb., 04:19, Stuart Rackham wrote:
> On 25/02/12 23:34, Thomas wrote:
>
>
&g
--
FvwmCommand -i0 FvwmBanner
--
but then the ';;' was shown behind the zero and a warning occurs:
asciidoc: WARNING: FvwmCommand.txt: line 96: missing style: [blockdef-
listing]: horizontal
Can anybody help me?
Thanks in advance,
Thomas
--
You received this message because you are sub
27 matches
Mail list logo
