That is an unfortunate, though expected, response. In this day in age with global support a standard in so many facets of business many businesses have standardized documentation by simply using a unicode font standard across many communications. In this case PC's / Mac's will work every time because fonts can be added to them as needed.
However, to read the same font on an iPad or other mobile device means that either the font needs to be embedded or available on the device. iOS doesn't have a way to add fonts unless you hack the OS, - not recommended -, and this is the same way with most Android devices, root access is needed. This means that documentation created using unicode font sets cannot be read on mobile devices.
QuickOffice can read these documents and is fast becoming the mobile office suite standard. From an end user perspective it simply looks like Adobe Reader mobile addition has a bug. All PCs can read this, the only device that looks to have a problem from an end user perspective are mobile devices using Adobe Reader.
Technically, the reality of the situation is that some apps on iOS and Android embed certain unicode fonts in their app directly, but all the end user sees is an aparent bug in Reader mobile. It would seem simple to resolve this by allowing users to add a font to the app somehow. For certain platforms there are language packs that can be downloaded, it would seem that something like this would help on the mobile platform.
- Rob
