From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: \setupalign[flushleft] doesn't like ~
Date: Sat, 25 May 2013 12:53:47 +0200 [thread overview]
Message-ID: <20130525125347.6a046371@aga-netbook> (raw)
In-Reply-To: <517A3A3B.2010100@wxs.nl>
Dnia 2013-04-26, o godz. 10:26:35
Hans Hagen <pragma@wxs.nl> napisał(a):
> On 4/26/2013 2:26 AM, Marcin Borkowski wrote:
> > Dnia 2013-04-26, o godz. 01:45:37
> > Hans Hagen <pragma@wxs.nl> napisał(a):
> >
> >> On 4/26/2013 1:09 AM, Marcin Borkowski wrote:
> >>> With \setupalign[flushleft], nonbreakable spaces get larger than
> >>> they should. I'm afraid it's a bug.
> >>>
> >>> Best,
> >>>
> >>> An MWE:
> >>
> >> more info needed .. as this looks similar:
> >> [...]
> >
> > In both cases I get:
> >
> > 3.912pt+1.956pt-1.304pt
> > 3.912pt
> >
> > but in the latter one, the space produced by "~" is noticeably
> > wider.
>
> maybe you mean (non)frenchspacing
>
> \usemodule[ipsum]
>
> \showframe
>
> \starttext
>
> \setupalign[flushleft] \setupspacing[fixed] \ipsum \par
> \setupalign[flushleft] \setupspacing[packed] \ipsum \par
> \setupalign[flushleft] \setupspacing[broad] \ipsum \par
>
> \stoptext
>
> (defaults are language dependent)
Sorry for my delay - I was quite busy, now I got back to this.
It's not the question of \(non)frenchspacing.
This is indeed strange: I compiled this (with the newest ConTeXt):
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\starttext
Lorem ipsum dolor sit~amet, consectetur adipiscing elit. Donec euismod
mattis pellentesque. Duis ut ullamcorper sem. Sed varius neque quis
lacus hendrerit dapibus. Ut non elit eu nibh dignissim feugiat. Quisque
elementum lacinia pretium. Aliquam vel tellus in~ipsum lacinia
sagittis. Morbi vitae justo ante, sit~amet vulputate sem. Vivamus
faucibus ante vel dolor aliquet placerat. Ut pulvinar tellus sit~amet
augue congue dapibus. Donec justo odio, dignissim id rhoncus eget,
tristique at justo. Morbi quis libero id nisl malesuada aliquam non non
libero. Proin tristique ultricies ipsum, vel facilisis odio luctus
quis. Nullam tellus leo, posuere in~eleifend quis, lobortis eu sem.
In~hac habitasse platea dictumst. Suspendisse non quam a~ante mollis
dignissim. Class aptent taciti sociosqu ad litora torquent per conubia
nostra, per inceptos himenaeos.
\the\fontinterwordspace \font
+\the\fontinterwordstretch\font
-\the\fontinterwordshrink \font
\setbox\scratchbox\hbox{sit amet}\copy\scratchbox \the\wd\scratchbox\par
\setbox\scratchbox\hbox{sit~amet}\copy\scratchbox \the\wd\scratchbox
\setupalign[flushleft]
Lorem ipsum dolor sit~amet, consectetur adipiscing elit. Donec euismod
mattis pellentesque. Duis ut ullamcorper sem. Sed varius neque quis
lacus hendrerit dapibus. Ut non elit eu nibh dignissim feugiat. Quisque
elementum lacinia pretium. Aliquam vel tellus in~ipsum lacinia
sagittis. Morbi vitae justo ante, sit~amet vulputate sem. Vivamus
faucibus ante vel dolor aliquet placerat. Ut pulvinar tellus sit~amet
augue congue dapibus. Donec justo odio, dignissim id rhoncus eget,
tristique at justo. Morbi quis libero id nisl malesuada aliquam non non
libero. Proin tristique ultricies ipsum, vel facilisis odio luctus
quis. Nullam tellus leo, posuere in~eleifend quis, lobortis eu sem.
In~hac habitasse platea dictumst. Suspendisse non quam a~ante mollis
dignissim. Class aptent taciti sociosqu ad litora torquent per conubia
nostra, per inceptos himenaeos.
\the\fontinterwordspace \font
+\the\fontinterwordstretch\font
-\the\fontinterwordshrink \font
\setbox\scratchbox\hbox{sit amet}\copy\scratchbox \the\wd\scratchbox\par
\setbox\scratchbox\hbox{sit~amet}\copy\scratchbox \the\wd\scratchbox
\stoptext
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
and the numbers (widths) shown don't exhibit any discrepancies, but in
the pdf, the spaces are significantly wider (both in Evince and Adobe
Reader). OTOH, the \copy commands don't show any differences between
spaces and "ties".
Now I'm confused - but something is still wrong.
--
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-05-25 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 23:09 Marcin Borkowski
2013-04-25 23:45 ` Hans Hagen
2013-04-26 0:26 ` Marcin Borkowski
2013-04-26 8:26 ` Hans Hagen
2013-05-25 10:53 ` Marcin Borkowski [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=20130525125347.6a046371@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).