[RbnJrg]

Originally Posted by Doitsu

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:

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.)

Hi Doitsu;

In spanish, practically is not used "Indice de contenido"; many times is used "Indice" and many times is used "Contenido". In my case, I'd prefer to have the possibility of using sometimes "Indice" and sometimes "Contenido". Also, it would be nice to have the option in the plugin (as you explained well by PM) that the users can see (or can't) the nav.xhtml file by writing in content.opf:

<itemref idref="navid" linear="no"/>

or

<itemref idref="navid" linear="yes"/>

Maybe with some settings in an .ini file -or a check box in the plugin gui- is possible to handle this kind of option.

Many thanks for your help.
Rubén