[Scribus] Docbook XML import

PLinnell mrdocs
Mon Apr 4 23:14:56 CEST 2005


On Monday 04 April 2005 22:44, Phil Hughes wrote:
<more snipping>
> Uninteresting stuff (that I wrote) deleted.
>
> > Hi,
> >
> > This one flew right by me and sorry for the slow reply.
> >
> > There is no native Docbook import filter yet for Scribus.
> >
> > That said, the Open Office importer works quite well and will
> > inherit OO styles. I have a suspicion this might work well given
> > the relative simplicity of the xml you have described.
> >
> > http://xml.openoffice.org/ has many different xml filters for OO,
> > which could used to transform Docbook > OO > Scribus Text import.
> > Note 1.2.2cvs which is a stable branch of CVS has added Open
> > Office 2.0 support.
> >
> > With some carefully created Scribus document templates, you might
> > find the text will import with your pre-set fonts,sizes and style
> > intact.
> >
> > All of this will work with 1.2.2cvs (stable). We have snapshots
> > of 1.2.2cvs on www.scribus.net and rpms and debs are available.
> >
> > Do let us know how you fare.
> >
> > Cheers,
> > Peter
>
> This will be a production situation, TUX will be monthly starting
> in May and it is also the way we do Linux Journal so getting rid of
> the Open Office step would be a real plus. We have been using the
> same vi with key maps -> Docbook XML
> sequence for a while now. We wrote the other tools to product
> Quark, HTML, ... so I am not scared to tackle this as a programming
> project.
>
> My Scribus knowledge, however, is on the low end. So, what is the
> most logical approach would be the biggest help. Early on, it felt
> like doing this in two pieces made the most sense.
>  1. Clean up the Docbook XML getting rid of all the stuff that we
>     don't need.
>  2. Write import filters for the paragraph types.
>
> Does that make sense? If not, we (that means me or Mitch, the guy I
> will sucker into doing any hard work) are pretty fearless of having
> to write code in virtually any language--Mitch leaning toward C++
> and me toward Python.
>
> Thanks.

Yes, it does make sense and you can use python or c++ to write a 
custom scribus import plug-in.

The gettext plug-in has been written to facilitate additional text 
imports.

Please take a look here: 
http://docs.scribus.net/index.php?lang=en&sm=gettexthowto&page=gettexthowto

For in-depth discussion on IRC, please note all the devels save one 
are on Central European Time.

Let us know how we can help.

Peter





More information about the scribus mailing list