"Jose' Matos" <[EMAIL PROTECTED]> schrieb am 10.02.05 16:56:32: >
Hi Jose', Andreas and other LyX developers, let me start by asking a favour from all: please use the word "DocBook" (case is unimportant) in the subject line whenever you post something relating to DocBook. Andreas' original post was something like "Directions wanted" and made me miss it completely until someone started posting "xxxx DocBook xxxx - was: Directions wanted". I use a search facility to fish only those posts that have to do with DocBook support in LyX. > > b) putting image files in a subdirectory or not, what name to use for the > > subdirectory > > math-images (?!) ;-) > Give the user control of where to store the images. This is not something that LyX can decide for itself. Whatever decision you take, it is going to be the wrong one for somebody - I dare say, for the majority of the users. If a directory name is hardwired somewhere, you force the user to use some script to automatically rename it each time he exports the file to DocBook. > > c) How to align math bitmaps vertically. It's no problem to get > > ascent/descent from preview.sty, but how to code it in XML? > > Docbook defines valign=(top|center|bottom) which is not good enough, > > XHTML apparently also knows "valign=-7px" > > What do others use? > Aligning is a presentational property. As such, it does not belong to the structural markup (as DocBook is). Let the stylesheets decide. > > d) What file formats should we produce? All, just PNG, just EPS or > > PNG+EPS ? > > I think that we can play here the same tricks as we do with latex. But to > be simple I would say both, and not passing the extension (since some > stylesheets take care of this). The other option would be to declare the > different formats... > Let the user decide. Put checkboxes somewhere, in some configuration dialog. Ask the user the question: - What formats shall be created? Checkbox Document Format Image Format Convert using... ------------------------------------------------------------------------------------------------------ Yes/No HTML PNG Yes/No --- Yes/No PS EPS Yes/No png2eps Yes/No PDF EPDF Yes/No png2epdf Yes/No RTF BMP Yes/No png2bmp Yes/No TXT ASCIIart Yes/No png2ascii The first Yes/No in a row means "convert to this format", the second one means "convert all PNG images in the images directory to the required image format using the utility xxxx". The image format column is dependent on the document format column, i.e. fixed: for HTML we use PNG, for PS we use EPS and so on. The utilities offered are wrappers around some simple scripts that can be delivered with LyX, i.e. we don't deliver the basic xxx2yyy utilities, but we do deliver the wrapper scripts that use those utilities to transform from zzz to whatever. Something like that...you get the idea. > > e) Should we use Chris' <!ENTITY % output.print.png "IGNORE"> > > everywhere, just SGML or not at all? > > Just SGML. It is valid so why not to use it. > Agreed. ;-) > > g) What "density" or magnification should be used for maths? > > (Not knowing the final font size) > > Me neither. :-) > Make it a user-entered quantity. Again, whatever you can't decide at programming (or design) time, let the user decide it. Only the user knows the right density of his images, so make it a paremeter to enter in some configuration dialog (maybe in the above). Use a sensible default like, say, 100. > > b) Yes, something like myFile_images/ > > That is fair. > No. Let the user decide. See above. > > c) Produce illegal valign attributes which can be used directly for XHTML > > I will close my eyes here. ;-) Let the stylesheets decide. For SGML, the stylesheets come with Norman Walsh' scripts. If the user wishes, he may use his own ones. We will *have* to provide modufied stylesheets (more precisely: customization layers) anyway, as I do in my lyxtox package: http://www.karakas-online.de/mySGML/explain-dsssl-stylesheets.html > > > d) EPS + PNG, let other tools do the rest > > I agree. > I disagree. Totally. :-) You can't leave the user alone with the task of creating a TXT version, or, even more important, an RTF version! I use my lyxtox package productively. I write my software/consulting/whatever documentation with it. When I talk about "single source publishing" with my clients, they feel like I am talking about some martians. When I ask them "may I write the documentation with my tools?", they say "will there be a Word format for me? If so, go for it, if not, then you will have to use Word". The client is king. So the client wins. And the client wants Word. This means for me that I have to produce a decent RTF. Like it or not, RTF (with BMP's as images) is crucial for accepting this procedure in a corporate environment. We are not talking about "corporate as in IBM", who know what DocBook is - and even use it - , but we are talking about "corporate as in large Logistics provider in European Community, province Germany". ;-) So my plea is: create as many formats as possible automatically, and give the user the power to decide which ones he needs each time. DON'T put the burden of creating an RTF on the user's shoulders! It's damn difficult and nobody will make it (just as nobody managed to get images in PDFs created from DocBook SGML - sure it is possible, but show me *one* who managed to get it in the whole world, the Internet is full of people asking for this, but empty of answers...read about it in http://www.karakas-online.de/mySGML/explain-figures.html ). > > e) Only for EPS + PNG > > Ok. > No. See above. > > > PS: Have you seen that it is possible for docbook 5.0 to be release > > > without a dtd? More and more xml is becoming the default. > > What for? Where's the point? With DocBook SGML, we already have a procedure, and we know it works. SGML needs a DTD, so our working procedure needs it too. Everything else is "furure music", as Germans say. ;-) We (the users) need a working procedure, now - well, actually yesterday! ;-) > > > Ciao > > Ciao. > Ciao. > > /Andreas > > José Abílio > Chris -- Regards Chris Karakas http://www.karakas-online.de
