From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: underbar and hyphenation
Date: Tue, 25 Jul 2006 19:33:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0607251929250.4036@nqvgln> (raw)
In-Reply-To: <6faad9f00607250721o32cc0898nef7e593f4555cc94@mail.gmail.com>
On Tue, 25 Jul 2006, Mojca Miklavec wrote:
> Hello,
>
> is there any way to make hyphenation work when using \underbar?
Perhaps you can try some of the techniques in Chapter 10 of Metafun
manual. There is no mention of hypenation, but looking at Fig 10.3 it
seems that hypenation is taken care of. Working with a rectangular
region should be easier, but then one needs to take care of
pagebreaks.....
Aditya
next prev parent reply other threads:[~2006-07-25 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 14:21 Mojca Miklavec
2006-07-25 16:41 ` Aditya Mahajan
2006-07-25 17:53 ` Peter Rolf
2006-07-25 23:22 ` Aditya Mahajan
2006-07-25 23:33 ` Aditya Mahajan [this message]
2006-07-26 7:23 ` Mojca Miklavec
2006-07-26 8:30 ` Hans Hagen
2006-07-26 13:13 ` Jano Kula
2006-07-26 15:06 ` Hans Hagen
2006-07-26 15:24 ` Taco Hoekwater
2006-07-27 10:53 ` Jano Kula
2006-07-27 11:42 ` Hans Hagen
2006-07-27 12:37 ` Jano Kula
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=Pine.WNT.4.63.0607251929250.4036@nqvgln \
--to=adityam@umich.edu \
--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).