<x-flowed>[EMAIL PROTECTED], 2001-03-23 15:02 +0430
>Jack Coates LRP-QoS How-to document makes me think about the question of
>how-to LEAF documentation should be structured. There are obviously two
>aspects to this question:
>1/ A technical one
>This one is already solved from what I understand from the list: DocBook
>(XML version ?) is the way to go. As far as I am concerned it just means
>spending some time in the doc to understand how that works :-)
Jacques,
I don't want to force authors to use DocBook XML, but I do want us to make
as many of them as possible available in this format. To facilitate this
I'm converting Guides to DocBook XML. After they're converted I want to
place the DocBook XML source in CVS. If you want to help with this, add
yourself to task_id 21161. I could use the help. :)
https://sourceforge.net/pm/task.php?group_project_id=5259&group_id=13751
>2/ A document organisation issue
>Is there any direction / standard document structure we should try to
>adopt as far as the different chapters are concerned ? I think it would be
>a great help for the LEAF users to find some kind of structured
>documentation especially for the different packages(considered
>traditionnally as a weak point of LRP project)
For documents I've helped author, I tried to follow the structure outlined
by the LDP for Guides and HOWTOs. see
http://linuxdoc.org/LDP/LDP-Author-Guide/
>What do you think?
Structure is good, as long as it doesn't prevent document creation.
--
Mike Noyes <[EMAIL PROTECTED]>
http://leaf.sourceforge.net/
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
</x-flowed>
