> BTW, in German, AFAIK, you should use `-', not \[en].
Are you sure about this? I just checked a few examples
(real books, so I assume these were created by professional
typesetters) both old (letterpress stuff, yay!) and new, and
they all use the en dash (or, in an old book, something longer,
> If anyone can think of a context where a hyphen break between
> two numbers is OK, I'd be very interested to hear of it!
> And, if the exceptions are so special, then I'm sure that
> Werner's workround of "\:" should be acceptable, since people
> are not going to need it all that often.
> Meanwh
> > I see. Well, `preconv -e ...' will be replaced with `soelim -e ...',
> > so this isn't a real problem.
>
> OK. I think a link will still be needed,
Hmm, I quite dislike a hard link.
> because simply checking whether preconv exists on $PATH is a lot
> easier for man to do than trying to
> I can't think of a context where a true hyphen between numbers could
> be accetably broken.
>
> I'm excluding cases where a number-range is implied, as in
>
> Items 2-7
>
> since this should properly be represented by an en-dash (with or
> without padding), as in
>
> 2\(en7 2\^\(en\^7
Ted Harding wrote:
> On 10-Aug-06 Steve Izma wrote:
>>
>> Well, I'll disagree. [...] when setting
>> indexes on short lines (e.g., two columns on book page, which
>> gives you about 10 to 12 picas, usually indented), any place
>> where you can get a line break is very important.
>
> Yes, that d
Given the ease with which one can allow a break at a hyphen, I'm
happy with it the way it is. But then I use groff to typeset novels
(for a friend), so I carefully proof-read everything and fix what
needs attention. I'm not one of those who wants to just toss the text
at a formatter and get perf
On 10-Aug-06 Steve Izma wrote:
>> From: Keith Marshall <[EMAIL PROTECTED]>
>> Date: Thu, 10 Aug 2006 14:28:29 +0100
>>
>> I won't! If I write a numeric range, such as `200-400',
>> I *don't* want a line break to occur within it.
>
> Well, I'll disagree. I can't find any reference to this in eith
On Thu, Aug 10, 2006 at 09:25:09AM -0400, [EMAIL PROTECTED] wrote:
> From: Werner LEMBERG <[EMAIL PROTECTED]>
> Date: Thu, 10 Aug 2006 07:39:19 +0200 (CEST)
> To: groff@gnu.org
> Subject: [Groff] explicit hyphen and numbers
>
> ...
> Since it isn't possible to set the hcode value for numbers, thi
On Tue, Aug 08, 2006 at 12:20:25PM -0600, Clarke Echols wrote:
> I haven't done labels, but I wrote a package to print business cards
> on pre-perforated business-card stock.
> :
On the basis that 0x01 example is worth 1K words,
here is a test sheet for Avery 5163 2 x 4 inch Mailing Labels
On 10-Aug-06 Werner LEMBERG wrote:
>
> Folks,
>
>
> Urs showed up an interesting problem in groff: A hyphen between two
> numbers does *not* insert a breakpoint! To be more specific, the
> .cflags values 2 and 4 of a character x are only active if the
> characters before and after x both have n
On Thursday 10 August 2006 1:37 pm, Larry Kollar wrote:
> Werner LEMBERG wrote:
> > Urs showed up an interesting problem in groff: A hyphen between two
> > numbers does *not* insert a breakpoint! To be more specific, the
> > .cflags values 2 and 4 of a character x are only active if the
> > charac
Werner LEMBERG wrote:
> Urs showed up an interesting problem in groff: A hyphen between two
> numbers does *not* insert a breakpoint! To be more specific, the
> .cflags values 2 and 4 of a character x are only active if the
> characters before and after x both have non-zero hyphenation codes (as
On Thu, Aug 10, 2006 at 08:14:14AM +0200, Werner LEMBERG wrote:
> Colin Watson wrote:
> > For Unicode fonts (which ought to be increasingly the norm), the
> > proposal to write out all glyph properties in the font file seems
> > odd; as far as I understand the point of Bruno's Unicode fonts
> > ver
On Thu, Aug 10, 2006 at 08:16:51AM +0200, Werner LEMBERG wrote:
> Colin Watson wrote:
> > man-db uses a classical troff pipeline rather than using groff
> > directly, so this is not possible. It also has its own soelim
> > implementation, created in order to be able to handle compressed
> > files.
14 matches
Mail list logo
