<font class="Apple-style-span" face="georgia, serif">Thank you, Bruno: very informative, as always.</font><div><font class="Apple-style-span" face="georgia, serif"><br></font></div><div><font class="Apple-style-span" face="georgia, serif">It would be nice if Blue Sky were a bit more open about what their plans and timescales are, and there was some kind of "official roadmap"… Anyone listening? ;-)</font></div>
<div><font class="Apple-style-span" face="georgia, serif"><br></font></div><div><font class="Apple-style-span" face="georgia, serif">Personally, I think that no TeX system —no matter how fast, user-friendly or OS-compliant— can afford *nowadays* to do without [some form of] Unicode and Open Type support, let alone a commercial one.</font></div>
<div><font class="Apple-style-span" face="georgia, serif"><br></font></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><font class="Apple-style-span" face="georgia, serif">Thanks,<br>
<br>Paolo</font></blockquote><div><font class="Apple-style-span" face="georgia, serif"><br></font><div class="gmail_quote"><font class="Apple-style-span" face="georgia, serif">2009/8/19 Bruno Voisin </font><span dir="ltr"><font class="Apple-style-span" face="georgia, serif"><<a href="mailto:bvoisin@me.com">bvoisin@me.com</a>></font></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Le 19 août 09 à 13:21, Paolo Matteucci a écrit :<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I’d like to ask you a somewhat related question. My two main problems with Textures have always been that it doesn’t support (or didn’t use to support —not quite sure where we’ve got to with the latest beta release) hyperref fully and, much more importantly, (2) [although Textures was probably the first TeX program ever to be able to access "system fonts" easily] there isn’t [yet] a way to access [à la XeTeX, say] all AAT/OT font glyphs [easily]…<br>
<br>
What are your thoughts about these two points? Have you got any "inside information" about if and when these issues might be resolved?<br>
</blockquote>
<br></div>
Hi Paolo,<br>
<br>
No I've no inside information about Textures, unfortunately.<br>
<br>
And about your two questions, I'm afraid the answer is also a "I don't know" to both. I checked about hyperref support and it appears it's not supported, even with the [hypertex] option.<br>
<br>
BTW, the Textures drivers htexture.def for hyperref and textures.def for graphics/x have both been written for Classic Textures (version 2.1 and below) and don't really work with OS X Textures. For example, with the graphics/x package each graphics inclusion in the log window will yield a message "Graphic file (Type EPSF)" even though the graphics file is not an EPSF. Here's what I'm getting with a PNG file:<br>
<br>
File: figs-png/singcylamphor.png Graphic file (type EPSF)<br>
<br>
This message is not generated by Textures but by textures.def, I imagine by the following line:<br>
<br>
\ProvidesFile{#3}[Graphic file (type #1)]%<br>
<br>
But in any case the PNG file is correctly included, independent of what the Log says.<br>
<br>
Back to hyperref: At the time I still had a PPC Mac, I looked at the way hyperlinks worked with Classic Textures and realized this way was different from the way we're used to now with PDF output. You didn't just need to click on a hyperlink, you needed to use a modifier key (probably Cmd i.e. the Apple or clover key, but I'm not sure). So it's no surprise it will have to be re-implemented in some way to work the way we're used to now (and which we need: my need with hyperlinks is to produce PDF files that I can send for work to people so they can use them in Acrobat or Preview or any PDF viewer, not to produce hyperlinks which only work in Textures).<br>
<br>
It's probably also not trivial, as Textures for now can only produce PDF files through the Print dialog, by printing to a PDF file. But so doing so creates PDF files with no hyperlinks, only the visual aspect of the output is reserved in the PDF file created by Apple's Quartz framework. There must be some way to circumvent this limitation, as iWork (Pages etc.) export PDF files with hyperlinks while using the Quartz framework.<br>
<br>
As for the fonts, I don't know what's planned. The TeX Metrics window (in the Window menu) gives a rough idea about what Textures knows about fonts. In particular if you click on the "PostScript name" column header you'll see the fonts used in the current preview window come to the top of the column. That's about all I know.<br>
<br>
It seems in any case what we could do with the last versions of Classic Textures -- use any font known to the OS by using a special syntax for calling it (I don't remember this syntax) -- is not yet implemented in OS X Textures. I don't know either if there are plans of Unicode support and OpenType support. I hope so.<br>
<br>
Cheers,<br><font color="#888888">
<br>
Bruno<br>
<br>
</font><br><br>
<br>_______________________________________________<br>
Textures mailing list<br>
<a href="mailto:Textures@email.esm.psu.edu">Textures@email.esm.psu.edu</a><br>
List Page: <a href="http://email.esm.psu.edu/mailman/listinfo/textures" target="_blank">http://email.esm.psu.edu/mailman/listinfo/textures</a><br>
<br></blockquote></div><br></div>