[texdoc] Weird behavior of `texdoc'

[Paulo Roberto Massa Cereda]

Hello, friends.

I did a quick test on Sierra with iTerm and I could not reproduce the
issue. Yudai, do you remember if you ran into this issue before,
perhaps before a potential system update?

At the moment, I am far from my machines, but as soon as I get back, I
will perform a couple of additional tests. I recall El Capitan having
some issues regarding encodings (I had a lot, actually), but I cannot
find the source. Anyway, I will report back in a couple of hours,
hopefully. :)

Cheerio!

Paulo

2017-02-14 6:33 GMT-02:00 Yudai NAKATA <yudai.nkt at gmail.com>:
> Hi Manuel,
>
>> Can you try 'texdoc -v
>> bxjalipsum' and paste here the line that starts with "texdoc info: View
>> comand:" in the output? What happens if you run this command manually
>> from your terminal?
>
> It returns “texdoc info: View comand: less
> "/usr/local/texlive/2016/texmf-dist/doc/latex/bxjalipsum/README.md””.
> Strangely, manually running `less "/usr/local/…` displays the
> characters correctly.
>
> P.S. comand should be command, I guess ;-)
>
> Best regards,
> Yudai Nakata
>
> On 2017年2月14日 at 8:28:36, Manuel Pégourié-Gonnard (mpg at elzevir.fr) wrote:
>> Hi Yudai,
>>
>> Thanks for your detailled report!
>>
>> On 13/02/2017 12:32, Yudai NAKATA wrote:
>> > This line contains non-ASCII characters (→: U+2192 RIGHTWARDS ARROW), and
>> > `texdoc bxjalipsum` renders this line as follows.
>> >
>> >> - `*.sty` <86><92> $TEXMF/tex/latex/BXjalipsum
>> >
>> I agree that this is not the expected behaviour.
>>
>> > In fact,
>> > bxjalipsum’s README.md
>> > doesn’t get corrupted if I explicitly pipe the stdout of `texdoc
>> > bxjalipsum` to a pager, i.e., the command
>> > `texdoc bxjalipsum | $PAGER` will work.
>> >
>> This is weird because if I remember correctly, texdoc is supposed to
>> pass the document to your pager anyway. Can you try 'texdoc -v
>> bxjalipsum' and paste here the line that starts with "texdoc info: View
>> comand:" in the output? What happens if you run this command manually
>> from your terminal?
>>
>> > Is this a normal behavior? It seems like a bug IMHO, but I apologize
>> > if this behavior is just as you expected.
>> >
>> No, this is not the behaviour I would expect either, let's try to fix
>> this together!
>>
>> Thanks,
>> Manuel.
>>
>