ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: ntg-context@ntg.nl
Subject: Re: new manual
Date: Wed, 27 Mar 2013 21:15:25 +0100	[thread overview]
Message-ID: <20130327211525.5cc3e680@aga-netbook> (raw)
In-Reply-To: <5152E85A.1060404@wxs.nl>

Dnia 2013-03-27, o godz. 13:38:50
Hans Hagen <pragma@wxs.nl> napisał(a):

> Hi,
> 
> I uploaded a work-in-progress manual:
> 
> http://www.pragma-ade.com/general/manuals/fonts-mkiv.pdf

I have to say that I am *very* impressed.

1. Aesthetically, this seems to be the most beautiful of ConTeXt
manuals.

2. I've only read half a page, but the style also seems to be very nice
- the introduction was just great.

3. From the number of pages and the table of contents I assume that
I'll be able to learn a lot about fonts from this - and that's great!

Now the file has been sent to my Kindle, and the only thing I'm afraid
of is the reading experience on 6"...  Hans, I know that you don't like
(today's) ebook readers, but what about preparing a version with larger
fonts/smaller margins for us Kindle users?  Given the typographical
quality of most Kindle ebooks, you may assume that when we read on
a Kindle, we don't care too much about aesthetics (which, btw, is
incomprehensible for me: the technology to typeset text automatically
in an (at least) decent way (including hyphenation) has been around for
some 30 years, and yet they didn't manage to do it right...), so you
might just change a few things in \setuplayout etc. and throw it into
the net...

> Hans

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2013-03-27 20:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 12:38 Hans Hagen
2013-03-27 19:54 ` Mikael Morin
2013-03-28  1:14   ` Hans Hagen
2013-03-27 20:15 ` Marcin Borkowski [this message]
2013-03-27 21:58   ` Hans Hagen
2013-04-02 19:36 ` Willi Egger
2013-04-11 16:50   ` Giulio Bertellini
  -- strict thread matches above, loose matches on Subject: below --
2013-04-11 21:42 Vyatcheslav Y.
2003-12-18 15:58 Hans Hagen
2003-12-18 16:48 ` David Arnold
2003-12-23 12:18 ` Nigel King
2003-12-23 12:39   ` Hans Hagen
2003-12-23 13:16     ` Nigel King
2003-12-23 13:55       ` Hans Hagen
2003-12-23 15:20         ` Nigel King
2003-12-23 19:50           ` Hans Hagen
2003-12-23 14:29       ` Janko Hauser
2003-12-23 12:41   ` Felix Franz
2003-12-23 14:14   ` Tobias Burnus
2002-12-02 13:47 Hans Hagen
2002-12-02 15:59 ` Tobias Burnus
1998-08-12 17:32 Hans Hagen

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=20130327211525.5cc3e680@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --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).