Hello Bob all,
I'm not clear that this customization to copy the link element's text
into the title attribute should be the default behavior. It was my
understanding that the title attribute was meant to add information
about the target of the link. It would seem to me that copying the
text
Hello Dave,
redlettucemail schrieb:
After a bit more testing, the code doesn't quite work. If there is an
'emphasis' tag inside a 'link', that text is not generated as a title.
For instance, I have citations with 'et al' in an emphasis, and the
generated title has the text of the citation
[mailto:docbook-a...@lists.oasis-open.org]for
orderedlist and itemizedlist elements, I need to remove the p tag that
is generated after li and ul in XHTML files. Currently, the
p tag forces text that occurs in a listitem to be placed on the next line
after the bullet point. Is there something I
Robert Nagle wrote:
(I find it odd that in 2010 the browsers don't render XHTML code with
a id=test / correctly).
The majority of browsers do this (exception here is IE) but you have to
serve XHTML with proper content type which almost nobody does today.
However, there is an easy fix on the
Hi,
I am formating and translating a language course (written in English and
for the Russian language).
There are some parts which are like a dictionary (the vocabulary): could
I use the TEI dictionary part and include it in my docbook document?
If it is possible, could you explain how to do
Jirka, Thanks, I never would have guessed that. I must have overlooked
those parameters. Oxygen uses saxon, so that works for me.
Just out of curiosity: you added a saxon namespace at the top; why?
Is xsl:param name=chunker.output.methodsaxon:xhtml/xsl:param a
saxon-only switch? What would be
Bob, Thanks. This solution worked perfectly.
Also: about suppressing the body attributes, this worked too although
I have a feeling that Jirka's suggestions about parameters to use when
using XHTML output might remove the need for that.
Robert
On Sun, Dec 12, 2010 at 7:57 PM, Bob Stayton
Robert Nagle wrote:
Just out of curiosity: you added a saxon namespace at the top; why?
Actually it is not necessary in this case. It's just recommended.
Is xsl:param name=chunker.output.methodsaxon:xhtml/xsl:param a
saxon-only switch? What would be some other values you could add to
this
Hi Dave,
The extra space is an artifact of some browsers, not all. It should not appear
in that context. That said ...
The p tag is coming from the para element inside the listitem. Actually,
the first para in the listitem. This template customization would remove the p
wrapper:
On Sun, Dec 12, 2010 at 4:12 PM, Robert Nagle idiotprogram...@gmail.com wrote:
that html uses a name = while xhtml output uses a id /
A different solution would be to change the way the anchor.attribute
is called to actually create h2 id=sect2Blah/h2 rather than the
a id=sect2/. This is a fairly
I'm not an accessibility expert, but I've been looking into some of these
issues lately. A lot of this is just common sense and applies to all readers,
not just those with what are commonly thought of as disabilities.
My understanding is that it is better to not have alternate text at all than
In the Stayton book in the section on SVG in HTML, there is an example
of using an SVG graphic for PDF and PNG for HTML. I tried it and it
didn't work.
This is the XML I used:
mediaobject
imageobject role=fo
imagedata format=SVG scale=75
Spoke too soon. I was doing a view source in Firefox. If I open the HTML
file on disk it's referencing a PNG.
Nevermind
On 12/13/2010 10:16 PM, Steve Johnson wrote:
In the Stayton book in the section on SVG in HTML, there is an example
of using an SVG graphic for PDF and PNG for HTML. I
13 matches
Mail list logo
