Should be legal I would think, but I doubt anyone would really come after you anyway.
One trick used to save space in PDF files is to embed only the font characters actually used in the document, if you can do that much, I don't see why you couldn't include the entire font.
But if we're talking about standard windows fonts, etc.. and you intend to run the app on the target machine/OS you could probably get away with assuming the font is there already and not include it at all.
Hi Zach. That's what I thought too; we're not distributing it, just using it within our apps. But then I found this on MSDN:
As with most types of software, font files are licensed, rather than sold. Licenses that govern the use of fonts vary from vendor to vendor but in general most licenses, including those covering the fonts Microsoft supplies with applications and Windows, do not allow the fonts to be embedded within applications or otherwise redistributed. Therefore, as a developer it is your responsibility to ensure that you have the required license rights for any font you embed within an application or otherwise redistribute.
Due to certain formatting considerations, I would prefer to restrict the fonts used, and also include some unique ones.
So, either we fork out the dollars to license the fonts, or hope that our app remains under the radar?