Comments on: First experiments with itext http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/ Silvia's blog Sun, 28 Feb 2010 17:51:54 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: joab jackson (joabj) 's status on Friday, 21-Aug-09 13:46:34 UTC - Identi.ca http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1236 joab jackson (joabj) 's status on Friday, 21-Aug-09 13:46:34 UTC - Identi.ca Fri, 21 Aug 2009 13:46:42 +0000 http://blog.gingertech.net/?p=478#comment-1236 [...] Captioning for HTML 5 video (blog) http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/ [...] [...] Captioning for HTML 5 video (blog) http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/ [...]

]]> By: silvia http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1148 silvia Sat, 01 Aug 2009 09:51:24 +0000 http://blog.gingertech.net/?p=478#comment-1148 @pvagner : these comments are exactly what I would like to get! To change the itext language, you have to go through the menu that is created through the "text" button (which I have now alt annotated after some other feedback to "Access Subtitles, Captions and Audio Descriptions - press space bar"). This opens a menu with the different time-aligned text types, each with a submenu of the different languages. I have been made aware that this is not accessible but have not found out yet how to fix that. I have a hunch that it may need to be a treewidget according to http://www.w3.org/TR/wai-aria/ , but haven't tried that yet. Thanks a lot for your help! @pvagner : these comments are exactly what I would like to get!

To change the itext language, you have to go through the menu that is created through the “text” button (which I have now alt annotated after some other feedback to “Access Subtitles, Captions and Audio Descriptions – press space bar”). This opens a menu with the different time-aligned text types, each with a submenu of the different languages. I have been made aware that this is not accessible but have not found out yet how to fix that. I have a hunch that it may need to be a treewidget according to http://www.w3.org/TR/wai-aria/ , but haven’t tried that yet.

Thanks a lot for your help!

]]> By: silvia http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1147 silvia Sat, 01 Aug 2009 09:44:56 +0000 http://blog.gingertech.net/?p=478#comment-1147 @Ms2ger any proposals for new names and generally better naming welcome! @Ms2ger any proposals for new names and generally better naming welcome!

]]> By: Ms2ger http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1140 Ms2ger Fri, 31 Jul 2009 12:40:47 +0000 http://blog.gingertech.net/?p=478#comment-1140 No problem. Itextlist does indeed look promising (apart from the name, but I don't have a counter-proposal). No problem. Itextlist does indeed look promising (apart from the name, but I don’t have a counter-proposal).

]]> By: pvagner http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1139 pvagner Fri, 31 Jul 2009 12:38:48 +0000 http://blog.gingertech.net/?p=478#comment-1139 Hello, This is perfect. I am testing the demo with NVDA. It picks up audio text fine. However I am perhaps doing something wrong I seem to be unable to change the itext language and also I am unable to locate the list of cue points. I am testing with latest nightly of Seamonkey 2.0 and Firefox 3.5. I can recognize the video element which has control buttons disabled by default, then I can see a few hiperlinks saying play, stop, loudness and text. Is the text link supposed to trigger an action allowing to do something? I know comments like this may not be appropriate in such an early stage of development but Iam so excited about it so I'm trying to work out what I am doing wrong. Thanks. Hello,
This is perfect. I am testing the demo with NVDA. It picks up audio text fine. However I am perhaps doing something wrong I seem to be unable to change the itext language and also I am unable to locate the list of cue points. I am testing with latest nightly of Seamonkey 2.0 and Firefox 3.5.
I can recognize the video element which has control buttons disabled by default, then I can see a few hiperlinks saying play, stop, loudness and text. Is the text link supposed to trigger an action allowing to do something?
I know comments like this may not be appropriate in such an early stage of development but Iam so excited about it so I’m trying to work out what I am doing wrong.
Thanks.

]]> By: silvia http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1138 silvia Fri, 31 Jul 2009 11:36:42 +0000 http://blog.gingertech.net/?p=478#comment-1138 Thanks, Ms2ger, for re-typing the code. I know what a pain it is. :-) I don't think we can do without the @charset attribute, but I do agree that @display may not be necessary. Or rather, it could be associated with a superior tag like the itextlist that I am currently considering. That would also remove the @category attribute. It would be something like: <itextlist category="CC" @activelang="es"> <itext lang="es" src="elephant.spanish.srt" charset="ISO-8859"/> <itext lang="en" src="elephant.english.srt"/> </itextlist> Thanks, Ms2ger, for re-typing the code. I know what a pain it is. :-)

I don’t think we can do without the @charset attribute, but I do agree that @display may not be necessary. Or rather, it could be associated with a superior tag like the itextlist that I am currently considering. That would also remove the @category attribute.

