From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: negative kerning
Date: Mon, 18 Jan 2010 23:03:03 +0100 [thread overview]
Message-ID: <71D658B7-12A0-4BF2-8C14-1362F6116422@uni-koblenz.de> (raw)
In-Reply-To: <4B549D04.60002@wxs.nl>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
Am 18.01.2010 um 18:40 schrieb Hans Hagen:
> On 18-1-2010 18:28, Horacio Suarez wrote:
>>
>> hello all:
>>
>> I need someting like a negative kerning to reduce some paragraphs length.
>>
>> I was reading the mails but I didn´t find it or was too complex for me.
>
> otherwise you need to locally mess around with tolerance and penalties or the width of a space
What is the best way to „mess around“? Is it preferable (if changing the text or layout is no option) to set a bigger inter-word space or a more tolerant expansion or both?
The latter I tried to achieve, but with no luck (attachment).
[-- Attachment #2: test-sloppypar2.tex --]
[-- Type: application/octet-stream, Size: 1051 bytes --]
\setuplayout[width=middle,header=0pt,footer=0pt]
\startluacode
fonts.expansions.classes['big-expansion'] = {
stretch = 4, shrink = 4, step = .5, vector = 'default', factor = 5
}
\stopluacode
\definefontfeature
[extraexpansion][default]
[expansion=big-expansion]
\usetypescript[pagella]
\setupbodyfont[pagella,13.4pt]
% \setupalign[hz,hanging,stretch]
\definetolerancemethod
[horizontal] [extraspace]
{\spaceskip.35em plus.25em minus.2em\relax}
\definetolerancemethod
[horizontal] [extrastretch]
{\emergencystretch=18pt}
\definestartstop
[SloppyPar]
[before={\start
\setuptolerance[horizontal,extrastretch,extraspace]
\setfontfeature{extraexpansion}}, % changes nothing
after=\stop]
\overfullrule=6pt
\starttext \showframe[text]
\startcolumns[balance=no]
\startSloppyPar
{\bf sloppy:}\par
\input tufte \par \it \input knuth
\stopSloppyPar
\column
{\bf normal:}\par
\input tufte \par \it \input knuth
\stopcolumns
\stoptext
%%% Local Variables:
%%% mode: context
%%% TeX-master: t
%%% End:
[-- Attachment #3: Type: text/plain, Size: 75 bytes --]
Perhaps someone has further/better suggestions …
Greetings
Andreas
[-- Attachment #4: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-01-18 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 17:28 Horacio Suarez
2010-01-18 17:40 ` Hans Hagen
2010-01-18 22:03 ` Andreas Harder [this message]
2010-01-18 17:46 ` Wolfgang Schuster
2010-01-18 22:39 ` Thomas A. Schmitz
2010-01-19 11:37 ` Horacio Suarez
[not found] <mailman.334.1263852201.4207.ntg-context@ntg.nl>
2010-01-19 16:29 ` Vyatcheslav Yatskovsky
2010-01-19 17:12 ` 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=71D658B7-12A0-4BF2-8C14-1362F6116422@uni-koblenz.de \
--to=aharder@uni-koblenz.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).