On 21 March 2012 03:59, Anatoly Berdichevsky <[email protected]> wrote: > Hi, > > using asciidoc I came across the following problems. > Maybe someone can help me to figure it out. > The problems are expressed in asciidoc under the line "___..." > > The versions that I use: > > > asciidoc 8.6.6 > dblatex version 0.2.7 > pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/openSUSE) > Python 2.6.5 > XSLT stylesheets DocBook - LaTeX 2e (0.2.7) > > BR > > Anatoly > > > _____________________________________________________________________________ > > :numbered: > > > *1.* The images cannot be positioned side by side. The table does not > allow to put images inside cells. > |====== > |image::image1.jpg["image1"]|image::image2.jpg["image2"]| > image::image3.jpg["image3"] > |====== >
You can use inline image macros (only one : ) to do this. > > > *2.* The colors background/foreground are not shown in the pdf > representation. > [red]#red text# [yellow-background]#on yellow# > [big]#large# [red yellow-background big]*all bold* > Correct, there is a note in the manual that text attributes do not apply to html 4 or PDF. This is because the standard toolchains do not style the roles by default. The attribute is translated into a role name and you can use the role styling capabilities of the docbook toolchains to style them. > > *3.* In the table overlap the long lines from beside standing columns > in the pdf representation. > |====== > | > Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1Test1| > Test2Test2Test2Test2Test2Test2Test2Test2Test2 > |====== > The content of each cell is one word, so there is nowhere to break the line, HTML can expand the table since you can scroll a screen, but PDF can't since (last time I looked) you can't scroll a piece of paper. > > *4.* The size of the letters is not considered in the pdf > representation. > [red yellow-background big]*all bold* See answer to 2 above. > > > *5.* The German specific letters, like ä, ö. ü, ß lead with the > transformation into pdf to the mistakes. > > Einführung > ---------- > Einführung 1 > ^^^^^^^^^^^^ > Works with FOP (when used in the right order, ie ~~~ follows ___ not ^^^) fails with dblatex, I think this is a known problem with latex for all but ascii. Perhaps you could try Xetex (I think) or other Unicode supporting version. > > *6.* The small images are positioned in html representation on the > left side, in pdf representation they are always positioned in the > middle. > > image::image1.jpg["image1"] Thats the default positioning of your docbook-PDF toolchain, see FAQ #3 for pointers to documentation on how to configure it. > > > *7.* With the "toclevels=5" parameter can be numbered only three > content levels. Level 4 is not numbered. > > Level 1 > ------- > Level 2 > ~~~~~~~ > Level 3 > ^^^^^^^ > Level 4 > +++++++ I guess the manual should say how many levels are supported. PS toclevels only goes to 4 not 5. > > > *8.* In the *.txt file one always leaves two empty lines at the end > of the documentation, otherwise it leads with > the pdf generating to the mistakes. I don't have any problem with either toolchain generating PDF from .txt files without any end of line at the end of the file. Please provide more information, eg what goes wrong? Cheers Lex -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
