From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: hyphenatedurl (WHY?)
Date: Sat, 12 Jul 2008 07:41:56 +0200 [thread overview]
Message-ID: <C520978A-138F-48B8-8D60-C2DC46CEFF09@st.estfiles.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0807111849400.18605@nqv-yncgbc>
Am 12.07.2008 um 00:50 schrieb Aditya Mahajan:
> On Fri, 11 Jul 2008, Hans Hagen wrote:
>
>> Steffen Wolfrum wrote:
>>> Hi,
>>>
>>> God bless the command \hyphenatedurl{...} !
>>>
>>> Only, I am wondering why it starts a new line not *after* but
>>> *before*
>>> the slash, dot or whatever there is to structure a long url.
>>> Is this an english/dutch convention, completely different than
>>
>> i just took what i liked (i.e. found less confusing); since i hate
>> long
>> url's (one reason why one can have clickable ones with alternative
>> rendering) i don't care to much either .. anything looks bad in
>> running
>> text -)
>
> Sometimes, you need to refer to long URLs in bibliographies. For the
> tugboat articles, I ended up doing line breaking by hand :(
>
>>> paragraph wrapping? Or is it common usus, just me never noticed it
>>> outside ConTeXt??
>>
>> in mkiv you can set up your own preferences with
>>
>> \sethyphenatedurlnormal
>> \sethyphenatedurlbefore
>> \sethyphenatedurlafter
>>
>> and in mkii you can play with
>>
>> \chardef\urlsplitmode = 1 | 2 | 3 | 4
That's it!
> Did not know about this. Thanks.
Now it is written down ... Googleable ;o)
I am happy for every secret undocumented command that is mentioned on
this list.
Somehow this list's archive actually is the missing ConTeXt-manual ...
Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2008-07-12 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 19:59 Steffen Wolfrum
2008-07-11 20:17 ` Jesse Alama
2008-07-11 21:46 ` Hans Hagen
2008-07-11 21:43 ` Hans Hagen
2008-07-11 22:50 ` Aditya Mahajan
2008-07-12 5:41 ` Steffen Wolfrum [this message]
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=C520978A-138F-48B8-8D60-C2DC46CEFF09@st.estfiles.de \
--to=context@st.estfiles.de \
--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).