I’m running into an issue with a customization. We are defining custom menu entries, some of which contain special characters like U+2611 (check box with check: ? for those of you with font support in email). Everything works OK in my Windows Vista + Arbortext 5.4 setup, but the special characters don’t appear in the customer’s Windows XP + Arbortext 5.4 setup.
Has anyone run into this before? If so, did you find a workaround for displaying these special characters? Thanks for any wisdom you can share.
I don't have specific experience with this particular area of Arbortext, but it sounds like a font issue to me. Vista and Windows 7 use a different default font for GUI elements (compared to XP). The new font is Segoe UI and I'm pretty sure the old font was Tahoma. It is likely that the XP font Tahoma did not contain a glyph for U+2611.
An alternative (or parallel?) theory might be that font substitution support was improved in Vista+W7 but I haven't read anything about that.
I don't know if there is a way to customise the UI font for Arbortext, but if there was I would be tempted to try that first to see if that helps. I guess as a brute force fallback you could create a new WinXP user profile and set the Windows GUI font for the whole of that user profile, then run Arbortext. You could also use something like FontForge to explore the Windows XP GUI font and discover if it does have U+2611 or not.
(BTW, if you haven't found it yet, there is a Win32 version of FontForge available from here:
Thanks, Gareth. I was thinking along similar lines. But I'm really really really hoping the solution doesn't require modifying the end users' Windows Appearance settings to replace the default UI font universally. I think that would pretty much be a non-starter.
FWIW, my Vista system--which displays things correctly--shows Tahoma as the font for Windows menus in the Windows Appearance control panel.