ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "kauśika cittūr via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: "kauśika cittūr" <citturs@gmail.com>
Subject: Line breaks, \wordright and hyphenation
Date: Sun, 24 Oct 2021 07:42:59 +0530	[thread overview]
Message-ID: <5510430.DvuYhMxLoT@sreeramtplt> (raw)

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

Dear list,

In short, my question is: why does \wordright cause a line-break when the line 
preceding it breaks with hyphenation and does not otherwise? How to avoid it 
(if at all possible)?

I have this delimitedtext instance called 'amnata' defined as below:

\definemeasure[amnatamargin][3cm]
\definedelimitedtext
  [amnata]
\setupdelimitedtext
  [amnata]
  [
	left=,
	right=,
	leftmargin={\measure{amnatamargin}},
	rightmargin={\measure{amnatamargin}},
  ]

I am using this to quote paragraph(s) of other authors. 
Since, I also want to indicate where the quote is from, I use this as follows:

\startamnata
  ⋮
\wordright{author}
\stopamnata

so that the author's name appears at the right-edge of the block.

When the penultimate line inside the block breaks without hyphenation, then 
argument of \wordright is typeset as expected (i.e. in the same line).

On the other hand, when the penultimate line inside this block breaks with 
hyphenation, the argument of \wordright is pushed to the next line even when 
there is enough space for it on the same line.

Here is a sample illustrating this:

\startamnata
A quote from another author : Suppose that thereisalongwordhere.
\wordright{– author}
\stopamnata

\startamnata
A quote from another author : Here, the text does not cause 
hyphenation in the first line.
\wordright{– author}
\stopamnata

[I have attached the output here as an image] 

How do I ensure that this does not happen, if that is possible at all? I 
suppose this is expected behaviour but I am not able to understand why.

Thanks,
kauśika

[-- Attachment #2: sample-output.png --]
[-- Type: image/png, Size: 25935 bytes --]

[-- Attachment #3: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2021-10-24  2:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24  2:12 kauśika cittūr via ntg-context [this message]
2021-10-24  7:24 ` kauśika cittūr via ntg-context
2021-10-25  2:04 ` kauśika cittūr via ntg-context
2021-10-26 16:13   ` [Solved] " kauśika cittūr via ntg-context
2021-10-24 11:08 Benjamin Buchmuller via ntg-context
2021-10-24 12:01 ` Hans Hagen via ntg-context
2021-10-24 12:41   ` kauśika cittūr 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=5510430.DvuYhMxLoT@sreeramtplt \
    --to=ntg-context@ntg.nl \
    --cc=citturs@gmail.com \
    /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).