[XeTeX] XeTeXpicfile

2011-11-11 Thread Philip TAYLOR
The documentation states : \XeTeXpicfile ‹filename› [ scaled ‹int› | xscaled ‹int› | yscaled ‹int› | width ‹dimen› | height ‹dimen› | rotated ‹decimal› ] and indeed, an attempt to use XeTeXpicfile with a fractional scale factor such as 0.666, as in XeTeXpifile myimage.png scaled 0.666

Re: [XeTeX] Synching PDF paper size with typesetting size

2011-11-11 Thread BPJ
On 2011-11-07 13:43, William Adams wrote: %converted to BP 'cause using mm made Acrobat 8 report an error Aha, that's what I've been experiencing when trying to create pdfs in PA4 (210 x 280 mm) format. What's the conversion formula? According to wikipedia 1 DTP point == 0.3528 mm. Is that it?

Re: [XeTeX] XeTeXpicfile

2011-11-11 Thread Stephen Moye
On Nov 11, 2011, at 3:55 AM, Philip TAYLOR wrote: > The documentation states : > >> \XeTeXpicfile ‹filename› [ scaled ‹int› | xscaled ‹int› | yscaled ‹int› | >> width ‹dimen› | height ‹dimen› | rotated ‹decimal› ] > > and indeed, an attempt to use XeTeXpicfile with a fractional scale > factor s

Re: [XeTeX] Synching PDF paper size with typesetting size

2011-11-11 Thread Zdenek Wagner
2011/11/11 BPJ : > On 2011-11-07 13:43, William Adams wrote: >> >> %converted to BP 'cause using mm made Acrobat 8 report an error > > Aha, that's what I've been experiencing when trying > to create pdfs in PA4 (210 x 280 mm) format. > > What's the conversion formula? According to > wikipedia 1 DTP

Re: [XeTeX] XeTeXpicfile

2011-11-11 Thread Philip TAYLOR
Stephen Moye wrote: I've never used this myself, but the documentation you quote does say: scaled ‹int› which presumably means that an *integer* is required as an argument to 'scaled'. That would lead me to believe that 'scaled' works like TeX's scaling. Oh : "scaled 666" was /not/ what

[XeTeX]   in XeTeX

2011-11-11 Thread Oleg Parashchenko
Hello, how does XeTeX process the unicode symbol \u00a0 (non-breaking space), * just like any other glyph, or * there is some hidden magic to interpret the symbol as a space with special properties? -- Oleg Parashchenko olpa@ http://uucode.com/ http://uucode.com/blog/ XML, TeX, Python, Mac,

Re: [XeTeX]   in XeTeX

2011-11-11 Thread Le Farfadet Spatial
Hello everybody out there! On 11/11/2011 13:55, Oleg Parashchenko wrote: how does XeTeX process the unicode symbol \u00a0 (non-breaking space), * just like any other glyph, or * there is some hidden magic to interpret the symbol as a space with special properties? I have processed by mistake

Re: [XeTeX]   in XeTeX

2011-11-11 Thread Zdenek Wagner
2011/11/11 Le Farfadet Spatial : > > Hello everybody out there! > > On 11/11/2011 13:55, Oleg Parashchenko wrote: >> >> how does XeTeX process the unicode symbol \u00a0 (non-breaking space), >> >> * just like any other glyph, or >> * there is some hidden magic to interpret the symbol as a space wit

Re: [XeTeX]   in XeTeX

2011-11-11 Thread Le Farfadet Spatial
Hello everybody out there! On 11/11/2011 15:11, Zdenek Wagner wrote: How does XeTeX convert \language to the rules As far as I know, the language is a parameter transmitted to packages that have different rules depending on the language used. It also affects, for instance, the way punctuati

Re: [XeTeX]   in XeTeX

2011-11-11 Thread Zdenek Wagner
2011/11/11 Le Farfadet Spatial : > > Hello everybody out there! > > On 11/11/2011 15:11, Zdenek Wagner wrote: >> >> How does XeTeX convert \language to the rules > > As far as I know, the language is a parameter transmitted to packages that > have different rules depending on the language used. It

Re: [XeTeX] XeTeXpicfile

2011-11-11 Thread Heiko Oberdiek
On Fri, Nov 11, 2011 at 08:55:33AM +, Philip TAYLOR wrote: > The documentation states : > > >\XeTeXpicfile ‹filename› [ scaled ‹int› | xscaled ‹int› | yscaled ‹int› | > >width ‹dimen› | height ‹dimen› | rotated ‹decimal› ] > > and indeed, an attempt to use XeTeXpicfile with a fractional scal

Re: [XeTeX] XeTeXpicfile

2011-11-11 Thread Steve Peter
On Nov 11, 2011, at 7:06 AM, Philip TAYLOR wrote: >> I've never used this myself, but the documentation you quote does say: >> scaled ‹int› >> >> which presumably means that an *integer* is required as an argument to >> 'scaled'. >> That would lead me to believe that 'scaled' works like T