Hi Wolfram,
> On 17. Sep 2020, at 11:44, Wolfram Schneider
> wrote:
>
> On Wed, 16 Sep 2020 at 20:34, Michael Gmelin wrote:
>>
>> @Wolfram: Do you think you could look into this (paperless man
>> page). Thanks!
>
> the page https://man.freebsd.org/paperless
>
> looks fine for me. What are you missing?
>
When I checked yesterday, it just returned an empty page (I only tried
once though).
Today it shows up, but it has some serious[0] rendering issues (starting
at about "Install and configure uwsgi"), which are probably caused by
misinterpreting '\\"' at the end of line 135 of the man page.
It renders fine using man(1) on the console (which uses mandoc(1)) and
also when converting it to html using `mandoc -T html'.
`mandoc -T lint' is also happy with the man page.
`groff -T html -man' does complain though, shows these issues at
line 135:
:135: a space character is not allowed in an escape name
:135: warning: numeric expression expected (got `u')
:135: warning: can't find font `['
and creates output like the one seen on man.freebsd.org.
Based on this, I assume that man.cgi uses groff or a similar tool and
not mandoc to create html output.
I'll change literal parts of the paperless man page later today, so that
examples render nicer using `mandoc -T html', which will also fix groff
output as a side-effect by getting rid of the offending escape
sequence. I'll bump the revision and hope that it will be picked up
sooner or later.
Since we switched to mandoc(1) being the default for man(1) in HEAD
more than five years ago, I think it would make sense to do the same
for man.cgi to keep things consistent. QA is usually done
using mandoc -T lint for syntax, igor for style, and by checking
manually on the console, none of which would have revealed that problem
(not just for ports, but also in base).
Adapting the style sheet shouldn't be too hard. I'm happy to help with
that, if needed.
Thanks
Michael
[0]Serious in the sense that relevant information is lost.
> -Wolfram
>
>
>> -m
>>
On 1. Sep 2020, at 11:55, Michael Gmelin wrote:
>>>
>>>
>>>
On Mon, 31 Aug 2020 20:33:34 +0200
Wolfram Schneider wrote:
> On Wed, 26 Aug 2020 at 18:50, Kurt Jaeger wrote:
>
> Hi!
>
>>> man.cgi has provisions for most of this already, it's only
>>> missing some job to regulary extract the latest
>>>
>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/13.0-CURRENT/ports.txz
>>>
>>> for the current tree of the manuals.
>>
>> How does it actually create the pages though?
>
> wosch probably knows this.
Indeed ;-)
>>>
>>> Thanks!
>>>
The ports manual pages will be updated once when a new release
comes out. Maybe every 3-9 months. The update takes hours and a
lot of resources (60GB download of all packages and unpacking).
>>>
>>> It would be cool if you could share the scriptwork that does this.
>>> Getting to a higher update frequency for ports would be really
>>> useful, but it feels like that this will require coordination
>>> between different teams/individuals.
>>>
-Wolfram
>>>
>>> Do you have any idea why the man page below isn't included?
>>>
>> E.g., the
>> man page paperless(7) created by deskutils/py-paperless [0] still
>> isn't available over man.cgi, even though the port was created a
>> long time before 12.1 was released and is in 12.1's ports.txz.
>>>
>>> Cheers,
>>> Michael
>>>
>>> --
>>> Michael Gmelin
>>> ___
>>> freebsd-ports@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>>> To unsubscribe, send any mail to
>>> "freebsd-ports-unsubscr...@freebsd.org"
>>
>
>
> --
> Wolfram Schneider https://wolfram.schneider.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
