[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possible bug with utf8 encoded files, when sourced via .so

From: Steffen Nurpmeso
Subject: Re: Possible bug with utf8 encoded files, when sourced via .so
Date: Tue, 26 Mar 2019 17:17:15 +0100
User-agent: s-nail v14.9.13-32-g7e84ad8b

Paul Ito wrote in <address@hidden
 |Very new to this list, so please be gentle.
 |I have the following issue:
 |I want to include a utf8-encoded file "text.txt" (with lots of german \
 |umlauts in my case) into a groff file "include.roff", 
 |that would then be processed with the -ms macro along with the -Kutf8 flag.
 |However, this does not seem to work properly, as all the fancy umlauts \
 |aren't recognized and get "butchered".
 |Having the same text and processing it directly works fine.
 |Am I missing something here, or is this a bug in the way, utf8 input \
 |is handled?
 |include.roff might look like this:
 |[fancy formatting, headings, etc here]
 |.so text.txt
 |where text.txt includes all the text that matters
 |the command I run is
 |groff -Tpdf -Kutf8 -ms include.roff > out.pdf
 |(with groff version 1.22.3 on ubuntu 18.10)

I think this has come up on this list already.  According to your
words it seems that the inclusion happens after the character set
conversion has taken place.  So using the traditional UNIX roff
pipeline could help you out, as in "soelim FILE | preconv | rest".
I think having an option to .so which allows special preconv
setting, or a different way to achive that, would also be cool.
I wished i had more time.  (I am hoping for a self-maintained roff
clone, somewhen.)

|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]