-
Notifications
You must be signed in to change notification settings - Fork 19
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
How do we represent Kana for book title/publisher name/creator name #309
Comments
We don't have the equivalent of I think the title of this issue is misleading though, as it doesn't have anything to do with If you're trying to translate something, this is how it could be handled right now:
If we move to language maps, this would be expressed as:
|
Thanks @HadrienGardeur for referring. This is not different language script or translation. And I am not requesting equivalent of "file-as" (since even though "file-as" has equivalent item in wpub we still can not resolve the problem. That is why I try to avoid just put "file-as" in title.).
As you can see from above example, "クモノイト" is just marked as additional information to this title and value of "file-as" could be anything rather than Kana. But RS needs more specific information to parse it and say "ok, クモノイト is Kana for this title 蜘蛛の糸 now we can use クモノイト as hint to sort books in library" |
Well, kana (hiragana / katagana) being scripts, a title in japanese + kana can be referenced via I believe an alternate title in kana can be expressed as:
|
oh, ok thanks @llemeurfr yes seems So it could be:
|
This is split from https://github.com/w3c/wpub/issues/299#issuecomment-413542119
In epub 3 we use following way to represent Kana ("クモノイト", pronunciation) versionand Kanji version ("蜘蛛の糸") of title.
Can we find a way to represent this more properly?
The use case is RS needs Kana information of title or author to sort side-load Japanese book correctly. I have to say even though in epub "file-as" is still not a good solution since "file-as" can have too much information (such as script) rather than Kana.
How can we do this better?
The text was updated successfully, but these errors were encountered: