For problems like these, the first question is: How do you do it in the browser at all (without Royale)?
I think the answer is @font-face. If that's true, the way we handle this right now is to have you use a custom html template. The ASDoc example is using one. HTH, -Alex On 3/6/18, 8:30 PM, "doug777" <[email protected]> wrote: >OK I'll take a look as suggested. > >Re EmbedFont : Actually it's not that important. We use it to get special >characters e.g. > >[Embed(systemFont="Arial", fontName="currencyFont", >mimeType="application/x-font", fontFamily="Arial Regular", >unicodeRange="U+20A1-20B9", embedAsCFF="false")] > >And some similar things from foreign language fonts. > >All the characters can be replaced with a standard letter equivalent. Not >quite as nice, but no big deal. > >Doug > > > >-- >Sent from: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy >ale-users.20374.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cbed36 >cf0ce554a46467f08d583e41e22%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6 >36559938135665620&sdata=G7mOf1z0IFJYo7l82yLHagUhMbL7H7Yxe7U%2FtZFIaCo%3D&r >eserved=0
