From: MF <massifr@fastwebnet.it>
To: ntg-context@ntg.nl
Subject: Risposta: line correction
Date: Fri, 29 Sep 2017 11:53:13 +0200 [thread overview]
Message-ID: <1506678793.1786.37.camel@fastwebnet.it> (raw)
In-Reply-To: <2952da06-009f-6beb-fcfc-14b94b2e1ebe@wxs.nl>
> > In general, I'm ok without grid snapping, because the default
> > typesetting of taller formulas inside text is good enough for my
> > goals.
>
> for a bit more complex doc with many different unpredictable
> elements
> snapping seldom works ... we never use it (in production it often
> leads
> to more whitespace than one wants) ... the tex glue model is good
> enough
>
> (the requirement often comes from cases where snapping is the only
> way
> to get spacing right ... similar to the use of ragged right and no
> hyphenation because the used system can't handle it well ... in the
> worst case the limitations of a system then become undisputable
> 'good
> practice' and 'it's the default' and 'it's better for reader' etc)
>
So for quotations and adjust the space around them are you suggesting
manual adjustment?
I was already more convinced of keeping snap-to-grid turned off. Now
the problem is how to adjust the spaces around quotations (and floats)
at the minimum cost.
Since the line heights of the main text and the ones of quotations do
not change, the adjustment depends only on the number of lines of
quotations. I could compile a table for more common cases:
# of lines | adjustment
1 line | ... pt
2 lines | ... pt
3 lines | ... pt
...
20 lines | ... pt
I should teach users how to insert adjustments, but the task would be
eased because they should only copy a value from a table or insert a
name that corresponds the the number of lines (i.e. "adjust-3-lines",
"adjust-4-lines", etc.)
Greetings,
Massi
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-09-29 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 14:21 MF
2017-09-28 19:48 ` Henri
2017-09-28 21:30 ` mf
2017-09-28 21:47 ` luigi scarso
2017-09-29 8:33 ` Hans Hagen
2017-09-28 21:51 ` Henri
2017-09-28 21:55 ` Henri
2017-09-28 22:35 ` mf
2017-09-29 3:19 ` Rik Kabel
2017-09-29 9:30 ` Risposta: " MF
2017-09-29 12:08 ` Hans Hagen
2017-09-29 8:37 ` Hans Hagen
2017-09-29 9:53 ` MF [this message]
2017-09-29 21:38 ` Risposta: " Rik Kabel
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=1506678793.1786.37.camel@fastwebnet.it \
--to=massifr@fastwebnet.it \
--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).