Re: LyX+DocBook confusion
On Fri, Aug 24, 2001 at 10:02:17PM -0400, Larry Kollar wrote: I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Me too. For starters, tables outside of floats don't get wrapped properly. Looking over the code doesn't give me any obvious ways to fix things, either -- I see the InsetFloat:: object (insets/insetfloat.C) generates the table and /table tags, and LyXTabular::DocBook() (tabular.C) generates everything in between. I'd code up an ugly hack like setting testing a global, but then again I'm a tech writer instead of a Real Programmer. The most winning behavior IMO would be to wrap non-floating tables in informaltable ... /informaltable (no title/caption necessary). Your analisys is correct. In 1.2.0 the table will search if it is inside a float table or not, and from there decide between table or informaltable. I take this oportunity to ask everyone that uses lyx-docbook to comment what they like most and what is missing. I would like to have the docbook support at the same level as we have the latex support, and for that I would like to have feedback from the users. :-) Off to stir things up in lyx-doc... Larry -- José
Re: LyX+DocBook confusion
On Fri, Aug 24, 2001 at 10:02:17PM -0400, Larry Kollar wrote: I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Me too. For starters, tables outside of floats don't get wrapped properly. Looking over the code doesn't give me any obvious ways to fix things, either -- I see the InsetFloat:: object (insets/insetfloat.C) generates the table and /table tags, and LyXTabular::DocBook() (tabular.C) generates everything in between. I'd code up an ugly hack like setting testing a global, but then again I'm a tech writer instead of a Real Programmer. The most winning behavior IMO would be to wrap non-floating tables in informaltable ... /informaltable (no title/caption necessary). Your analisys is correct. In 1.2.0 the table will search if it is inside a float table or not, and from there decide between table or informaltable. I take this oportunity to ask everyone that uses lyx-docbook to comment what they like most and what is missing. I would like to have the docbook support at the same level as we have the latex support, and for that I would like to have feedback from the users. :-) Off to stir things up in lyx-doc... Larry -- José
Re: LyX+DocBook confusion
On Fri, Aug 24, 2001 at 10:02:17PM -0400, Larry Kollar wrote: > > >I'm just trying to do some documentation in LyX using the DocBook > > layout style and I'm finding a few things which are making life difficult. > > Me too. > > For starters, tables outside of floats don't get wrapped properly. > Looking over the code doesn't give me any obvious ways to fix things, > either -- I see the InsetFloat:: object (insets/insetfloat.C) generates > the and tags, and LyXTabular::DocBook() (tabular.C) > generates everything in between. > > I'd code up an ugly hack like setting & testing a global, but then > again I'm a tech writer instead of a Real Programmer. The most > winning behavior IMO would be to wrap non-floating tables in > ... (no title/caption necessary). Your analisys is correct. In 1.2.0 the table will search if it is inside a float table or not, and from there decide between table or informaltable. I take this oportunity to ask everyone that uses lyx-docbook to comment what they like most and what is missing. I would like to have the docbook support at the same level as we have the latex support, and for that I would like to have feedback from the users. :-) > Off to stir things up in lyx-doc... > > Larry -- José
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 05:24:31PM +0100, John Bland wrote: Hi, I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Firstly, is there a way to make text appear in a different font, eg emphasised or typewriter styles in LyX just end up as normal text in ps/pdf or docbook-html output. Typewrite text it isn't translated as yet. It should so it is a bug. It will be translated to literal/literal in next version. Now emphasis should work, what is the tool chain that you use to produce the final output? Secondly, and more importantly, is graphics inclusion. It's proving to be a major pita. How do you get references to figure numbers in the text? Using the usual label+crossreference doesn't work in any output form. The figure floats get given numbers as expected though. That is already corrected in the cvs version. If should use the Name field to get what you want... How do you get figures included properly? Using eps figures that display fine in LyX are not included when viewing in ps/pdf. The outputted sgml contains references to the file but without extension and with no reference to the file type. eg including file1.eps generates something like: graphic fileref=file1/graphic The stylesheets from Norman Walsh use that to be able to determine the best format for the output format. For the printing output eps is fine but for the html output gif or png it is prefered. using something like db2html on this then converts this reference to file1.gif, which doesn't exist and so the figures don't get included. Besides, who wants gif when you've got png? That is configurable in the stylesheets. In my case I have changed that to png Including a bitmap image instead eg file1.png generates this: graphic fileref=file1.eps/graphic This will be taken care in the next version, as Baruch stated. What?! db2html then trys to include the eps direct into the html img src, and not many browsers I know can handle eps figures ;0). And I didn't want an eps file included, I wanted the perfectly fine .png file. Also, the DTD is for version 3.01 of DocBook which is now deprecated afaik. Are these things fixed in the cvs version (which is offline from here at least)? The next version will use docbook 4 (both the xml and sgml versions). This change didn't make into the fix series because it was a new feature. I have some changes to add to cvs in this will be one of the first. Cheers, Frink (exhasperated) Relax. ;-) -- John Bland M.Phys (Hons) AMInstP /\ PhD Student Sys Admin Email: j.bland at cmp.liv.ac.uk / \ Condensed Matter Group http://ringtail.cmp.liv.ac.uk/ /\ Liverpool University Everybody relax, I'm here. -- Jack Burton -- José
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 09:29:55PM +0300, Baruch Even wrote: * John Bland [EMAIL PROTECTED] [010823 20:30]: [Answered] Secondly, and more importantly, is graphics inclusion. It's proving to be a major pita. I'm working on a new version and would be glad for all info you can provide on the constructs to use to get graphics in DocBook. I can use the same model as we have now. We will need to change it for docbook 5.0, but that is another story. (BTW this is the comments of your code and is correct. :-) As said above, it would be a great help if you could take each of this problems and tell me what DocBook code needs to be generated, the current state for graphics in DocBook is pretty lame. Also, the DTD is for version 3.01 of DocBook which is now deprecated afaik. Are these things fixed in the cvs version (which is offline from here at least)? I believe the new graphics code will do 4.0, but I'm not completely sure, it's been a while since I checked the DocBook texts to know what to output. There is a new version of the DocBook The Definitive Guide that is available at www.docbook.org and that refers to version 4. -- Baruch Even http://baruch.ev-en.org/ -- José
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 09:29:55PM +0300, Baruch Even wrote: I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Firstly, is there a way to make text appear in a different font, eg emphasised or typewriter styles in LyX just end up as normal text in ps/pdf or docbook-html output. Probably a missing translation of these attributes. The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We also need to disable in dialogs features that are not available when using linuxdoc/docbook. For example, in docbook all the scaling options in the graphics dialog should be disabled.
Re: LyX+DocBook confusion
On Fri, Aug 24, 2001 at 01:52:17PM +0300, Dekel Tsur wrote: The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We also need to disable in dialogs features that are not available when using linuxdoc/docbook. For example, in docbook all the scaling options in the graphics dialog should be disabled. Agreed, there is no way to pass this info to docbook. Or we could take care of that with the new code. Is that feasible? (Baruch) Example: If the user requests a scaled picture we create a temporary figure and pass that one to the output. -- José
Re: LyX+DocBook confusion
* Jose Abilio Oliveira Matos [EMAIL PROTECTED] [010824 15:43]: On Fri, Aug 24, 2001 at 01:52:17PM +0300, Dekel Tsur wrote: The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We also need to disable in dialogs features that are not available when using linuxdoc/docbook. For example, in docbook all the scaling options in the graphics dialog should be disabled. Agreed, there is no way to pass this info to docbook. Or we could take care of that with the new code. Is that feasible? (Baruch) The new code can probably be extended to do it, but I'd rather not do it for this version, I'm still fighting my way to get what I have into a working version so that it will be present in 1.2 Example: If the user requests a scaled picture we create a temporary figure and pass that one to the output. If current improvement will make it into 1.2, this can be done for 1.3. -- Baruch Even http://baruch.ev-en.org/
Re: LyX+DocBook confusion
I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Me too. For starters, tables outside of floats don't get wrapped properly. Looking over the code doesn't give me any obvious ways to fix things, either -- I see the InsetFloat:: object (insets/insetfloat.C) generates the table and /table tags, and LyXTabular::DocBook() (tabular.C) generates everything in between. I'd code up an ugly hack like setting testing a global, but then again I'm a tech writer instead of a Real Programmer. The most winning behavior IMO would be to wrap non-floating tables in informaltable ... /informaltable (no title/caption necessary). Off to stir things up in lyx-doc... Larry
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 05:24:31PM +0100, John Bland wrote: Hi, I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Firstly, is there a way to make text appear in a different font, eg emphasised or typewriter styles in LyX just end up as normal text in ps/pdf or docbook-html output. Typewrite text it isn't translated as yet. It should so it is a bug. It will be translated to literal/literal in next version. Now emphasis should work, what is the tool chain that you use to produce the final output? Secondly, and more importantly, is graphics inclusion. It's proving to be a major pita. How do you get references to figure numbers in the text? Using the usual label+crossreference doesn't work in any output form. The figure floats get given numbers as expected though. That is already corrected in the cvs version. If should use the Name field to get what you want... How do you get figures included properly? Using eps figures that display fine in LyX are not included when viewing in ps/pdf. The outputted sgml contains references to the file but without extension and with no reference to the file type. eg including file1.eps generates something like: graphic fileref=file1/graphic The stylesheets from Norman Walsh use that to be able to determine the best format for the output format. For the printing output eps is fine but for the html output gif or png it is prefered. using something like db2html on this then converts this reference to file1.gif, which doesn't exist and so the figures don't get included. Besides, who wants gif when you've got png? That is configurable in the stylesheets. In my case I have changed that to png Including a bitmap image instead eg file1.png generates this: graphic fileref=file1.eps/graphic This will be taken care in the next version, as Baruch stated. What?! db2html then trys to include the eps direct into the html img src, and not many browsers I know can handle eps figures ;0). And I didn't want an eps file included, I wanted the perfectly fine .png file. Also, the DTD is for version 3.01 of DocBook which is now deprecated afaik. Are these things fixed in the cvs version (which is offline from here at least)? The next version will use docbook 4 (both the xml and sgml versions). This change didn't make into the fix series because it was a new feature. I have some changes to add to cvs in this will be one of the first. Cheers, Frink (exhasperated) Relax. ;-) -- John Bland M.Phys (Hons) AMInstP /\ PhD Student Sys Admin Email: j.bland at cmp.liv.ac.uk / \ Condensed Matter Group http://ringtail.cmp.liv.ac.uk/ /\ Liverpool University Everybody relax, I'm here. -- Jack Burton -- José
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 09:29:55PM +0300, Baruch Even wrote: * John Bland [EMAIL PROTECTED] [010823 20:30]: [Answered] Secondly, and more importantly, is graphics inclusion. It's proving to be a major pita. I'm working on a new version and would be glad for all info you can provide on the constructs to use to get graphics in DocBook. I can use the same model as we have now. We will need to change it for docbook 5.0, but that is another story. (BTW this is the comments of your code and is correct. :-) As said above, it would be a great help if you could take each of this problems and tell me what DocBook code needs to be generated, the current state for graphics in DocBook is pretty lame. Also, the DTD is for version 3.01 of DocBook which is now deprecated afaik. Are these things fixed in the cvs version (which is offline from here at least)? I believe the new graphics code will do 4.0, but I'm not completely sure, it's been a while since I checked the DocBook texts to know what to output. There is a new version of the DocBook The Definitive Guide that is available at www.docbook.org and that refers to version 4. -- Baruch Even http://baruch.ev-en.org/ -- José
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 09:29:55PM +0300, Baruch Even wrote: I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Firstly, is there a way to make text appear in a different font, eg emphasised or typewriter styles in LyX just end up as normal text in ps/pdf or docbook-html output. Probably a missing translation of these attributes. The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We also need to disable in dialogs features that are not available when using linuxdoc/docbook. For example, in docbook all the scaling options in the graphics dialog should be disabled.
Re: LyX+DocBook confusion
On Fri, Aug 24, 2001 at 01:52:17PM +0300, Dekel Tsur wrote: The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We also need to disable in dialogs features that are not available when using linuxdoc/docbook. For example, in docbook all the scaling options in the graphics dialog should be disabled. Agreed, there is no way to pass this info to docbook. Or we could take care of that with the new code. Is that feasible? (Baruch) Example: If the user requests a scaled picture we create a temporary figure and pass that one to the output. -- José
Re: LyX+DocBook confusion
* Jose Abilio Oliveira Matos [EMAIL PROTECTED] [010824 15:43]: On Fri, Aug 24, 2001 at 01:52:17PM +0300, Dekel Tsur wrote: The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We also need to disable in dialogs features that are not available when using linuxdoc/docbook. For example, in docbook all the scaling options in the graphics dialog should be disabled. Agreed, there is no way to pass this info to docbook. Or we could take care of that with the new code. Is that feasible? (Baruch) The new code can probably be extended to do it, but I'd rather not do it for this version, I'm still fighting my way to get what I have into a working version so that it will be present in 1.2 Example: If the user requests a scaled picture we create a temporary figure and pass that one to the output. If current improvement will make it into 1.2, this can be done for 1.3. -- Baruch Even http://baruch.ev-en.org/
Re: LyX+DocBook confusion
I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Me too. For starters, tables outside of floats don't get wrapped properly. Looking over the code doesn't give me any obvious ways to fix things, either -- I see the InsetFloat:: object (insets/insetfloat.C) generates the table and /table tags, and LyXTabular::DocBook() (tabular.C) generates everything in between. I'd code up an ugly hack like setting testing a global, but then again I'm a tech writer instead of a Real Programmer. The most winning behavior IMO would be to wrap non-floating tables in informaltable ... /informaltable (no title/caption necessary). Off to stir things up in lyx-doc... Larry
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 05:24:31PM +0100, John Bland wrote: > > Hi, > >I'm just trying to do some documentation in LyX using the DocBook > layout style and I'm finding a few things which are making life difficult. > > Firstly, is there a way to make text appear in a different font, eg > emphasised or typewriter styles in LyX just end up as normal text in > ps/pdf or docbook-html output. Typewrite text it isn't translated as yet. It should so it is a bug. It will be translated to in next version. Now emphasis should work, what is the tool chain that you use to produce the final output? > Secondly, and more importantly, is graphics inclusion. It's proving to be > a major pita. > > How do you get references to figure numbers in the text? Using the usual > label+crossreference doesn't work in any output form. The figure floats > get given numbers as expected though. That is already corrected in the cvs version. If should use the Name field to get what you want... > How do you get figures included properly? Using eps figures that display > fine in LyX are not included when viewing in ps/pdf. The outputted sgml > contains references to the file but without extension and with no > reference to the file type. eg including file1.eps generates something > like: > > The stylesheets from Norman Walsh use that to be able to determine the best format for the output format. For the printing output eps is fine but for the html output gif or png it is prefered. > using something like db2html on this then converts this reference to > file1.gif, which doesn't exist and so the figures don't get included. > Besides, who wants gif when you've got png? That is configurable in the stylesheets. In my case I have changed that to png > Including a bitmap image instead eg file1.png generates this: > > This will be taken care in the next version, as Baruch stated. > What?! db2html then trys to include the eps direct into the html img src, > and not many browsers I know can handle eps figures ;0). And I didn't want an > eps file included, I wanted the perfectly fine .png file. > > Also, the DTD is for version 3.01 of DocBook which is now deprecated > afaik. Are these things fixed in the cvs version (which is offline from > here at least)? The next version will use docbook 4 (both the xml and sgml versions). This change didn't make into the fix series because it was a new feature. I have some changes to add to cvs in this will be one of the first. > Cheers, >Frink (exhasperated) Relax. ;-) > -- > John Bland M.Phys (Hons) AMInstP /\ PhD Student & Sys Admin > Email: j.bland at cmp.liv.ac.uk / \ Condensed Matter Group > http://ringtail.cmp.liv.ac.uk/ /\ Liverpool University > "Everybody relax, I'm here." -- Jack Burton -- José
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 09:29:55PM +0300, Baruch Even wrote: > * John Bland <[EMAIL PROTECTED]> [010823 20:30]: > > [Answered] > > Secondly, and more importantly, is graphics inclusion. It's proving to be > > a major pita. > > I'm working on a new version and would be glad for all info you can > provide on the constructs to use to get graphics in DocBook. I can use the same model as we have now. We will need to change it for docbook 5.0, but that is another story. (BTW this is the comments of your code and is correct. :-) > As said above, it would be a great help if you could take each of this > problems and tell me what DocBook code needs to be generated, the > current state for graphics in DocBook is pretty lame. > > > Also, the DTD is for version 3.01 of DocBook which is now deprecated > > afaik. Are these things fixed in the cvs version (which is offline from > > here at least)? > I believe the new graphics code will do 4.0, but I'm not completely > sure, it's been a while since I checked the DocBook texts to know what > to output. There is a new version of the "DocBook The Definitive Guide" that is available at www.docbook.org and that refers to version 4. > -- > Baruch Even > http://baruch.ev-en.org/ -- José
Re: LyX+DocBook confusion
On Thu, Aug 23, 2001 at 09:29:55PM +0300, Baruch Even wrote: > >I'm just trying to do some documentation in LyX using the DocBook > > layout style and I'm finding a few things which are making life difficult. > > > > Firstly, is there a way to make text appear in a different font, eg > > emphasised or typewriter styles in LyX just end up as normal text in > > ps/pdf or docbook-html output. > > Probably a missing translation of these attributes. > > The best thing to do if you want this fixed in the next version is to > hunt the DocBook commands to do what is needed and to post them for > whatever feature we are missing from DocBook. We also need to disable in dialogs features that are not available when using linuxdoc/docbook. For example, in docbook all the scaling options in the graphics dialog should be disabled.
Re: LyX+DocBook confusion
On Fri, Aug 24, 2001 at 01:52:17PM +0300, Dekel Tsur wrote: > > The best thing to do if you want this fixed in the next version is to > > hunt the DocBook commands to do what is needed and to post them for > > whatever feature we are missing from DocBook. > > We also need to disable in dialogs features that are not available when using > linuxdoc/docbook. > For example, in docbook all the scaling options in the graphics dialog > should be disabled. Agreed, there is no way to pass this info to docbook. Or we could take care of that with the new code. Is that feasible? (Baruch) Example: If the user requests a scaled picture we create a temporary figure and pass that one to the output. -- José
Re: LyX+DocBook confusion
* Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> [010824 15:43]: > On Fri, Aug 24, 2001 at 01:52:17PM +0300, Dekel Tsur wrote: > > > The best thing to do if you want this fixed in the next version is to > > > hunt the DocBook commands to do what is needed and to post them for > > > whatever feature we are missing from DocBook. > > > > We also need to disable in dialogs features that are not available when using > > linuxdoc/docbook. > > For example, in docbook all the scaling options in the graphics dialog > > should be disabled. > > Agreed, there is no way to pass this info to docbook. Or we could take > care of that with the new code. Is that feasible? (Baruch) The new code can probably be extended to do it, but I'd rather not do it for this version, I'm still fighting my way to get what I have into a working version so that it will be present in 1.2 > Example: If the user requests a scaled picture we create a temporary > figure and pass that one to the output. If current improvement will make it into 1.2, this can be done for 1.3. -- Baruch Even http://baruch.ev-en.org/
Re: LyX+DocBook confusion
>I'm just trying to do some documentation in LyX using the DocBook > layout style and I'm finding a few things which are making life difficult. Me too. For starters, tables outside of floats don't get wrapped properly. Looking over the code doesn't give me any obvious ways to fix things, either -- I see the InsetFloat:: object (insets/insetfloat.C) generates the and tags, and LyXTabular::DocBook() (tabular.C) generates everything in between. I'd code up an ugly hack like setting & testing a global, but then again I'm a tech writer instead of a Real Programmer. The most winning behavior IMO would be to wrap non-floating tables in ... (no title/caption necessary). Off to stir things up in lyx-doc... Larry
Re: LyX+DocBook confusion
* John Bland [EMAIL PROTECTED] [010823 20:30]: Hi, I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Firstly, is there a way to make text appear in a different font, eg emphasised or typewriter styles in LyX just end up as normal text in ps/pdf or docbook-html output. Probably a missing translation of these attributes. The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We (the developers) can probably do that too, but for most of the time we are using LaTeX and not DocBook and so we rely on our users to help us detect and fix such problems. Secondly, and more importantly, is graphics inclusion. It's proving to be a major pita. I'm working on a new version and would be glad for all info you can provide on the constructs to use to get graphics in DocBook. As said above, it would be a great help if you could take each of this problems and tell me what DocBook code needs to be generated, the current state for graphics in DocBook is pretty lame. Also, the DTD is for version 3.01 of DocBook which is now deprecated afaik. Are these things fixed in the cvs version (which is offline from here at least)? I believe the new graphics code will do 4.0, but I'm not completely sure, it's been a while since I checked the DocBook texts to know what to output. -- Baruch Even http://baruch.ev-en.org/
Re: LyX+DocBook confusion
* John Bland [EMAIL PROTECTED] [010823 20:30]: Hi, I'm just trying to do some documentation in LyX using the DocBook layout style and I'm finding a few things which are making life difficult. Firstly, is there a way to make text appear in a different font, eg emphasised or typewriter styles in LyX just end up as normal text in ps/pdf or docbook-html output. Probably a missing translation of these attributes. The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We (the developers) can probably do that too, but for most of the time we are using LaTeX and not DocBook and so we rely on our users to help us detect and fix such problems. Secondly, and more importantly, is graphics inclusion. It's proving to be a major pita. I'm working on a new version and would be glad for all info you can provide on the constructs to use to get graphics in DocBook. As said above, it would be a great help if you could take each of this problems and tell me what DocBook code needs to be generated, the current state for graphics in DocBook is pretty lame. Also, the DTD is for version 3.01 of DocBook which is now deprecated afaik. Are these things fixed in the cvs version (which is offline from here at least)? I believe the new graphics code will do 4.0, but I'm not completely sure, it's been a while since I checked the DocBook texts to know what to output. -- Baruch Even http://baruch.ev-en.org/
Re: LyX+DocBook confusion
* John Bland <[EMAIL PROTECTED]> [010823 20:30]: > > Hi, > >I'm just trying to do some documentation in LyX using the DocBook > layout style and I'm finding a few things which are making life difficult. > > Firstly, is there a way to make text appear in a different font, eg > emphasised or typewriter styles in LyX just end up as normal text in > ps/pdf or docbook-html output. Probably a missing translation of these attributes. The best thing to do if you want this fixed in the next version is to hunt the DocBook commands to do what is needed and to post them for whatever feature we are missing from DocBook. We (the developers) can probably do that too, but for most of the time we are using LaTeX and not DocBook and so we rely on our users to help us detect and fix such problems. > Secondly, and more importantly, is graphics inclusion. It's proving to be > a major pita. I'm working on a new version and would be glad for all info you can provide on the constructs to use to get graphics in DocBook. As said above, it would be a great help if you could take each of this problems and tell me what DocBook code needs to be generated, the current state for graphics in DocBook is pretty lame. > Also, the DTD is for version 3.01 of DocBook which is now deprecated > afaik. Are these things fixed in the cvs version (which is offline from > here at least)? I believe the new graphics code will do 4.0, but I'm not completely sure, it's been a while since I checked the DocBook texts to know what to output. -- Baruch Even http://baruch.ev-en.org/
