I am currently working on a project that will be distributed throughout the
world, and I have been struggling with fonts and regions within Director for
some time now. I have actually got them working fairly well, but I have just
encountered a problem that I can not solve without doing some radical things,
that I'd rather not do, because of the effect it might have on other programs
running on the system. Here is a description of the problem.
[num][li]Create a projector with an embedded font.
[li]Login to a Win2K or WinXP account that has a double-byte character in the
username
[li]Run the application
[li]You will get a message for every font you have embedded with the message:
An Error Occurred:
Not enough memory available for attempted operation
[OK Button]
[li]The application will run, but any text or field sprites that you have that
use those fonts will default to system defaults[/num]
This will also happen in the development environment if you open a .dir
file with embedded fonts while logged in as a user with a name that includes
double-byte characters. The embedded fonts can be any embedded font (single or
double-byte). The problem seems to be that the code that expands the font into
the temp folder (c:\Documents and Settings\<username>\Local Settings\Temp\) is
not using double-byte savvy code for the path operations. All of the other
temporary files (TempFolder.AAA, dlls, Xtras) work properly, but fonts do not.
I have published this in Director MX, MX 2004, and Japanese MX 2004. I have
not tried to publish this with a pristine version of MX (without the updated
TextXtra), which is rumored to use the system temp folder instead. This is one
option, but then restricted users will have font problems instead. This is not
a good trade off. I have other ideas about how to fix this, but I want to know
if there are any known solutions. Here are some questions I have:
[num][li]Is there a way (short of messing with the registry) to set the temp
folder used by Director for expanding fonts (or if necessary all of the temp
files)?
[li]Is there any likelihood this will be fixed in the near future?
[li]Has anyone else had this problem and found a viable solution?
[li]Can the expansion of the fonts be avoided by including them on the CD in a
folder, something like Xtras in a fast start movie?[/num]

Thank you for any help,

Clayton