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