[GRASS-dev] Re: [GRASS GIS] #612: g.html2man: parsing leads to man page errors

[GRASS GIS]

#612: g.html2man: parsing leads to man page errors
--------------------------+-------------------------------------------------
  Reporter:  hamish       |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect       |      Status:  new                      
  Priority:  normal       |   Milestone:  6.5.0                    
 Component:  Docs         |     Version:  6.4.0 RCs                
Resolution:               |    Keywords:  g.html2man               
  Platform:  Unspecified  |         Cpu:  All                      
--------------------------+-------------------------------------------------
Comment (by glynn):

 Replying to [comment:7 hamish]:

 > yeah, I look at doing that first. But the <H2>NAME really wasn't
 appropriate for the intro and driver custom HTML pages I looked at

 I'm not so sure.

 > and so I went with the meta-tag solution.

 Actual <meta> tags would be a reasonable solution for any files which
 genuinely shouldn't have a NAME section, e.g.

 {{{
 <meta name="name" content="grass-dbf" scheme="GRASS">
 }}}

 > I couldn't see how to make that work with the python version (does
 HTMLParser.py strip out the comments before we can get our hands on
 them?), and so I left it for now.

 It's possible to add a handler for comments, but I don't consider this
 appropriate.

 Comments are comments; you are supposed to be able to use them as you
 wish, without any consequences. The only situation where it's appropriate
 for an application to take note of comments in its input is if it intends
 to include them as comments in its output.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/612#comment:8>
GRASS GIS <http://grass.osgeo.org>