Thomas Hoevel wrote:
mabian wrote:
I hope the above points can be taken care soon because they make the current version quite unusable.
The "#20" is there since December 2015 (and not just since RC2) and you are the first to complain about it. If it was "quite unusable" then we should have heard many complaints so far.
Probably only a few people use fonts which name, as processed by PDFSharp, has spaces in it.
Or people don't get annoyed by having to deal with a "font remap" window each time the pdf is opened in an application like Illustrator.
Or they don't use fonts of the type that triggers the troublesome case.
In the process we are developing, hundreds of PDF files are produced automatically and then worked in Illustrator, this loading delay can be significant.
So, maybe not unusable but for sure a bit annoying - at least in the context I described.
Thomas Hoevel wrote:
mabian wrote:
If I understand well the specs, the /FontName and /BaseFont directives expect the postscript name of the font.
What are the specs? How should spaces be treated?
I took a look at the PDF 1.7 specs (see attachment) and there's no explicit mention of forbidden spaces.
But I never saw a name with spaces in all PDFs I inspected, other than the ones produced with PDFSharp.
The specs are quite clear in describing how to get the correct name to put in the BaseFont and FontName statements, though they don't explicitly mention escaping rules.
I'm surprised like you that nobody else reported this issue.
For the moment being, the quickest solution for us was reverting to an earlier version, of course with the risk of getting some bugs and losing enhancements that were introduced in later versions..
Thanks,
Mario