Bug #149 - PDF generated directly from PgS drops characters outside of BMP
|Product:||PageStream 126.96.36.199 (All Platforms)||Reported By:||Tim Doty|
|Severity:||Normal||Assigned To:||Deron Kazmaier|
|Priority:||Average|| ||sign in to watch (1 is watching)|
|Status:||Fixed in 188.8.131.52||Reported:||2007-04-05 14:47:00|
|Category:||File Operations||Updated:||2007-04-05 14:47:00|
|Summary:||PDF generated directly from PgS drops characters outside of BMP|
|Keywords:||Save as PDF,font,encoding|
|Attached Files:||No files attached.|
| ||Sign In to add a file.|
Although PgS displays and prints via postscript characters outside of the Unicode BMP (e.g., Sumero-Akkadian) it does not include them when generating a PDF. Interestingly the problem with Alphabetum noted with printing directly to postscript is not present when generating a PDF.
|Deron Kazmaier wrote...||2009-03-01 22:20:36|
A number of font issues have been address to PDF in the last year. As of 184.108.40.206, all glyphs in a TrueType font can be used in a single document, and versions prior allowed up to 256 from any of the glyphs. One note, Apple Display does not appear to support 2byte CID mapping so using >255 glyphs in a font is not going to generate a PDF that is compatible with older/less robust browsers.
[Status updated to 'Fixed in 220.127.116.11' on Sun, 01 Mar 2009 22:20:36 -0500]
|Add a Comment|
|Sign in to add a comment.|
Bug #149 - PDF generated directly from PgS drops characters outside of BMP by Tim Doty Save as PDF,font,encoding
created:2007-04-05 14:47:00 last updated:2007-04-05 14:47:00
Copyright © 1985-2021 GrasshopperLLC. All Rights Reserved.