Am Thu, 28 Jan 2010 19:43:29 +0100 (CET)
schrieb Werner LEMBERG :
> > It's a simple pipeline.
>
> You are probably misunderstanding. I was wondering whether the
> internal pipeline in the groff binary (this is, how the -K and -s
> command line option interact) should be changed that way.
Sorry I
>> Perhaps it makes sense to exchange preconv and soelim in the groff
>> pipe?
>>
>> soelim Input.ms | preconv -eutf8 | troff -ms -Tps | grops
>
> Works perfectly!
>
>> This should be easy to implement, methinks...
>
> It's a simple pipeline.
You are probably misunderstanding. I was wonderi
Am Thu, 28 Jan 2010 16:58:35 +0100 (CET)
schrieb Werner LEMBERG :
>
> > I'm experimenting with the -K utf8 option, because I'd like to input
[...]
> > But when I use
> > additional files with the .so request, the characters are not
> > recognized. What am I doing wrong?
>
> Nothing. This is a kn
> I'm experimenting with the -K utf8 option, because I'd like to input
> utf8 formatted source code:
>
> groff -s -K utf8 -ms -Tps Input.ms > Output.ps
>
> This works, as long as I have one single input file. But when I use
> additional files with the .so request, the characters are not
> recog
Hello all.
(By mistake I first sent this posting to g...@groff.org instead of
gr...@gnu org. Oh my.)
I'm experimenting with the -K utf8 option, because I'd like to input
utf8 formatted source code:
groff -s -K utf8 -ms -Tps Input.ms > Output.ps
This works, as long as I have one single input fi
