From: SourceForge.net <no...@so...> - 2010-11-11 07:44:33
|
RFEs item #3107140, was opened at 2010-11-11 07:44 Message generated for change (Tracker Item Submitted) made by dpawson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2010-12-15 18:18:06
|
RFEs item #3107140, was opened at 2010-11-11 02:44 Message generated for change (Comment added) made by nwalsh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 13:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2011-10-25 03:37:49
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2011-12-13 18:43:48
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by nwalsh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Norman Walsh (nwalsh) Date: 2011-12-13 10:43 Message: Dave? More detail? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2011-12-13 19:11:23
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by dpawson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Dave Pawson (dpawson) Date: 2011-12-13 11:11 Message: I object to the glossary entry on accessibility grounds. Why should the blind reader have to follow a link to have the term explained (or a sighted reader for that matter) Ditto alt, on an inline? Not on for my 2c. If you won't add markup please accept that and clear this rfe. Semantic markup as the acronym marked up, and provides the expansion there, and at the same point in the document. Just my view. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2011-12-13 10:43 Message: Dave? More detail? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2012-01-13 04:08:08
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by nwalsh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2012-01-12 20:08 Message: I'm not prepared to say that we won't add markup for this case, but I think we need to understand it better. Are you using a reader on the DocBook XML sources? I was assuming that you were generating HTML of some sort with embedded markup for the reader. The suggestion to use glossary doesn't prevent you from inlining the expansions in the generated text. Could you provide some concrete examples of the markup that you'd like to use? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2011-12-13 11:11 Message: I object to the glossary entry on accessibility grounds. Why should the blind reader have to follow a link to have the term explained (or a sighted reader for that matter) Ditto alt, on an inline? Not on for my 2c. If you won't add markup please accept that and clear this rfe. Semantic markup as the acronym marked up, and provides the expansion there, and at the same point in the document. Just my view. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2011-12-13 10:43 Message: Dave? More detail? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2012-01-13 06:15:45
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by dpawson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Dave Pawson (dpawson) Date: 2012-01-12 22:15 Message: I'm not fussy about the gi, but something like <acronym>RNIB<expansion>Royal National Institute of the Blind</expansion></rnib> would provide quick access for a TTS engine (or a sighted reader) ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2012-01-12 20:08 Message: I'm not prepared to say that we won't add markup for this case, but I think we need to understand it better. Are you using a reader on the DocBook XML sources? I was assuming that you were generating HTML of some sort with embedded markup for the reader. The suggestion to use glossary doesn't prevent you from inlining the expansions in the generated text. Could you provide some concrete examples of the markup that you'd like to use? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2011-12-13 11:11 Message: I object to the glossary entry on accessibility grounds. Why should the blind reader have to follow a link to have the term explained (or a sighted reader for that matter) Ditto alt, on an inline? Not on for my 2c. If you won't add markup please accept that and clear this rfe. Semantic markup as the acronym marked up, and provides the expansion there, and at the same point in the document. Just my view. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2011-12-13 10:43 Message: Dave? More detail? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2012-01-18 17:48:32
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by nwalsh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Norman Walsh (nwalsh) Date: 2012-01-18 09:48 Message: Why is <acronym>RNIB<alt>Royal National Institute of the Blind</alt></acronym> not an acceptable alternative? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2012-01-12 22:15 Message: I'm not fussy about the gi, but something like <acronym>RNIB<expansion>Royal National Institute of the Blind</expansion></rnib> would provide quick access for a TTS engine (or a sighted reader) ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2012-01-12 20:08 Message: I'm not prepared to say that we won't add markup for this case, but I think we need to understand it better. Are you using a reader on the DocBook XML sources? I was assuming that you were generating HTML of some sort with embedded markup for the reader. The suggestion to use glossary doesn't prevent you from inlining the expansions in the generated text. Could you provide some concrete examples of the markup that you'd like to use? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2011-12-13 11:11 Message: I object to the glossary entry on accessibility grounds. Why should the blind reader have to follow a link to have the term explained (or a sighted reader for that matter) Ditto alt, on an inline? Not on for my 2c. If you won't add markup please accept that and clear this rfe. Semantic markup as the acronym marked up, and provides the expansion there, and at the same point in the document. Just my view. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2011-12-13 10:43 Message: Dave? More detail? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2012-01-18 17:53:11
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by dpawson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Dave Pawson (dpawson) Date: 2012-01-18 09:53 Message: <acronym>RNIB<alt>Royal ... </alt></acronym> is fine by me. Sigh. I guess it is an alternative... I'd have preferred expansion as better semantics but I'll be satisfied with this Norm. Please close the rfe. Dave ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2012-01-18 09:48 Message: Why is <acronym>RNIB<alt>Royal National Institute of the Blind</alt></acronym> not an acceptable alternative? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2012-01-12 22:15 Message: I'm not fussy about the gi, but something like <acronym>RNIB<expansion>Royal National Institute of the Blind</expansion></rnib> would provide quick access for a TTS engine (or a sighted reader) ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2012-01-12 20:08 Message: I'm not prepared to say that we won't add markup for this case, but I think we need to understand it better. Are you using a reader on the DocBook XML sources? I was assuming that you were generating HTML of some sort with embedded markup for the reader. The suggestion to use glossary doesn't prevent you from inlining the expansions in the generated text. Could you provide some concrete examples of the markup that you'd like to use? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2011-12-13 11:11 Message: I object to the glossary entry on accessibility grounds. Why should the blind reader have to follow a link to have the term explained (or a sighted reader for that matter) Ditto alt, on an inline? Not on for my 2c. If you won't add markup please accept that and clear this rfe. Semantic markup as the acronym marked up, and provides the expansion there, and at the same point in the document. Just my view. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2011-12-13 10:43 Message: Dave? More detail? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |
From: SourceForge.net <no...@so...> - 2012-03-20 19:25:59
|
RFEs item #3107140, was opened at 2010-11-10 23:44 Message generated for change (Comment added) made by nwalsh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XML Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Dave Pawson (dpawson) Assigned to: Norman Walsh (nwalsh) Summary: aconym expansion inline Initial Comment: Provide markup within the acronym tag to enable a tts system to read out the acronym expansion immediately after the acronym itself. I note the rejection of the previous rfe. This is a simple accessibility request. Markup should be optional. termdef may be appropriate. ---------------------------------------------------------------------- >Comment By: Norman Walsh (nwalsh) Date: 2012-03-20 12:25 Message: Thanks, Dave. ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2012-01-18 09:53 Message: <acronym>RNIB<alt>Royal ... </alt></acronym> is fine by me. Sigh. I guess it is an alternative... I'd have preferred expansion as better semantics but I'll be satisfied with this Norm. Please close the rfe. Dave ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2012-01-18 09:48 Message: Why is <acronym>RNIB<alt>Royal National Institute of the Blind</alt></acronym> not an acceptable alternative? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2012-01-12 22:15 Message: I'm not fussy about the gi, but something like <acronym>RNIB<expansion>Royal National Institute of the Blind</expansion></rnib> would provide quick access for a TTS engine (or a sighted reader) ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2012-01-12 20:08 Message: I'm not prepared to say that we won't add markup for this case, but I think we need to understand it better. Are you using a reader on the DocBook XML sources? I was assuming that you were generating HTML of some sort with embedded markup for the reader. The suggestion to use glossary doesn't prevent you from inlining the expansions in the generated text. Could you provide some concrete examples of the markup that you'd like to use? ---------------------------------------------------------------------- Comment By: Dave Pawson (dpawson) Date: 2011-12-13 11:11 Message: I object to the glossary entry on accessibility grounds. Why should the blind reader have to follow a link to have the term explained (or a sighted reader for that matter) Ditto alt, on an inline? Not on for my 2c. If you won't add markup please accept that and clear this rfe. Semantic markup as the acronym marked up, and provides the expansion there, and at the same point in the document. Just my view. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2011-12-13 10:43 Message: Dave? More detail? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2011-10-24 20:37 Message: I notice that the stylesheets already use any alt element within acronym and abbrev as the value of the title attribute. ---------------------------------------------------------------------- Comment By: Norman Walsh (nwalsh) Date: 2010-12-15 10:18 Message: Dave, We talked about this on the call today. It seems that there are two existing approaches that would work. First, you could put the acronyms in a glossary, point to the glossary entries, and get the expansions from there. If you wanted a one-off entry without all the glossary machinery, you could use alt for this purpose. If neither of those approaches satisfies your use case, could you provide a little more detail for us? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384107&aid=3107140&group_id=21935 |