Re: [docbook-apps] xlink:title not getting into HTML, 1.77.1

[Jennifer Moore <jennifer@uncharted-worlds.org>]

Hi Bob

thanks for your reply!

> Can you supply more details:
>
> 1.  Are you using DocBook 4 or DocBook 5 XML?

5.

> 2.  Can you provide an example of your linking element with xlink:title
> in it?

OK, experiment coming up.  I've gone back and found an XML and HTML pair 
from an old article, that I hadn't touched for a couple of years.

XML original:
====
<link 
xlink:href="http://www.guardian.co.uk/commentisfree/2010/apr/25/david-cameron-david-mitchell"; 
xlink:title="Article, 25 April 2010">this article</link>
====

When I last did the HTML transform on that one, back in 2010, it wrote:
====
<a 
href="http://www.guardian.co.uk/commentisfree/2010/apr/25/david-cameron-david-mitchell"; 
title="Article, 25 April 2010">this article</a>
====

Doing it again just now, without changing the XML at all, produces:
====
<a class="ulink" 
href="http://www.guardian.co.uk/commentisfree/2010/apr/25/david-cameron-david-mitchell"; 
target="_top">this article</a>
====

> I presume since you are using Oxygen that your file validates and the
> xlink namespace is properly declared.

Well my understanding of namespace protocol is only middling, so 
wouldn't like to guarantee "yes", but here's what I've got...

XML declaration is like this:

<article xmlns="http://docbook.org/ns/docbook"; version="5.0"
	xmlns:xlink="http://www.w3.org/1999/xlink";>

Top-level XSL file has:

<xsl:stylesheet
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="1.0">

- should there be something else there?  oXygen does point me at that 
file, as the destination associated with the following "info" message 
from the transform reporting bit:

== quote from oXygen ==
SystemID: [redacted]/XSL/WordPressCustom/docbookWP.xsl
Description: Note: namesp. cut : stripped namespace before processing 
        Election day
== end quote ==
("Election day" is the name of the article)

which looks a bit suspicious maybe?  I think it's always thrown up that 
same message, but as it always used to do (or seem to be doing) 
everything fine in practice, I've always ignored it till now.  Could it 
be one of those things where it's technically always been an error but 
the software used to be more forgiving of it?

anyway that's what I've got so far...

thanks again

Jennifer

--
www.uncharted-worlds.org/blog/
newest recording www.single-bass.co.uk/songs/heavy-woman