From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: ntg-context@ntg.nl
Subject: Re: Scribus vs ConTeXt
Date: Tue, 28 Feb 2012 23:40:46 +0100 [thread overview]
Message-ID: <4F4D57EE.5040208@gyza.cz> (raw)
In-Reply-To: <64FEA91F-C757-4BE9-81B2-599252394624@fiee.net>
You have generally right ... But I think that you must not take the
measure of the devilish speed the development rate of development of
ConTEXt :-)
I often I make a text document using the Context and the resulting PDF
document I put into Scribus. With Scribus I put graphics, titles etc.
For normal use Scribus is a good choice. But you have right - for
professional work in the end one needs a professional tool like InDesign
or QuarkXpress.
Jaroslav
Dne 28.2.2012 23:26, Henning Hraban Ramm napsal(a):
> But it still lacks a lot of essential features for professional work
> (at least in my area), e.g. usable master pages and nondestructional
> import of vector graphics (esp. PDF), CMYK and spot colors. Correct me
> if it gained these lastly - I know they're working on it, but the
> development speed is much much slower than ConTeXt’s. Maybe it’s more
> stable and reliable therefore...
>
> Scribus has at least one feature that sets it ahead of InDesign
> (besides being Open Source): render frames (similar functionality as
> ConTeX’s filter module - replace foreign sourcecode by its result).
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-02-28 22:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 19:34 Kip Warner
2012-02-28 19:43 ` Khaled Hosny
2012-02-29 0:43 ` Kip Warner
2012-02-28 20:20 ` Jaroslav Hajtmar
2012-02-28 22:26 ` Henning Hraban Ramm
2012-02-28 22:40 ` Jaroslav Hajtmar [this message]
2012-02-29 0:43 ` Kip Warner
2012-02-29 16:29 ` William Adams
2012-02-29 17:41 ` Marco Pessotto
2012-02-29 18:02 ` Michael Hallgren
2012-02-29 19:30 ` Martin Schröder
2012-02-29 19:40 ` Marco Pessotto
2012-02-29 20:08 ` Kip Warner
2012-02-29 20:35 ` Aditya Mahajan
2012-02-29 19:55 ` William Adams
2012-02-29 20:10 ` Kip Warner
2012-02-29 20:25 ` Henning Hraban Ramm
2012-02-29 21:02 ` Kip Warner
2012-03-01 12:56 ` William Adams
2012-03-01 16:15 ` Martin Schröder
2012-03-01 17:29 ` William Adams
2012-02-29 20:01 ` Khaled Hosny
2012-02-29 20:06 ` Kip Warner
2012-02-29 20:08 ` Kip Warner
2012-02-29 21:27 ` Alan Braslau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F4D57EE.5040208@gyza.cz \
--to=hajtmar@gyza.cz \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).