Re: [docbook-apps] Generating title for link element
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 of the link into the title attribute is not useful for that purpose. I mean, the text is present in the link element, and would be read by the screen reader. Duplicating that text in the title attribute would be redundant, wouldn't it? Yes it would be redundant and highly undesirable from an accessibility point of view to have link text duplicated in title-attribute, esp. as default behaviour. I just have been getting up-to-date on this topic via accessibility lists and literature: Actually, the very best practice with links is to have a descriptive word or phrase as the visible link text (including an accessible indication if the link is site external). Since title-tag visibility is very variable between user agents (browser,screen reader + indiv. settings) and user requirements (e.g. low vision: title tooltip text doesn't resize), the information in title should, in the best case, be a dispensable bit of extra information. HTH Nathalie -- Nathalie Sequeira webseiten mit *n-faktor robust*benutzbar*barrierefrei www.n-faktor.net Türingstr. 6 6020 Innsbruck Mobil: 0650 224 3336 n...@n-faktor.net - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Generating title for link element
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 except for 'et al'. I'll need to find out how to select the content of a link and its children. While not an expert on accessibility, I feel it is a W3C recommendation to have an 'alt' attribute for images and 'title' for textual links - but I'd like to hear from others on this. Dave Gardiner It seems the system is preserving you from making an overdone accessibility-error :) (plz see my previous post to the thread) Just imagine: your screen reader reads to you first the (for us) visible link text, and then reads it again. Someone who sees doesn't need the same info over again either, they're going to go click that link BECAUSE they already read the visible text :) The thing with accessibility is that it's always relative. YES, USE the possibilities offered by HTML to make texts more accessible. USE semantically structured markup, use the available tags and attributes to make everyones lives easier. But do so wisely and frugally. With alt, for example: if you have purely decorative images, it's much more useful (and usable/accessible) to leave alt empty (alt=) instead of finding some weird description just so that alt has something in it -- then a blind user will know: this image is not important for the understanding of the content. Truly content-relevant images, however, should include more than what is usually offered in terms of explanation :) HTH! Nathalie - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] listitem/para output in XHTML
[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 can change inthe code for xsl:template match=d:itemizedlist/d:listitem ? Dave Gardiner
Re: [docbook-apps] HTML/XHTML: a:name vs. a:id?
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 stylesheet side if you are using Saxon. Saxon supports xhtml output method even in XSLT 1.0 code. This output method automatically adds closing tags to problematic elements like a, script, div, ... xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:saxon=http://icl.com/saxon; exclude-result-prefixes=saxon version=1.0 xsl:import href=.../path/to/xhtml/chunk.xsl/ xsl:param name=chunker.output.methodsaxon:xhtml/xsl:param xsl:param name=chunker.output.indentyes/xsl:param xsl:param name=chunker.output.omit-xml-declarationyes/xsl:param /xsl:stylesheet HTH, Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
[docbook-apps] Is-it possible to include TEI parts in a docbook book?
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 this? Thanks Eric! - - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] HTML/XHTML: a:name vs. a:id?
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 some other values you could add to this parameter? Robert On Mon, Dec 13, 2010 at 5:30 AM, Jirka Kosek ji...@kosek.cz wrote: 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 stylesheet side if you are using Saxon. Saxon supports xhtml output method even in XSLT 1.0 code. This output method automatically adds closing tags to problematic elements like a, script, div, ... xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:saxon=http://icl.com/saxon; exclude-result-prefixes=saxon version=1.0 xsl:import href=.../path/to/xhtml/chunk.xsl/ xsl:param name=chunker.output.methodsaxon:xhtml/xsl:param xsl:param name=chunker.output.indentyes/xsl:param xsl:param name=chunker.output.omit-xml-declarationyes/xsl:param /xsl:stylesheet HTH, Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Re: HTML: suppress abstract in html body?
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 b...@sagehill.net wrote: Hi Robert, An abstract that appears inside an info element is handled by the titlepage system. You can edit the titlepage spec file to remove abstract, and regenerate the titlepage templates to get rid of it. If your abstract appears outside of info, then you can just define an empty template to turn it off: xsl:template match=abstract/ The template that generates the meta element does not use a template that matches on abstract, but selects the content directly (it is in the template named 'head.content' in html/docbook.xsl). Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Robert Nagle idiotprogram...@gmail.com To: docbook-apps@lists.oasis-open.org Sent: Sunday, December 12, 2010 4:15 PM Subject: [docbook-apps] Re: HTML: suppress abstract in html body? At the risk of trying your patience, I wish to clarify what i mean by my previous message. I want the abstract to appear in the meta description= of HTML output but not in the body itself. rj On Sun, Dec 12, 2010 at 5:57 PM, Robert Nagle idiotprogram...@gmail.com wrote: For HTML Output, I notice that with a parameter (generate.meta.abstract), the value of ABSTRACT can be used to generate meta description= information in the head. Can anyone suggest a way to suppress the value of the abstract element in HTML output (i.e., div class=abstract title=AbstractpThis is a test of the emergency broadcast system. /p/div I realize that in css I could change the class to visibility: hidden, but I want to avoid doing that if possible. -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] HTML/XHTML: a:name vs. a:id?
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 parameter? You can create your own serializer and reference it from here, see: http://saxon.sourceforge.net/saxon6.5.5/extensions.html#output -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] listitem/para output in XHTML
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: xsl:template match=listitem/*[1][self::para] xsl:apply-templates/ /xsl:template I suspect you might also accomplish the formatting change with CSS, although I'm not clear how. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: redlettucemail To: docbook-apps@lists.oasis-open.org Sent: Monday, December 13, 2010 3:03 AM Subject: [docbook-apps] listitem/para output in XHTML 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 can change in the code for xsl:template match=d:itemizedlist/d:listitem ? Dave Gardiner
Re: [docbook-apps] HTML/XHTML: a:name vs. a:id?
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 major customization if your input is heterogenous. Keith - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Generating title for link element
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 it is to repeat the link text as alternate text. It's a little bit like the adage, If you have nothing good to say, don't say anything at all. :-) All that is accomplished by putting in the text twice is forcing people to read it twice, which is more of a nuisance than a help. I would argue that if the link text is the title of the target section, that is good enough. If the link text is a description, that is also good enough. Alternate text is useful only if you have a link that doesn't actually tell you what you're linking to (like click here). From: Bob Stayton [mailto:b...@sagehill.net] Sent: Friday, December 10, 2010 9:58 AM To: redlettucemail; docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Generating title for link element Hi Dave, Indeed, it is important. Currently a title attribute is automatically generated on the a element for a cross reference when the target element of the link has a title. The title attribute in the link is the title of the target. 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 of the link into the title attribute is not useful for that purpose. I mean, the text is present in the link element, and would be read by the screen reader. Duplicating that text in the title attribute would be redundant, wouldn't it? I'm curious what others with experience in accessibility requirements think. Bob Stayton Sagehill Enterprises b...@sagehill.netmailto:b...@sagehill.net - Original Message - From: redlettucemailmailto:redlettucem...@mailscan.acenet.net.au To: docbook-apps@lists.oasis-open.orgmailto:docbook-apps@lists.oasis-open.org Sent: Thursday, December 09, 2010 5:25 PM Subject: Re: [docbook-apps] Generating title for link element Bob, That worked beautifully thanks. That piece of code should be in the next release of the stylesheets, as a title attribute is important from an accessibility point of view. Dave Gardiner
[docbook-apps] Question about role-based images
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 fileref=Graphics/network-topology_one-subnet.svg align=center scalefit=1//imageobject imageobject role=html imagedata format=PNG scale=75 fileref=Graphics/network-topology_one-subnet.png align=center scalefit=1//imageobject /mediaobject The HTML is: div class=mediaobject align=centerimg src=Graphics/network-topology_one-subnet.svg width=405 align=middle Version info for XSLTproc: Using libxml 20706, libxslt 10126 and libexslt 815 xsltproc was compiled against libxml 20706, libxslt 10126 and libexslt 815 libxslt 10126 was compiled against libxml 20706 libexslt 815 was compiled against libxml 20706 Solution? -- Steve Johnson, Senior Content Developer Caringo ste...@caringo.com - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] UPDATE: [docbook-apps] Question about role-based images
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 tried it and it didn't work. This is the XML I used: mediaobject imageobject role=fo imagedata format=SVG scale=75 fileref=Graphics/network-topology_one-subnet.svg align=center scalefit=1//imageobject imageobject role=html imagedata format=PNG scale=75 fileref=Graphics/network-topology_one-subnet.png align=center scalefit=1//imageobject /mediaobject The HTML is: div class=mediaobject align=centerimg src=Graphics/network-topology_one-subnet.svg width=405 align=middle Version info for XSLTproc: Using libxml 20706, libxslt 10126 and libexslt 815 xsltproc was compiled against libxml 20706, libxslt 10126 and libexslt 815 libxslt 10126 was compiled against libxml 20706 libexslt 815 was compiled against libxml 20706 Solution? -- Steve Johnson, Senior Content Developer Caringo ste...@caringo.com - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
