[sane-devel] [janitorial] post 1.0.28

Povilas Kanapickas povilas at radix.lt
Wed Aug 7 18:21:13 BST 2019

Hi Olaf,

On 8/7/19 4:26 PM, Olaf Meeuwissen wrote:
> # Updating the HTML version of the manual pages requires a tool from a
> # site that no longer exists ... :-/
> # I've been looking at using something else but with nothing so far that
> # produces something acceptable.

Are we talking about http://sane-project.org/html/ or everything under
http://sane-project.org/docs.html? I may be able to help.

> Apart from that, I don't think we want to wait another two years or so
> for our next release.  I would like to see our next release in four to
> six months.  And the ones after that in a similar time frame.  How's
> that sound?

Looks great to me.

> Our documentation, including the website(!), also needs updating and
> this is something I'd like to start working on although I'm not quite
> sure yet what direction to go in.  Markdown for files in git would
> improve rendering in the GiLab web interface but GNU standards have
> their own ideas about filenames.  Perhaps that some build tweak can
> bridge that divide.

I wonder if we could just append .md to the GNU filenames and then
suppress any warnings resulting from that.

> For the website, using one of the many static site generators could make
> the site look more current as well as more maintainable.  Nobody really
> likes plain HTML, I think.  That said, it's not just the looks, much of
> the information is also badly dated.

Agreed. I think the focus should be on updating the outdated information
though. Looking in plain html is nothing until you see the last status
update was 10 years ago.
> Concerning the SANE API specification, I've been thinking of ripping it
> out of the sane-backends code and convert it for use with Sphinx, even
> setting up integration with readthedocs.io so the API spec would be
> available in a versioned fashion as well as a "current" version on our
> website.



More information about the sane-devel mailing list