| |||||||||||||
Glibc change exposing bugsGlibc change exposing bugsPosted Nov 12, 2010 5:01 UTC (Fri) by nicooo (guest, #69134)In reply to: Glibc change exposing bugs by HelloWorld Parent article: Glibc change exposing bugs
The rest of the world uses HTML and PDF for that kind of documentation.
(Log in to post comments)
Glibc change exposing bugs Posted Nov 12, 2010 7:33 UTC (Fri) by paulj (subscriber, #341) [Link]
Funnily enough, a lot of PDFs are written in some other language and generated through TeX (that I read anyway), with PDF being just one possible output format. Which is just how GNU _Tex_info works too..
Glibc change exposing bugs Posted Nov 12, 2010 10:42 UTC (Fri) by marcH (subscriber, #57642) [Link]
HTML does not support indexes, a very useful feature of the info document format. I find most PDF viewers cumbersome for screen browsing; not every surprising since it is a *printer* format at the core.
I find it too bad that a not-so-good default user interface is rebuffing users before then even start to see the nice features of the format. The fix is to promote alternatives user interfaces, something I keep doing constantly (and which has already been done here).
Glibc change exposing bugs Posted Nov 12, 2010 13:59 UTC (Fri) by HelloWorld (guest, #56129) [Link]
What's your point? You can generate both PDF and HTML from info.
Glibc change exposing bugs Posted Nov 12, 2010 20:10 UTC (Fri) by nicooo (guest, #69134) [Link]
That's texinfo. Using info for online documentation is what everyone hates.
Glibc change exposing bugs Posted Nov 12, 2010 23:32 UTC (Fri) by Wol (guest, #4433) [Link]
And pdf is (done properly) one big page, just like man :-)
Which is why I like man, and like pdf, and just curse profusely every time I'm exhorted to use info!
Cheers,
|
|||||||||||||