On Wed, 24 Dec 2014 12:43:05 +0100, Lex Trotman <[email protected]> wrote:
On 24 December 2014 at 20:30, jvdh <[email protected]> wrote:
On Tuesday, 23 December 2014 23:20:15 UTC+1, Lex Trotman wrote:
On 23 December 2014 at 22:02, Marco Ciampa <[email protected]> wrote:
> Hi all,
> I'm an old newbie, not really a programmer nor Linux expert that
tries
> to
> be useful translating free software and free software manuals in my
> mother tongue (Italian).
>
> To this aim I have started the experiment to port all KiCad
> documentation,
> odt based, into a light markup to easy the translation effort through
> the
> use of po files.
> This is the result of this effort:
>
> https://github.com/ciampix/kicad-doc
>
> Now to the point. I would like to make asciidoc or asciidoctor to
> produce good pdf / epub results. I do not know, even superficially,
> docbook and xslt but I know that to this aim I have to start coding
> with this format and associated tools.
Sadly yes if you are using the FOP toolchain.
>
> Is there a way to do it easily? I mean I am not even able to produce
a
> decent pdf cover without page number and possibly with the KiCad
logo on
> top of it!
if you use the dblatex backend instead of FOP (and I would think this
to be
the right way since it produces better pdf in my view), than you could
avoid
messing with xsl (mostly). simple things like whether to emit title
pages
and frontmatter etc. _can_ be switched on and of in the shipped
asciidoc/dblatex xsl stylesheet and more complicated things could be
adjusted in replacying the LateX styles used by dblatex (which means
struggling with TeX instead of xml/xsl...). it also is possible to
output
the `.tex' file generated by dblatex and to try and handpolish this
later on
(of course this is not desirable compared to doing it in the stylefiles
itself, but ....). the stylefiles in question are somewhere in the
dblatex
tree and have names following this scheme: `dbk_something.sty' plus a
file
`docbook.sty'. I got away for my purposes with minor tweaks to
`dbk_headfoot', `dbk_locale', `dbk_revision', and `docbook'.
Heh, since the original post talked warily about XML/XSL I didn't
*dare* introduce the possibility of having to play with Latex as well
:)
well, I do know xml/xsl as badly as latex internals and thus find the one
as "unfathomable" as the other. but one must try...
not sure which one is the worse recommendation ;-)
regarding the title page, lex is probably right to propose to do that
separately and glue it together (e.g. with `pdftk').
You could try producing the cover page in something like Libreoffice,
printing it to pdf and then I believe there are tools that can glue
there is a command line tool to due this:
http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/
Yes thats one, although the OP did seem to indicate Linux not windows,
thats why I pointed to the tool list
there is a command line tool for it (called "pdftk server" by the guy who
wrote it on the webpage) which
is available under MacOSX and Ubuntu at least. quite useful.
Cheers
Lex
PDFs together (maybe even directly in libreoffice, see
http://en.wikipedia.org/wiki/List_of_PDF_software) so you can glue it
to the start of the PDF of the book contents you made conveniently
with a2x.
>
> With rest + Sphinx I am able to produce an almost perfect pdf, epub
and
> html. I would like to do it with Asciidoc too, because I personally
like
> much more asciidoc syntax than rest, this without having to study too
> much docbook and xslt transformations.
>
> Is it feasible? Is it better to buy a good docbook + xslt manual and
> start studing seriously?
See http://sagehill.net/docbookxsl/CustomizingPart.html (referenced by
Asciidoc FAQ #3), it covers book covers :)
Cheers
Lex
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
> +--------------------+
> | Linux User #78271 |
> | FSFE fellow #364 |
> +--------------------+
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
--
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.
For more options, visit https://groups.google.com/d/optout.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
--
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.
For more options, visit https://groups.google.com/d/optout.
