On 24 October 2014, Ingo Schwarze <[email protected]> wrote:
> Hi,
> 
> Gleydson Soares wrote on Thu, Oct 23, 2014 at 09:11:36PM -0300:
> > On Thu, Oct 23, 2014 at 10:36:44AM -0300, Gonzalo L. Rodriguez wrote:
> 
> >> -USE_GROFF =               Yes
> 
> > mandoc conplains:
> > 
> > $ mandoc -Tlint -Werror stunnel.8       
> > mandoc: stunnel.8:35:2: ERROR: skipping unknown macro: 'br\&
> > mandoc: stunnel.8:85:37: ERROR: skipping bad character: 0xc2
> > mandoc: stunnel.8:85:38: ERROR: skipping bad character: 0xa0
> > mandoc: stunnel.8:1084:11: ERROR: skipping bad character: 0xc5
> > mandoc: stunnel.8:1084:12: ERROR: skipping bad character: 0x82
> > mandoc: stunnel.8:1085:16: ERROR: skipping bad character: 0xc5
> > mandoc: stunnel.8:1085:17: ERROR: skipping bad character: 0x82
> > $
> > 
> > are you sure to zap groff?
> 
> Yes, it's a perlpod(1) manual, and these particular errors are
> harmless.
> 
>  - 35:2 has no ill effect, actually, it's bug in mandoc(1) that
>         this bogus message is shown, i will look into fixing it.
>  - 85:37-38 is merely a bug in the manual,
>             two stray gibberish eight bit bytes

    Not really, 0xC2 0xA0 is Unicode "NO-BREAK SPACE":

        http://www.fileformat.info/info/unicode/char/a0/index.htm

    There are probably more of these around, various *roff tools produce
them.

>  - 1084-1085 is just a stray Unicode character in the author's name,
>              Michal with a dark L, not properly roff-encoded,
>              as usual.
> 
> > otherwise OK gsoares@
> 
> I didn't look at the rest of the port, but OK schwarze@
> for removing USE_GROFF.
> 
> Yours,
>   Ingo

    Regards,

    Liviu Daia

Reply via email to