www.delorie.com/archives/browse.cgi | search |
Perhaps a compromise - store the font name and extents for each string, and if you have to substitute, you can at least clip the new rendering to the old extents so they won't intersect anything else that they didn't intersect before. Plus, we could make a font substitution a hard error in an exporter, unless you give some command line option to OK it. We'd have to come up with good rules for when to update the saved extents to match the "current" ones, though. Perhaps a warning popup if the text is moved or changed and the old extents didn't match? There's no reason we can't use polygons in exporters to render fonts any different than what we see on screen, and we'd need a REALLY good reason to do that ahead of time and save the results anywhere.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |