> Please don't try to determine the workflow for everyone from a family to a > high end publishing company. There's no reason, if we can have a export > function, that people should not be able to use it. It might not be perfect > and it might not be ideal in everyone's eyes but the world isn't like that.
High end publishing company??? My experience from publishing comes from trying to get my documents to print nicely on an old used inkjet printer. I have never worked commercially with publishing, everything I know absout publishing is self learned from books and the Internet (much of it from this mailing list). What I do know about is conversions between different formats. I learned about how smart HTML was 20 years ago, I cried when almost every good part of HTML was destroyed by HTML3. While looking for solutions for multiple ways of publication I found SGML, XSLT, DocBook and similar solutions. Their main disadvantage were that they lacked WYSIWYG. And what I am saying is that it is virtually impossible to create an export function that does what people expect from it, because the content of a Scribus document is not structured enough to allow for a decent export logic. Sure, if someone wants to, write that export function. But please, don't give people expectations that it will create a finished ebook from a Scribus document. We already see problems with people thinking it is a PDF editor, if people also start thinking it's an ebook editor we will get even more disappointed users. Stick to the main task: Page layout. There are other tools for other tasks. /Peter