From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: modifying URL wrapping rules
Date: Thu, 20 Nov 2008 07:19:26 -0600 [thread overview]
Message-ID: <492563DE.6020000@sil.org> (raw)
In-Reply-To: <49251FCD.4060504@wxs.nl>
On 11/20/2008 2:29 AM, Hans Hagen wrote:
> Lars Huttar wrote:
>> On 11/19/2008 2:35 PM, Lars Huttar wrote:
>>> However, I have a few unsolved problems here.
>>>
>>> 1) I don't see a way, with the '\sethyphenatedurlbefore' or 'after'
>>> mechanism, to tell it not to break a URL between two slashes, as in
>>> "http://". At first I thought that since our text only had a few URLs,
>>> we'd likely never care. But ... you guessed it. One URL got broken
>>> between the slashes: "http:/
>>> /www.sil.org/..."
>> I found a way to deal with this... Based on a tip from
>> http://xpt.sourceforge.net/techdocs/language/latex/latex03-LaTexUsage/ar01s04.html,
>> I used
>> {\lefthyphenmin=64 http://}\hyphenatedurl{www.sil.org/...}
>> It seems to work in practice -- hyphenation and breaking are disabled
>> for the "http://" chunk. And hyphenation seems to successfully resume
>> afterwards.
>> This also fixes the problem of a URL breaking before the "//".
>>
>> The other problems are still outstanding though (wanting to break a URL
>> after a slash, not before; and before a hyphen, not after).
>>
>> Thanks for any ideas...
>
> cleaner than the lefthyphenmin hackery .,..
>
> {\hbox{http://}\hyphenatedurl{www.sil.org/...
Thank you!
> in context mkiv i can provide a hyphenater based on the url syntax
> (after all, mkiv already has an analyser for urls)
That would be great, but as I understand it, using mkiv would require us
to move to a beta version of ConTeXt... and we're right at the end (we
hope!) of a production cycle, where moving to any new version (whether
beta or not) could cost us a lot of time if any behavior changes.
So while I would be glad to see a hyphenator based on URL syntax, I
don't think a mkiv version won't help us this time.
Lars
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-11-20 13:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 21:12 Lars Huttar
2008-11-18 21:44 ` Arthur Reutenauer
2008-11-18 21:59 ` Lars Huttar
2008-11-18 22:13 ` Arthur Reutenauer
2008-11-19 20:35 ` Lars Huttar
2008-11-19 23:23 ` Lars Huttar
2008-11-20 8:29 ` Hans Hagen
2008-11-20 13:19 ` Lars Huttar [this message]
2008-11-20 23:36 ` Lars Huttar
2008-11-21 8:22 ` Hans Hagen
2008-11-21 15:35 ` Lars Huttar
[not found] <4926D553.4020803@sil.org>
[not found] ` <96CA6B61-8532-483F-8810-9DD7306F1CF2@st.estfiles.de>
2008-11-21 18:01 ` Lars Huttar
2008-11-21 19:31 ` Lars Huttar
2008-11-21 20:35 ` Mojca Miklavec
2008-11-21 22:53 ` Hans Hagen
2008-11-21 23:11 ` Mojca Miklavec
2008-11-24 13:39 ` Lars Huttar
2008-11-24 14:45 ` Hans Hagen
2008-11-24 16:25 ` Lars Huttar
2008-11-25 14:47 ` Steffen Wolfrum
2008-11-25 15:11 ` 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=492563DE.6020000@sil.org \
--to=lars_huttar@sil.org \
--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).