ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re[2]: Enabling protruding
Date: Thu, 24 Jan 2002 11:32:27 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20020124112706.039925c0@server-1> (raw)
In-Reply-To: <919194372.20020123194446@bigfoot.com>

At 07:44 PM 1/23/2002 +0100, Giuseppe Bilotta wrote:

>Nothing doing. I tried the following small test file
>
>\setupfontsynonym[Serif][handling=pure]
>\setupfonthandling[normal][left=1,right=1]
>
>\starttext
>
>\def\text{This is some kind of test, to see if it hangs,
>thisisaverylongwordindeed. }
>
>\dorecurse{20}{\text}
>
>\setupalign[hanging]
>\dorecurse{20}{\text}
>
>\stoptext
>
>and no hanging is done.

interesting, took me a while to identify the problem (has to do with empty 
parameter). I'll send you a new syst-gen.tex to test.

now, to the hanging: one complication is that once a font is 'defined', its 
characteristics are kind of fixed; i could remove this limitation but it 
would not help at all, since hanging get fixed in tex itself. this means 
that for the preloaded cmr fonts, (or any preloaded font) one has to 
redefine them; also, because of the design sizes, cmr's are not mapped onto 
Serif, so here we need to manually set the fonts (unless one defines them 
as any ps collection, ignoreing the design size)

% output=pdftex

\setupfontsynonym[cmr10][handling=pure]
\setupfontsynonym[Serif][handling=pure]
\setupfonthandling[normal][left=1,right=1]

% so here we load 'm again

\usetypescript[cmr] \setupbodyfont[10pt]

% handy for tracing the hanging

\showframe

% off we go

\starttext
   \dorecurse{100}{testtest, }
   \setupalign[hanging]
   \dorecurse{100}{testtest, }
   \setupbodyfont[pos,10pt]
   \dorecurse{100}{testtest, }
\stoptext
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                                   fall-back web server: 
www.pragma-pod.nl
-------------------------------------------------------------------------


  reply	other threads:[~2002-01-24 10:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23 16:28 Giuseppe Bilotta
2002-01-23 17:21 ` Hans Hagen
2002-01-23 18:44   ` Re[2]: " Giuseppe Bilotta
2002-01-24 10:32     ` Hans Hagen [this message]
2002-01-24 11:10       ` Re[3]: " Giuseppe Bilotta
2002-01-24 13:45         ` Hans Hagen
2002-01-24 15:36           ` Taco Hoekwater
2002-01-24 16:05             ` Hans Hagen
2002-01-25 14:47               ` Re[5]: " Giuseppe Bilotta
2002-04-15 11:08         ` no hanging punctuation Albrecht Kauffmann
2002-04-18  9:05           ` Lutz Haseloff
2002-04-18 10:19             ` Patrick Gundlach
2002-04-18 10:33               ` Lutz Haseloff
2002-04-18 12:10                 ` Bill McClain
2002-01-25 15:38       ` Enabling protruding Bill McClain
2002-01-25 16:15         ` 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=5.1.0.14.1.20020124112706.039925c0@server-1 \
    --to=pragma@wxs.nl \
    --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).