> Readin info groff I found how to do utf-8 output, but nothing about
> input :(
This is correct, unfortunately. groff doesn't yet support UTF8 input.
You have to convert your file first to something groff can understand.
Below is a small perl script which does that. Note that it doesn't
`fake
Hello,
is there a way to restrict the tables of content (.TC) to a depth ? Haven't
found anything in s.tmac.
--
with best regards / salutations distinguées / Cordiali Saluti /
med vänliga hälsningar / mit freundlichen Gruessen
Ruediger Haertel
Back from vacation
> What exactly is the DESC file?
It describes the capabilities of an output device. See the
groff_font manpage for details of what the device does.
> When I type in "groff" on my Debian testing box all it
> does is wait for input (it doesn't return any output).
Right. Giv
Hi,
I'm having problems with the new ubuntu hoary and groff. Hoary works
with utf-8 by default, and groff isn't working well about thar,
special characters aren't reconized. I was thinking about it's a
problem about ubuntu, but I wanted to be sure if groff is supossed to
support utf-8 input. Jus
Keith MARSHALL wrote:
> Alejandro López-Valencia wrote:
>
>>Ersin Akinci wrote:
>>
>>>Thanks for all your suggestions and help! I did manage to find my
>>>"problem", though. Just for the record (for anyone else who might
>>>have this problem), compiling statically will yield the "No DESC"
>>>err
Alejandro López-Valencia wrote:
> Ersin Akinci wrote:
>> Thanks for all your suggestions and help! I did manage to find my
>> "problem", though. Just for the record (for anyone else who might
>> have this problem), compiling statically will yield the "No DESC"
>> error. You need to compile linke
> (1) I googled on groff and japanese. There seems to be a "ja-groff"
>or "jgroff" with the proper extensions, but trying to find it
>became a kafkaesque adventure. I found diff.gz files at BSD ports
>(this is a slackware 10.0), and description files, and then ".tbz"
>files which
> If I understand correctly, you would like the format line to be
> optional,
Yes.
> but if specified to be preceded by the work "col".
Yes.
> As an option, the second format statement above might also be used
> (col "ll").
Mhm, perhaps it is better to use just one the formats. I don't see a
