By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,501 Members | 2,850 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,501 IT Pros & Developers. It's quick & easy.

I was pleased to see a couple of ttf files in my runtime distribution fileset

P: n/a
MLH
Does this mean that I can count on A97 to scour my app for TrueType
fonts used in it and automatically include the ttf files needed for a
runtime distribution fileset? This is NOT what happened with the ADT
and Access 2.0. You had to find them yourself, determine what font
files names were needed and include them in the ADT setup wizard
data file. I would like to know if the automatic inclusion of the font
files is reliably implemented in A97 - what's your own experience say?
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
MLH wrote:
Does this mean that I can count on A97 to scour my app for TrueType
fonts used in it and automatically include the ttf files needed for a
runtime distribution fileset? This is NOT what happened with the ADT
and Access 2.0. You had to find them yourself, determine what font
files names were needed and include them in the ADT setup wizard
data file. I would like to know if the automatic inclusion of the font
files is reliably implemented in A97 - what's your own experience say?


Doubtful. The runtime package likely just includes a few core fonts that are
normally used by Access.

You could very easily use a font that doesn't belong to Microsoft and for which
you have no legal right to distruibute so it would not be prudent for the wizard
to simply "scan" your app and include all the fonts found.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


Nov 13 '05 #2

P: n/a
MLH
You know what they say, "If it sounds too good to be true..."

Doubtful. The runtime package likely just includes a few core fonts that are
normally used by Access.

You could very easily use a font that doesn't belong to Microsoft and for which
you have no legal right to distruibute so it would not be prudent for the wizard
to simply "scan" your app and include all the fonts found.


Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.