It would be something like:
<itextlist category=”CC” @activelang=”es”>
<itext lang=”es” src=”elephant.spanish.srt” charset=”ISO-8859″/>
<itext lang=”en” src=”elephant.english.srt”/>
</itextlist>

]]> By: Ms2ger http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1137 Ms2ger Fri, 31 Jul 2009 10:50:53 +0000 http://blog.gingertech.net/?p=478#comment-1137 That should've been <itext lang="es" type="text/srt" charset="ISO-8859" display="auto" src="subtitles/elephant.spanish.srt" category="CC"></itext> and <itext lang="es" src="subtitles/elephant.spanish.srt" cat="CC"> respectively. (I seem to have forgotten to mention that I'd drop the end-tag too.) That should’ve been <itext lang=”es” type=”text/srt” charset=”ISO-8859″ display=”auto” src=”subtitles/elephant.spanish.srt” category=”CC”></itext> and <itext lang=”es” src=”subtitles/elephant.spanish.srt” cat=”CC”> respectively. (I seem to have forgotten to mention that I’d drop the end-tag too.)

]]> By: Bruce Lawson’s personal site  : Accessibility of HTML 5 video http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1136 Bruce Lawson’s personal site  : Accessibility of HTML 5 video Fri, 31 Jul 2009 09:09:50 +0000 http://blog.gingertech.net/?p=478#comment-1136 [...] that we can work with Mozilla and Apple on something similar to what Silvia Pfeiffer presents in http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/ Although I haven’t looked at the source code, I assume that this demo uses the less than [...] [...] that we can work with Mozilla and Apple on something similar to what Silvia Pfeiffer presents in http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/ Although I haven’t looked at the source code, I assume that this demo uses the less than [...]

]]> By: silvia http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1132 silvia Fri, 31 Jul 2009 01:13:31 +0000 http://blog.gingertech.net/?p=478#comment-1132 Ms2ger, Thanks for your feedback! Would you mind re-posting those examples that seem to have been munged. Please escape < with < . SRT as it is currently defined does not contain the charset, which is why it is an attribute in itext. This why the proposal allows for different file types. The next file types I am going to experiment with are LRC and DFXP. It may well not be necessary to have a type attribute for these, but it makes it more explicit. As for @category and @display - I have indeed a new suggestion for how to specify these with less "text" - it includes the creation of a hierarchical element on top of the itext element, see https://wiki.mozilla.org/Accessibility/Experiment1_feedback#Thoughts_.2F_Feedback and itextlist. As for ISO-8859-1 - it is indeed different to ISO-8859, since some characters were displayed wrongly if I used the other one. I am not a charset expert, so cannot explain why, but I know when choosing the wrong one I got the wrong characters. Ms2ger,

Thanks for your feedback! Would you mind re-posting those examples that seem to have been munged. Please escape < with &lt; .

SRT as it is currently defined does not contain the charset, which is why it is an attribute in itext. This why the proposal allows for different file types.

The next file types I am going to experiment with are LRC and DFXP. It may well not be necessary to have a type attribute for these, but it makes it more explicit.

As for @category and @display – I have indeed a new suggestion for how to specify these with less “text” – it includes the creation of a hierarchical element on top of the itext element, see https://wiki.mozilla.org/Accessibility/Experiment1_feedback#Thoughts_.2F_Feedback and itextlist.

As for ISO-8859-1 – it is indeed different to ISO-8859, since some characters were displayed wrongly if I used the other one. I am not a charset expert, so cannot explain why, but I know when choosing the wrong one I got the wrong characters.

]]> By: Ms2ger http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/comment-page-1/#comment-1131 Ms2ger Thu, 30 Jul 2009 16:30:42 +0000 http://blog.gingertech.net/?p=478#comment-1131 It looks interesting to me, but from a quick read I'd say that in the current proposal (at least in the demo) there's too much boilerplate code. At least one of the arguments pro HTML5 is that it doesn't require more typing than necessary (see the doctype, meta charset, etc.). So, personally, I'd drop @type and shorten @category. I'd also put @charset in the SRT file itself, or at least in the HTTP headers, where it is less likely to be out of sync with the content. (I guess that's not possible with the format as it stands today, but it needs a better spec anyway. I guess a charset declaration could be added at the same time.) Finally, I'd make @display default to "auto", and make the behavior dependent on the language and the category. (E.g. always display the cue points.) I.e., instead of I'd prefer something closer to . (Also, shouldn't that use "ISO-8859-1" rather than "ISO-8859"?) It looks interesting to me, but from a quick read I’d say that in the current proposal (at least in the demo) there’s too much boilerplate code. At least one of the arguments pro HTML5 is that it doesn’t require more typing than necessary (see the doctype, meta charset, etc.).

So, personally, I’d drop @type and shorten @category. I’d also put @charset in the SRT file itself, or at least in the HTTP headers, where it is less likely to be out of sync with the content. (I guess that’s not possible with the format as it stands today, but it needs a better spec anyway. I guess a charset declaration could be added at the same time.) Finally, I’d make @display default to “auto”, and make the behavior dependent on the language and the category. (E.g. always display the cue points.)

I.e., instead of I’d prefer something closer to .

(Also, shouldn’t that use “ISO-8859-1″ rather than “ISO-8859″?)

]]>