OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] CSS based docbook editor

On Fri, 02 Apr 2010 15:46:59 +0200
Nathalie Sequeira <n@n-faktor.net> wrote:

> >> - can validate document structure against docBook in general and
> >> check for required elements within the specific library project
> >>     
> > What does that mean?
> > oXygen can validate against the docboook schema, and any
> > extensions you apply to docbook
> >   
> To be more precise, what I mean is that it would be great if the
> editor were able to check that information needed for the database
> used  for library queries is included:
> When we upload the docBooks to the server, metadata we have in 
> <bookinfo> is inserted in the database, allowing for subject, author, 
> text type, etc. searches and filtering. Beyond validation against 
> docBook schema, it would be useful if the editor could check whether
> - for example - <bibliosource> has a relation in place defining the
> text type. Would that already  be an extension of docbook?

No. Not a normal 'validation' task.
You need Schematron or similar validator for this kind of action.
Definitely not an editor task. 

> >> - And especially:
> >> ability to import and transform rtf documents preformatted in a 
> >> specified way by contributing authors 
> >>     
> >
> > don't look for that in an editor. It is not an editors task?
> > That is a transform task. 
> >   
> Oh dear.
> We are currently using an ancient instance of  logictran r2net to 
> convert to docbook, but we need to validate the result every time
> (and often repeatedly, going back to the rtf if errors arise,
> editing, reconverting, and revalidating...), so I was hoping to find
> a one-stop solution to simplify our publication procedure.
> But that seems to be out of the question.

You might use something to 'pipeline' the tasks?
so that, to the user, it looks like one action.
Definitely not an editor task though. 
rtf to docbook is possible though. Steve?

> Is there any "state-of-the-art" path to follow, or anything we should 
> watch out for, in cases where the original texts were written in word 
> processors and thus are formatted as doc / rtf etc.?

Identify what you want to do. 
List them separately.
Join the different tasks only
when you can do so easily.

That seems a simpler approach, better than looking
for a 'magic' tool that does everything, all at once!




Dave Pawson

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]