Am Freitag, 13. Juli 2007 00:31 schrieb Craig Ringer: > John R. Culleton wrote: > > On Thursday 12 July 2007 04:56, Jfo wrote: > >> Hi > >> > >> I believe that for Scribus to be really useful in the general DPT > >> community it must import Word and Word Publisher text and graphics > >> WITH FORMATTING. > > > > Do you mean Microsoft Publisher? I didn't think it was in serious use. > > I get documents in MS Publisher format from clients occasionally. Only, > of course, when they manage to avoid every warning they're given at > every step that the company can not and will not accept jobs designed in > Publisher because we can not guarantee decent quality reproduction. > > I've never seen a serious workflow involving Publisher.
Because it doesn't exist ;) > > > What Scribus needs most is a table formatter. TeX has several. Context > > alone has three. (Knuth plain tex, Wichura TaBle, Natural tables.) > > I also use the TeXsis table writer by itself for formatting invoices. > > so on table writing the score is TeX 4, Scribus 0. > > That's one of the big ones I see come up a lot here. Other biggies that > people mention a lot include: Is on the roadmap for 1.3.8. > > - Booklet printing / simple imposition (but workarounds exist) Is currently worked on in Summer of Code project. > - Performance tuning Is currently worked on. 1.3.5cvs has already remarkable improvements. > - Editable master pages There is already an acknowledged feature request in the bug tracker. > - Enhanced text handling (getting there nicely) > > People do mention Publisher import, but usually with a view to migration > > >from Publisher (in the hope they can avoid re-doing their layouts) > > rather than as something they want as part of their workflow. > > Of course, as we all know all this stuff is really hard and time > consuming :S http://steve-parker.org/articles/ms_publisher/ Cheers Christoph
