ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: jbf via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: jbf <roma83537@gmail.com>
Subject: Re: \hyphenatedurl in non-hyphenation context
Date: Tue, 15 Feb 2022 10:16:16 +1100	[thread overview]
Message-ID: <ca68297d-31da-e175-2014-469f624a4518@gmail.com> (raw)
In-Reply-To: <2b64dde0f1d143888a379881db1ff518@unibe.ch>


[-- Attachment #1.1: Type: text/plain, Size: 1642 bytes --]

You could try this (note the url setup then called in before 
\hyphenatedurl):

\setuppapersize[A6]

\setuphead[chapter][align={right,nothyphenated}]

\startsetupsurl

\setupalign[hyphenated]

\stopsetups

\starttext

\chapter[title={asdfasdf\goto{\setup[url]\hyphenatedurl{https://doi.org/10.12345/12345.12345}}[url(https://doi.org/10.12345/12345.12345)]}]

bla

\stoptext

Julian

On 14/2/22 22:17, Denis Maier via ntg-context wrote:
>
> Hi,
>
> I have defined chapter headings set to nothyphenated. Yet, sometimes 
> occur DOIs in these chapter headings, and I would obviously want those 
> to be broken across lines.
>
> %%%%%%%%%%%%%%%%%%%%%%%%%
>
> \setuppapersize[A6]
>
> \setuphead[chapter][align={right,nothyphenated}]
>
> \starttext
>
> \chapter[title={asdf asdf 
> \goto{\hyphenatedurl{https://doi.org/10.12345/12345.12345}}[url(https://doi.org/10.12345/12345.12345)]}]
>
> bla
>
> \stoptext
>
> %%%%%%%%%%%%%%%%%%%%%%%%%
>
> For now, I’m changing the definition to 
> \setuphead[chapter][align={right,lesshyphenation}], but is there a way 
> to disable hyphenation, but still break urls across lines?
>
> Best,
>
> Denis
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 9560 bytes --]

[-- Attachment #2: 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:[~2022-02-14 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 11:17 Denis Maier via ntg-context
2022-02-14 23:16 ` jbf via ntg-context [this message]
2022-02-15  8:51   ` Denis Maier 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=ca68297d-31da-e175-2014-469f624a4518@gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=roma83537@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).