ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: \quotation, protrusion and linebreaking
Date: Tue, 11 Oct 2022 20:21:57 +0200	[thread overview]
Message-ID: <23945123-cea0-6764-9f9c-041f011c31ff@fiee.net> (raw)
In-Reply-To: <87pmeyckbb.fsf@vuxu.org>

Am 11.10.22 um 20:00 schrieb Leah Neukirchen via ntg-context:
> Hello,
> 
> I noticed the following problem:
> 
> 
> \showframe
> 
> \startluacode
>    fonts.protrusions.vectors.pure[0x201C] = { 1, 1 }
> \stopluacode
> 
> \definefontfeature[default][default][protrusion=pure]
> \setupalign[hanging]
> 
> \starttext
> 
> This text is unquoted.
> 
> “This text is quoted manually.”
> 
> \quotation{This text is quoted by a macro.}
> 
> This is a very long line followed by a nice linebreak, very supercalifragilisticexpialidocious.
> 
> This is a very long line followed by an ugly linebreak, not \quotation{supercalifragilisticexpialidocious}
> 
> \stoptext
> 
> 
> The macro-quoted text is not protruded.  I fixed this locally with a macro
> \def\q#1{\protrusionboundary1\quotation{#1}}
> Should this be default?
> 
> But the missing hyphenation I have to add myself with \-.  Ideas?

Try
\setupdelimitedtext[quotation][method=font]

Hraban

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-10-11 18:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 18:00 Leah Neukirchen via ntg-context
2022-10-11 18:21 ` Henning Hraban Ramm via ntg-context [this message]
2022-10-11 19:06   ` Leah Neukirchen via ntg-context
2022-10-12  8:14     ` Henning Hraban Ramm via ntg-context
2022-10-12 18:49       ` Denis Maier via ntg-context
2022-10-12 19:12         ` Hans Hagen via ntg-context
2022-10-12 19:17           ` Denis Maier via ntg-context
2022-10-12 20:25             ` Wolfgang Schuster via ntg-context
2022-10-12 22:43               ` Alan Braslau via ntg-context
2022-10-13  3:56                 ` Wolfgang Schuster via ntg-context
2022-10-12 19:54     ` Rik Kabel via ntg-context

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=23945123-cea0-6764-9f9c-041f011c31ff@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).