[Bug 10320] Allow an arbitrary string as the voice for forwards compatilbity

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10320

--- Comment #11 from Philip Jägenstedt <philipj@opera.com> 2010-10-03 02:21:19 UTC ---
As part of my presentation for OVC I implemented most of the WebSRT parser and
the interfaces, but none of the rendering rules. I also added the <v bla>
syntax and tried it out a bit:

http://people.opera.com/philipj/2010/10/02/ovc/demos/captions.html
http://people.opera.com/philipj/2010/10/02/ovc/demos/transcript.html
http://people.opera.com/philipj/2010/10/02/ovc/demos/metadata.html (a bit
stupid)

There are some issues that we may or may not want to address:

* In the movie I was translating, no characters have any names, and there are 3
people I would have called "Advisor", but I ended up calling the two least
important of them "Advisor (brown)" and "Advisor (black)" based on their color
of clothing. If it wasn't needed to disambiguate in the same scene, I would
have just called them all "Advisor". I think it's safe to assume that if we use
<v THIS STRING HERE> for styling, some characters will appear under several
names and some names be used for several characters. Not sure if it's a
real-world problem.

* For the HoH, you need to have cues for laughter, "hmpf" and such. I expressed
that as <v Character><sound>Hmpf!, which isn't really 2 voices as the syntax
implies. Essentially, what I want is a hook that means "show this when sound is
not available", which is how I'm using <sound>.

* Not sure how to mark up on-screen text that needs to be translated, like the
title of the film and "The End". I just made them italics. Have no strong
opinion.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 3 October 2010 02:21:23 UTC