Quote:
Originally Posted by taos
Almost.
In the "Name" column of the KoboReader.sqlite database, all addtional languages must now be preceeded by an "Extra:_" (e.g. "e1" -> "Extra:_e1"). In addition, the entries for "ExtraLocales" in Kobo eReader.conf must now exactly match the "Name" of the dictionary languages (and no longer the corresponding "Suffix") in the KoboReader.sqlite database without the "Extra:_" prefix. While the e1, e2, etc dictionaries ("Name" of language - "Extra:_" = "Suffix" of language) would still work after adding the "Extra:_" prefix in the databse, you would have to either change, for example, the "Euskera" in the "Name" column of the database to "Extra:_eu" or replace the "eu" in the "ExtraLocales" line in Kobo eReader.conf by "Euskera" (in addition to adding the "Extra:_" prefix in the database to go from "Euskera" to "Extra:_Euskera").
If you want to use the full name, maybe because it looks nicer in the language and dictionary settings or when you choose your dictionary from the look-up window, there's one limitation I came across: if you don't use the latin script for the language name it can be difficult (due to different encodings in the database and .conf file?) to find an exact match: I can't get to match "Extra:_Русский" from the database to "\x420\x443\x441\x441\x43a\x438\x439" in the .conf file (both rendered as "Русский" in the GUI).
|
It does not work (for me) if you use any name different of e1, e2, ... in the database and/or the file kobo ereader.conf. I have tried as you say
Extra:_euskera as name in database and
euskera in the config file without success. I have tried other names, always following the rule you mentioned: database name:
Extra:_XXXX, name in config file:
XXXX and
. Only
Extra:_e1 in database and
e1 in config file works.