Thank you for the comment. The phrase, "newcomer-friendly" is where I'm at.<br><br>Neale<br><br><div class="gmail_quote">On Thu, Dec 4, 2008 at 8:40 AM, <span dir="ltr"><<a href="mailto:xetex-request@tug.org">xetex-request@tug.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send XeTeX mailing list submissions to<br>
<a href="mailto:xetex@tug.org">xetex@tug.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:xetex-request@tug.org">xetex-request@tug.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:xetex-owner@tug.org">xetex-owner@tug.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of XeTeX digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. vmargin package (Benct Philip Jonsson)<br>
2. Re: vmargin package (Ulrike Fischer)<br>
3. Re: Request for Participation (RFP) (Will Robertson)<br>
4. Res: Request for Participation (RFP) (Flavio Costa)<br>
5. Re: xetex and xfrac? (Stephen Moye)<br>
6. Re: xetex and xfrac? (Axel E. Retif)<br>
7. Re: Could not load both Bold and BoldItalic. (Peter Dyballa)<br>
8. Re: xetex and xfrac? (Stephen Moye)<br>
9. Re: Could not load both Bold and BoldItalic. (Ulrike Fischer)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 04 Dec 2008 13:53:44 +0100<br>
From: Benct Philip Jonsson <<a href="mailto:bpj@melroch.se">bpj@melroch.se</a>><br>
Subject: [XeTeX] vmargin package<br>
To: <a href="mailto:xetex@tug.org">xetex@tug.org</a><br>
Message-ID: <<a href="mailto:4937D2D8.2030305@melroch.se">4937D2D8.2030305@melroch.se</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Does the vmargin package work with XeLaTeX,<br>
i.e. will the pdf pagesize be the one set with<br>
vmargin? The vmargin manual makes a point of<br>
the fact that it works with the pdflatex package,<br>
so I thought that maybe something hairy is<br>
going on here...<br>
<br>
/BP 8^)><br>
--<br>
Benct Philip Jonsson -- melroch atte melroch dotte se<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
"C'est en vain que nos Josu?s litt?raires crient<br>
? la langue de s'arr?ter; les langues ni le soleil<br>
ne s'arr?tent plus. Le jour o? elles se *fixent*,<br>
c'est qu'elles meurent." (Victor Hugo)<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 4 Dec 2008 14:06:48 +0100<br>
From: Ulrike Fischer <<a href="mailto:news2@nililand.de">news2@nililand.de</a>><br>
Subject: Re: [XeTeX] vmargin package<br>
To: <a href="mailto:xetex@tug.org">xetex@tug.org</a><br>
Message-ID: <4qzg6278as5o$.<a href="mailto:dlg@nililand.de">dlg@nililand.de</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Am Thu, 04 Dec 2008 13:53:44 +0100 schrieb Benct Philip Jonsson:<br>
<br>
> Does the vmargin package work with XeLaTeX,<br>
> i.e. will the pdf pagesize be the one set with<br>
> vmargin? The vmargin manual makes a point of<br>
> the fact that it works with the pdflatex package,<br>
> so I thought that maybe something hairy is<br>
> going on here...<br>
<br>
As far as I can see vmargin doesn't set the pdf pagesize. You will have<br>
to do it yourself (also if you use pdflatex)<br>
<br>
\documentclass{article}<br>
\usepackage{vmargin}<br>
\setpapersize{A5}<br>
\pdfpagewidth\paperwidth<br>
\pdfpageheight\paperheight<br>
\begin{document}<br>
abc<br>
\end{document}<br>
<br>
<br>
<br>
--<br>
Ulrike Fischer<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 5 Dec 2008 00:04:53 +1030<br>
From: "Will Robertson" <<a href="mailto:wspr81@gmail.com">wspr81@gmail.com</a>><br>
Subject: Re: [XeTeX] Request for Participation (RFP)<br>
To: "Unicode-based TeX for Mac OS X and other platforms"<br>
<<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID:<br>
<<a href="mailto:27990a880812040534j67a2b81cje0db7db0df51fd60@mail.gmail.com">27990a880812040534j67a2b81cje0db7db0df51fd60@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Thu, Dec 4, 2008 at 3:59 PM, VAFA KHALIGHI<br>
<<a href="mailto:vafa.khalighi@students.mq.edu.au">vafa.khalighi@students.mq.edu.au</a>> wrote:<br>
> the fontspec manual is already super-basic and super-easy to follow by the<br>
> way.<br>
<br>
I think that Neale is looking for more of a step-by-step guide for<br>
basic situations, with complete examples, whereas the fontspec manual<br>
(for now) makes many assumptions about what features a font may<br>
contain and so on.<br>
<br>
But I'm not the best person to comment, since obviously I know how to<br>
use fontspec rather well :)<br>
<br>
Will<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 4 Dec 2008 05:50:38 -0800 (PST)<br>
From: Flavio Costa <<a href="mailto:flaviocosta@yahoo.com.br">flaviocosta@yahoo.com.br</a>><br>
Subject: [XeTeX] Res: Request for Participation (RFP)<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <<a href="mailto:993132.13609.qm@web32602.mail.mud.yahoo.com">993132.13609.qm@web32602.mail.mud.yahoo.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Neale possibly thinks about something closer to what TikZ manual is. TikZ manual is more newcomer-friendly than fontspec's.<br>
<br>
Flavio Costa<br>
<br>
<br>
<br>
<br>
________________________________<br>
De: Will Robertson <<a href="mailto:wspr81@gmail.com">wspr81@gmail.com</a>><br>
Para: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Enviadas: Quinta-feira, 4 de Dezembro de 2008 11:34:53<br>
Assunto: Re: [XeTeX] Request for Participation (RFP)<br>
<br>
On Thu, Dec 4, 2008 at 3:59 PM, VAFA KHALIGHI<br>
<<a href="mailto:vafa.khalighi@students.mq.edu.au">vafa.khalighi@students.mq.edu.au</a>> wrote:<br>
> the fontspec manual is already super-basic and super-easy to follow by the<br>
> way.<br>
<br>
I think that Neale is looking for more of a step-by-step guide for<br>
basic situations, with complete examples, whereas the fontspec manual<br>
(for now) makes many assumptions about what features a font may<br>
contain and so on.<br>
<br>
But I'm not the best person to comment, since obviously I know how to<br>
use fontspec rather well :)<br>
<br>
Will<br>
<br>
<br>
<br>
Veja quais s?o os assuntos do momento no Yahoo! +Buscados<br>
<a href="http://br.maisbuscados.yahoo.com" target="_blank">http://br.maisbuscados.yahoo.com</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://tug.org/pipermail/xetex/attachments/20081204/b4526766/attachment-0001.html" target="_blank">http://tug.org/pipermail/xetex/attachments/20081204/b4526766/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 04 Dec 2008 08:54:59 -0500<br>
From: Stephen Moye <<a href="mailto:stephenmoye@mac.com">stephenmoye@mac.com</a>><br>
Subject: Re: [XeTeX] xetex and xfrac?<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <<a href="mailto:122874226262388910541573380910521009289-Webmail@me.com">122874226262388910541573380910521009289-Webmail@me.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Thursday, December 04, 2008, at 05:50AM, "Axel E. Retif" <<a href="mailto:axel.retif@mac.com">axel.retif@mac.com</a>> wrote:<br>
>On 3 Dec, 2008, at 10:46, Stephen Moye wrote:<br>
><br>
>> I have tried to get xfrac to work using xetex and fontspec, but have<br>
>> had only limited success. If, for example, I set<br>
>><br>
>> \setmainfont{Goudy Std}<br>
>><br>
>> and<br>
>><br>
>> \sfrac{1}{2}<br>
>><br>
>> (notice, not in math mode, but in text mode) there is a 1/2<br>
>> fraction, but the spacing is not optimal. I tried:<br>
>><br>
>> \DeclareInstance{xfrac}{"Goudy Std"}{text}{%<br>
>> slash-right-kern = 1pt,<br>
>> slash-left-kern = 1pt,<br>
>> }<br>
>><br>
>> but this does not seem to do anything.<br>
>><br>
>> I understand that xfrac is an experimental package at present, but<br>
>> just want to make sure that I am doing the right thing -- or not.<br>
><br>
>I guess xfrac doesn't understand fonts that way, but with the tfm<br>
>family names (cmr, for Computer Modern; hlh, for Lucida, etc.); but try<br>
><br>
>\DeclareInstance{xfrac}{default}{text}{%<br>
> slash-right-kern = 1pt,<br>
> slash-left-kern = 1pt,<br>
>}<br>
><br>
>This will affect sfrac in san serif and italics as well, though.<br>
><br>
><br>
>Best,<br>
><br>
>Axel<br>
<br>
Brilliant! Worked like the proverbial charm. Fortunately, I'm using \sfrac only with the roman -- no italics and no sans are involved.<br>
<br>
Many thanks.<br>
<br>
Stephen Moye<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 04 Dec 2008 05:04:25 -0600<br>
From: "Axel E. Retif" <<a href="mailto:axel.retif@mac.com">axel.retif@mac.com</a>><br>
Subject: Re: [XeTeX] xetex and xfrac?<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <<a href="mailto:F12DA8F2-1F28-462A-81C4-63CFACFFD6EC@mac.com">F12DA8F2-1F28-462A-81C4-63CFACFFD6EC@mac.com</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<br>
<br>
On 4 Dec, 2008, at 04:50, Axel E. Retif wrote:<br>
<br>
> On 3 Dec, 2008, at 10:46, Stephen Moye wrote:<br>
><br>
>> I have tried to get xfrac to work using xetex and fontspec, but have<br>
>> had only limited success. If, for example, I set<br>
<br>
[...]<br>
<br>
>> \DeclareInstance{xfrac}{"Goudy Std"}{text}{%<br>
>> slash-right-kern = 1pt,<br>
>> slash-left-kern = 1pt,<br>
>> }<br>
>><br>
>> but this does not seem to do anything. [...]<br>
><br>
> I guess xfrac doesn't understand fonts that way, but with the tfm<br>
> family names (cmr, for Computer Modern; hlh, for Lucida, etc.); but<br>
> try<br>
><br>
> \DeclareInstance{xfrac}{default}{text}{%<br>
> slash-right-kern = 1pt,<br>
> slash-left-kern = 1pt,<br>
> }<br>
><br>
> This will affect sfrac in san serif and italics as well, though.<br>
<br>
There is a way to avoid this ---say you don't want that change in your<br>
san serif font, but only in roman and italics, then<br>
<br>
\DeclareInstance{xfrac}{default}{text}{%<br>
slash-right-kern = 1pt,<br>
slash-left-kern = 1pt,<br>
}<br>
\DeclareInstance{xfrac}{sanserif}{text}{%<br>
slash-right-kern = 0pt,<br>
slash-left-kern = 0pt,<br>
}<br>
<br>
\sfrac{1}{2}, \textit{\sfrac{1}{2}}, \textsf{\sfrac[sanserif]{1}{2}}.<br>
<br>
Best,<br>
<br>
Axel<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Thu, 4 Dec 2008 15:05:34 +0100<br>
From: Peter Dyballa <Peter_Dyballa@Web.DE><br>
Subject: Re: [XeTeX] Could not load both Bold and BoldItalic.<br>
To: <a href="mailto:news2@nililand.de">news2@nililand.de</a>, Unicode-based TeX for Mac OS X and other<br>
platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <38773403-B3F3-4737-959A-5F3A7D4B1458@Web.DE><br>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;<br>
format=flowed<br>
<br>
<br>
Am 04.12.2008 um 10:22 schrieb Ulrike Fischer:<br>
<br>
>>> OK. Then its "the system" that provides the fonts in a form that<br>
>>> they<br>
>>> can be used!<br>
>><br>
>><br>
>> No ? you fooled me! Your example shows the "conventional" side of<br>
>> xdvipdfmx, which comes from dvipdfm (direct convertor from DVI to<br>
>> PDF) and dvipdfmx (which added capabilities to handle complex CJK<br>
>> PostScript fonts) that use TeX fonts, i.e., they work TFM based.<br>
><br>
> I don't understand how the tex->xdv-step which needs the TFM can<br>
> benefit<br>
> from features of xdvipdfmx which is called later.<br>
<br>
It can't, I mean: it would be backwards, in time (maybe quantum<br>
computer will be able to perform this, too; instead of a count<br>
down ...). XeTeX needs information about the glyphs (characters from<br>
a particular font) it is going to use. Its primary font interface is<br>
direct: tables in the font that describe the glyphs in terms of<br>
dimensions, positions, writing direction, ability to build ligatures,<br>
etc. OpenType (OT or OTF, based on PostScript or on TrueType),<br>
TrueType (TT or TTF), Apple Advanced Typography (AAT) fonts provide<br>
this information. It is used by ICU (International Components for<br>
Unicode), AAT, or (SIL) Graphite renderers to create shaped text<br>
(therefore the ability to artificially lengthen/shorten, embold/thin,<br>
or slant). (Pango, a Greek-Japanese construct for "all tongues," is<br>
another effort here.) Primitive fonts like PostScript Type 1 and 3<br>
(?) and 42 do not have any other information than dimensions and an<br>
arbitrary encoding plus optional creation of ligatures (therefore<br>
this information can be retrieved as an Adobe Font Metrics, AFM, file).<br>
<br>
TeX has its way to create a good layout of a page. Font information<br>
is passed to it from the fonts used ? or from TeX Font Metrics (TFM)<br>
files if the font is a bare one. With eTeX TeX can "write" in both<br>
directions. Other extensions are necessary to write up-down. The XDV<br>
output file is rather primitive (as is DVI, too): use character so-<br>
and-so from some particular font scaled to some size and put it at<br>
this position. The output driver uses this information to create some<br>
other, more in use and also more useful format, because it allows to<br>
search for text (instead of glyphs or characters).<br>
<br>
> Anyway: even if I remove the TFM of utopia (so that pdflatex fails)<br>
> xelatex still can<br>
> handle the font.<br>
<br>
*I* have a very simple explanation based on observation: xdvipdfmx is<br>
more polite than Japanese! When it fails, it does no harm. I.e., when<br>
a PDF file existed before it's neither overwritten nor removed by<br>
xdvipdfmx' failure. Check the PDF file's date and compare it to the<br>
moment you ran xdvipdfmx!<br>
<br>
><br>
> Btw: I'm not saying that xetex can handle *every* type1. There are<br>
> certainly some which are so old, buggy, incomplete or special that<br>
> xetex<br>
> will fail.<br>
<br>
<br>
Then these fonts aren't PostScript Type 1.<br>
<br>
--<br>
Mit friedvollen Gr??en<br>
<br>
Pete<br>
<br>
Banken sprengen hei?t Sonne rein lassen.<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Thu, 04 Dec 2008 09:19:55 -0500<br>
From: Stephen Moye <<a href="mailto:stephenmoye@mac.com">stephenmoye@mac.com</a>><br>
Subject: Re: [XeTeX] xetex and xfrac?<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <<a href="mailto:165803300802641344632045643822103276080-Webmail@me.com">165803300802641344632045643822103276080-Webmail@me.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
On Thursday, December 04, 2008, at 06:04AM, "Axel E. Retif" <<a href="mailto:axel.retif@mac.com">axel.retif@mac.com</a>> wrote:<br>
>On 4 Dec, 2008, at 04:50, Axel E. Retif wrote:<br>
><br>
>> On 3 Dec, 2008, at 10:46, Stephen Moye wrote:<br>
>><br>
>>> I have tried to get xfrac to work using xetex and fontspec, but have<br>
>>> had only limited success. If, for example, I set<br>
><br>
>[...]<br>
><br>
>>> \DeclareInstance{xfrac}{"Goudy Std"}{text}{%<br>
>>> slash-right-kern = 1pt,<br>
>>> slash-left-kern = 1pt,<br>
>>> }<br>
>>><br>
>>> but this does not seem to do anything. [...]<br>
>><br>
>> I guess xfrac doesn't understand fonts that way, but with the tfm<br>
>> family names (cmr, for Computer Modern; hlh, for Lucida, etc.); but<br>
>> try<br>
>><br>
>> \DeclareInstance{xfrac}{default}{text}{%<br>
>> slash-right-kern = 1pt,<br>
>> slash-left-kern = 1pt,<br>
>> }<br>
>><br>
>> This will affect sfrac in san serif and italics as well, though.<br>
><br>
>There is a way to avoid this ---say you don't want that change in your<br>
>san serif font, but only in roman and italics, then<br>
><br>
>\DeclareInstance{xfrac}{default}{text}{%<br>
> slash-right-kern = 1pt,<br>
> slash-left-kern = 1pt,<br>
>}<br>
>\DeclareInstance{xfrac}{sanserif}{text}{%<br>
> slash-right-kern = 0pt,<br>
> slash-left-kern = 0pt,<br>
>}<br>
><br>
>\sfrac{1}{2}, \textit{\sfrac{1}{2}}, \textsf{\sfrac[sanserif]{1}{2}}.<br>
><br>
>Best,<br>
><br>
>Axel<br>
<br>
Better and better.<br>
<br>
Thank you again.<br>
<br>
Stephen<br>
<br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Thu, 4 Dec 2008 15:40:12 +0100<br>
From: Ulrike Fischer <<a href="mailto:news2@nililand.de">news2@nililand.de</a>><br>
Subject: Re: [XeTeX] Could not load both Bold and BoldItalic.<br>
To: <a href="mailto:xetex@tug.org">xetex@tug.org</a><br>
Message-ID: <1eu0an4qpstej$.<a href="mailto:dlg@nililand.de">dlg@nililand.de</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Am Thu, 4 Dec 2008 15:05:34 +0100 schrieb Peter Dyballa:<br>
<br>
>> Anyway: even if I remove the TFM of utopia (so that pdflatex fails)<br>
>> xelatex still can<br>
>> handle the font.<br>
><br>
> *I* have a very simple explanation based on observation: xdvipdfmx is<br>
> more polite than Japanese! When it fails, it does no harm. I.e., when<br>
> a PDF file existed before it's neither overwritten nor removed by<br>
> xdvipdfmx' failure. Check the PDF file's date and compare it to the<br>
> moment you ran xdvipdfmx!<br>
<br>
I prefer to check the terminal output:<br>
<br>
This is the message if xdvipdfmx fails for some reason:<br>
<br>
Output file removed.<br>
<br>
Error 1 (driver return code) generating output;<br>
file test-xetex.pdf may not be valid.<br>
<br>
<br>
And this is the message of a working run (with Utopia-Regular):<br>
<br>
Output written on test-xetex.pdf (1 page).<br>
<br>
--<br>
Ulrike Fischer<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
XeTeX mailing list<br>
<a href="mailto:XeTeX@tug.org">XeTeX@tug.org</a><br>
<a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
<br>
<br>
End of XeTeX Digest, Vol 57, Issue 9<br>
************************************<br>
</blockquote></div><br>