Keith, The only changes I made to the xml to make the second pdf, Proposaltoreinvigerate_fjcc_myStyles2.pdf, were to change from a hierarchical section structure to a nonhierarchical, changing sect1, sect2, sect3 tags to just section, and putting <title> tags around the title, which moved it above the table of contents. The only styling I did was changing the color of some section titles and using bullets in the lists instead of numbers.
I am editing the xml file in a plain text editor. I make the the pdf file with the two commands xsltproc.exe --output tmp.fo myStyles.xsl Proposaltoreinvigerate_fjcc2.xml fop tmp.fo Proposaltoreinvigerate_fjcc_myStyles2.pdf Are you not seeing pages in the PDF file? That is strange because I do. I think I can get the logo in without much trouble. I make the HTML file with xsltproc.exe --nonet --novalid --output Proposaltoreinvigerate_fjcc_myStyles.html c:\docbook\xsl\html\docbook.xsl Proposaltoreinvigerate_fjcc2.xml The --nonet flag stops xsltproc from getting hung looking for the DTD according to something I read. I am looking forward to seeing the feedback you get on your doc. Regards, Francis On Thu, Jun 11, 2020 at 3:07 PM Keith N. McKenna <keith.mcke...@comcast.net> wrote: > On 6/11/2020 2:48 PM, F Campos Costero wrote: > > Keith, > > I understand you may be busy with other things. Did you get the > documents I > > sent? I would be interested to hear your thoughts on how to proceed. > > Francis > > > Francis; > > Sorry for not replying sooner. I did get them. The second one that you > did with my proposal doc wasn't bad but it still lacked the Logo and > there were no page breaks in it at all. What edits did you have to make > to the XML file? I do notice that the notice that the XML file is using > DTD 4.1.2. Not sure if it makes any difference to the app you are using, > but when I try to open it in XML Notepad it chokes on the download. > > I expect that it is worth the effort to continue at this point. I'm just > about ready to send out the ready to send out the analysis doc to both > dev@ and doc@ to see if we get any feedback on other things to use. > > Regards > Keith > <snip> > > > > > > > >
