[scribus-dev] Fwd: Re: Scribus implementation

JLuc jluc at no-log.org
Tue Apr 22 06:54:32 UTC 2014


Le 22/04/2014 03:58, Saravanan Kuppusamy a écrit :
> I hope the forum found the email I sent (fount below). I am very grateful if you could advise me on that please.

Using scribus would require to upgrade your tools and workflow accordingly.

JLuc
>
>
> On Tue, Apr 15, 2014 at 9:53 PM, Saravanan Kuppusamy <sarankup at gmail.com
> <mailto:sarankup at gmail.com>> wrote:
>
>     Dear ciao,
>
>     Many thanks for your detailed responses. We understand that the Scripter via Python. As I mentioned initially, we
>     uses XML for typesetting in InDesign application. InDesign helps in in preserving XML as below. For example,
>
>     [1] XML from our client will be like the below:
>     <author><firstname>Saravanan</firstname><lastname>Kuppusamy</lastname></author>
>
>     [2] Through XSLT, we generate XML as below (This XML will be imported into InDesign template):
>     <author><firstname>Saravanan</firstname><x>, </x><lastname>Kuppusamy</lastname></author>
>
>     [3] Inside of InDesign, our operator will make some corrections like changing the content as below (We should update
>     the content inside of InDesign, and no-excuse in our business):
>     <author><firstname>Saran</firstname><x>, </x><lastname>Kuppusamy</lastname></author>
>
>     [4] After PDF is done from InDesign, we export the XML from InDesign for other online products like EPUB, HTML, etc.,
>     <author><firstname>Saran</firstname><lastname>Kuppusamy</lastname></author>
>
>     The biggest advantage of InDesign here is, InDesign preserves XML as is. The [1] and [2] process is managed outside
>     of InDesign, but not [3] and [4]. Does Scribus supports [3] an [4] process? This question is really the deciding
>     factor for me.
>
>     If you could educate me on this, would be more grateful. Thanks in advance.
>
>
>     On Tue, Apr 15, 2014 at 6:45 PM, a.l.e <ale.comp_06 at xox.ch
>     <mailto:ale.comp_06 at xox.ch>> wrote:
>
>         hi,
>
>             If anyone replies to this, please CC to Saravanan. I don't know how to
>             answer his questions.
>
>
>         since saravanan posted his question to this list, i must think that he is reading the answers... but let's put
>         him / her in CC: to make sure that the answer gets through.
>
>         the easiest way to do automation inside of scribus is to use the scripter, which uses python. this means that
>         you have access to all python's library to manage your xml and create your scribus documents.
>
>         there are some commands missing in the scribus "API"m but you seem to be ready to put your hands in the engine
>         to extend it... and this should not be that hard, either!
>
>         finally, you can also create plugins by using c++. as cédric wrote, scribus is already using much XML
>         internally, so you should not have a hard time figuring out how to create your own importers and exporters.
>
>         just ask if you need more hints and help!
>
>         ciao
>         a.l.e
>
>
>
>
>





More information about the scribus-dev mailing list