On 2020-12-23 at 13:04, Aaron Boxer wrote:
> On Wed, Dec 23, 2020 at 11:42 AM The Wanderer <wanderer@fastmail.fm>
> wrote:
>
>> On 2020-12-23 at 11:25, Aaron Boxer wrote:
>>
>>> Hi,
>>> I have some questions about a lintian warning I am getting from my package.
>>> It complains that the NAME section of the man page can't be parsed.
>>> Here is how the section appears in my man page:
>>>
>>> NAME
>>> grk_compress — compresses images to JPEG 2000 format
>>>
>>> Note: I generate the man page from markdown files via pandoc.
>>>
>>> How can I get more insight into the problem?
>>
>> I have no particular relevant expertise, but one thing I notice
>> instantly is that that doesn't quite look like a standard hyphen.
>>
>> Indeed, copying it into a text file and examining it with a hex viewer
>> shows that — is apparently 0x8094, whereas - is 0x2d.
(Correction: that's 0xe28094, which in UTF-8 is
https://www.fileformat.info/info/unicode/char/2014/index.htm.)
>> It might be worth checking whether that one character is the cause of
>> this.
>
> Unfortunately, switching to en dash does not fix the problem
What's the hex value of the generated character?
Again, I could be barking up a completely wrong tree. However, as I
understand matters there are Unicode emdash and endash characters
(U+2014 and U+2013 respectively), both of which are distinct from the
ASCII hyphen (U+002D). It's not impossible that the system involved may
understand the latter but not the two former.
Yes, correct, thanks. I switched to good old ASCII hyphen and the warning is now gone!
--
The Wanderer
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw