RE: [docbook-apps] Ripping out a@name generating code from thestylesheets [was: <link linkend> in XHTML output]

["David Cramer" <dcramer@motive.com>]

> -----Original Message-----
> From: Michael(tm) Smith [mailto:smith@sideshowbarker.net] 
> Sent: Thursday, October 02, 2008 10:55 AM
> To: Jirka Kosek
> Cc: David Cramer; DocBook Apps
> Subject: Re: [docbook-apps] Ripping out a@name generating 
> code from thestylesheets [was: <link linkend> in XHTML output]
> 
> Jirka Kosek <jirka@kosek.cz>, 2008-10-02 17:08 +0200:
> 
> > Michael(tm) Smith wrote:
> > 
> > > That reminds me: Wasn't there some discussion a while 
> back about the 
> > > DocBook Project revising the stylesheets so that they 
> never output 
> > > a@name at all? I think all browsers in wide use today 
> understand @id 
> > > just fine and don't need a@name. Or is there some other 
> reason for 
> > > keeping the a@name stuff that I'm missing?
> > 
> > If you are delivering your HTML generated from DocBook to QNX 
> > operating system @id is of no use ;-)
> > 
> > Not very common case, but I few months ago I did very extensive 
> > customization of stylesheet to output very small HTML 
> subset supported 
> > on that operating system.
> 
> To me, that would suggest we make the a@name output a user 
> option, but change the default to be to not to output it anymore.
> 
>   --Mike

Elsewhere in the thread I mentioned previously, Brett Leber had asked
about dropping a@name:

http://thread.gmane.org/gmane.text.docbook.apps/18971/focus=19025 

He links to an article on the subject, but that site is down for me. In
his post, he quotes from the article: "Note that Netscape 4 does not
properly support this, neither do some mobile browsers. In the case of
the latter, at least, we can expect them to add support for this in the
foreseeable future, whereas those who still have to support Netscape 4
will be less fortunate."

David