From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with \sethyphenatedafter
Date: Thu, 25 Feb 2016 08:26:50 +0100 [thread overview]
Message-ID: <56CEACBA.9070003@gmx.es> (raw)
In-Reply-To: <56CD6FAA.5010808@wxs.nl>
On 02/24/2016 09:54 AM, Hans Hagen wrote:
> On 2/24/2016 8:44 AM, Pablo Rodriguez wrote:
>> On 02/22/2016 10:30 PM, Hans Hagen wrote:
>>> [...]
>>> i'll add
>>>
>>> \enabledirectives[hyphenators.urls.packslashes]
>> [...]
>> Am I doing somehting wrong? Or do I require LuaTeX-0.89.2 (Linux 32bit
>> has version 0.89.0 in the ConTeXt Suite [I just mention it, I’m fine
>> with that].)
>
> you should not use
>
> \sethyphenatedurlafter{/}
On a second thought, I wonder whether it would make sense to enable
\enabledirectives[hyphenators.urls.packslashes] when any of
\setuphyphenated, \\sethyphenatedurlbefore or \sethyphenatedurlafter is
used in the document.
I would say, even is the slash is included in them or not.
I think it might be useful (although I still wonder).
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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-02-25 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 17:26 Pablo Rodriguez
2016-02-22 21:30 ` Hans Hagen
2016-02-22 23:22 ` Pablo Rodriguez
2016-02-24 7:44 ` Pablo Rodriguez
2016-02-24 8:54 ` Hans Hagen
2016-02-24 9:11 ` Pablo Rodriguez
2016-02-25 7:26 ` Pablo Rodriguez [this message]
2016-02-25 9:32 ` 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=56CEACBA.9070003@gmx.es \
--to=oinos@gmx.es \
--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).