From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Type-setting filenames
Date: Thu, 18 Sep 2008 11:09:49 +0200 [thread overview]
Message-ID: <48D21ADD.60804@wxs.nl> (raw)
In-Reply-To: <OFCF091CCA.7CDD1698-ON802574C8.002EB43D-802574C8.002FD0AF@converteam.com>
richard.stephens@converteam.com wrote:
>>> I am using \filename to type-set filenames. Some of these are very
>>> long
>>> (greater than 30 characters) and overhang
>>> the right hand margin, sometimes even disappearing off the edge of the
>>> page. The first line break is just before the
>>> full stop. There are usually plenty of spaces in the names. Can I
>>> get
>>> ConTeXt to put a line-break into filenames?
>> Did you try \hyphenatedfilename ?
>
> Yes, I tried that, no difference. I presume that \hyphenatedfilename is
> for use with filenames that already have hyphens in them?
> Mine don't, but I want them to split. Perhaps splitting filenames is
> frowned upon - if so, what is the best way to put them into documents?
> Or perhaps I should use shorter filenames, but why should I compromise
> readability? One example is "Transfer functions for PID and KF
> controllers.xmcd"
>
> Any ideas or comments?
\def\myfilename#1{{\spaceskip.25em plus
1em\relax\tttf\normallanguage\zerocount#1}}
\myfilename{Transfer functions for PID and KF controllers.xmcd}
\myfilename{Transfer functions for PID and KF controllers.xmcd}
\myfilename{Transfer functions for PID and KF controllers.xmcd}
\myfilename{Transfer functions for PID and KF controllers.xmcd}
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-09-18 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 8:42 richard.stephens
2008-09-18 9:09 ` Hans Hagen [this message]
2008-09-18 9:20 ` Wolfgang Schuster
2008-09-18 12:00 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 10:19 richard.stephens
2008-09-17 14:20 richard.stephens
2008-09-17 14:34 ` Thomas A. Schmitz
2008-06-25 9:03 richard.stephens
2008-06-25 9:16 ` Wolfgang Schuster
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=48D21ADD.60804@wxs.nl \
--to=pragma@wxs.nl \
--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).