Subject: Re: cmyk colour support broken? - msg#00260

Previous Message by Date: click to view message preview

Re: Failed make XeTeX in Fedora Core 4

2006/5/19, Sukhi Venkat (TnQ) <skvenkat-sOy8QHi4LcX/PtFMR13I2A@xxxxxxxxxxxxxxxx>: > > BTW: Where do I put all the fonts in (which folder?) It depends on where your fontconfig directory in (you can have a look at your /etc/fonts/fonts.conf), in most of the cases, /usr/share/fonts/ will work. - jjgod.

Next Message by Date: click to view message preview

Re: Failed make XeTeX in Fedora Core 4

On 19 May 2006, at 4:32 pm, Sukhi Venkat (TnQ) wrote: > BTW: Where do I put all the fonts in (which folder?) OpenType (or TrueType) fonts go wherever your system is configured to look for fonts with Fontconfig... you can probably put them in a personal ~/.fonts directory, or a system-wide directory such as /usr/ local/share/fonts or something. Check your system's fonts.conf to see how it is configured, or install fonts through your desktop manager's interface, if you have one. JK

Previous Message by Thread: click to view message preview

Re: cmyk colour support broken?

On 19 May 2006, at 4:18 pm, William Adams wrote: > On May 19, 2006, at 11:03 AM, Jonathan Kew wrote: > >> This is probably because xdv2pdf doesn't really know how to do CMYK >> colo[u]r; it converts it internally to RGB and passes that on >> CoreGraphics when it draws the text. >> >> The original reason for this is that the first form of color >> supported in XeTeX was the font attribute (rather than \specials), >> which was rendered directly through ATSUI styles; and ATSUI only >> supports RGB(A) color specification. This is no longer how things >> work; I don't draw through ATSUI any more, but directly with >> CoreGraphics, having used ATSUI to get the positioned glyphs -- so in >> principle, I think xdv2pdf could be revised to use proper CG color >> spaces, etc. Just hasn't happened yet. Sorry! >> >> If you're only using OpenType (rather than AAT) fonts, and could >> render the document on Linux using xdvipdfmx as the driver, that >> might work better -- I don't know what the color support is like >> there, but it's probably better. > > any hope of being able to compile xdvipdfmx for Mac OS X? Yes, that's one of my goals. It can be compiled right now, if you have appropriate libraries and header files installed (fontconfig and freetype are the main ones that come to mind). But it has at least one serious limitation that means it's not ready to ship as an alternative to xdv2pdf just yet: it won't handle fonts in suitcase or .dfont files. If you're working with .otf or (Windows-style) .ttf files, it might be worth a try. Oh, graphics support is fairly limited at this point, too. But it's supposed to handle .jpg and .png, at least. JK

Next Message by Thread: click to view message preview

compile xdvipdfmx on Mac OS X (was Re: cmyk colour support broken?)

On May 19, 2006, at 11:45 AM, William Adams wrote: > I think I can work within all that --- I'll let you know when I bump > into a stumbling block. That didn't take long: checking for kpse_find_file in -lkpathsea... no configure: error: kpathsea library not found This version of dvipdfmx requires the kpathsea library and its headers. If you know where it is you might try setting the LDFLAGS environment variable with -L pointing to the directory containing libkpathsea.a. I updated GW-TeX in i-Installer and made sure cli activation was checked --- what else should I do here? William -- William Adams senior graphic designer Fry Communications This email message and any files transmitted with it contain information which is confidential and intended only for the addressee(s). If you are not the intended recipient(s), any usage, dissemination, disclosure, or action taken in reliance on it is prohibited. The reliability of this method of communication cannot be guaranteed. Email can be intercepted, corrupted, delayed, incompletely transmitted, virus-laden, or otherwise affected during transmission. Reasonable steps have been taken to reduce the risk of viruses, but we cannot accept liability for damage sustained as a result of this message. If you have received this message in error, please immediately delete it and all copies of it and notify the sender.