Hi, the debugging mode is for end-users with less knowledge of docbook or fop. They build there template (or parts) with an wysiwyg-editor.
Von: [email protected] [mailto:[email protected]] Im Auftrag von Aaron DaMommio Gesendet: Dienstag, 9. April 2013 17:22 An: Sticker Markus EXT FRD EPOS Cc: [email protected]; [email protected] Betreff: Re: AW: AW: AW: [docbook] Some text after a section Okay, so you want to make your processing instructions visible, and you are converting them to paragraphs to do that, but sometimes a para is not valid in the location where the processing instruction is? Are you doing XSLT customizations to help with this at all? I can imagine many template customizations that would help in this situation. Here are some ideas: - Customize titles so that if the topic contains a certain PI, it outputs the text of the PI as part of the title - It's not clear to me precisely how you are converting your PIs to paras, but if you post-processed the result with an XSLT, you could detect when the para is 1st child of a section, and then convert it to a subtitle in that case (since a subtitle is valid at section start) - Instead of trying to output a built-up document, why not write out your source? I assume that there is some reason why it is inconvenient to view the source files so that you want to display your PIs in the output. But maybe there is a convenient intermediate file that you could be looking at when you are debugging. In our system, for example, it is frequently helpful to look at files at the stage in our process where xinclusion has been done and a book has been converted to one big file, but before other transformations have happened. Maybe you could set up a situation where such a file becomes an output, and then inspect it as text to see where the PIs are. On Tue, Apr 9, 2013 at 10:07 AM, <[email protected]<mailto:[email protected]>> wrote: Hi, OK. We use processing-instructions (build by several preprocessors out of our tool-chain) for getting different version of one document (pdf, rtf, html). These documents are generated on the server. If we need to debug the resulting document the processing instruction have to become visible. Because sometimes there are many expressions to hide parts / graphics / ... Sometimes the processing instruction are not in the very best node to add a para. Unfortunately. Currently I build a very dirty hack (using glossary) to get the instructions, but this is not my preferred way to work with documents. Best regards Markus Von: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] Im Auftrag von Aaron DaMommio Gesendet: Dienstag, 9. April 2013 16:53 An: Stefan Seefeld Cc: Sticker Markus EXT FRD EPOS; [email protected]<mailto:[email protected]> Betreff: Re: AW: AW: AW: [docbook] Some text after a section Marcus, I'm reading what you've sent, and I still don't understand what you are trying to do. Can you try again to describe what you want, perhaps more generally, leaving out the processing instructions, and just describe the results you are trying to get? Then someone may be better able to suggest a solution that works with DocBook. --Aaron DaMommio On Tue, Apr 9, 2013 at 9:45 AM, Stefan Seefeld <[email protected]<mailto:[email protected]>> wrote: On 04/09/2013 10:25 AM, [email protected]<mailto:[email protected]> wrote: > Hi, > > thank you, Stefan. This is a good advice but don't meet my problem/question. > Also I if use profiling, the issue will remain. Your question reminds me a little of how people who aren't trained to think in terms of structured documents approach styling questions, for example by asking "how can I make this text bold", instead of thinking about the semantics of the desired style. You were asking how to add highlighted text that's fully oblivious to the document structure, and my advise was to instead think about the semantics of the annotation you want. My understanding was that in fact the text you want isn't oblivious to the document structure, quite the opposite: it's an annotation of document structure, which you just happen to want to put outside the formatted section instead of inside. I believe that thinking along those lines will make it easier to get to a solution that works with DocBook and not against it. Stefan -- ...ich hab' noch einen Koffer in Berlin... --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected]<mailto:[email protected]> For additional commands, e-mail: [email protected]<mailto:[email protected]> -- -------------------------------------- Aaron DaMommio: Husband, father, writer, juggler, and expert washer of dishes. - My blog: http://aarondamommio.blogspot.com - Need a juggler? http://amazingaaronjuggler.blogspot.com/ ======================================= -- -------------------------------------- Aaron DaMommio: Husband, father, writer, juggler, and expert washer of dishes. - My blog: http://aarondamommio.blogspot.com - Need a juggler? http://amazingaaronjuggler.blogspot.com/ =======================================
