Quote:
Originally Posted by DiapDealer
I understand that some books may contain multi-language content, but can someone explain what is gained (or hoped to be gained) by putting a dc:language entry in the OPF for each language that appears in the book, rather than just the single primary language entry?
If dictionary look-ups are what the eventual goal is, I was under the impression that was better achieved by adding spans around different language sections in the (x)html with the proper "lang" attribute defined.
|
I earlier moved arabic from the first language to the last which solved the issue for ade but importing into ibooks the the layout is right to left with arabic being placed last
for me the solution was to delete the language but a more general solution is to use a single language at this level which renders as you intend. Since ade uses the first language and ibooks the last. The simplest solution is to make first and last one and the same
With the general rule being that the styling nearest the text wins I think Apple are most likely correct in their interpretation. On a practical basis Ade's implementation is likely to be most common.
So far the only system that comes close to listening to the css styling rules is google playbooks.