-
Notifications
You must be signed in to change notification settings - Fork 407
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
Empty attribute "xml:lang" reported as invalid, even though is valid #777
Comments
HTML 5.0 also says it explicitly:
It's a pretty rare to find, though. You can use zxx for non-linguistic content. You have text you have no idea what language it is in? |
My case is that of a body of text sprinkled with some words in different languages, for which I applied, to all, the same pattern:
One word in particular is in a fictional language, so I left the value of its My case is irrelevant, though. I can put up with doing it different for that lone word. P.S.: I actually found it strange that the HTML standard went with an empty value for signifying “Unknown”, since ISO 639-2 does have |
Definitely a bug. I was just curious what you ran into. Thanks. |
Matt, any chance you can fix the Schema and make a PullRequest? Otherwise I'd take this in the next week or so... |
I did it. I will create a pull request. |
Fixed an merged in |
I'm trying to upload a book to play store but I keep getting this error please help me |
Are you getting it from HTML, SVG or the package document? It looks like the package document schema has the same problem, as it validates against xsd:language which doesn't allow for empty strings. |
An empty `xml:lang` attribute can explicitly indicate that the content does not inherit the context language. Fixes #777
An empty `xml:lang` attribute can explicitly indicate that the content does not inherit the context language. Fixes #777
I believe we are now not detecting a missing xml:lang="en" attribute entirely for content documents when you relaxed the xml:lang="" check. Ace no longer reports an error when we have
I would expect that to flag an error that we also require xml:lang="en" as well as lang="en" |
I'm not sure this is the right place for reporting this, as it's valid as far as epubcheck is concerned. It's best practice to define both attributes because xhtml content documents may get served up as text/html, but it's not a requirement. The only requirement is that the languages match if both attributes are specified. It's technically better to specify |
EpubCheck v4.0.2 (installed via Homebrew on Mac) chokes with
xml:lang
attributes that have no value assigned, such as:by saying:
But Language tags in HTML and XML states that:
The text was updated successfully, but these errors were encountered: