From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: "fake" space for better reflow
Date: Wed, 30 Nov 2016 17:58:17 +0100 [thread overview]
Message-ID: <13brzj3asikey$.dlg@nililand.de> (raw)
In-Reply-To: <da039816-8ccb-4218-ca61-130c8e60959a@wxs.nl>
Am Wed, 30 Nov 2016 12:45:17 +0100 schrieb Hans Hagen:
> On 11/30/2016 10:09 AM, Ulrike Fischer wrote:
>> If I compile a small document
>>
>> \starttext
>> \input knuth
>>
>> \stoptext
>>
>>
>> and then use in the adobe reader "view->zoom->reflow" I get as
>> result
>>
>> Thus,Icametotheconclusionthatthedesignerofanewsystemmustnotonlybetheimplementerandfirstlarge--scaleuser;thedesignershoulda
> Cut and paste goes well so I think it's a bug in acrobat then.
I'm not sure. Imho cut and paste use an heurisitic more or less
based on the size of the space (there are quite a number of
questions on tex.SX where the heuristic fails, e.g. in code
listings), while reflow seems to need glyphs. The speech of Ross
Moore on TUG14 seems to indicate that \pdfinterwordspaceon was
introduced in pdftex to get around this problem.
http://river-valley.zeeba.tv/%E2%80%9Cfake-spaces%E2%80%9D-with-pdftex%E2%80%94best-of-both-worlds/
>> I know it is due to the missing space glyph. With pdflatex I would
>> try to use \pdfinterwordspaceon but this primitive never found its
>> way into luatex. Is there any solution? (One that could be
>> translated to lualatex would be best).
> One can write a filter that does it before shipout. Typically a case for
> callbacks.
Well the main question is, what is the "does it" in this case.
pdftex inserts a space from a dummy.pdf. One use the fake space more
or less like this:
\pdfinterwordspaceon
\pdfmapline{=dummy-space <dummy-space.pfb}
\pdfglyphtounicode{space}{0020}
XXX YYY
\bye
But this doesn't sound like the correct way to go in a unicode/open
type world.
(I'm also not quite if shipout is the correct time. Imho one would
probably avoid to add spaces e.g. in math).
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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:[~2016-11-30 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 9:09 Ulrike Fischer
2016-11-30 11:45 ` Hans Hagen
2016-11-30 16:58 ` Ulrike Fischer [this message]
2016-11-30 21:18 ` 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='13brzj3asikey$.dlg@nililand.de' \
--to=news3@nililand.de \
--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).