Originally Posted by paulpeer
It surely is an ADE issue. ADE only displays a small subset of Unicode characters by default.
I could also rephrase my question: is there somewhere a list of devices that do not use ADE's engine?
If they support Adobe DRM, then they are using the ADE SDK.
FBReader does not provide full ePub support, but it is often "good enough" and it does allow the use of any font installed on the device and that font is used for everything (i.e. for TOCs). It also supports right to left languages (I think, but I have never tested this). Devices with FBReader out of the box include the PocketBooks, the Onyx Boox 60/Bookeen Neo and the Azbooka N516. The Azbooka is for DRM-free ebooks only. The Onyx and PocketBooks use ADE for ePubs, but the PocketBooks have the option of switching to FBReader for DRM-free ePubs.
OpenInkPot is the native firmware on the Azbooka, and can be added by the owner to a Hanvon N516 and a Hanlin V3. It is also possible to add FBReader to the V3's standard firmware. It can be added as 3rd party software to all the iLiad devices.
Finally, it is entirely possible for any Reader vendor to replace Adobe's default font in mobile Adobe Digital Editions. Jinke has done this to support Asian languages on the Hanlins, and Bookeen allows the user to select the default font (I don't know how good the language coverage is in their built-in fonts though). I assume that any Reader vendor could also fix the "TOC in another font" bug too, although this is more appropriately an Adobe issue.