attribute 'lang' error schema not satisfied

Leonatus · 02-25-2016, 10:22 AM

I have here an epub, obviously created with Sigil and Calibre. At running FlightCrew, I receive multiple errors of this type:

Quote:

Error schema not satisfied : attribute 'lang' is not declared for element 'span' near column 153

It refers for ex. to the following spot in the HTML:

Quote:

–*De tels avertissements ne sont pas rares, déclara-t-il Dans la Vita
Nuova

(I emphasized the respective passages)
The encoding looks like this:

Quote:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="fr">
<head>
<title>Le Fantôme de la rue Michel-Ange</title>
<meta content="http://www.w3.org/1999/xhtml; charset=utf-8" http-equiv="Content-Type"/>

There might be restrictions in the XML schema, but I can't see them, and I find no hint on how to mend the error messages.

There are no interferences to the readability of the book; in epubcheck, there don't even appear error messages. But, anyway, I would like to know what's wrong there. Is there a crack online who could help? Thanks in advance!

Toxaris · 02-25-2016, 11:38 AM

It should be , although I would set it in the opf if it is for all content.

Leonatus · 02-25-2016, 01:45 PM

thank you, Toxaris, I had forgotten to say that, to set the declaration lowercase, was one of the first things I tried, but to no avail. It seems, besides, that this kind of declaration is not case-sensitive, but I'm no expert. At the spots of further occurence of the error messages, there are f. ex "FR-CA", which I changed into "fr-CA" or "fr-ca", all without effect.

The spans are there, because the setting into a different language occurs, indeed, only exceptionally. Thus, the spans seem correct to me, so far.

Toxaris · 02-25-2016, 01:57 PM

Well, you can of course also use . That one is valid for XML. That one will validate.

According to the W3 both are valid for XHTML, but the xml:lang seems to be the better one to use.

Leonatus · 02-25-2016, 02:53 PM

Yep, this did it! I hadn't found any restriction on this either.Maybe it's just a FlightCrew speciality.
Anyway, I hope this will help me for my own books in the future!
Thank you once more!

Leonatus · 03-24-2016, 05:40 AM

Addition: I noticed that FlightCrew even produces error messages, when the language declaration in the head section of a html is like this:

Code:

... lang="de" xml:lang="de"

When the first language declaration is deleted, FlightCrew is satisfied.

Only for people with the same problem.

fbrzvnrnd · 03-24-2016, 06:21 AM

Code:

lang="de"

is wrong. You have to use:

Code:

xml:lang="de"

Toxaris · 03-24-2016, 08:16 AM

Quote:

Originally Posted by fbrzvnrnd

Code:

lang="de"

is wrong. You have to use:

Code:

xml:lang="de"

No, officially both are correct and should be supported, see the W3 site. It seems however, that at least the validators do not seem to support the specification without the xml addition.

fbrzvnrnd · 03-24-2016, 08:35 AM

Quote:

Originally Posted by Toxaris

No, officially both are correct and should be supported, see the W3 site. It seems however, that at least the validators do not seem to support the specification without the xml addition.

Uh, XHTML 1.0? We are using the XHTML 1.1
Anyway you could be right: the latest version of XHTML1.1 says: "This document supersedes the previous edition of XHTML 1.1. It reflects clarifications and corrections as a result of many years of use by the community. It also includes an XML Schema implementation of the language, and integrates the lang attribute to increase compatibility with User Agents and Assistive Technologies".

So it seems the "lang" support has changed in time. My old Oxygen validator do not allow the lang attribute, but the last epubcheck allows it.

Leonatus · 03-24-2016, 08:44 AM

In my case, both declarations were included in the "head" sector of the html; the error message came in spite of the "correct" one beeing as well present.

And while doitsu's epubcheck accepted this, it was only Flightcrew that sensitive enough.

Doitsu · 03-24-2016, 11:30 AM

Quote:

Originally Posted by Leonatus

And while doitsu's epubcheck accepted this, it was only Flightcrew that sensitive enough.

Since ePubCheck is the official IDPF validator, you might want to ignore all FlightCrew messages that contradict ePubCheck.

BTW, the IDPF actually recommends that you use both both the lang and xml:lang attributes "for optimal accessibility."

JSWolf · 03-24-2016, 11:49 AM

Quote:

Originally Posted by Leonatus

