mat8iou Posted March 11, 2016 Share Posted March 11, 2016 We are having a similar problem what is mentioned here - it has only occurred since the upgrade to 2016 though. On files we exported before the upgrade, everything looks fine. On ones exported since, the fonts are rasterised. We use the export to PDF command, as generally it has given more reliable results in the past. Using Print to PDF works fine with the fonts, but we would prefer it if we could use export. Having investigated a bit further, not all fonts are affected. Based on a quick test, Benton Sans and Arial export fine, but News Gothic and Eurostile do not. Like I said, this was never an issue when we used 2015. It happens even on a newly created file and on every computer in the office. I've attached an example file that illustrates the issue. Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted March 11, 2016 Vectorworks, Inc Employee Share Posted March 11, 2016 What font types are those on your machine? You can find this by looking the font up in FontBook, then right clicking on the font and choosing "Open in Finder" They should be .TTF or .OTF, or something similar as their file type. Quote Link to comment
mat8iou Posted March 11, 2016 Author Share Posted March 11, 2016 Thanks for the reply. Just had a look. From the original example (2 working, 2 not working), both those that worked were a .ttf file. Both those that didn't were a FOnt Suitcase. I'm not particularly familiar with how Font Suitcases work on Macs - my understanding was that they are generally just a package containing a range of different font weights, to make them more manageable? As I mentioned before, we never had a problem with using these same fonts in VW2015. Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted March 11, 2016 Vectorworks, Inc Employee Share Posted March 11, 2016 Yep that just means its a bundle, I think there is a way to determine what type, I'll look into it further. I ask because Tech Support is currently tracking similar issues suddenly, where the font appears rasterized in exports (it isn't actually the same as regular Rasterize, but it appears that way or very close to it) and so far, many of the fonts have been PostScript/Type 1, but a few have been OTF or older TTF. They're trying to find an accurate pattern and get it submitted to engineering. Quote Link to comment
mat8iou Posted March 11, 2016 Author Share Posted March 11, 2016 It seems that this could somehow be the cause of the problem. I took one of the problem fonts (Eurostile) and used the method described here: http://stackoverflow.com/questions/7412462/using-os-9-resource-fork-fonts-in-css-with-font-face/7418915#7418915 to extract the .ttf files from the Font Suitcase. I then had to move the Font Suitcase out of the Fonts Folder before adding the .ttf files as it otherwise assumed they were duplicates. After re-starting Vectorworks, I exported a PDF of one document using that fond and it came out fine. So I seem to have identified the cause of the problem? I don't understand why this never used to be a problem though and it affects a lot of the other fonts on our systems (61 suitcases within the Microsoft folder within the fonts folder - presumably installed by Office). Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted March 11, 2016 Vectorworks, Inc Employee Share Posted March 11, 2016 Its a regression, they DID change the way fonts are handled in 2016 but it should NOT have adversely affected font compatibility. However thank you very much, i'm going to try that with a few test cases we have here and if thats the solution, its relatively painless and possibly something that can be automated on our end. Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted March 11, 2016 Vectorworks, Inc Employee Share Posted March 11, 2016 Congratulations! You just cracked this issue single handedly. This is being submitted to engineering now, very likely it is possible for Vectorworks to be set to look for that particular contained font within the suitcase and use that automatically. However I will be posting the full workaround steps for this problem in the meantime. Quote Link to comment
mat8iou Posted March 11, 2016 Author Share Posted March 11, 2016 (edited) Thanks for the info. I wouldn't have worked it out if you hadn't pointed me in the direction of looking at the actual fonts in the first place. Edited March 11, 2016 by mat8iou Quote Link to comment
Art V Posted March 25, 2016 Share Posted March 25, 2016 Is this an issue with (older) Mac TTF fonts only or can this happen on Windows as well? It's been a long time since I had a Mac but that the time Mac and Windows TTF fonts were different, unlike OpenType TTF fonts. That being said, I've had occasions in the past where rotated text was rasterized in PDF and non-rotated text was not thought it seems it is no longer happening since v2015. Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted March 25, 2016 Vectorworks, Inc Employee Share Posted March 25, 2016 So far I have only seen this on Mac, but font handling on the two works very differently even though the intent is for the final results to appear the same. Historically, font related issues in Vectorworks are platform specific. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.