<div> I solved my compiler problems and tried out your fix. It's better, but it still has some problems:</div> <div> </div> <div>- Illustrator no longer complains about certain fonts. If a font weight or slant is used, however, there are still problems. It tacks the font weight to the end of the font name (eg "GaramondBold"). Illustrator doesn't realize that this is Garamond with the Bold style. Fonts like "Times New Roman" get scrunched together as "TimesNewRoman", also giving errors.</div> <div> </div> <div>- TrueType fonts still have the wrong glyphs. It looks fine as a PDF render, but letters turn into boxes once it is opened in Illustrator. Curiously, if I use Adobe Acrobat to change the font in the PDF, save, then open in Illustrator, all the glyphs are correct.</div> <div> </div> <div>OpenType fonts now have the correct glyphs. The only problem is that the spaces get removed in the font name. If I set the font back manually, it all works fine.</div> <div><br><br> </div> <div class="gmail_quote">On Wed, Nov 26, 2008 at 2:09 AM, Adrian Johnson <span dir="ltr"><<a href="mailto:ajohnson@redneon.com" target="_blank">ajohnson@redneon.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div>AngryZealot wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I hope you will forgive my ignorance, but I am having difficulty compiling your patches. I checked out the repository with Git but it does not seem to contain the changes the web viewer shows. I dropped in the files from the web browser into the 1.8.4 source, but this broke the build. Do you have a version that is compatibile with the 1.8.4 release?<br> </blockquote><br></div>You most likely checked out out the master repository instead of my repository. From the link I provided if you navigate up to the cgit main page of my repo there is a git clone url at the bottom of the page. My patches are in the "tag" branch so the commands to check out this branch are:<br> <br> git clone git://<a href="http://anongit.freedesktop.org/~ajohnson/cairo" target="_blank">anongit.freedesktop.org/~ajohnson/cairo</a><br> cd cairo<br> git checkout tag<br><br><br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div><br>On Tue, Nov 25, 2008 at 6:56 AM, Adrian Johnson <<a href="mailto:ajohnson@redneon.com" target="_blank">ajohnson@redneon.com</a> <mailto:<a href="mailto:ajohnson@redneon.com" target="_blank">ajohnson@redneon.com</a>>> wrote:<br> <br>   James Cloos wrote:<br>    >>>>>> "AZ" == AngryZealot  <<a href="mailto:angryzealot@gmail.com" target="_blank">angryzealot@gmail.com</a><br></div> <div> <div></div> <div>   <mailto:<a href="mailto:angryzealot@gmail.com" target="_blank">angryzealot@gmail.com</a>>> writes:<br>    ><br>    > AZ> My project requires PS or PDF output that can be edited in Adobe<br>    > AZ> Illustrator. ...<br>     ><br>    > AZ> A quick look at the ps backend makes me think the issue is<br>   with font<br>    > AZ> subsetting. The fonts are saved with the name "f-%d-%d" ...<br>    > AZ> Illustrator naturally can't find a system font f-0-0, so it<br>    converts<br>    > AZ> everything to outlines. If I manually edit the postscript file by<br>    > AZ> replacing f-0-0 with the appropriate font name, everything works<br>    > AZ> beautifully, and Illustrator handles the text just fine.<br>     ><br>    > Most apps create subset font names by prepending six majuscule ASCII<br>    > letters and a plus sign to the original font name, following Adobe's<br>    > recomendation in the PDF reference.  I'm sure Illustrator expects<br>    that<br>    > and would Do The Right Thing were cairo to also use that style.<br>    ><br>    > The norm is either a random string or some relevant digest<br>   (perhaps of<br>    > the font's version and the list of glyphs included in the subset).<br>     ><br>    > There are workflows where avoiding subsetting is required, so a<br>   flag for<br>    > that is useful.  But it would also be useful to use the normal<br>   method of<br>    > naming font subsets.<br>     ><br>    > -JimC<br><br>   I've have written a couple of patches for the PDF backend that prepends<br>   the font tag and sets the /FontFamily key to the unmodified font name.<br>   If this fixes the problem I can make the Type 1 and OpenType/CFF<br>    subsetters also provide the original font name.<br><br>   The patches are at:<br><br>     <a href="http://cgit.freedesktop.org/~ajohnson/cairo/log/?h=tag" target="_blank">http://cgit.freedesktop.org/~ajohnson/cairo/log/?h=tag</a><br> <br>   _______________________________________________<br>   cairo mailing list<br></div></div>   <a href="mailto:cairo@cairographics.org" target="_blank">cairo@cairographics.org</a> <mailto:<a href="mailto:cairo@cairographics.org" target="_blank">cairo@cairographics.org</a>> <div><br>   <a href="http://lists.cairographics.org/mailman/listinfo/cairo" target="_blank">http://lists.cairographics.org/mailman/listinfo/cairo</a><br><br><br></div></blockquote><br></blockquote></div><br>