From: Marco Pessotto <melmothx@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: What's the proper way to typeset a slash in a text flow?
Date: Tue, 21 Dec 2010 13:04:08 +0100 [thread overview]
Message-ID: <87r5dbxrgn.fsf@universe.krase.net> (raw)
In-Reply-To: <CBA3871C-EC23-4352-A439-12FAA3462D6D@gmail.com>
Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:
> Am 21.12.2010 um 00:34 schrieb Marco Pessotto:
>
>>
>> See the following minimal example (I'm not trying to typeset urls or
>> filesystem paths in this way, just regular text):
>>
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%
>> \def\myslash{/\penalty-5000}
>> \starttext
>>
>> \type{/}
>>
>> {\bfd Love/Hate/Play/Love/Hate/Play/Love/Hate/Play/Love/Hate/Play}
>>
>> \type{\slash}
>>
>> {\bfd Love\slash Hate\slash Play\slash Love\slash
>> Hate\slash Play\slash Love\slash Hate\slash Play\slash Love\slash
>> Hate\slash Play}
>>
>> \type{\textslash}
>>
>> {\bfd Love\textslash Hate\textslash Play\textslash Love\textslash
>> Hate\textslash Play\textslash Love\textslash Hate\textslash
>> Play\textslash Love\textslash Hate\textslash Play}
>>
>> \type{\myslash}
>>
>> {\bfd Love\myslash Hate\myslash Play\myslash Love\myslash Hate\myslash
>> Play\myslash Love\myslash Hate\myslash Play\myslash Love\myslash
>> Hate\myslash Play}
>>
>> \stoptext
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%
>>
>> Neither one of the first three solutions above give me the right thing,
>> because the line won't break at /. What am I missing?
>>
>> A workaround seems to be
>>
>> \def\myslash{/\penalty-5000}
>>
>> and then using \myslash instead of \slash, but I'm pretty sure I'm not
>> doing this right.
>
> MkIV: \setbreakpoints[compound]
>
Ah, that's odd, because I've already defined that and I didn't realize
it fixed the problem (but I was used to type \slash from LaTeX, breaking
the typesetting).
This \setbreakpoints looks like a panacea to me (it already fixed the
hyphen issue some weeks ago, but I didn't know it fixed the slash too).
I'm thinking how to make this information more accessible (because from
my point of view hate/love is not a compound word) on the wiki.
I found this in cont-new.mkiv
% potential new defaults: \setbreakpoints[compound]
Is this going to happen or there are serious reasons not to have it as
default?
Thanks again
--
Marco
___________________________________________________________________________________
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:[~2010-12-21 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 23:34 Marco Pessotto
2010-12-20 23:55 ` Hans Hagen
2010-12-21 8:31 ` Marco Pessotto
2010-12-21 5:43 ` Wolfgang Schuster
2010-12-21 12:04 ` Marco Pessotto [this message]
2010-12-22 11:45 ` Hans Hagen
2010-12-22 12:01 ` Marco Pessotto
2010-12-22 13:06 ` 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=87r5dbxrgn.fsf@universe.krase.net \
--to=melmothx@gmail.com \
--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).