From: Hans Hagen <j.hagen@xs4all.nl>
To: Sandra Snan <sandra.snan@idiomdrottning.org>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: interline space default changed?
Date: Thu, 9 Jan 2020 15:07:52 +0100 [thread overview]
Message-ID: <d63fbab5-e573-162c-a407-833d360e7119@xs4all.nl> (raw)
In-Reply-To: <87ftgorbbq.fsf@idiomdrottning.org>
On 1/9/2020 2:47 PM, Sandra Snan wrote:
> Thank you so much for the swift reply, Hans. Much appreciated.
>
> Hans Hagen <j.hagen@xs4all.nl> writes:
>
>> On 1/9/2020 11:08 AM, Sandra Snan wrote:
>>> I was rerunning ConTeXt on some older documents and the interline space
>>> isn't the same. Sure, the new default looks great, but what was the old
>>> default? I need to match what I've already published. Thank you♥
>> The interlinespace is defined in 'ex' units so it depends on that value
>> in the font that you use ... maybe the font changed?
>
> That's certainly possible. I switched computers and distros so all of
> those things might've been refreshed or altered upstream. I'm using
> Junicode for the main & bold but with Tex Gyre Schola for italic, and
> then grabbing miscellaneoussymbols out of a DejaVu Serif fallback and
> using DejaVu Sans Mono for mono (althought this particular page doesn't
> have any mono). If it isn't that case that those fonts have changed
> their metrics, which I wouldn't know, I'm kinda out of the loop
> generally (#unplugged), I was thinking that maybe the culprit could be
> that it used to work off of the italic's ex height and now works off of
> the main's ex height but that's just wild guessing on my part.
if you still have the old installation you can do this someplace in the
file:
\the\dimex2.8ex % or whatever value you used for interlinespacing
and then use the reported value in the updated installation
> I'm working around the problem by setting the interline space to
> 3.0675ex which makes the recompiled pages match the previously compiled
> pages exactly. (I don't know why that number. I found it by trying every
> number and seeing what matched.) The previously compiled pages didn't
> have an interline space set.
>
> Thanks again.
>
> Sandra
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-01-09 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 10:08 Sandra Snan
2020-01-09 12:04 ` Pablo Rodriguez
2020-01-09 12:29 ` Hans Hagen
2020-01-09 13:47 ` Sandra Snan
2020-01-09 14:07 ` Hans Hagen [this message]
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=d63fbab5-e573-162c-a407-833d360e7119@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=sandra.snan@idiomdrottning.org \
/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).