-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yiddish in captions/subtitles #38
Comments
Propose closing this given that:
|
We don't appear to have much momentum towards that objective @palemieux so in the short term I would advocate simply adding the missing codepoints. |
@nigelmegitt My point is that Yiddish is already included through CLDR, and that we should not try to modify the supplemental IMSC-specific tables. |
@palemieux OK I guess we don't try to be exhaustive in listing all the languages, so that's reasonable. |
The Working Group just discussed
The full IRC log of that discussion<nigel> Topic: Yiddish in captions/subtitles imsc#38<nigel> github: https://github.com//issues/38 <nigel> Pierre: I confirmed recently that Yiddish is present in CLDR. <nigel> RESOLUTION: WG agrees to close with no action |
From https://lists.w3.org/Archives/Public/public-tt/2015Jun/0001.html
http://en.wikipedia.org/wiki/Unicode_and_HTML_for_the_Hebrew_alphabet
Why are 05F0-05F2 excluded? (They're Yiddish, but is there a reason to
discriminate against Yiddish? Yiddish theater is real)
And, why would you exclude 059x, 05Ax, 05C4-05C7?
A perfectly reasonable thing to do w/ captions would be to caption
someone chanting from the Torah, or chanting a Haftarah which means
you'd need almost all of these (? is included in the text, but I
suppose you could argue for dropping from captions, I'd personally
include it, since omitting it would take more effort).
(raised by Pierre-Anthony Lemieux on 2015-06-11)
From tracker issue http://www.w3.org/AudioVideo/TT/tracker/issues/391
The text was updated successfully, but these errors were encountered: