View Single Post
Old 05-29-2015, 06:34 PM   #81
Doitsu
Grand Sorcerer
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 5,746
Karma: 24032915
Join Date: Dec 2010
Device: Kindle PW2
Quote:
Originally Posted by KevinH View Post
I will think about how best to allow different languages for the nav.xhtml that is generated from the toc.ncx.
I did some tests and of the few available epub3 apps only Azardi (Windows, Linux, OSX) actually used the TOC heading title.
I.e., epub3 users will most likely only see localized TOC strings if the app manufacturer decides to release localized versions.

Nevertheless, I'd recommend that the plugin check the language metadata of the epub and automatically select a localized TOC string based on the first two letters of the ISO language code.

For a traditional FIGS localization the plugin could query the following tuple list:

Code:
toc = [('en', 'Table of Contents'), ('fr', 'Table des matičres'), ('it',
       'Tavola dei Contenuti'), ('de', 'Inhaltsverzeichnis'), ('es',
       'Índice de contenido')]
(The translations were pulled from the Sigil UI.)
Doitsu is offline   Reply With Quote