On Monday 26 September 2005 20:43, Bryce Harrington wrote:
> On Mon, Sep 26, 2005 at 08:17:36PM +0200, Craig Bradney wrote:
> > On Monday 26 September 2005 09:19, bulia byak wrote:
> > > On 9/25/05, Bryce Harrington <bryce@...> wrote:
> > > > Anyway, to summarize:
> > > >
> > > > 1. Ditch ill2svg.pl. It sucks.
> > > > 2. Encourage scribus to implement -i / -e and add it as an
> > > > extension. Scribus kicks ass.
> > >
> > > I agree. Scribus really needs command line facilities. But for those
> > > who can't or don't want to install all of Scribus, perhaps we can keep
> > > ill2svg as the last resort.
> > I dont think installing Scribus is a major issue on any system, however
> > for us to support many more command line options is a little hard without
> > the GUI right now.
> > I've done a lot of cleaning in preparation for this stuff, and Craig
> > Ringer and Peter Vanek have rewritten the plugin systems, and we prepare
> > even more for 1.3.2cvs. Perhaps it might be possible in 1.3.2cvs to do
> > some conversion, you never know, although the GUI will still be required
> > as theres a lot of cide that is directly tied to the canvas/scrollview at
> > this point in time.
> Cool. Is 1.3.2cvs likely to be released within the next couple months
> or so?
2 months, minimum I'd say. We plan a lot of disruption in CVS at times. Major
classes will hopefully be rewritten, if we have the time, plus a possible
move away from autotools. The initial work on migrating loading and saving
into plugins has begun and will start in earnest when we close off 1.3.1
(this week hopefully).
> I think as a starting point it's probably fine if the GUI is required,
> so long as the operation can be automated. I'd guess 99% of the time
> the user will be running Inkscape in GUI mode for this anyway.
> Another thing that will be needed is a way to specify which format to
> use. E.g., something like
> $ scribus -i myfile.ai -I EPS -e myfile.svg -E SVGTiny
> Or whatever. Of course, also would need a way to get a list of what
> formats scribus supports. scribus --list-formats or something...
Scribus understands "SVG", ie, whatever tags have been coded in, it might go a
good way to getting them right. For a lot of things, the SVG importer either
needs fixing, adding to or rewriting. I think major work on it will depend on
some other work, like a rewrite of our pageitem class.
> It'd also be nice to have it able to auto-detect based off the mimetype
> and/or filename extension (there's probably a library to do this).
> However, being able to manually specify the format would be useful -
> sometimes those detectors don't work 100%, and with all the variants
> there are of postscript I could easily imagine that to be an issue for
> scribus users. Thus it'd probably be easier to go with the manual
> specification of available formats for now - from how scribus' menu
> stuff works, I imagine this would be the simpler thing to implement
> anyway. Also, there are enough tools out there to detect file formats
> independently (e.g., `file`, `mimetype`, etc.) that this could easily be
> scripted in a scribus wrapper.
Yes, we can either add a dependency or pull in only the necessary code for our
needs. Shouldn't be a major deal. We need cross platform solutions though,
however I guess that stuff is pretty basic these days to port if its not