On 16/01/13 06:57, Andrew Birchall wrote:
> Thanks a lot for your fix.
> However the problem I have is that it copies the docbook source file
> into the output directory and uses that to build the pdf.
> This means it no longer finds the images which are relative to the
> source file in a sub-directory of the source directory.

It will behave like this when generating PDF files. The -D option was
implemented for HTML based outputs (xhtml, epub, chunked, htmlhelp
formats) which consist of an assemblage of images, CSS and HTML as was
the related resources options -- so it's never a problem with these
outputs, data-uri or no data-uri.

So it comes back to the fact that the -D option is no good for PDF
outputs, this is a design limitation not a bug (if I had documented that
when it was implemented I could have saved us all some time :-)

I will document the limitation and get a2x to emit a warning, to put
generated PDFs in another location you will need to copy them after a2x
has executed.


Cheers, Stuart


> This is the same problem I noticed when generating the pdf straight from
> the asciidoc txt source.
> It's not a problem when generating HTML docs as I use the data-uri option.
> Thanks
> Andy
> 
> On Monday, January 14, 2013 10:11:52 PM UTC, Stuart Rackham wrote:
> 
> 
> 
>     On 15/01/13 07:56, Andrew Birchall wrote:
>     > It seems when using a2x you can't output to a separate destination
>     > directory from where the source file is located?
>     >
>     > E.g. using dblatex to create a PDF from docbook source file:
>     > python a2x.py -D mydocs/publish mydocs/my-document.xml
>     >
>     > I get a2x: ERROR: missing docbook file:
>     > /cygdrive/c/asciidoc-8.6.8/mydocs/publish/my-document.xml
>     >
>     > So it seems I have to have the source file in the same location as
>     the
>     > destination-dir. Which seems to defeat the whole point of the -D
>     > (--destination-dir) option?
> 
>     XML source behaves differently to AsciiDoc source because when a
>     DocBook
>     XML source file is specified as the input a2x simply skips XML file
>     generation and assumes the XML file already exists in the destination
>     directory (AsciiDoc source generates XML to the destination directory).
> 
>     I've fixed this anomaly:
>     
> https://code.google.com/p/asciidoc/source/detail?r=531e926fd958b45ad99a5a64990df16e8bec37f3
>     
> <https://code.google.com/p/asciidoc/source/detail?r=531e926fd958b45ad99a5a64990df16e8bec37f3>
> 
> 
> 
>     Cheers, Stuart
> 
> 
>     >
>     > I really want to publish the completed output documents to a separate
>     > directory to where I keep the source files (.txt, .xml, etc.)
>     >
>     > Many thanks for any help.
>     >
>     > --
>     > You received this message because you are subscribed to the Google
>     > Groups "asciidoc" group.
>     > To view this discussion on the web visit
>     > https://groups.google.com/d/msg/asciidoc/-/nYAuionP3E0J
>     <https://groups.google.com/d/msg/asciidoc/-/nYAuionP3E0J>.
>     > To post to this group, send email to [email protected]
>     <javascript:>.
>     > To unsubscribe from this group, send email to
>     > [email protected] <javascript:>.
>     > For more options, visit this group at
>     > http://groups.google.com/group/asciidoc?hl=en
>     <http://groups.google.com/group/asciidoc?hl=en>.
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "asciidoc" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/asciidoc/-/G2KBikBmqL4J.
> 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.

Reply via email to