From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Alignment for narrower text
Date: Sun, 03 Apr 2016 18:19:37 +0200 [thread overview]
Message-ID: <57014299.9000402@gmail.com> (raw)
In-Reply-To: <57003cda.c8f2c20a.48efd.2050SMTPIN_ADDED_BROKEN@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]
> Jan Tosovsky <mailto:j.tosovsky@email.cz>
> 2. April 2016 um 23:42
> I thought Hans could also mean something like example below, but while
> leftskip should 'indent' all lines inside paragraph, it works only for
> the first one. Moreover, protrusion is not applied as well. And \crlf
> doesn't seem to be soft linebreak as it behaves like normal \par
> command - which is most likely explanation for that indenting issue.
>
> {\leftskip=2cm
> “line1\crlf
> line2\crlf
> line3\crlf
> line4.
> }
Indenting the whole textblock with \leftskip (or better ConTeXt’s
narrower environment)
doesn’t prevent protrusion as can be seen in the following example.
\definefontfeature[default][default][protrusion=quality]
\setupbodyfont[modern-designsize]
\starttext
“\vl Text\par
\vl Text
\startnarrower
“\vl Text\par
\vl Text
\stopnarrower
\blank[3*line]\setupalign[hanging]
“\vl Text\par
\vl Text
\startnarrower
“\vl Text\par
\vl Text
\stopnarrower
\stoptext
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2162 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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:[~2016-04-03 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52eaa335.c3d00e0a.7dbf.ffffcaccSMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-30 19:34 ` Wolfgang Schuster
2014-01-30 19:49 ` Jan Tosovsky
[not found] ` <00af01cf1df4$6c661990$45324cb0$@tosovsky@email.cz>
2016-03-30 18:55 ` Jan Tosovsky
[not found] ` <016701d18ab5$cb1723a0$61456ae0$@tosovsky@email.cz>
2016-03-30 22:32 ` Hans Hagen
2016-03-31 19:28 ` Jan Tosovsky
[not found] ` <020801d18b83$85bd5710$91380530$@tosovsky@email.cz>
2016-04-01 7:21 ` Hans Hagen
2016-04-01 20:04 ` Jan Tosovsky
2016-04-02 6:37 ` Wolfgang Schuster
2016-04-02 21:42 ` Jan Tosovsky
[not found] ` <57003cda.c8f2c20a.48efd.2050SMTPIN_ADDED_BROKEN@mx.google.com>
2016-04-03 16:19 ` Wolfgang Schuster [this message]
2014-01-30 19:08 Jan Tosovsky
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=57014299.9000402@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).