From: Kip Warner <kip@thevertigo.com>
To: hajtmar@gyza.cz
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Scribus vs ConTeXt
Date: Tue, 28 Feb 2012 16:43:17 -0800 [thread overview]
Message-ID: <1330476197.3130.2.camel@kip-laptop> (raw)
In-Reply-To: <4F4D371A.3070204@gyza.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
On Tue, 2012-02-28 at 21:20 +0100, Jaroslav Hajtmar wrote:
> Hello,
> I work quite often with Scribus (but I am not expert). I use it mainly
> to leaflets, posters (great tools for posters for me) and other similar
> things that contain a lot of graphics, overlays, etc. I can imagine
> writing a small magazine with lots of images, etc. For extensive work
> (thesis and large documents with a large majority of the text) in the
> Scribus current version can not imagine it. Those who can not nothing in
> TeX or ConTeXt Scribus is an interesting option. It's clickable tool
> that allows to one who does not understand typography and not feeling
> for it do make a nice shit.
> Typography expert can produce very nice documents. Or also, someone who
> has a great feel for typography.
> Scribus is developing quite quickly and quite well with developers
> trying to improve it. For some time it will definitely be a tool that
> can tread on the heels of InDesign
>
> Jaroslav Hajtmar
Thanks Jaroslav. That was comprehensive.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-29 0:43 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
2012-02-29 0:43 ` Kip Warner [this message]
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=1330476197.3130.2.camel@kip-laptop \
--to=kip@thevertigo.com \
--cc=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).