On Mon, Sep 19, 2022 at 01:38:35PM -0400, Peter Schaffter wrote:
> I recently discovered that documents with .so'd files containing
> non-ASCII input require preprocessing with soelim(1). If we have
>
> file: source
> .pl 1v
> .ds FOO àéîöù
>
> file: main
> .so source
> .nop \*[FOO]
>
> running
On Mon, Sep 19, 2022, G. Branden Robinson wrote:
> > Now, the '-s' flag issue... Unless I am misunderstanding or
> > misreading something,
> > soelim main | groff -Tutf8 -k
> > and
> > groff -Tutf8 -ks main
> > should produce identical output, however the -s flag is ignored and
> > groff spits
Hi Peter,
At 2022-09-19T13:38:35-0400, Peter Schaffter wrote:
> I recently discovered that documents with .so'd files containing
> non-ASCII input require preprocessing with soelim(1). If we have
>
> file: source
> .pl 1v
> .ds FOO àéîöù
>
> file: main
> .so source
> .nop \*[FOO]
>
> running
>
DJ Chase wrote in
:
|On Sat Sep 17, 2022 at 3:30 PM EDT, Steffen Nurpmeso wrote:
|> P.S.: with the help from people of IRC i have now tested LuxiMono,
|> IBMPlexMono, and NotoMono, and only LuxiMono gets it somehow right
|> (but looks terrible as a monospace font imho).
...
|JetBrains Mono /
I recently discovered that documents with .so'd files containing
non-ASCII input require preprocessing with soelim(1). If we have
file: source
.pl 1v
.ds FOO àéîöù
file: main
.so source
.nop \*[FOO]
running
groff -Tutf8 -k main
spits out garbage, whereas
soelim main | groff -Tutf8 -k
correc
