Re: [suse-beta-e] openSUSE user documentation
Thanks Adrian, This message is sent to opensuse-doc@opensuse.org as well, I'll continue to search Google to see if I can find something useful. Anders. Adrian Schröter skrev:
Am Monday 29 May 2006 10:03 schrieb Anders Norrbring:
I'm looking at posting a how-to at opensuse.org, but I'm kindof confused by the site.. I can't find any way to upload my DocBook XML files, just a web based section editing function..
Do I have to copy-and-paste all of it into that web based editor? Or can I somehow use my XML files?
The wiki remains to be a wiki ;)
But we did plan to support also handbook style writings via doc.opensuse.org. You should get in contact via our doc writers, via opensuse-doc@opensuse.org
bye adrian
Hi Anders, On Monday 29 May 2006 10:51, Anders Norrbring wrote:
Thanks Adrian, This message is sent to opensuse-doc@opensuse.org as well, I'll continue to search Google to see if I can find something useful.
Anders.
Adrian Schröter skrev:
Am Monday 29 May 2006 10:03 schrieb Anders Norrbring:
I'm looking at posting a how-to at opensuse.org, but I'm kindof confused by the site.. I can't find any way to upload my DocBook XML files, just a web based section editing function..
Do I have to copy-and-paste all of it into that web based editor? Or can I somehow use my XML files?
The wiki remains to be a wiki ;)
But we did plan to support also handbook style writings via doc.opensuse.org. You should get in contact via our doc writers, via opensuse-doc@opensuse.org
bye adrian
Currently, we have similiar problems with our docs. I developed XSLT stylesheets to transform Novdoc or DocBook XML into Wiki syntax. Check it out from [1]. It's in a preliminary alpha state, but it creates more or less useful outputs. Maybe the output must be manually corrected. And of course, not all elements are supported. You transform your XML document into wiki with: xsltproc --output DOC.wiki db2mediawiki/docbook.xsl DOC.xml You should keep in mind that transforming your rich marked up DocBook document into Wiki syntax is "semantic degradation": It's always possible to transform from DocBook into Wiki but not back. :) Hope this helps, Tom ------- [1] https://forgesvn1.novell.com/svn/novdoc/trunk/xslt/db2mediawiki -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.suse.com
Thomas Schraitle skrev:
Hi Anders,
On Monday 29 May 2006 10:51, Anders Norrbring wrote:
Thanks Adrian, This message is sent to opensuse-doc@opensuse.org as well, I'll continue to search Google to see if I can find something useful.
Anders.
Adrian Schröter skrev:
Am Monday 29 May 2006 10:03 schrieb Anders Norrbring:
I'm looking at posting a how-to at opensuse.org, but I'm kindof confused by the site.. I can't find any way to upload my DocBook XML files, just a web based section editing function..
Do I have to copy-and-paste all of it into that web based editor? Or can I somehow use my XML files? The wiki remains to be a wiki ;)
But we did plan to support also handbook style writings via doc.opensuse.org. You should get in contact via our doc writers, via opensuse-doc@opensuse.org
bye adrian
Currently, we have similiar problems with our docs. I developed XSLT stylesheets to transform Novdoc or DocBook XML into Wiki syntax. Check it out from [1]. It's in a preliminary alpha state, but it creates more or less useful outputs. Maybe the output must be manually corrected. And of course, not all elements are supported.
You transform your XML document into wiki with:
xsltproc --output DOC.wiki db2mediawiki/docbook.xsl DOC.xml
You should keep in mind that transforming your rich marked up DocBook document into Wiki syntax is "semantic degradation": It's always possible to transform from DocBook into Wiki but not back. :)
Hope this helps, Tom
------- [1] https://forgesvn1.novell.com/svn/novdoc/trunk/xslt/db2mediawiki
I'll take a look at it! Thanks a lot.. :) I saw before me that I had to edit 3000 lines manually.. Gah.. -- Anders Norrbring Norrbring Consulting
Hi, On Monday 29 May 2006 11:21, Anders Norrbring wrote:
[...]
------- [1] https://forgesvn1.novell.com/svn/novdoc/trunk/xslt/db2mediawiki
I'll take a look at it! Thanks a lot.. :) I saw before me that I had to edit 3000 lines manually.. Gah..
Hehe. :) Depending on your DocBook source you will find bugs in the output (well it's alpha). At the moment it is not very well documented and it relies somewhat on openSUSE Wiki page. For example, admonition boxes like tip, warning, etc. are build through a openSUSE Wiki template. That simplifies the transformation process a lot. If you need more info just ask. :-) Have fun, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.opensuse.org
Thomas Schraitle skrev:
Hi,
On Monday 29 May 2006 11:21, Anders Norrbring wrote:
[...]
------- [1] https://forgesvn1.novell.com/svn/novdoc/trunk/xslt/db2mediawiki I'll take a look at it! Thanks a lot.. :) I saw before me that I had to edit 3000 lines manually.. Gah..
Hehe. :) Depending on your DocBook source you will find bugs in the output (well it's alpha). At the moment it is not very well documented and it relies somewhat on openSUSE Wiki page. For example, admonition boxes like tip, warning, etc. are build through a openSUSE Wiki template. That simplifies the transformation process a lot.
If you need more info just ask. :-)
Alright, I'm gonna ask.. :) I just tried to make it with both Altova XMLSpy and oXygen 7.1... The result I get isn't very impressive.. I used the docbook.xsl file. Output: <!-- --> <!----> Kinda depressing.. -- Anders Norrbring Norrbring Consulting
Hi Anders, On Monday 29 May 2006 12:03, Anders Norrbring wrote:
Thomas Schraitle skrev: [...]
Output: <!-- --> <!---->
Make an update and try it again, please. It is far from being finished but it produces a better output now. :) Have fun, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.opensuse.org
Thomas Schraitle skrev:
Hi Anders,
On Monday 29 May 2006 12:03, Anders Norrbring wrote:
Thomas Schraitle skrev: [...]
Output: <!-- --> <!---->
Make an update and try it again, please. It is far from being finished but it produces a better output now. :)
At least I got an output.. :) The errorlist from the conversion is attached. -- Anders Norrbring Norrbring Consulting No template matches quote in entry. No template matches command in entry. No template matches option in entry. No template matches quote in entry. No template matches parameter in entry. No template matches quote in entry. No template matches cmdsynopsis in entry. No template matches filename in entry. No template matches quote in entry. No template matches menuchoice in entry. No template matches quote in entry. No template matches ulink in entry. WARNING: Unknown Element guimenuitem in mode="wrap" WARNING: Unknown Element itemizedlist in mode="wrap" WARNING: Unknown Element itemizedlist in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element itemizedlist in mode="wrap" No template matches subtitle in sect2. WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" No template matches subtitle in sect2. WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element caution in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element tip in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element itemizedlist in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element parameter in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element orderedlist in mode="wrap" WARNING: Unknown Element itemizedlist in mode="wrap" WARNING: Unknown Element variablelist in mode="wrap" WARNING: Unknown Element variablelist in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element variablelist in mode="wrap" WARNING: Unknown Element variablelist in mode="wrap" WARNING: Unknown Element variablelist in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element itemizedlist in mode="wrap" WARNING: Unknown Element screen in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" No template matches blockquote in sect1 (fdl-using). WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap" WARNING: Unknown Element link in mode="wrap"
Hi Anders, On Monday 29 May 2006 14:10, Anders Norrbring wrote:
Thomas Schraitle skrev: [...]
Make an update and try it again, please. It is far from being finished but it produces a better output now. :)
At least I got an output.. :) The errorlist from the conversion is attached.
Thank you. I will go through it this week or next week. Bye, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.opensuse.org
Thomas Schraitle skrev:
Hi,
On Monday 29 May 2006 11:21, Anders Norrbring wrote:
[...]
------- [1] https://forgesvn1.novell.com/svn/novdoc/trunk/xslt/db2mediawiki I'll take a look at it! Thanks a lot.. :) I saw before me that I had to edit 3000 lines manually.. Gah..
Hehe. :) Depending on your DocBook source you will find bugs in the output (well it's alpha). At the moment it is not very well documented and it relies somewhat on openSUSE Wiki page. For example, admonition boxes like tip, warning, etc. are build through a openSUSE Wiki template. That simplifies the transformation process a lot.
If you need more info just ask. :-)
Aah... I have a too well-defined book I guess.. :) I just ran it with xsltproc and got this: beata:~/wiki # xsltproc --output file.wiki novdoc/docbook.xsl file.xml No template matches article in book (index). No template matches appendix in book (index). No template matches appendix in book (index). No template matches appendix in book (index). No template matches appendix in book (index). -- Anders Norrbring Norrbring Consulting
Hi Anders, On Monday 29 May 2006 12:07, Anders Norrbring wrote:
Thomas Schraitle skrev:
[...] If you need more info just ask. :-)
Aah... I have a too well-defined book I guess.. :) I just ran it with xsltproc and got this:
beata:~/wiki # xsltproc --output file.wiki novdoc/docbook.xsl file.xml No template matches article in book (index). No template matches appendix in book (index). No template matches appendix in book (index). No template matches appendix in book (index). No template matches appendix in book (index).
Yes, book is not very well supported at the moment. I think of a kind of "chunking mechanism" like in HTML, but in Wiki it's more complicated. Better transform it chapter-wise. You can use the rootid feature like this: xsltproc --output file.wiki --stringparam rootid "CHAPTER_ID" \ db2mediawiki/docbook.xsl file.xml Replace the CHAPTER_ID with the id of your corresponding chapter. Roughly speaking lists, figures and some inline elements should be supported, probably not all DocBook features. If the stylesheets encounter an unknown element it will print the above message to inform the user. Hope that helps, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.opensuse.org
Thomas Schraitle skrev:
Hi Anders,
On Monday 29 May 2006 12:07, Anders Norrbring wrote:
Thomas Schraitle skrev:
[...] If you need more info just ask. :-) Aah... I have a too well-defined book I guess.. :) I just ran it with xsltproc and got this:
beata:~/wiki # xsltproc --output file.wiki novdoc/docbook.xsl file.xml No template matches article in book (index). No template matches appendix in book (index). No template matches appendix in book (index). No template matches appendix in book (index). No template matches appendix in book (index).
Yes, book is not very well supported at the moment. I think of a kind of "chunking mechanism" like in HTML, but in Wiki it's more complicated.
Better transform it chapter-wise. You can use the rootid feature like this:
xsltproc --output file.wiki --stringparam rootid "CHAPTER_ID" \ db2mediawiki/docbook.xsl file.xml
Replace the CHAPTER_ID with the id of your corresponding chapter. Roughly speaking lists, figures and some inline elements should be supported, probably not all DocBook features. If the stylesheets encounter an unknown element it will print the above message to inform the user.
I'll give it another shot.. I prefer working in oXygen on my Windows box, but I'll do some testing on both platforms. I'll send you the pack of xml files for inspection, they're currently drafts since most id elements are missing. But I thought maybe you can find the time to give some pointers? -- Anders Norrbring Norrbring Consulting
Hi Anders, On Monday 29 May 2006 12:54, Anders Norrbring wrote:
Thomas Schraitle skrev:
[...] Replace the CHAPTER_ID with the id of your corresponding chapter. Roughly speaking lists, figures and some inline elements should be supported, probably not all DocBook features. If the stylesheets encounter an unknown element it will print the above message to inform the user.
I'll give it another shot.. I prefer working in oXygen on my Windows box, but I'll do some testing on both platforms.
Sure. It's very handy to create a transformation scenario with oXygen but you need to connect the XSLT stylesheet with the XML file.
I'll send you the pack of xml files for inspection, they're currently drafts since most id elements are missing. But I thought maybe you can find the time to give some pointers?
That would be very helpful. I am not sure if I find time today but I will look at it as time permits. Thanks, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.opensuse.org
Thomas Schraitle skrev:
Hi Anders,
On Monday 29 May 2006 12:54, Anders Norrbring wrote:
Thomas Schraitle skrev:
[...] Replace the CHAPTER_ID with the id of your corresponding chapter. Roughly speaking lists, figures and some inline elements should be supported, probably not all DocBook features. If the stylesheets encounter an unknown element it will print the above message to inform the user. I'll give it another shot.. I prefer working in oXygen on my Windows box, but I'll do some testing on both platforms.
Sure. It's very handy to create a transformation scenario with oXygen but you need to connect the XSLT stylesheet with the XML file.
I'll send you the pack of xml files for inspection, they're currently drafts since most id elements are missing. But I thought maybe you can find the time to give some pointers?
That would be very helpful. I am not sure if I find time today but I will look at it as time permits.
Is the XSLT stylesheet specific to the novdoc DTD? I just switched from DocBook 4.4 to NovDoc, and naturally just about nothing validates.. :) I guess I have some work to do here.. -- Anders Norrbring Norrbring Consulting
Hi Anders, On Monday 29 May 2006 13:26, Anders Norrbring wrote:
Thomas Schraitle skrev: [...]
Is the XSLT stylesheet specific to the novdoc DTD?
Yes. Although NovDoc and DocBook shares the same element names the stylesheets can create unpredited results if they encounter unusual structures.
I just switched from DocBook 4.4 to NovDoc, and naturally just about nothing validates.. :)
Yes, that can be expected. :) The NovDoc DTD is more strict in some content modells and it contains less elements and attributes than the DocBook DTD. We use it as an exchange DTD between us and different teams at Novell. However for some kind of documents it might be too strict.
I guess I have some work to do here..
I looked at your document. Is's perfectly valid but personally I would avoid mixing block elements (for example orderedlist) inside a para. Although it is valid to write that in DocBook is not possible in Novdoc. Separate these things would be create better results. Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.opensuse.org
Thomas Schraitle skrev:
Hi Anders,
On Monday 29 May 2006 13:26, Anders Norrbring wrote:
Thomas Schraitle skrev: [...]
Is the XSLT stylesheet specific to the novdoc DTD?
Yes. Although NovDoc and DocBook shares the same element names the stylesheets can create unpredited results if they encounter unusual structures.
I just switched from DocBook 4.4 to NovDoc, and naturally just about nothing validates.. :)
Yes, that can be expected. :) The NovDoc DTD is more strict in some content modells and it contains less elements and attributes than the DocBook DTD. We use it as an exchange DTD between us and different teams at Novell. However for some kind of documents it might be too strict.
I guess I have some work to do here..
I looked at your document. Is's perfectly valid but personally I would avoid mixing block elements (for example orderedlist) inside a para. Although it is valid to write that in DocBook is not possible in Novdoc. Separate these things would be create better results.
Yeah.. This document has been put together rather hasty.. I'll clean it up, and use the novdoc DTD just to make sure it's valid for Novell/SUSE documentations, it's really no big deal.. It's not like it's a 600 page book. :) -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
Is the XSLT stylesheet specific to the novdoc DTD? I just switched from DocBook 4.4 to NovDoc, and naturally just about nothing validates.. :) I guess I have some work to do here..
please, if ever you reach a viable result, document it on the wiki, even incomplete results would be great. Having a toolchain between doc and the wiki is of vital importance in my opinion. thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
jdd skrev:
Anders Norrbring wrote:
Is the XSLT stylesheet specific to the novdoc DTD? I just switched from DocBook 4.4 to NovDoc, and naturally just about nothing validates.. :) I guess I have some work to do here..
please, if ever you reach a viable result, document it on the wiki, even incomplete results would be great. Having a toolchain between doc and the wiki is of vital importance in my opinion.
I'll try to.. :) Right now I'm struggling with revalidating my DocBook v4.4 document to be NovDoc compaible. *gah* One hassle I just don't seem to get is how to define the target point for xref. xref looks just like in DocBook, but it would be REALLY nice if I knew how to set the target to make the jump.. -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
jdd skrev:
Anders Norrbring wrote:
Is the XSLT stylesheet specific to the novdoc DTD? I just switched from DocBook 4.4 to NovDoc, and naturally just about nothing validates.. :) I guess I have some work to do here..
please, if ever you reach a viable result, document it on the wiki, even incomplete results would be great. Having a toolchain between doc and the wiki is of vital importance in my opinion.
I'll try to.. :) Right now I'm struggling with revalidating my DocBook v4.4 document to be NovDoc compaible. *gah*
One hassle I just don't seem to get is how to define the target point for xref. xref looks just like in DocBook, but it would be REALLY nice if I knew how to set the target to make the jump..
last time I did some docbook, I did it with vi, I could never make an editor work for that task :-( for 4 pages doc, it's not a real problem, but for more... so your experience is great :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
Hi, On Monday 29 May 2006 17:35, Anders Norrbring wrote:
[...] One hassle I just don't seem to get is how to define the target point for xref. xref looks just like in DocBook, but it would be REALLY nice if I knew how to set the target to make the jump..
Could you show me an example where do you have difficulties? Bye, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.opensuse.org
Thomas Schraitle skrev:
Hi,
On Monday 29 May 2006 17:35, Anders Norrbring wrote:
[...] One hassle I just don't seem to get is how to define the target point for xref. xref looks just like in DocBook, but it would be REALLY nice if I knew how to set the target to make the jump..
Could you show me an example where do you have difficulties?
Well, as I mentioned in the private e-mail, it's the rareness of the ID attribute that I miss, but then, it's just a matter of rethinking what and how you write the document! -- Anders Norrbring Norrbring Consulting
participants (3)
-
Anders Norrbring -
jdd -
Thomas Schraitle