[epo-core] List of supported projects
J. Shirley
jshirley at gmail.com
Mon Sep 15 18:50:43 BST 2008
On Mon, Sep 15, 2008 at 10:45 AM, Jesse Vincent <jesse at fsck.com> wrote:
>>
>> To try again, my work is not around formatting instead around cohesive
>> structure. The PseudoPod work is more targeting my comment about Pod
>> itself being a good reference format by expanding the offerings to
>> have singular pages have more substance beyond reference lists. It
>> doesn't address the notion that Pod documents are single documents and
>> there is no way to cohesively bind multiple pod documents together
>> outside of pod documents.
>>
> Ah, right. I believe the design criterion was that the data about how to
> bind multiple documents together should stay in the POD. When we wrote a
> book in PseudoPod, it had the bits we needed to do that. But was an aeon ago
> and I've burned those brain cells pretty hard.
>
> Anyway, having now mentioned that it exists and seen that you don't feel
> like it meets your needs, I'm happy to step back.
>
> -jesse
>
The main frustration that if you insert a chapter in between 10
chapters, you have to modify the ToC on all 10. Plus whatever other
indexes, and renumbering, etc.
To answer Matt's email about docbook, that may be better.
Just have docbook source pod (or rather use pod2docbook?) and then
additional conversion stuff, bypass any custom code and use the
various docbook renderers...
... or, we're getting to narrowly scoped in details. Let me rephrase
my original email :)
I think a good project to start with is a cohesive documentation
management utility or method that allows better structural integrity
at a higher level than what Pod provides without manually editing and
managing all of the relations between documents.
How's that? Then if it's agreed to focus on that, we can worry about specifics.
More information about the epo-core
mailing list