Re: [Groff] Invalid HTML on groff website

2014-07-31 Thread Steffen Nurpmeso
Peter Schaffter wrote: |On Tue, Jul 08, 2014, Steffen Nurpmeso wrote: |> Stumbled over during finding the ultimative underline mail-archive |> entry, why did i look at the source?, but indeed [1] at least |> embeds a in a , has a useless and keeps a |> open over boundaries. |> Just in ca

Re: [Groff] Invalid HTML on groff website

2014-07-31 Thread Peter Schaffter
On Tue, Jul 08, 2014, Steffen Nurpmeso wrote: > Stumbled over during finding the ultimative underline mail-archive > entry, why did i look at the source?, but indeed [1] at least > embeds a in a , has a useless and keeps a > open over boundaries. > Just in case noone noticed it yet. Finally go

Re: [Groff] \[-+] not available? why?

2014-07-31 Thread Ted Harding
On 31-Jul-2014 16:53:08 Werner LEMBERG wrote: > >> Is it possible to make .char \[-+] ... something that is part of >> the S font by default? > > No. However, it might be added to the constructed symbols provided > for -Tps (in file `tmac/ps.tmac', using `.fchar'). > > Werner That is prob

Re: [Groff] unquoted escape warning

2014-07-31 Thread Tadziu Hoffmann
> > This works fine for me, putting a big space between the 1 > > and the 4. > > > >3 over { 1 "\h'1i'" 4 } = pi > > yes, the warning has gone. > > I presume it was a warning, because the required spacing was > created even without the double quotes. Just wanted to add that eqn defines comm

Re: [Groff] \[-+] not available? why?

2014-07-31 Thread Werner LEMBERG
> Is it possible to make .char \[-+] ... something that is part of > the S font by default? No. However, it might be added to the constructed symbols provided for -Tps (in file `tmac/ps.tmac', using `.fchar'). Werner

Re: [Groff] unquoted escape warning

2014-07-31 Thread Anton Shterenlikht
>Date: Thu, 31 Jul 2014 16:01:28 +0100 >From: Ralph Corderoy > >This works fine for me, putting a big space between the 1 and the 4. > >3 over { 1 "\h'1i'" 4 } = pi yes, the warning has gone. I presume it was a warning, because the required spacing was created even without the double quotes.

Re: [Groff] unquoted escape warning

2014-07-31 Thread Ralph Corderoy
Hi Carsten, > > See section 14, Quoted Text, in > > http://www.kohala.com/start/troff/v7man/eqn/eqn2e.ps eqn doesn't > > understand all troff, so it's trying to typeset that. Quoting avoids > > this. > > But quoting with \ leads to print "\h'15'" itself? But that section says to quote with ""s?

Re: [Groff] unquoted escape warning

2014-07-31 Thread Carsten Kunze
> See section 14, Quoted Text, in > http://www.kohala.com/start/troff/v7man/eqn/eqn2e.ps eqn doesn't > understand all troff, so it's trying to typeset that. Quoting avoids > this. But quoting with \ leads to print "\h'15'" itself? --Carsten

Re: [Groff] unquoted escape warning

2014-07-31 Thread Ralph Corderoy
Hi Anton, > This line: > > \h'15' > > gives "unquoted escape" warning [from eqn] See section 14, Quoted Text, in http://www.kohala.com/start/troff/v7man/eqn/eqn2e.ps eqn doesn't understand all troff, so it's trying to typeset that. Quoting avoids this. Cheers, Ralph.

Re: [Groff] unquoted escape warning

2014-07-31 Thread Carsten Kunze
> .EQ L \*[EQNXT] > \h'15' > E = > { mu ( 3 lambda + 2 mu ) } > over >{ lambda + mu } > ~ ~~~ > mark ; > ~ ~~~ > nu = lambda over { 2 ( lambda + mu ) } > .EN Does it work when you put the request before the .EQ line?

[Groff] unquoted escape warning

2014-07-31 Thread Anton Shterenlikht
This line: \h'15' gives "unquoted escape" warning. As far as I can see from the manual, this horisontal motion is correct. It is used to shift an equation right: .EQ L \*[EQNXT] \h'15' E = { mu ( 3 lambda + 2 mu ) } over { lambda + mu } ~ ~~~ mark ; ~ ~~~ nu = lambda over { 2 ( lambda + m