[BRLTTY] Is there still need for the manual to mention drivers in the kernel?

[Dave Mielke]

[quoted lines by Lee Maschmeyer on 2008/03/26 at 16:02 -0400]

>While looking at the manual (build 3643) I ran across mention of giving 
>driver parameters if the driver was in the kernel or a module (putting them 
>in the LILO config file for example). Is this still pertinent? I've been 
>using brltty for 5 years and I think all this predates any of my experience. 
>Does it serve any purpose other than scare the bejunior out of newbies?

That paragraph has now been removed.

>Also and not very related, I saw on the internet that the command sgml2txt 
>is "an old and obsoleted form of the linuxdoc -b command." I suppose this is 
>known and just hasn't been worth the bother to change, 

It's risky to make such assumptions. No, it wasn't known, at least by myself. 
Further investigation reveals, though, that linuxdoc itself appears to be 
somewhat obsolete. Its own man page says:

   The  linuxdoc  suite  is  provided  for backward compatibility, because 
   there are still many useful documents  written  in  LinuxDoc  DTD  sgml 
   source.

So ... Should we actually be upgrading to some newer format?

>but it's interesting that the text version of the manual can't really be 
>displayed successfully by less, at least on Red Hat Enterprise Linux. (It 
>works but displays hex characters in Stefane Doyon's name among many other 
>places.) The text version is however the best place to look if you have to 
>search for something.

Neither sgml2txt nor linuxdoc -B txt offers UTF-8 output. I suppose, though, 
that we could pass the Latin1 output through iconv.

-- 
Dave Mielke           | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave at mielke.cc | Canada  K2A 1H7   | if you're concerned about Hell.
http://FamilyRadio.com/                   | http://Mielke.cc/bible/