MobileRead Forums - View Single Post - Dictionary lookup in iBooks 1.1: "Dictionary not available for this language"

buecherhans · 07-02-2010, 12:55 PM

is there a <meta> code that I can add to the header of the ebooks that I create?

I tried: <meta http-equiv="content-language" content="en" />
and it seams to work, while a code like
<meta name="DCTERMS.language" content="en" scheme="DCTERMS.RFC4646"/>
that was produced by OpenOffice conversion does not work to get the iPad dictionary to work.

My knowledge of (x)html metacodes is very limited. I want to be save for the future if I add some extra lines that I don't understand. I spend quite some time to produce a clean html code for some books and it paid off. Other lousy conversion code that worked on the Sony causes problems on the iPad.

So, I would appreciate if someone could give us some lines of html that would Calibre cause to use the right language setting. Reconverting is a pain but faster than other other procedures published in this thread. And hopefully also save for future devices.

07-02-2010, 12:55 PM	#48
buecherhans Enthusiast Posts: 28 Karma: 20 Join Date: Feb 2010 Location: Karlsruhe, Germany Device: iPad, iPhone	is there a <meta> code that I can add to the header of the ebooks that I create? I tried: <meta http-equiv="content-language" content="en" /> and it seams to work, while a code like <meta name="DCTERMS.language" content="en" scheme="DCTERMS.RFC4646"/> that was produced by OpenOffice conversion does not work to get the iPad dictionary to work. My knowledge of (x)html metacodes is very limited. I want to be save for the future if I add some extra lines that I don't understand. I spend quite some time to produce a clean html code for some books and it paid off. Other lousy conversion code that worked on the Sony causes problems on the iPad. So, I would appreciate if someone could give us some lines of html that would Calibre cause to use the right language setting. Reconverting is a pain but faster than other other procedures published in this thread. And hopefully also save for future devices.