Are these Typekit fonts?
Those are not packaged.
If not, what fonts are they?
Finally, why aren’t you sending a PDF?
Thanks for responding, much appreciated.
The fonts themselves are definitely ok. I have tested them without the '/' in the title and they package fine.
Example font is "SymbolITC Bk/Bd BT"
To test the font, I removed the "/" form the name, uploaded it as a new font, changed the font in the document and packaged it fine, so it has to be the name that is a problem - although it has never been an issue before.
We usually supply full packaged artwork with a high resolution pdf as standard. Printers can then adjust the artwork at production stage if they need to (colours etc) to get the best result. Also, I need to share files with other designers within our agency.
Ican work around this by removing the "/" but it would be very time consuming, and older jobs we may need to access and update in the future which use the "/" named fonts would not work and would have to be changed every time which is not ideal
I am having precisely the same issue which has only begun in the last few weeks, the offending font appears to be Swis721 Rm/Bd BT.
I can alleviate the problem following exactly the work around above, but for the same reasons this could become a real pain.
That font, if I’m not mistaken, is part of the CorelDRAW collection. Is that the Type 1 or TrueType version?
Which ever one it is, try the other.
It's a Type 1, part of the Bitstream TypeHigh library which I purchased as a whole (quite) a few years ago (I've never been near CorelDRAW). I've been using it constantly for the past ten years and never had a problem packaging it until last week. I have seven catalogues / large cluster leaflets all currently on the go which use the font, as part of a template designed and used for the last few years without any issues. Looking back through updates, these templates are used annually, going to print around the start of March, so it could be an update since then that has upset things.