Hi Peter,
At 2023-08-27T00:06:39-0400, Peter Schaffter wrote:
> On Sat, Aug 26, 2023, Bjarni Ingi Gislason wrote:
> > Lesson to learn: always use the information you have and give it to
> > the program, for example "groff" with option "-K.
> >
> > groff -Kutf8 -V file
> >
> > preconv -eutf8
On Sat, Aug 26, 2023, Bjarni Ingi Gislason wrote:
> Lesson to learn: always use the information you have and give it to
> the program, for example "groff" with option "-K.
>
> groff -Kutf8 -V file
>
> preconv -eutf8 file | troff -Tps | grops
Thanks, Bjarni. Odd to be discovering this for the
preconv -d shows
fallback encoding: 'ISO-8859-1'
processing 'txtFS_cF9dOUO.txt'
no coding tag
len: 95
uchardet read: 95 bytes
charset: ISO-8859-13
encoding used: 'ISO-8859-13'
.lf 1 txtFS_cF9dOUO.txt
.sp |1i-1v
Ce qui me pla\[u0106]\[u00AE]t le plus, c'est quand je suis assis
On Sat, Aug 26, 2023 at 04:47:02PM -0400, Peter Schaffter wrote:
> Subject: Baffling accented glyphs issue
>
> chats_1 contains a single accented glyph (î). The glyph is mangled
> in the ps output. chats_2 contains the same glyph plus an additional
> one (é). Here, neither g
On Saturday, 26 August 2023 21:47:02 BST Peter Schaffter wrote:
> Here's something I haven't encountered before. Have a look at the
> attached files. ps output was produced with
>
> groff -k file > file.ps
>
> chats_1 contains a single accented glyph (î). The glyph is mangled
> in the ps
1) Look at the output of
preconv
The option '-k' for "groff" can't find the encoding with just one
example of a character different from ascii or latin1.
groff -k -V file
preconv file | troff -Tps | grops
2) Add the same character to the file.
preconv
Lesson to learn: always use the
Here's something I haven't encountered before. Have a look at the
attached files. ps output was produced with
groff -k file > file.ps
chats_1 contains a single accented glyph (î). The glyph is mangled
in the ps output. chats_2 contains the same glyph plus an additional
one (é). Here,
