Re: Does AsciiDoc have support for scientific papers?
On Fri, Jul 24, 2020 at 11:16:04AM -0700, mcp wrote: > I'm looking into using something other than LaTex directly for writing > scientific papers. I'm considering org-mode and using their export to latex > to pdf feature. Does AsciiDoc have anything to compare? > > > MCP https://asciidoc.org/latex-filter.html -- Saluton, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20201007083856.GA32001%40marco-N24-25JU.
sanity checks for both asciidoc & asciidoctor
Sanity checks = Hello devs, before posting a double feature request I would like to hear some comments on the subject. Discussing about the (apparent) small different behaviour of asciidoc and asciidoctor for an asciidoc source processor (po4a) for translation support (for instance balanced / unbalanced block fences ... BTW why not force a balancing and maintain the old slack behaviour with a --compat or the like option?) we all agreed that sanity checks on asciidoc content should be done by the asciidoc compiler (either asciidoc or asciidoctor). Why not implement such a subcommand with the same option for both compilers? Something like: asciidoc(tor) --sanity-check that would check these: - report missing third party files or includes - detect that the file is finished while still in a fenced block - detect internal links to non-existent anchors - detect inline formatting not closed at the end of a paragraph and more if you find some other things to do... feedback please! -- Saluton, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20201007061308.GA19815%40marco-N24-25JU.
Re: asciidoc 9.0.0 General Release
On Tue, Jun 02, 2020 at 04:09:47PM +1000, Lex Trotman wrote: > On Tue, 2 Jun 2020 at 15:26, Matthew Peveler wrote: > > > > We are happy to announce the general release of asciidoc 9.0.0. This > > release completes the porting of the original asciidoc.py from Python2 to > > Python 3, as well as a handful of new features and bug fixes. Highlights > > for the release are that asciidoc now runs on python 3.5+, adds support for > > docbook5, and uses lru_cache for macros.match method giving a 10-15% > > speed-up on documents with large numbers of repeated macros. Thanks to all > > the contributors who have made this long overdue release a reality. Beyond > > that, using asciidoc 9.0.0 should be similar to previous releases in terms > > of toolchains. > > > > Great, well done! > > Cheers > Lex Wonderful! Congrats! -- Saluton, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20200602173710.GA20284%40marco-N24-25JU.
Re: Conversion from LibreOffice to ASCIIDOC
On Wed, Apr 15, 2020 at 12:27:12PM +, leslie.satenst...@gmail.com wrote: > Hi Marco > Thank you for some history and your challenges with the conversion of > word to asciidoc. [..] > Again, I very much appreciate your converter and if you wish, will > provide feedback about my success. Hope you don't mind if I bounce the thread again into the asciidoc mailing list... The thing is: using _any_ lightweight markup language is preferable against an apparently simpler and more ubiquitous ODT format for many reasons: - is revision control aware - is easily translatable via po4a (https://github.com/mquinson/po4a) - different translations are manageable all at the same time - there is a separation between format and content that easy the translation efforts - the tasks of authors and translators are separate and independent - the production of different kind of documents are automatic - you can check the document validity before commits See here: https://gitlab.com/kicad/services/kicad-doc Feel free to ask any question... -- Saluton, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20200416081437.GA32739%40marco-N24-25JU.
Re: Conversion from LibreOffice to ASCIIDOC
On Tue, Apr 14, 2020 at 06:47:10PM -0700, Gmail Backup wrote: > The option in Word is no called something like "Save as Filtered HTML”. > It still has a bunch of Word-isms but is much better. It’s mostly correct > HTML, but uses many deprecated features. > > Worst part of the conversions I did were bulleted lists. The documents > I needed to convert had 6 level deep lists where the nesting was > semantically important. It also had lists that skipped levels and other > unnatural things. I was converting to HTML so didn’t need the pandoc > stuff so your mileage will vary. I successfully converted the KiCad manuals into Asciidoc format using a more convoluted but more precise method: I converted the odt into rest with a friend of mine python script: https://pypi.org/project/metapensiero.odt2sphinx/ and then using pandoc for the rest to asciidoc conversion... Good luck! -- Saluton, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20200415072852.GA3458%40marco-N24-25JU.
Re: how is the asciidoc migration to Python 3?
On Thu, Nov 28, 2019 at 04:55:03PM -0800, Matthew Peveler wrote: > As Lex and others stated, asciidoc-py3 is available in Debian, Gentoo, and > Fedora. I've also cut the 9.0.0rc1 release today with the hope that we'll > get a 9.0.0 final in the near future after I finish up updating/fixing some > remaining build tasks (like for the website). It is not yet available on > PyPI as there's some architecture stuff I'd like to improve first (like > getting rid of asciidoc's reliance on globals to maintain state). Good, I'm looking forward for it! > asciidoc3 is an unaffiliated fork of asciidoc. I've heard about this. Question to you and to others (and to the fork's author): are there technical reasons behind this fork or are these just "social" reasons? The reason of this question is that every time I see a fork I see a (potential) lot of resource wasting going on... -- Saluton, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20191129065830.GA15253%40marco-N24-25JU.
Re: how is the asciidoc migration to Python 3?
On Tue, Nov 26, 2019 at 06:10:33AM -0800, Berthold Gehrke wrote: > Yep, > please take a look at > https://asciidoc3.org > 100% Python3 and 100% compatibleness. Available for GNU/Linux, Windows, > tarball, deb, rpm, PyPI ... > > Best regards from Munich, > Berthold Gehrke Wonderful! Is it already part of some distro, mainly Debian? -- Saluton, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20191126152651.GA25956%40marco-N24-25JU.
how is the asciidoc migration to Python 3?
Hi devs, since all main distros (see Debian) are phasing out python2, how is the status of the python3 migration of asciidoc? -- Best regards, Marco Ciampa -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20191126113301.GA19453%40marco-N24-25JU.
Re: Asciidoc specification
On Fri, Oct 25, 2019 at 03:03:28PM -0600, Dan Allen wrote: > I want to add one more thing, hopefully tempering the defensive tone I took > in my previous replies. [...] No problem, understandable. A big project is like a son... Thank you for your clarifying emails. I'm much relieved now. -- Best regards, Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20191025214204.GA11707%40marco-N24-25JU.
Re: Asciidoc specification
On Fri, Oct 25, 2019 at 09:00:53AM +1000, Lex Trotman wrote: > On Fri, 25 Oct 2019 at 03:13, Grant Edwards wrote: > > > > On Thursday, October 24, 2019 at 5:29:24 AM UTC-5, Jaime Tarrasa wrote: > >> > >> Almost a year ago, I asked about the Asciidoc Standard, because I'm > >>writing a parser in Pascal. Since then, little has been done. > > > > > > This list is more about the original Python implemenation (which is > > no longer actively developed). > > > > The asciidoctor implemenation (in Ruby) is actively developed, and > > they are working on creating an AsciiDoc markup language standard under > > the aegis of the Mozilla Foundation: > > Its the Eclipse foundation, but you need to sign a legal agreement to > contribute, goodbye all non-corporate contributors. Arghh! Right, please no! I really wonder why... why? > > > > https://asciidoctor.org/news/2019/01/07/asciidoc-spec-proposal/ > > > > The Asciidoctor discussion list is probably where you should be > > asking standards-related questions. Thanks... Best regards, Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20191025065224.GB25546%40marco-N24-25JU.
Re: Asciidoc specification
On Thu, Oct 24, 2019 at 02:15:32PM +0200, Domingo Gallardo wrote: > I remember to all of you interested in some feature that this is an > open source project. If you want something, please contribute. It's not that simple. You simply can't "fork" a standard. You have to organize a group, usually not too small, to create the draft standard specification. Then you organize a revison process of the draft, at the end of that the creation committee, together with the revision folks and all the public you can gather together you create a Release Candidate of the RFC. I do not see all this. I see, well, here nothing. Perhaps it is already happening somewherelse? If it is so, I would like to have a look to the draft. And probably I am not alone. -- Best regards, Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20191024154307.GA7582%40marco-N24-25JU.
Re: Asciidoc specification
On Thu, Oct 24, 2019 at 03:29:24AM -0700, Jaime Tarrasa wrote: > > Almost a year ago, I asked about the Asciidoc Standard > <https://groups.google.com/d/msg/asciidoc/wj9kjl8gwC4/Ol5HA2RyDgAJ>, > because I'm writing a parser in Pascal. Since then, little has been done. > > Look at markua format, It is a good markup language. It has a clear > specification <http://markua.com/>: Elements structure, what is valid, what > is optional, what is compulsory, what is free for implementor, and > precedence of rules. It removes any ambiguity and solves any doubt. > > I have already implemented the full markua specification parser that > translates into FB2 and html (except courses stuff) > > In fact, I asked about specification already in 2016 > <https://groups.google.com/d/msg/asciidoc/5tJHg6UQAT0/BMaIB5EAAQAJ>. That > is over three years ago. I'm afraid that it means that specification is not > an issue for asciidoc/asciidoctor maintainers. The message *is "Use my > implementation. I will post changes in the list as they come out. Move on > and don't nitpick"*. Writing Asciidoc specification should be in the top of > your TODO list related to asciidoc. > > I don't think it is such a daunting task. You don't have to submit it to > ISO, just a clear webpage like markua. You, programmers, probably have a > draft of what attributes use, etc. just ordering, cleaning it up a little > and uploading to a webpage. > I TOTALLY AGREE WITH YOU... -- Best regards, Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/20191024111729.GB29974%40marco-N24-25JU.
bug report and status of the project
Hi devs, I am here to bring up this topic because we (KiCad doc developers) are currently using asciidoc for our documentation. We eventually planned an asciidoctor migration mainly to get rid of these kind of quirks that we encounter from time to time (https://lists.launchpad.net/kicad-doc-devs/msg00155.html) due to the amount of docs and the many languages we handle. Now the questions: 1) If we post a bug report, how many chances there are that some near future version of asciidoc will address those issues? 2) the port of asciidoc from python 2 to 3 can be helpful for the fixing of bugs like this? 3) how is the port of asciidoc from python 2 to 3? Is there a deadline? 4) going around on github I bumped into this: https://github.com/dagwieers/asciidoc-odf it seems to be very useful in my opinion. How many chances are that this piece of text could be made working again? BTW: why http://asciidoc.org sports only the old 9 November 2013: AsciiDoc 8.6.9? -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Starting the AsciiDoc Specification Journey
Hi people! On Tue, Jan 08, 2019 at 05:04:35PM +1000, Lex Trotman wrote: > Hi Dan, > > Thanks for starting the process. > [...] > > To me the point of the standardisation process is to ensure that > markup in a document is interpreted in the same way in all > implementations, and the semantics of that markup are the same, not > its presentation. Thats the core of the "Asciidoc is a semantic > markup, not a presentational markup" statement. > > So it seems to me that we need to standardise the syntax of Asciidoc > markup and to some extent the semantics, but not the output, and that > unfortunately makes it difficult to generate automated tests, however > I'm happy to hear solutions. This is paramount for a number of reasons and I can add one: po4a supports asciidoc and a specification of the format (not of the output) is fundamental for the parsing and extracting of the .po strings process... TIA for this GREAT effort! -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoc tables (and blocks?)
On Tue, Jun 05, 2018 at 10:53:02AM +1000, Lex Trotman wrote:
> > "23. Tables
> >
> > The AsciiDoc table syntax looks and behaves like other delimited block
> > types and supports standard block configuration entries [...]"
>
> Yes, its probably a bit subtle, a "behaves like" b does not mean that
> a is a b, nor that it "behaves identically", in particular the
> delimiter is different by not being all the same character, but the
> minimum size of the whole delimiter sequence is still four "like" :)
> other delimiters.
Ok thank you all for the clarification needed & sorry for the annoyance
I guess that this regular expression used by po4a for identifying both
blocks and table is wrong:
} elsif ($line =~
m/^(\/{4,}|\+{4,}|-{4,}|\.{4,}|\*{4,}|_{4,}|={4,}|~{4,}|\|={4,})$/) {
So I guess that if I want to keep it all together (blocks and tables) I
need at least to modify last subexpression to make it catch the three
"|===" tables syntax too, like this ...
} elsif ($line =~
m/^(\/{4,}|\+{4,}|-{4,}|\.{4,}|\*{4,}|_{4,}|={4,}|~{4,}|\|={3,})$/) {
^
right?
TIA
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
GNU/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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at https://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Re: asciidoc tables (and blocks?)
On Tue, Jun 05, 2018 at 07:58:11AM +1000, Lex Trotman wrote: > On Tue, 5 Jun 2018 at 02:49, Marco Ciampa wrote: > > > > Hi all ... I'm bit confused here ... > > writing here because noone seems on line on irc... > > ... according to asciidoc blocks are (I am looking based > > the examples ... docs not so clear) |(pipe) (4 same chars) and in > > asciidoctor examples (like tables) there are only three... > > which is right? > > > > asking here because I have some sources with tables formed of just three > > chars that the po4a asciidoc parser is unable to parse since it expect 4 > > chars at least... asciidoc docs specifically talks about 4 or more chars > > for blocks ... here: > > http://www.methods.co.nz/asciidoc/userguide.html#X104 "Delimited blocks > > are blocks of text enveloped by leading and trailing delimiter lines > > (normally a series of four or more repeated characters)." why here there > > are just three? > > https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#tables > > > > > Asciidoc User Guide Section 16 where the quote above is from is > "Delimited Blocks". Tables are in section 23 so the statement in > section 16 does not apply to tables and also does not apply because > table delimiters do NOT have all the same character. > > As the Asciidoctor reference says table delimiters are | and at least > 3 = a total of at least 4 chars the same as the delimited block > delimiters. I am sorry, my understanding of English could be fallable (very probably) but I read this: http://www.methods.co.nz/asciidoc/userguide.html#_tables "23. Tables The AsciiDoc table syntax looks and behaves like other delimited block types and supports standard block configuration entries [...]" so I read the "Delimiter block" specification... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
asciidoc tables (and blocks?)
Hi all ... I'm bit confused here ... writing here because noone seems on line on irc... ... according to asciidoc blocks are (I am looking based the examples ... docs not so clear) |(pipe) (4 same chars) and in asciidoctor examples (like tables) there are only three... which is right? asking here because I have some sources with tables formed of just three chars that the po4a asciidoc parser is unable to parse since it expect 4 chars at least... asciidoc docs specifically talks about 4 or more chars for blocks ... here: http://www.methods.co.nz/asciidoc/userguide.html#X104 "Delimited blocks are blocks of text enveloped by leading and trailing delimiter lines (normally a series of four or more repeated characters)." why here there are just three? https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#tables TIA -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: AsciiDoc3 Python3 Port released asciidoc3.org
On Wed, Apr 18, 2018 at 12:28:14PM +0100, Derek Jones wrote: > Dan, > > How many other people have jumped to the same conclusion that > I did? > > Why not point the news page at the Github release blog? > Hi devs, sorry for the intrusion... Why not DIY? https://github.com/asciidoctor/asciidoctor.org just update the relevant sections and ask for a pull... Best regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: partially enumerated headers
On Thu, Jun 23, 2016 at 07:17:42PM +1000, Lex Trotman wrote: > > ... another reason to choose asciidoctor over asciidoc ... > > My recommendations are: > > 1. new projects should always use asciidoctor, [...] I am waiting for being able to create pdf and epub out of asciidoc docs as we do here: https://github.com/kicad/kicad-doc http://kicad-pcb.org/help/documentation/ with asciidoc (python) and eager to use the kbd: macro also :-) -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: partially enumerated headers
On Wed, Jun 22, 2016 at 11:21:13PM -0600, Dan Allen wrote: > On Sat, Jun 11, 2016 at 4:20 AM, 'Marco Ciampa' via asciidoc < > asciidoc@googlegroups.com> wrote: > > > > > Googling "secnums asciidoctor" doesn nothing. Where can I find docs about? > > > > You are missing the "t" in sectnums. See > http://asciidoctor.org/docs/user-manual/#numbering > > > > > but I wonder if introducing a new parameter with the very same function > > of an existent one was a good idea at all and the reason for it was done... > > > > I stand by my decision. The name "numbered" is ambiguous (not clear what is > being numbered) and not consistent with other section-related attributes > (e.g., sectids) Ok I was not questioning your decision; I was just wondering the reason behind it. Sorry, sometimes I write a though to clear my ideas. Now it is clear why and I agree. > > > > I think that could be useful though if it was possibile to add a command > > in the headers like this: > > > > "from this X level down not/yes enumerated" > > > > something like > > > > :numbered level: 3 > > > > or > > > > :secnums level: 3 > > > > This is already supported in Asciidoctor. The attribute is named > sectnumlevels. See http://asciidoctor.org/docs/user-manual/#numbering-depth > > The way it is implemented is "number sections up to this level". > Oh I am very sorry, I should read the docs more carefully. Glad to hear this; I imagine that this is one of those very useful asciidoctor-only parameterer ... another reason to choose asciidoctor over asciidoc ... Thanks again, Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: partially enumerated headers
What do you think about this? Is it a good or a bad idea? -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: partially enumerated headers
On Fri, Jun 10, 2016 at 05:32:47PM -0600, Dan Allen wrote: > You need to toggle the numbered attribute midstream in the document. > > :numbered: > > :numbered!: > > and so forth. Ok thanks. > If you're using Asciidoctor, we recommend using the attribute sectnums > instead of numbered. Googling "secnums asciidoctor" doesn nothing. Where can I find docs about? Searching randomly I find a reference to it here: http://asciidoctor.org/docs/asciidoc-recommended-practices/ but I wonder if introducing a new parameter with the very same function of an existent one was a good idea at all and the reason for it was done... I think that could be useful though if it was possibile to add a command in the headers like this: "from this X level down not/yes enumerated" something like :numbered level: 3 or :secnums level: 3 that would be much more a neat solution and would spare mixing code with the text content throughout the document (separating content from code is always considered a good practice!). Thanks for the time you invest in answering sometimes trivial thinks like this... Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
partially enumerated headers
Is it possible to have an enumeration of headers starting from a specific level and how? Example: = Title ... == Chapter not enumerated ... === Enumerated subchapter ... Enumerated subsubchapter ... Results: Title ... Chapter not enumerated ... 1. Enumerated subchapter ... 1.1. Enumerated subsubchapter ... ... TIA Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: howto debug a doc (asciidoctor-pdf)
On Thu, May 26, 2016 at 12:58:07PM -0600, Dan Allen wrote: > This problem is already reported here: > > https://github.com/asciidoctor/asciidoctor-pdf/issues/447 > > Please add any additional examples to that issue. > > This is a low-level error in either Prawn or Asciidoctor PDF. I don't think > you should have to change your AsciiDoc to fix it. The content should flow > within the space it has available or be truncated if that's not possible. > Deleting and commenting out pieces of text I figured out that the problem seems to be the table "Right toolbar icons" in https://github.com/KiCad/kicad-doc/blob/master/src/eeschema/eeschema_generic_commands.adoc and seems another kind of problem (multi vertical cell). bye -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: howto debug a doc (asciidoctor-pdf)
On Thu, May 26, 2016 at 09:15:24PM +1000, Lex Trotman wrote: [...] > > from > > /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:111:in > > `table' > > Have you got a table that won't fit on the page (from above)? It > would probably be good to provide a gist or something with the > document in it to help debug. The document is here: https://github.com/KiCad/kicad-doc/tree/master/src/gerbview from here https://github.com/KiCad/kicad-doc BTW some docs works flawlessly, some not. Specifically do not work eechema and newpcb manuals (big docs). But what I meant was: how to get an error message that points directly in the part of the doc that generate the problem? That would be useful for doc writers and for asciidoc dev debug... TIA, regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
howto debug a doc (asciidoctor-pdf)
ms/prawn-table-0.2.2/lib/prawn/table/cell.rb:325:in `height' from /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:373:in `block in row_heights' from /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:369:in `each' from /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:369:in `row_heights' from /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:656:in `set_row_heights' from /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:148:in `initialize' from /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:111:in `new' from /home/marco/.rvm/gems/ruby-2.3.0/gems/prawn-table-0.2.2/lib/prawn/table.rb:111:in `table' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:1270:in `convert_table' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:96:in `convert' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:71:in `convert' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:80:in `block in content' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:80:in `map' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:80:in `content' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:112:in `convert_content_for_block' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:323:in `convert_section' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:96:in `convert' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:71:in `convert' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:80:in `block in content' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:80:in `map' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/abstract_block.rb:80:in `content' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/document.rb:1104:in `content' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:112:in `convert_content_for_block' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:163:in `convert_document' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/lib/asciidoctor-pdf/converter.rb:96:in `convert' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/document.rb:1044:in `convert' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor.rb:1503:in `convert' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/invoker.rb:94:in `block in invoke!' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/invoker.rb:86:in `each' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/invoker.rb:86:in `invoke!' from /home/marco/.rvm/gems/ruby-2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.11/bin/asciidoctor-pdf:31:in `' from /home/marco/.rvm/gems/ruby-2.3.0/bin/asciidoctor-pdf:23:in `load' from /home/marco/.rvm/gems/ruby-2.3.0/bin/asciidoctor-pdf:23:in `' from /home/marco/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `eval' from /home/marco/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `' I still do not see where exactly was the problem... asciidoctor works without any problem though... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Automatically adding the word "chapter"
On Tue, May 24, 2016 at 12:16:51PM +0200, 'Marco Ciampa' via asciidoc wrote: > On Tue, May 24, 2016 at 02:03:19AM -0700, Sabrina Maier wrote: > > Hi, > > > > I have this Problem too. Has somebody a solution? Where are the language > > xsl documents linked? > > > > To stop just the "Chapter" prepend, add in your document: > > // Disable chapter label > :chapter-label: > > or add to the a2x command line: > > -a chapter-label="" > > bye > Sorry, I was wrong. I mismatched asciidoc with asciidoctor ... My apologies, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Automatically adding the word "chapter"
On Tue, May 24, 2016 at 02:03:19AM -0700, Sabrina Maier wrote: > Hi, > > I have this Problem too. Has somebody a solution? Where are the language > xsl documents linked? > To stop just the "Chapter" prepend, add in your document: // Disable chapter label :chapter-label: or add to the a2x command line: -a chapter-label="" bye -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
FYI: asciidoctor-pdf works great with KiCad docs already...
Hope you appreciate the feedback. I am testing asciidoctor-pdf with the KiCad documentation (very large, multilanguage docs). Now it is based on: -> asciidoc (for HTML) + po4a (for i18n support) + docbook + (db)latex (for pdf & epub generation) So far I've tested and seem to work with all docs I throw at it :-) -> asciidoctor (for HTML) + po4a (for i18n support [*]) + asciidoctor-pdf (for pdf) + asciidoctor-epub3 (for epub [**]) much more clean and fast too! [*] in a makefile with a hack learned in this list: #I18n pdf $(DOCNAME)-%.pdf: $(DOCNAME)-%.adoc cat $(SCRIPTSBASEDIR)/attributes.adoc $(SCRIPTSBASEDIR)/cover-image.adoc $(DOCNAME)-$*.adoc | asciidoctor-pdf -a lang=$* $(ASCIIDOCTORVAR) - >$(DOCNAME)-$*.pdf [**] works only if refactoring the docs due to this bug: https://github.com/asciidoctor/asciidoctor-epub3/issues/47 due to this not tested completely though Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Introducing AsciiDocLIVE: free online AsciiDoc editor
On Tue, May 10, 2016 at 02:07:41PM -0700, Chuan Ji wrote: > Hi all, > > As a long time AsciiDoc fan, I've been building an online HTML5 AsciiDoc > editor: *AsciiDocLIVE (asciidoclive.com <https://asciidoclive.com>)*. Veeery very nice! Congrats! -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoctor i18n [was: asciidoc newbie questions in 2014...]
On Tue, May 10, 2016 at 03:32:41PM -0600, Dan Allen wrote: > Marco, > > I assume you are talking about Asciidoctor PDF. Correct. > It's true, Asciidoctor PDF > adds an additional (unofficial) attribute, chapter-label. We haven't been > including that in the translations yet. Ok but for asciidoc compatibility I would leave it blank > > You can remove the chapter label by simply setting the value to blank. > > :chapter-label: It worked thanks! Now I am able to obtain a perfectly comparable nationalized pdf file of the KiCad manuals using asciidoc-pdf instead of the asciidoc chain: asciidoc -> docbook -> latex -> pdf If you have nothing against it I would add a commented out Italian translation in the translation file... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoctor i18n [was: asciidoc newbie questions in 2014...]
> > On Sun, Apr 24, 2016 at 12:28:02AM -0600, Dan Allen wrote: > > Assigning these attributes manually is necessary until > > https://github.com/asciidoctor/asciidoctor/issues/1129 is resolved. That's > > where we stand right now. > > I am eager to contribute. > > Whenever you decide a standard way to set those strings, please let me > know. I'll be happy to contribute for the Italian translation. Using these strings I just noted that there is not a: chapter-caption so the header "Chapter n. ..." in the index is still untranslated... And since the string is undefined, I cannot even get rid of the "Chapter n." prepended text altogether leaving only the numeric number of the chapter. Hope you find this report useful, Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: include command-line
On Mon, May 09, 2016 at 04:10:37PM +, Grant Edwards wrote: > On 2016-05-09, 'Marco Ciampa' via asciidoc wrote: > > On Mon, May 09, 2016 at 02:03:06PM +, Grant Edwards wrote: > >> On 2016-05-09, 'Marco Ciampa' via asciidoc > >> wrote: > >> > On Mon, May 09, 2016 at 10:26:27AM +1000, Lex Trotman wrote: > >> >> Where would it be "included"? > >> > > >> > On the top, following the order of arguments like the include directive > >> > in the file. > >> > > >> > Like this: > >> > > >> > asciidoctor --include file1.adoc --include file2.adoc textfile.adoc > >> > >> One way this is done in bash is: > >> > >> $ asciidoctor <(cat file1.adoc file2.adoc textfile.adoc) > > > > Great idea, thanks! > > Perhaps my post wasn't clear. No, it was clear, it's my fault, I was in a hurry... > That doesn't work for either asciidoc > or asciidoctor because they both fail when the input file is a FIFO > (which is what happens when you used the <(cmd) syntax in bash. > > The other way to do it (which does work); > > $ cat file1.adoc file2.adoc textfile.adoc | asciidoctor - >output.html > > [I had assumed that if asciidoc(tor) couldn't handle a FIFO, it > couldn't handle a pipe either so I didn't even suggest it, but it > looks like it does work.] That is really interesting since I though that a FIFO was a PIPE (an anonymous PIPE) but evidently I was wrong (again)... Anyway that resolve my issue, thanks! -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: include command-line
On Mon, May 09, 2016 at 02:03:06PM +, Grant Edwards wrote: > On 2016-05-09, 'Marco Ciampa' via asciidoc wrote: > > On Mon, May 09, 2016 at 10:26:27AM +1000, Lex Trotman wrote: > >> Where would it be "included"? > > > > On the top, following the order of arguments like the include directive > > in the file. > > > > Like this: > > > > asciidoctor --include file1.adoc --include file2.adoc textfile.adoc > > One way this is done in bash is: > > $ asciidoctor <(cat file1.adoc file2.adoc textfile.adoc) Great idea, thanks! -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: include command-line
On Mon, May 09, 2016 at 10:26:27AM +1000, Lex Trotman wrote: > Where would it be "included"? On the top, following the order of arguments like the include directive in the file. Like this: asciidoctor --include file1.adoc --include file2.adoc textfile.adoc it could be useful for interpreting variables, macro substitution, etc so it is not a problem if it is before the headers (title, author, etc.) or it could contain the header data that could be common for a project. Definitely a preprocessor thing, just an include, happening before any other action, like the include:: directive I suppose. But from your answer/question I imagine that currently it is not possible. No problem, just asking because docs talk about the include directive and not that there is _not_ a command line include directive so I was asking in case I was missing it somehow. :-) TIA -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
include command-line
Is there a way to include a file via command line? In asciidoctor... TIA -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: how to put image in an asciidoctor generated pdf
On Wed, Apr 27, 2016 at 05:51:53PM -0600, Dan Allen wrote: > Marco, > > Actually, I'm glad your brought this up, because it gave me an idea. > > Currently, the order of items on the title page generated by Asciidoctor > PDF is fixed. However, what we could do is add a theme item that specifies > element order (by line). When combined with the margin_top / margin_bottom > and align properties, this would allow you to achieve a wide range of > layouts. > > I'll open an issue to explore that idea. > > I haven't found a way to describe advanced layouts yet. That's where > extending the converter in Ruby comes in. > > If you want a very sophisticated title page, what I recommend is using the > front-cover-image to insert a custom PDF page and set notitle attribute to > disable the auto-generated title page. I suspected that that was the way to do it. But I have to say that you (you and all the comunity behind asciidoctor) are doing really a great work. I know that you know it already but... saying it again do not harm... :-) Regards -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: how to put image in an asciidoctor generated pdf
Please forgive me, let die this thread. It is really _not_ important and those options are enough for me. Many thanks again, Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: how to put image in an asciidoctor generated pdf
Thanks, I'm impressed!
But...
I am totally fine with the cover page format that I obtain without using
the theme. Moreover if I add a yaml file for the theme, this changes a lot
(title centered instead of right, color black instead of gray, etc.)
I just would like to add an image under the title/author section, not a
logo above it. Is there an easy way to do it?
I have seen that someone did (from the link I posted):
> > plaindocs commented on 30 Mar 2015
> I added a second image below the title by duplicating the titlpage-logo loop
> in the ruby.
but I am not a ruby programmer and I do not want to mess with it either
(but I promise that I'll do some learning about ruby in the future...)
TIA
PS: I am well aware that this is not a fondamental topic...
On Wed, Apr 27, 2016 at 11:22:52AM -0600, Dan Allen wrote:
> Marco,
>
> Please see the theming guide {1}. Specifically, the section about the title
> page {2}.
>
> You can also set certain theme-related AsciiDoc attributes in the document
> itself. To add a cover page, use:
>
> :front-cover-image: image:cover-image.png[]
>
> or
>
> :front-cover-image: image:cover-page.pdf[]
>
> To add a background image on the title page, use:
>
> :title-page-background-image: image:title-page-bg.png[]
>
> I need to document these AsciiDoc attributes in the theming guide. They
> came about after I had setup that guide.
>
> Cheers,
>
> -Dan
>
> :1:
> https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc
> :2:
> https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc#title-page
>
> On Wed, Apr 27, 2016 at 12:11 AM, 'Marco Ciampa' via asciidoc <
> asciidoc@googlegroups.com> wrote:
>
> > Since I evidently miss some recent changes in asciidoctor development
> > (see the i18n thread) maybe I missed something in the asciidoctor-pdf
> > too. So here I am to ask: is there an _easy_ way to put an image on the
> > generated pdf cover page?
> >
> > I found this that answer partially at my question:
> >
> > https://github.com/asciidoctor/asciidoctor-pdf/issues/66
> >
> > but I haven't found doc about it and specifically how to put this image
> > under the title.
> >
> > TIA
> >
> > --
> >
> >
> > Marco Ciampa
> >
> > I know a joke about UDP, but you might not get it.
> >
> >
> >
> > GNU/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 asciidoc+unsubscr...@googlegroups.com.
> > To post to this group, send email to asciidoc@googlegroups.com.
> > Visit this group at https://groups.google.com/group/asciidoc.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
>
>
> --
> Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen
>
> --
> 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 group, send email to asciidoc@googlegroups.com.
> Visit this group at https://groups.google.com/group/asciidoc.
> For more options, visit https://groups.google.com/d/optout.
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
GNU/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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at https://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
how to put image in an asciidoctor generated pdf
Since I evidently miss some recent changes in asciidoctor development (see the i18n thread) maybe I missed something in the asciidoctor-pdf too. So here I am to ask: is there an _easy_ way to put an image on the generated pdf cover page? I found this that answer partially at my question: https://github.com/asciidoctor/asciidoctor-pdf/issues/66 but I haven't found doc about it and specifically how to put this image under the title. TIA -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoctor i18n [was: asciidoc newbie questions in 2014...]
On Sun, Apr 24, 2016 at 10:05:42PM +0200, 'Marco Ciampa' via asciidoc wrote: > On Sun, Apr 24, 2016 at 12:14:54PM +0200, 'Marco Ciampa' via asciidoc wrote: > > On Sun, Apr 24, 2016 at 12:28:02AM -0600, Dan Allen wrote: > > > On Sun, Apr 24, 2016 at 12:12 AM, Lex Trotman wrote: > > > > > > > Can't those be set in the document? After all it isn't going to > > > > change languages by itself :) > > > > > > > > > > Absolutely. That's explained in > > > http://asciidoctor.org/docs/user-manual/#customizing-built-in-labels. I > > > just didn't go into detail here. > > > > > > > Terrific, thanks! > > > > One more question. > > Say I would like to contribute to translate the labels in Italian. Are > there some default values for each language or have I to translate all > labels? As a /etc/asciidoc/lang-NN.conf for instance... > Sorry I did not read carefully this: > Assigning these attributes manually is necessary until > https://github.com/asciidoctor/asciidoctor/issues/1129 is resolved. That's > where we stand right now. I am eager to contribute. Whenever you decide a standard way to set those strings, please let me know. I'll be happy to contribute for the Italian translation. -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoctor i18n [was: asciidoc newbie questions in 2014...]
On Sun, Apr 24, 2016 at 12:14:54PM +0200, 'Marco Ciampa' via asciidoc wrote: > On Sun, Apr 24, 2016 at 12:28:02AM -0600, Dan Allen wrote: > > On Sun, Apr 24, 2016 at 12:12 AM, Lex Trotman wrote: > > > > > Can't those be set in the document? After all it isn't going to > > > change languages by itself :) > > > > > > > Absolutely. That's explained in > > http://asciidoctor.org/docs/user-manual/#customizing-built-in-labels. I > > just didn't go into detail here. > > > > Terrific, thanks! > One more question. Say I would like to contribute to translate the labels in Italian. Are there some default values for each language or have I to translate all labels? As a /etc/asciidoc/lang-NN.conf for instance... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoctor i18n [was: asciidoc newbie questions in 2014...]
On Sun, Apr 24, 2016 at 12:28:02AM -0600, Dan Allen wrote: > On Sun, Apr 24, 2016 at 12:12 AM, Lex Trotman wrote: > > > Can't those be set in the document? After all it isn't going to > > change languages by itself :) > > > > Absolutely. That's explained in > http://asciidoctor.org/docs/user-manual/#customizing-built-in-labels. I > just didn't go into detail here. > Terrific, thanks! -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoctor i18n [was: asciidoc newbie questions in 2014...]
On Fri, Apr 22, 2016 at 07:25:43PM -0600, Dan Allen wrote: > On Fri, Apr 22, 2016 at 2:30 AM, 'Marco Ciampa' via asciidoc < > asciidoc@googlegroups.com> wrote: > > > For an example I could have used asciidoctor instead of asciidoc more than > > a year ago with the i18n in place. > > > > And I am sorry for this. > > > > Can you describe what you think is currently missing in Asciidoctor when > compared to AsciiDoc Py? Asciidoctor supports exactly the same i18n > attributes. I want to make sure I'm not missing something. > > See http://asciidoctor.org/docs/user-manual/#builtin-attributes > > -Dan > Sorry probably I was not clear enough before (years ago!) and a simple answer was just around the corner. How can I do in asciidoctor: -a lang=it for example? -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoctor i18n [was: asciidoc newbie questions in 2014...]
On Fri, Apr 22, 2016 at 05:48:37PM +1000, Lex Trotman wrote: > From my (limited) perspective, the most important thing is to support > i18n of generated text, since it is a blocker for making documents in > other languages if humans translate content and the generated text > still comes out in English. That should be the first target of any > resources that make themselves available. > > Once that block is removed everything else is just an improvement :) I TOTALLY agree here. Tools to handle translation strings are already in place: po4a support asciidoc nicely. I always look with suspect at "big project" because although the due big efforts, they sometimes miss the point and in a "big" way. The step-by-step approach have many advantages: 1) gives user very quickly an improvement that is usable _now_ and every one is happy 2) you have faster feedback for the direction to choose 3) the smaller the step the little the probability to take a wrong direction 4) the smaller the step the less effort you have to change direction if you find yourself in a cul-de-sac. For an example I could have used asciidoctor instead of asciidoc more than a year ago with the i18n in place. And I am sorry for this. -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
asciidoctor i18n [was: asciidoc newbie questions in 2014...]
On Fri, Dec 26, 2014 at 08:05:30PM -0700, Dan Allen wrote: > On Fri, Dec 26, 2014 at 10:16 AM, Marco Ciampa wrote: > > If asciidoctor will incorporate > > support for .po file to gurantee easy i18n features that will definitely > > put it ahead of the pack. > > That's on the roadmap. I'm fairly certain it will happen (in some capacity) > in 2015. Ok now we are well inside 2015 :-) How is going the i18n effort? May I contribute / test / see the efforts? I think that this is very important for the whole asciidoc(tor) project. I am currently using po4a + asciidoc since asciidoctor do not pass the i18n info to docbook and asciidoctor-pdf do not handle it at all... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Using asciidoctor to create a website/blog
On Tue, Mar 29, 2016 at 07:58:28AM -0700, Fernando Basso wrote: > I am pondering the use of Asciidoctor to create a website for myself, where > I write about programming and other things that interest me. Can > Asciidoctor be used for something like that? How easy/hard it would be to > add a custom column to the pages, header (navigation), footer, etc? I know > my question is probably to broad, but any insight is appreciated. > > I took a look at the source for asciidoctor.org but could not understand > much so far. For instance, how is the right column on the main page > inserted? > > Thanks in advance for any help. > The KiCad site is done using asciidoc(tor) + hugo. https://github.com/KiCad/kicad-website bye -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: AsciiDoc vs AsciiDoctor
On Sun, Oct 18, 2015 at 07:35:01AM -0700, Thomas Beale wrote: > > 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 Pygments to Ruby). > > I had never seen a line of Ruby before this, nor any clue about running the > Ruby CLI. But it wasn't hard. I did all this under cygwin on Windows, which > is probably the least preferable, and a bit annoying to set up. But now it > works just like any Linux or MacOSX environment. > > Just go with the flow - I have interacted withe Asciidoctor development > team, and they are excellent. The language of implementation is the last > concern on my mind. > > W.r.t. Asciidoc and Asciidoctor, I strongly suggest you want to be on the > Asciidoctor path, if you are serious about publishing. See my blog post on > this > <http://wolandscat.net/2015/09/11/goodbye-to-adobe-framemaker-hello-asciidoctor/> Very interesting piece of article, thanks! To the list: is there a "Who use asciidoc(tor)" page somewhere? Since I discover new users everyday... -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: How to prevent line-wrapping in listing block?
On Fri, Aug 28, 2015 at 04:02:36PM +, Grant Edwards wrote: > On 2015-08-28, 'Marco Ciampa' via asciidoc wrote: > > On Fri, Aug 28, 2015 at 02:47:06PM +, Grant Edwards wrote: > >> On 2015-08-28, Grant Edwards wrote: > >>> How do you prevent asciidoc from wrapping source listings like this > >>> > > > > long_line_of_code + here - that_I_definitely_do_not_want - to() * be() * > > wrapped() > > ^here insert a space... > > > > like this: > > > > long_line_of_code + here - that_I_definitely_do_not_want - to() * be() * > > wrapped() > > That doesn't help. The line still gets wrapped (either inside a > listing block or standing alone). Is the "leading space disables > line wrapping" feature something new? I'm using asciidoc 8.6.9. So your asciidoc(tor) is broken or there is something else you do not say... See: http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#source-code Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: How to prevent line-wrapping in listing block?
On Fri, Aug 28, 2015 at 02:47:06PM +, Grant Edwards wrote: > On 2015-08-28, Grant Edwards wrote: > > How do you prevent asciidoc from wrapping source listings like this > > long_line_of_code + here - that_I_definitely_do_not_want - to() * be() * wrapped() ^here insert a space... like this: long_line_of_code + here - that_I_definitely_do_not_want - to() * be() * wrapped() bye -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
this trivial patch is waiting for what?
One of my friend asked me about this patch: https://github.com/asciidoc/asciidoc/pull/65 if only I knew the reason it is waiting ... Is there something I can do about it? Do you need something I do not know? Please ask! Regard, -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Creating asciidoc.txt from .chm help file ?
On Sat, Jun 13, 2015 at 05:27:05AM -0700, Jacques Nilo wrote: > Hello all > I am new to this forum and considering asciidoc to maintain a program > documentation. > I am wondering if it is possible to create an asciidoc.txt file from an > existing .chm windows help file. Any hint suggestions would be appreciated. > Best > Jacques You can also extract chm files to html using the command line tool 7-Zip install p7zip-full: 7z x file.chm once in html there are various ways to convert html to asciidoc, for example pandoc... -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Nested includes and title levels
On Mon, May 25, 2015 at 06:32:04PM -0700, Jeremiah Leary wrote:
> Well, that worked on the way down the hierarchy, but coming up had some
> issues. So the complete solution looks like this:
>
> :leveloffset: {counter:leveloffset}
>
> include::
>
> :leveloffset: {eval:{leveloffset} - 1}
>
> Now any of my files can be rendered at any level of document hierarchy.
>
> Regards,
>
> --Jeremy
>
Very interesting, thanks for sharing this!
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| GNU/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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Re: Asciidoc n00b trying to implement a new filter.
On Mon, Mar 23, 2015 at 07:18:45PM +1100, Lex Trotman wrote: > On 23 March 2015 at 18:45, Marco Ciampa wrote: > > On Mon, Mar 23, 2015 at 10:00:21AM +1100, Lex Trotman wrote: > >> Hi Ken, > >> > >> On [[is,xreflabel]] the manual says " The optional is only > >> really useful when generating DocBook output.". > >> > >> That is because the docbook toolchains copy the xreflabel to the > >> reference from the anchor. > >> > >> Since the HTMLs are generated directly by Asciidoc there is no > >> toolchain to do that. Asciidoc itself can't because it is a streaming > >> processor that does not load the whole document in one go. > > > > THAT is a big limit! > > Hi Marco, > > Its such a big limit that nobody has submitted a change to remove it to date > :) > > Seriously though it would be a complete re-write like asciidoctor. > > And the docbook xslt toolchain produces html without javascript. I missed this! I was always asking myself the reason why to have 2 different methods to produce HTML, that is a _good_ reason! Using HTML as an output doc format means that something there is the need to show doc text with a stripped down html viewer, without javascript and such... Thanks for the hint! -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Asciidoc n00b trying to implement a new filter.
On Mon, Mar 23, 2015 at 10:00:21AM +1100, Lex Trotman wrote: > Hi Ken, > > On [[is,xreflabel]] the manual says " The optional is only > really useful when generating DocBook output.". > > That is because the docbook toolchains copy the xreflabel to the > reference from the anchor. > > Since the HTMLs are generated directly by Asciidoc there is no > toolchain to do that. Asciidoc itself can't because it is a streaming > processor that does not load the whole document in one go. THAT is a big limit! Why not converting it in a 2 pass and do away with javascript? I am not [a real programmer|able to do] so keep it as a annoying little suggestion voice in the background... ;-) -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: New Release Policy
On Tue, Feb 24, 2015 at 04:19:24PM +0300, Ahmad Khayyat wrote: [...] I am writing this to say a big # ###### ## ### # # ## # # # # ### ## # # # ### ## # # # # # # ### ## # ## # # ## ### ## ## ## for your wonderful work on asciidoc. -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
On Tue, Feb 10, 2015 at 06:00:34AM -0800, Eduardo Santana wrote: > latexmath:[$\Omega$] This works! Thanks! -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoc pdf & epub cover pages and images Was: asciidoc newbie questions
On Tue, Feb 10, 2015 at 05:55:31AM -0800, Eduardo Santana wrote:
> Also try with {title} attribute:
>
>
>
>
>
>
>
> *{title}*
>
>
Thanks for your suggestion but it does not seems xml valid to me and
xmllint seems to confirm it...
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| GNU/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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
On Wed, Feb 04, 2015 at 01:32:15PM +1100, Lex Trotman wrote: > [...] > >> Are you saying that running this command on the command line works, > >> but it fails when a2x runs it? > > > > No. I am saying that that workaround is just that: a workaround that > > works so badly that seems that asciidoc works better without. So when I > > was converting into docbook and then converting docbook into pdf I was > > inadvertently avoiding that workaround. Avoiding that workaround made my > > compilaton work. > > Ok, well, all I can say is that it works for me, no alltt error, and I > am sure I didn't (knowingly) install extra latex packages because I > don't know how to. Perhaps I'm just lucky and something else > installed it for me. :) Ok that clarifies our misunderstanding because here that did not work and you were at the opposite situation. Now I am curious: what version of Linux are you using? Maybe it is just a bug of Ubuntu of course... I can try and compile it somewhere else starting from you configuration... -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
arco/Scrivania/Robotica/corso/programma/programma.xml
Build the listings...
xsltproc -o /tmp/tmpyoYMwM/listings.xml --xinclude --xincludestyle
--param current.dir '/home/marco/Scrivania/Robotica/corso/programma'
/usr/share/dblatex/xsl/common/mklistings.xsl
/home/marco/Scrivania/Robotica/corso/programma/programma.xml
xsltproc -o programma.rtex --xinclude --xincludestyle --param current.dir
'/home/marco/Scrivania/Robotica/corso/programma' --param listings.xml
'/tmp/tmpyoYMwM/listings.xml' /tmp/tmpyoYMwM/custom.xsl
/home/marco/Scrivania/Robotica/corso/programma/programma.xml
XSLT stylesheets DocBook - LaTeX 2e (0.3.4-3)
===
Build programma.pdf
built-in module pdftex registered
no support found for ifthen
no support found for ifxetex
no support found for fontspec
no support found for xltxtra
no support found for fontenc
no support found for inputenc
no support found for fancybox
built-in module makeidx registered
no support found for babel
no support found for cmap
no support found for pdf-cover-dblatex
building additional files...
checking if compiling is necessary...
the output file doesn't exist
pdflatex -interaction=batchmode programma.tex
pdflatex failed
programma.tex:93: Environment alltt undefined.
programma.tex:93: leading text: \begin{alltt}
programma.tex:96: \begin{quote} on input line 92 ended by \end{alltt}.
programma.tex:96: leading text: \end{alltt}
programma.aux:402: Missing \endcsname inserted.
programma.aux:402: leading text: ...7.3.2}{36}{Velocit�}{subsection.7.3.2}{}}
Unexpected error occured
Error: pdflatex compilation failed
a2x: ERROR: "dblatex" -t pdf -p
"/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s
"/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -P latex.output.revhistory=0
-P doc.publisher.show=0 -P doc.collab.show=0 -s pdf-cover-dblatex.sty -V
"/home/marco/Scrivania/Robotica/corso/programma/programma.xml" returned
non-zero exit status 1
>
> If you don't need 1) and 2) then just run dblatex as you are doing,
> using a2x is only a convenience if you want the Asciidoc defaults (as
> shown in the huge command above).
ok
> Cheers
> Lex
Many many thanks for your patience...
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| GNU/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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
On Wed, Feb 04, 2015 at 09:48:48AM +1100, Lex Trotman wrote:
> Are you sure you used the same options shown in the dblatex command
> printed in the error message?
yes
> Including the -p
> "/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s
> "/etc/asciidoc/dblatex/asciidoc-dblatex.sty" options?
no since I was not aware of this inclusion. Thanks for clarifying me this.
> These options
> are to workaround literal layout issues with dblatex and to make the
> dblatex PDF style more Asciidoc-ish. This is where the {alltt}
> package is required that causes the error you see. It seems to not be
> defined when you use xetex instead of tex. Perhaps you can install it
> in some way.
If these options are included by default by a2x for generating the pdf
output then the problem is not in not including those two files but
viceversa is the automatic inclusion of those files that create the
problem (so it could be a bug...).
Since the problem arises when using a2x in one command not when
converting the generated docbook into pdf via dblatex...
Or I did not understand you point
[...]
> > Then why not setting xetex as default on a2x? Before you write to me, I
> > already know you answer: because it is not a a2x default but a backend
> > (dblatex) default, right? :-)
>
> Well, they are the experts in dblatex, why don't they think that using
> xetex by default is the right thing?
I really do not know. May be a legacy defaul option left for
compatibility reasons but now a little obsolete? UTF-8 seems to me more
than enough a reason to switch from pdflatex to xetex...
And reading around xetex have much more very nice features...
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| GNU/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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Re: can someone explain me this?
On Tue, Feb 03, 2015 at 09:06:42AM +1100, Lex Trotman wrote: > Hi Still works `a2x -k` on an exact copy of you initial post > > Valid: `/* ... */` > Not Valid: `/*` > Valid `*/` > > Valid: *`C/C++`* > Not Valid: *`C++`* or *C++* > > > gives docbook > > Valid: /* ... */ > Not Valid: /* > Valid */ > Valid: C/C++ > Not Valid: C++ > or C++ > > which looks right to me and the PDF dblatex makes looks to match. > Have you done some customising? Mmmm really weird. Those combinations in a doc works flawlessly, and do not work in another... same compilation options. I have to investigate more... Sorry for the noise. I will report when I know more about... -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
On Tue, Feb 03, 2015 at 11:21:23PM +1100, Lex Trotman wrote:
> On 3 February 2015 at 22:56, Marco Ciampa wrote:
> > On Tue, Jan 27, 2015 at 09:00:25AM +1000, Lex Trotman wrote:
> >> >
> >> > Any hint?
> >> >
> >>
> >> Perhaps you should ask on the relevant toolchain list, dblatex and FOP
> >> are both separate projects. Whilst people here will answer if they
> >> know, it is not specifically the purpose of this list to answer
> >> toolchain questions. That said, did you search the list archives, I
> >> can't really believe that there has been no previous answer on how to
> >> set fonts.
> >
> > Easy answer, no, but anyway you are right.
> >
> > I asked here because I imagine that, using a2x I am brought to think that
> > somehow this is a asciidoc toolchain problem, so intrinsecly an asciidoc
> > problem.
>
> Its a common misunderstanding, a2x is simply a script that runs the
> toolchains.
If it is so a common misunderstanding then someone should consider that
users have some points here. It is because, since a2x is distributed with
asciidoctor, its output is in a way considered a2x responsibility.
Demanding the onus to the user to study every aspect of the backend it is
a weakness. It is like saying that if XYX Linux distro do not work,
distro devs are not to blame for not choosing the right version of the
lib but just the library devs since the library that is distributed with
is broken.
Sorry for my bad english, I hope I have explained my point clear enough.
> > In this respect I thought to report here an easy fix that I have found.
>
> Thank you.
>
> > Instead to use a2x directly, using a2x to produce docbook and then
> > specify this option to dblatex:
> >
> > so instead to use
> >
> > a2x test.adoc
> >
> > simply using
> >
> > a2x -f docbook test.adoc
> > dblatex -b xetex test.xml
>
> I think you can do it from a2x with:
>
> a2x --dblatex-opts="-b xetex" test.adoc
:-) why you assumed I did not try this?
I really do not know why, but this does _not_ work on my system
(Ubuntu Linux 14.04-64).
If I use a2x I always get an error. (this:
...
building additional files...
checking if compiling is necessary...
the output file doesn't exist
xelatex -interaction=batchmode programma.tex
xelatex failed
programma.tex:93: Environment alltt undefined.
programma.tex:93: leading text: \begin{alltt}
programma.tex:96: \begin{quote} on input line 92 ended by \end{alltt}.
programma.tex:96: leading text: \end{alltt}
Unexpected error occured
Error: xelatex compilation failed
a2x: ERROR: "dblatex" -t pdf -p
"/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s
"/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -b xetex -P
latex.output.revhistory=0 -P doc.publisher.show=0 -P doc.collab.show=0 -s
pdf-cover-dblatex.sty -V
"/home/marco/Scrivania/Robotica/corso/programma/programma.xml" returned
non-zero exit status 1
)
Using the 2 phase command instead, same options, works flawlessly.
BTW I observed that using first a2x to transform asciidoc to docbook and
then pdflatex to transform docbook to pdf does not produce the same
output of using a2x all in one command, even with the same latex options.
Do not ask me why it is so. I haven't the slightest idea...
> and you can set a2x options inside the asciidoc source, see
> http://asciidoc.org/a2x.1.html which will bring you back to "a2x
> test.adoc" and you will never forget the dblatex option :)
ah veeery nice! I missed this completely!
But I find this is a good and a bad thing at the same time since I could
be using a different asciidoc processor in the future, as asciidoctor,
and it means mixing asciidoc content data with processore specific
options (like mixing code and data): not a good thing IMHO.
> > resolved all font problems. Even accented chars in section titles!
>
> Understandable, xetex is unicode compliant IIUC.
Then why not setting xetex as default on a2x? Before you write to me, I
already know you answer: because it is not a a2x default but a backend
(dblatex) default, right? :-)
> > Hope will help someone. I think this should be reported on asciicod FAQ
> > page.
>
> Happy to get a PR.
testing continue...
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| GNU/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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
On Tue, Jan 27, 2015 at 09:00:25AM +1000, Lex Trotman wrote: > > > > Any hint? > > > > Perhaps you should ask on the relevant toolchain list, dblatex and FOP > are both separate projects. Whilst people here will answer if they > know, it is not specifically the purpose of this list to answer > toolchain questions. That said, did you search the list archives, I > can't really believe that there has been no previous answer on how to > set fonts. Easy answer, no, but anyway you are right. I asked here because I imagine that, using a2x I am brought to think that somehow this is a asciidoc toolchain problem, so intrinsecly an asciidoc problem. In this respect I thought to report here an easy fix that I have found. Instead to use a2x directly, using a2x to produce docbook and then specify this option to dblatex: so instead to use a2x test.adoc simply using a2x -f docbook test.adoc dblatex -b xetex test.xml resolved all font problems. Even accented chars in section titles! Hope will help someone. I think this should be reported on asciicod FAQ page. -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: can someone explain me this?
On Mon, Feb 02, 2015 at 11:28:42PM +1100, Lex Trotman wrote: > Umm, they all work for me. Mhf I am very sorry. I meant to create pdf with classic a2x command... Try to create a pdf... -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
can someone explain me this?
Trying to writing a guide on Arduino I stumbled in these: Valid: `/* ... */` Not Valid: `/*` Valid `*/` Valid: *`C/C++`* Not Valid: *`C++`* or *C++* Any hint? -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
On Thu, Jan 22, 2015 at 09:23:56AM +1000, Lex Trotman wrote: > On 22 January 2015 at 08:55, Marco Ciampa wrote: > > On Tue, Jan 20, 2015 at 10:53:32PM +1000, Lex Trotman wrote: > >> On 20 January 2015 at 05:57, Marco Ciampa wrote: > >> > The uppercase omega letter (for resistor's Ohms) Ω does not render in pdf > >> > dblatex (missin char) > >> > >> This is probably best asked on dblatex list, although someone here may > >> know. > >> > >> > and it is either not good in fop's pdfs (subscript > >> > or differen size char). > >> > >> Are you sure you are using Ohm not Greek omega, there are separate > >> code points I think. > > > > Ohm _is_ Greek omega. And I doubt that I have Ohm and not Greek omega > > right with a simple key combination on my keyboard (specifically > > AltGr+Shift+Q) > > No, they are two different things, Greek capital Omega is U+03A9 and > Ohm Sign is U+2126. They might not display the same, but as we agree > below, thats a font thing :) > > > > >> Otherwise its a font thing. > > > > I think it is precisely a font thing. I an few words: how to (easily) > > change fonts with asciidoc dblatex front-end? > > You set the fonts in the dblatex or FOP toolchains. Asciidoc and the > docbook it produces are both content markup, not presentation markup, > and so don't contain font information. > > The dblatex docs have never been clear to me how to do it, best I can > find is http://dblatex.sourceforge.net/doc/manual/xetex.font.html or > its latex style I think. > > Cheers > Lex Many thanks for the clarification. Now I have to find out how to apply that configuration option to the asciidoc toolchain ... Any hint? -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
asciidoc pdf & epub cover pages and images Was: asciidoc newbie questions
I would like to add these in the docbook FAQ: John Beard kindly found a
solution for the cover page image that was easy enough for me.
For pdf:
a2x -f pdf --dblatex-opts "-P latex.output.revhistory=0 -P doc.publisher.show=0
-s pdf-cover-dblatex.sty" document.adoc
where the content of pdf-cover-dblatex.sty is:
\NeedsTeXFormat{LaTeX2e}
\ProvidesPackage{asciidoc-dblatex}[2012/10/24 AsciiDoc DocBook Style]
%% Just use the original package and pass the options.
\RequirePackageWithOptions{docbook}
% custom cover page
\def\DBKcover{
\thispagestyle{empty}
\begin{center}
\includegraphics[width=1\textwidth]{images/logo.png} \\
\vspace*{1in}
\bfseries
\sffamily
{\Huge \DBKtitle \\[1ex]\large ~~~ \\}
\vspace*{2.1in}
{\color{blue} \Huge ~~~ \\ \huge ~~~ \\}
\vspace*{2.1in}
{\Large\DBKdate \\}
\end{center}
\vfill
}
For epub:
a2x -f epub -a docinfo document.adoc
where the content of document-docinfo.xml is:
DOCTITLE
DOCTITLE should and could be substituted with a simple sed script like this:
sed -e 's/DOCTITLE/Real title/' document-docinfo.xml
Hope someone will find this useful.
bye
--
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 asciidoc+unsubscr...@googlegroups.com.
To post to this group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Re: Omega letter...
On Tue, Jan 20, 2015 at 10:53:32PM +1000, Lex Trotman wrote: > On 20 January 2015 at 05:57, Marco Ciampa wrote: > > The uppercase omega letter (for resistor's Ohms) Ω does not render in pdf > > dblatex (missin char) > > This is probably best asked on dblatex list, although someone here may know. > > > and it is either not good in fop's pdfs (subscript > > or differen size char). > > Are you sure you are using Ohm not Greek omega, there are separate > code points I think. Ohm _is_ Greek omega. And I doubt that I have Ohm and not Greek omega right with a simple key combination on my keyboard (specifically AltGr+Shift+Q) > Otherwise its a font thing. I think it is precisely a font thing. I an few words: how to (easily) change fonts with asciidoc dblatex front-end? TIA -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Omega letter...
The uppercase omega letter (for resistor's Ohms) Ω does not render in pdf dblatex (missin char) and it is either not good in fop's pdfs (subscript or differen size char). HTML output is ok. I am using Asciidoc on Ubuntu 14.04. What can I do? TIA -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: RUSSIAN documents
On Mon, Jan 19, 2015 at 11:43:01AM -0800, Ivan Kuznetsov wrote: > how to make russian documents with toc and pdf? > > what mean > > user@debian:~$ a2x -a lang=ru -f pdf asciidoc_help.xml > a2x: ERROR: "dblatex" -t pdf -p > "/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s > "/etc/asciidoc/dblatex/asciidoc-dblatex.sty" > "/home/user/asciidoc_help.xml" returned non-zero exit status 1 is asciidoc_help.xml asciidoc? -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoc newbie questions
On Fri, Dec 26, 2014 at 08:05:30PM -0700, Dan Allen wrote: > That's on the roadmap. I'm fairly certain it will happen (in some capacity) > in 2015. Please let me know when you have in hands something that could run... I'll be happy to test it for you... > For now I am stuck between a powerful tool (sphinx) with ostic sintax > > (rest) and a powerful sintax (asciidoc) with a poor tool (a2x). > > > This is precisely the problem we (the Asciidoctor community) are trying to > solve. I had that exactly same problem too, which is what got me involved > in Asciidoctor. It's a lot of software to replace, so it can't be built in > a day, but that doesn't stop us from trying :) As above, let me be one of your tests... -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoc newbie questions
On Wed, Dec 24, 2014 at 03:29:07PM +0100, j. van den hoff wrote: > On Wed, 24 Dec 2014 12:43:05 +0100, Lex Trotman wrote: > >On 24 December 2014 at 20:30, jvdh wrote: Thank you for all the suggestions ... I'll try to do my best ... hope it is enough... -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoc newbie questions
; Personally I hate rest (I have to use it on other projects I > contribute to) and so I don't find out what sphinx can do, so I can't > comment. I used sphinx, like it and still hate rest too... > > I am wrong? Please let me know your thoughts > > > > If not, now I have all the elements to make a (not easy) decision... > > > > Anyway many thanks for your help in clarifying me the things out... > > Hope you find a happy solution, its good that people help with > translating manuals, and that needs encouraging. Thanks. > But I have to ask, > would those projects not prefer you to use the same format as their > original (presumably English) manual so it uses the same tools? Original manuals are ODT. For translation I find that format simply intractable. [Asciidoc|rest|markdown] + po are really nice for translation. I decided to contribute in form of translation only for a manageable format (= [*] + po). So I just have to choose between those upper three. -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: asciidoc newbie questions
On Wed, Dec 24, 2014 at 08:20:14AM +1000, Lex Trotman wrote: > On 23 December 2014 at 22:02, Marco Ciampa 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. I am not using FOP since, as others already pointed it out, IMHO it produces less than satisfactory pdf outputs... > > 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! > > 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 > 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. That is not what I meant with "easy". My aim is to _automate_ the pdf compilation, that was the main reason to escape from ODF format. > > 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 :) Yes, sadly it is not comprehensive, or I am not so "smart" (probably) or it simply does _not_ work at all (also probably)... IMHO that FAQ item should be expanded with some working examples. For istance I never succeded to produce a pdf of a "book" type document with an index and a cover page, not to mention the logo image on the cover... For my test I am evaluating all aspects of the format choice. These comprehend: * responsiveness of the doc tools experts (ok you were responsive and kind enough, thanks! :-) * easiness to circunvent problems .. (so and so... with asciidoc due to a2x docbook dependencies). Messing around witha hacks in latex / xslt / pdftk or so is definitely not the way to do these things... * completeness of the document sistem. For example, sphinx is able to produce an (almost) complete makefile that takes care of all the documentation production details. This together with being the tool chain able to create the best pdf / ebook right out-of-the-box without messing with pdftk (keep in mind that there is no epubtk able to do the same...) make it the clear tool winner... Having said so asciidoctor seems the (actually incomplete) tool more promising. Asciidoctor-pdf promise to produce (in the future) pdf without the docbook toolchain and if there will be something similar for epub that could be very interesting. If asciidoctor will incorporate support for .po file to gurantee easy i18n features that will definitely put it ahead of the pack. For now I am stuck between a powerful tool (sphinx) with ostic sintax (rest) and a powerful sintax (asciidoc) with a poor tool (a2x). I am wrong? Please let me know your thoughts If not, now I have all the elements to make a (not easy) decision... Anyway many thanks for your help in clarifying me the things out... -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
asciidoc newbie questions
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. 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! 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? -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
Re: Please update this translation - Italian
Sorry for the noise, I've done a pull request. Discard this email.
Il giorno lunedì 17 novembre 2014 02:30:36 UTC+1, Marco Ciampa ha scritto:
>
> https://code.google.com/p/asciidoc/source/browse/lang-it.conf
>
> [footer-text]
> #TODO: Translation of 'Version' and 'Last updated'.
> Version {revnumber}{basebackend-xhtml11?}{basebackend-xhtml11=}
> Last updated {docdate} {doctime}
>
> into
>
> [footer-text]
>
> Versione {revnumber}{basebackend-xhtml11?}{basebackend-xhtml11=}
> Ultimo aggiornamento {docdate} {doctime}
>
> Many 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 group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
Please update this translation - Italian
https://code.google.com/p/asciidoc/source/browse/lang-it.conf
[footer-text]
#TODO: Translation of 'Version' and 'Last updated'.
Version {revnumber}{basebackend-xhtml11?}{basebackend-xhtml11=}
Last updated {docdate} {doctime}
into
[footer-text]
Versione {revnumber}{basebackend-xhtml11?}{basebackend-xhtml11=}
Ultimo aggiornamento {docdate} {doctime}
Many 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 group, send email to asciidoc@googlegroups.com.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