In my case, both declarations were included in the "head" sector of the html; the error message came in spite of the "correct" one beeing as well present.

And while doitsu's epubcheck accepted this, it was only Flightcrew that sensitive enough.

If you find things that FC contradicts with EC or that EC reports as an error and FC doesn't or that FC reports as an error and EC does not, you might want to report these things so FC can be updated.

Doitsu · 03-24-2016, 11:58 AM

Quote:

Originally Posted by JSWolf

If you find things that FC contradicts with EC or that EC reports as an error and FC doesn't or that FC reports as an error and EC does not, you might want to report these things so FC can be updated.

Reporting FlightCrew bugs ẃould be rather pointless, since FlightCrew hasn't been updated since 2011 and neither the original developer nor the current maintainers will fix any bugs.

JSWolf · 03-24-2016, 05:42 PM

Quote:

Originally Posted by Doitsu

Reporting FlightCrew bugs ẃould be rather pointless, since FlightCrew hasn't been updated since 2011 and neither the original developer nor the current maintainers will fix any bugs.

Then why is FC still out there?

Doitsu · 03-24-2016, 07:37 PM

Quote:

Originally Posted by JSWolf

Then why is FC still out there?

Presumably because some people prefer it over epubcheck.

02-25-2016, 11:38 AM	#2
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	It should be <span lang="it">, although I would set it in the opf if it is for all content.

02-25-2016, 01:57 PM	#4
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	Well, you can of course also use <span xml:lang="it">. That one is valid for XML. That one will validate. According to the W3 both are valid for XHTML, but the xml:lang seems to be the better one to use.

03-24-2016, 05:40 AM	#6
Leonatus Wizard Posts: 1,055 Karma: 11391181 Join Date: Mar 2013 Location: Guben, Brandenburg, Germany Device: Kobo Clara 2E, Tolino Shine 3	Addition: I noticed that FlightCrew even produces error messages, when the language declaration in the head section of a html is like this: Code: ... lang="de" xml:lang="de" When the first language declaration is deleted, FlightCrew is satisfied. Only for people with the same problem.

03-24-2016, 06:21 AM	#7
fbrzvnrnd Fanatic Posts: 557 Karma: 400004 Join Date: Feb 2009 Device: ONYX M96	Code: lang="de" is wrong. You have to use: Code: xml:lang="de"

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Regex_function: attribute error	DrChiper	Calibre	2	11-21-2014 03:30 AM
Attribute Error on NoneType???	phossler	Editor	6	05-18-2014 10:21 AM
p attribute error on validation	landed	Calibre	2	02-13-2011 11:15 AM
Error: malformed database schema (books_insert_trg)	cbatalla	Calibre	4	05-08-2010 01:02 PM
Attribute error?	jusmee	Calibre	2	12-15-2009 08:22 PM

02-25-2016, 01:45 PM	#3
Leonatus Wizard Posts: 1,055 Karma: 11391181 Join Date: Mar 2013 Location: Guben, Brandenburg, Germany Device: Kobo Clara 2E, Tolino Shine 3	thank you, Toxaris, I had forgotten to say that, to set the declaration lowercase, was one of the first things I tried, but to no avail. It seems, besides, that this kind of declaration is not case-sensitive, but I'm no expert. At the spots of further occurence of the error messages, there are f. ex "FR-CA", which I changed into "fr-CA" or "fr-ca", all without effect. The spans are there, because the setting into a different language occurs, indeed, only exceptionally. Thus, the spans seem correct to me, so far.

02-25-2016, 02:53 PM	#5
Leonatus Wizard Posts: 1,055 Karma: 11391181 Join Date: Mar 2013 Location: Guben, Brandenburg, Germany Device: Kobo Clara 2E, Tolino Shine 3	Yep, this did it! I hadn't found any restriction on this either.Maybe it's just a FlightCrew speciality. Anyway, I hope this will help me for my own books in the future! Thank you once more!

03-24-2016, 08:44 AM	#10
Leonatus Wizard Posts: 1,055 Karma: 11391181 Join Date: Mar 2013 Location: Guben, Brandenburg, Germany Device: Kobo Clara 2E, Tolino Shine 3	In my case, both declarations were included in the "head" sector of the html; the error message came in spite of the "correct" one beeing as well present. And while doitsu's epubcheck accepted this, it was only Flightcrew that sensitive enough.

Advert

Advert