Re: [XeTeX] ** ERROR ** sfnt: Freetype failure...
Am 28.07.2010 um 04:41 schrieb tala...@fastmail.fm: ** ERROR ** sfnt: Freetype failure... This proprietary Classic Mac font format is not supported. By good reason: it neither exhibits features nor does it have tables useful for typesetting. -- Greetings Pete The human brain operates at only 10% of its capacity. The rest is overhead for the operating system. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] ** ERROR ** sfnt: Freetype failure...
Strange. The font is a contemporary font, produced as I said by StormType Foundry. It is an .odt font. I have successfully typeset an entire book using this font with XeLaTeX earlier this year. Just to check that my system hasn't changed somehow, I opened up the .tex file of that book again and recompiled, and it typeset fine. The document I am currently trying to typeset, and getting errors with, has a master document and calls upon five further documents by use of the \include command. I've just commented out all five further documents, and uncommented them one by one. The error seems to occur with two of the documents. However, I can't figure out what is any different about these two (in regards to the font choice). Thank you for your help Pete. Does anyone else have an idea of why the discrepancy? Kind regards, Talal On 28 Jul 2010, at 09:18, Peter Dyballa wrote: > > Am 28.07.2010 um 04:41 schrieb tala...@fastmail.fm: > >> ** ERROR ** sfnt: Freetype failure... > > > This proprietary Classic Mac font format is not supported. By good reason: it > neither exhibits features nor does it have tables useful for typesetting. > > -- > Greetings > > Pete > > The human brain operates at only 10% of its capacity. The rest is overhead > for the operating system. > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Pipes in XeTeX
On 2010-07-27 00:07:02 +0930, Florian Gilcher
said:
I really like the following feature of pdftex and others for
development purposes:
\input{|"darcs changes -s"} % print a detailed log of changes
and include that into my document as a "running log" for other reviewers.
Sure, it requires --shell-escape and --enable-write18, but thats just
fine in my environment.
Actually I think this is a MiKTeX-only feature of pdfTeX (or it was
last time I checked). Is there a significant problem to doing this?:
\immediate\write18{darcs changes -s > tmp.txt}
\input{tmp.txt}
Wrap it up in a macro and it's no less convenient than using the pipe, right?
Will
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] ** ERROR ** sfnt: Freetype failure...
I have just run the two problematic files through a piece of Mac software called "textsoap", which "cleans up" the text. Apparently, there were some hidden, offending glyphs or characters that were causing the problem. The file now compiles fine using Baskerville 10 Pro. Many thanks for your time. Talal On 28 Jul 2010, at 11:38, tala...@fastmail.fm wrote: > Strange. The font is a contemporary font, produced as I said by StormType > Foundry. It is an .odt font. I have successfully typeset an entire book using > this font with XeLaTeX earlier this year. Just to check that my system hasn't > changed somehow, I opened up the .tex file of that book again and recompiled, > and it typeset fine. > > The document I am currently trying to typeset, and getting errors with, has a > master document and calls upon five further documents by use of the \include > command. I've just commented out all five further documents, and uncommented > them one by one. The error seems to occur with two of the documents. However, > I can't figure out what is any different about these two (in regards to the > font choice). > > Thank you for your help Pete. Does anyone else have an idea of why the > discrepancy? > > Kind regards, > Talal > > On 28 Jul 2010, at 09:18, Peter Dyballa wrote: > >> >> Am 28.07.2010 um 04:41 schrieb tala...@fastmail.fm: >> >>> ** ERROR ** sfnt: Freetype failure... >> >> >> This proprietary Classic Mac font format is not supported. By good reason: >> it neither exhibits features nor does it have tables useful for typesetting. >> >> -- >> Greetings >> >> Pete >> >> The human brain operates at only 10% of its capacity. The rest is overhead >> for the operating system. >> >> >> >> -- >> Subscriptions, Archive, and List information, etc.: >> http://tug.org/mailman/listinfo/xetex > > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Fake old-style figures & small-caps with XeTeX?
27/07/10 @ 20:47 (+0100), thus spake cfr...@imapmail.org:
> On Tue 27th Jul, 2010 at 09:48, Khaled Hosny seems to have written:
>
> >On Tue, Jul 27, 2010 at 02:36:45AM +0200, Ernest Adrogué wrote:
> >>23/07/10 @ 17:12 (+0200), thus spake enrico.grego...@univr.it:
> Hi!
>
> Is it possible to generate fake old-style figures & small
> capitals for fonts missing these glyphs with XeTeX.
> I used to use the mathpoz package that does exactly that,
> but something tells me it's not compatible with XeTeX.
> >>>
> >>>
> >>>I guess it's the "mathpazo" package, for Palatino. You can
> >>>substitute the text font with the TeX Gyre version:
> >>>
> >>>
> >>>\usepackage{mathpazo}
> >>>\setmainfont[Numbers=OldStyle]{TeX Gyre Pagella}
> >>>
> >>>
> >>>With declarations in this order, XeLaTeX should be happy: and indeed it is,
> >>>I've tried compiling the documentation of amsmath and all goes well.
> >>
> >>I'll have to study this in more detail.
> >>I thought that "mathpazo" generated the small-caps and old-style
> >>figures by itself, but it seems that it doesn't.
> >
> >Though there are some DTP and office applications that fake small caps,
> >I've never seen one that fakes oldstyle figure, I don't think it is even
> >possible.
> >
> >> It simply selects
> >>another font wich is URW Palladio with real small-caps and old-style
> >>figures added. I don't know what's the point in having a version of
> >>URW Palladio without small-caps and another one with, all in the
> >>same LaTeX installation.
> >
> >Traditional TeX engines can only use small caps if they are in a separate
> >font.
>
> Just to clarify, this, you need separate TFM files, but it is perfectly
> OK for the small caps to be in the same font in the sense of being in
> the same pfb (or ttf for pdflatex which is not quite traditional, of
> course). This amounts to having them in separate fonts as far as TeX is
> concerned but the actual glyphs can all be in the same type 1 font.
Right now, I have two fonts with old-style numbers.
One, Linux Libertine, a true-type font.
Two, PFL Neu, a type 1 font based on URW Palladio.
These both have old-style figures in the same file, and I have seen
with Font Forge that the glyphs are labeled the same: zero.oldstyle,
one.oldstyle... etc.
However, I cannot use the old-style figures from the type1 font.
It prints a warning saying that the OpenType feature 'Numbers=OldStyle'
is not available.
Why can't XeTeX find the o.s. numbers? Is it a limitation of type 1
fonts?
If I put the old-style glyphs in a different file, and load the font
with the SmallCapsFont= option, then it still prints the warning
about old-style numbers not available, but you can actually get o.s.
figures selecting small-caps, e.g. \textsc{12345}. Whereas \textup{123}
uses normal figures. It's not ideal, but it works. The problem is that
it's inconsistent, because the true-type font is insensitive to
\textsc \textup as long as o.s. figures are concerned, it only obeys
the OpenType feature "Numbers" option.
Any comment appreciated :)
Cheers.
Ernest
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Pipes in XeTeX
On Jul 28, 2010, at 1:05 PM, Will Robertson wrote:
> On 2010-07-27 00:07:02 +0930, Florian Gilcher said:
>
>> I really like the following feature of pdftex and others for development
>> purposes:
>> \input{|"darcs changes -s"} % print a detailed log of changes
>> and include that into my document as a "running log" for other reviewers.
>> Sure, it requires --shell-escape and --enable-write18, but thats just fine
>> in my environment.
>
> Actually I think this is a MiKTeX-only feature of pdfTeX (or it was last time
> I checked). Is there a significant problem to doing this?:
>
> \immediate\write18{darcs changes -s > tmp.txt}
> \input{tmp.txt}
>
> Wrap it up in a macro and it's no less convenient than using the pipe, right?
>
> Will
Actually, pdftex in both texlive 2009 and 2010 supports it.
The difference between MiKTeX and texlive is that MiKTeX has a special CLI flag
for it (--enable-pipes) while pdftex on texlive checks for (--shell-escape).
A did a little digging yesterday night and it seems like about the only reason
XeTeX does not support this is because of a preprocessor macro checking for
pdftex in texmfmp.c and texmfmp.h (all involving open_in_or_pipe and
open_out_or_pipe):
http://scripts.sil.org/svn-public/xetex/TRUNK/texk/web2c/lib/texmfmp.c
http://scripts.sil.org/svn-public/xetex/TRUNK/texk/web2c/texmfmp.h
Now, I would try my theory if i could just get XeTeX (or, more specifically,
the bundled ICU) to build from sources on Snow Leopard...
Well: the problem with \write18: it is not quite the same (for example, i
cannot write to a pipe [1]), it clutters the file system and I cannot read from
any arbitrary source. Sure, thats a convenience problem, but considering that
the functionality is there and "the other pdf generating tex" supports it, it
would be nice if xetex had it too.
Regards,
Florian
[1] not that I know any case where that would be needed...
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Fake old-style figures & small-caps with XeTeX?
On Wed 28th Jul, 2010 at 03:00, Ernest Adrogué seems to have written:
27/07/10 @ 20:47 (+0100), thus spake cfr...@imapmail.org:
On Tue 27th Jul, 2010 at 09:48, Khaled Hosny seems to have written:
On Tue, Jul 27, 2010 at 02:36:45AM +0200, Ernest Adrogué wrote:
23/07/10 @ 17:12 (+0200), thus spake enrico.grego...@univr.it:
Hi!
Is it possible to generate fake old-style figures & small
capitals for fonts missing these glyphs with XeTeX.
I used to use the mathpoz package that does exactly that,
but something tells me it's not compatible with XeTeX.
I guess it's the "mathpazo" package, for Palatino. You can
substitute the text font with the TeX Gyre version:
\usepackage{mathpazo}
\setmainfont[Numbers=OldStyle]{TeX Gyre Pagella}
With declarations in this order, XeLaTeX should be happy: and indeed it is,
I've tried compiling the documentation of amsmath and all goes well.
I'll have to study this in more detail.
I thought that "mathpazo" generated the small-caps and old-style
figures by itself, but it seems that it doesn't.
Though there are some DTP and office applications that fake small caps,
I've never seen one that fakes oldstyle figure, I don't think it is even
possible.
It simply selects
another font wich is URW Palladio with real small-caps and old-style
figures added. I don't know what's the point in having a version of
URW Palladio without small-caps and another one with, all in the
same LaTeX installation.
Traditional TeX engines can only use small caps if they are in a separate
font.
Just to clarify, this, you need separate TFM files, but it is perfectly
OK for the small caps to be in the same font in the sense of being in
the same pfb (or ttf for pdflatex which is not quite traditional, of
course). This amounts to having them in separate fonts as far as TeX is
concerned but the actual glyphs can all be in the same type 1 font.
My comment here concerned the way traditional TeX engines work - not
XeTeX. (Though I believe XeTeX sometimes falls back to a similar system
but only as a last resort. Not sure, though.)
Right now, I have two fonts with old-style numbers.
One, Linux Libertine, a true-type font.
Two, PFL Neu, a type 1 font based on URW Palladio.
These both have old-style figures in the same file, and I have seen
with Font Forge that the glyphs are labeled the same: zero.oldstyle,
one.oldstyle... etc.
However, I cannot use the old-style figures from the type1 font.
It prints a warning saying that the OpenType feature 'Numbers=OldStyle'
is not available.
Why can't XeTeX find the o.s. numbers? Is it a limitation of type 1
fonts?
Yes. Type 1 fonts do not have OpenType features. They are a feature of
OpenType fonts.
If I put the old-style glyphs in a different file, and load the font
with the SmallCapsFont= option, then it still prints the warning
about old-style numbers not available, but you can actually get o.s.
figures selecting small-caps, e.g. \textsc{12345}. Whereas \textup{123}
uses normal figures. It's not ideal, but it works. The problem is that
it's inconsistent, because the true-type font is insensitive to
\textsc \textup as long as o.s. figures are concerned, it only obeys
the OpenType feature "Numbers" option.
Hopefully somebody else will answer this!
- cfr
Any comment appreciated :)
Cheers.
Ernest
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
[XeTeX] fontspec: loading different shapes/scales of one font as different font instances?
As the subject line says I wonder if it's possible with fontspec to load different shapes of the same font as different font instances? The thing is I'm going to write a script which generates XeLaTeX source and where the user is to be able to choose their own fonts/shapes/sizes for elements like text and headings, and I hope to be able to define a font instance for each of these elements but not to have to check if they want, say, italic or smallcaps headings scaled n and stick in formatting commands if they do! (Some of you may balk at italic/whatever headings, but in my case the linguistics anti-prescriptivism pill went down rather successfully, and I'd hate to be prescriptivist when I don't have to. Besides it is sometimes the case that bold is used with some technical signal value beside italics and I've found it convenient to set headings in smallcaps in such cases.[^1]) [^1]: This in turn requires an amount of \addcontentsline gymnastics. I'd appreciate pointers on methods/packages to globally styling headings/toc entries independently of each other. I'm probably showing my ignorance here, or my needs/wishes are really fringe! texdoc'ing "contents" or "toc" turns up nothing useful, and section.sty seemeth to be an olde and arcane dogge (at least to me!) /BP 8^)> -- ~~ "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) -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] ** ERROR ** sfnt: Freetype failure...
> I have just run the two problematic files through a piece of Mac software > called "textsoap", which "cleans up" the text. Apparently, there were some > hidden, offending glyphs or characters that were causing the problem. The > file now compiles fine using Baskerville 10 Pro. Would you be so kind as to share the original document with the offending characters (if you're allowed to do that, of course)? It's always interesting to know how to diagnose this kind of problem precisely, in case it happens to someone else in the future. Arthur -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] xunicode and TIPA
Hi
The xunicode package provides a textipa command which recognizes (most
of?) the commands from the tipa package. This is very useful, since
it allows one to convert legacy documents containing IPA to xelatex
with minimal trouble. However, the tipa package also provided an IPA
environment. This is not supplied by xunicode. Is there a way to
emulate that too? Here's a minimal document:
I know the definition for the IPA environment isn't correct; what I
want is characters inside that environment to be interpreted in the
same way that they are within the \textipa command provided by xunicode.
% !TEX TS-program = XeLaTeX
\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\ipafont}{Doulos SIL}
\def\useTIPAfont{\ipafont}
\newenvironment{IPA}{\ipafont}{} % I know this isn't sufficient
\begin{document}
\textipa{RPAQIOE} % This will give you correct phonetic characters
\begin{IPA}RPAQIOE % This obviously doesn't
\end{IPA}
\end{document}
Alan
--
Alan Munn
am...@gmx.com
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
Maybe you could hack something better along these lines, Alan :
% !TEX TS-program = XeLaTeX
\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\ipafont}{Doulos SIL}
\def\useTIPAfont{\ipafont}
\newenvironment{IPA}{\ipafont}{} % I know this isn't sufficient
\begin{document}
\textipa{RPAQIOE} % This will give you correct phonetic characters
\begin{textipa}
\bgroup
RPAQIOE
\egroup % This might !
\end{textipa}
\end{document}
Philip T aylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
> I know the definition for the IPA environment isn't correct; what I want > is characters inside that environment to be interpreted in the same way > that they are within the \textipa command provided by xunicode. What you want is a mapping from tipa's transliteration system to the corresponding Unicode values for IPA characters; you can do that with TECkit: it generates a file that XeTeX knows how to use. Arthur -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
On Jul 28, 2010, at 11:45 AM, Philip Taylor (Webmaster, Ret'd) wrote:
Maybe you could hack something better along these lines, Alan :
% !TEX TS-program = XeLaTeX
\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\ipafont}{Doulos SIL}
\def\useTIPAfont{\ipafont}
\newenvironment{IPA}{\ipafont}{} % I know this isn't sufficient
\begin{document}
\textipa{RPAQIOE} % This will give you correct phonetic characters
\begin{textipa}
\bgroup
RPAQIOE
\egroup % This might !
\end{textipa}
\end{document}
Thanks,
That works within the environment, but is there a way to incorporate
into the environment definition itself? (Otherwise it defeats the
purpose of trying to deal with legacy code.)
Alan
--
Alan Munn
am...@gmx.com
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: loading different shapes/scales of one font as different font instances?
The memoir class provides all sorts of options for redefining things, including the chapter/section headings. I have never tried redefining the TOC but I wouldn't be surprised if memoir has provision for that too. David BPJ wrote: As the subject line says I wonder if it's possible with fontspec to load different shapes of the same font as different font instances? The thing is I'm going to write a script which generates XeLaTeX source and where the user is to be able to choose their own fonts/shapes/sizes for elements like text and headings, and I hope to be able to define a font instance for each of these elements but not to have to check if they want, say, italic or smallcaps headings scaled n and stick in formatting commands if they do! (Some of you may balk at italic/whatever headings, but in my case the linguistics anti-prescriptivism pill went down rather successfully, and I'd hate to be prescriptivist when I don't have to. Besides it is sometimes the case that bold is used with some technical signal value beside italics and I've found it convenient to set headings in smallcaps in such cases.[^1]) [^1]: This in turn requires an amount of \addcontentsline gymnastics. I'd appreciate pointers on methods/packages to globally styling headings/toc entries independently of each other. I'm probably showing my ignorance here, or my needs/wishes are really fringe! texdoc'ing "contents" or "toc" turns up nothing useful, and section.sty seemeth to be an olde and arcane dogge (at least to me!) /BP 8^)> -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] ** ERROR ** sfnt: Freetype failure...
On 7/28/2010 6:14 AM, tala...@fastmail.fm wrote: I have just run the two problematic files through a piece of Mac software called "textsoap", which "cleans up" the text. Apparently, there were some hidden, offending glyphs or characters that were causing the problem. The file now compiles fine using Baskerville 10 Pro. Actually, given the error that you got, that solution shouldn't have worked. If the problem was with just unknown characters, your log should have read something along the lines of "character not supported" for each of the offending glyphs. Is it possible to see the original problem .tex and full log? - Mike "Pomax" Kamermans nihongoresources.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
Alan Munn wrote: On Jul 28, 2010, at 11:45 AM, Philip Taylor (Webmaster, Ret'd) wrote: Maybe you could hack something better along these lines, Alan : That works within the environment, but is there a way to incorporate into the environment definition itself? (Otherwise it defeats the purpose of trying to deal with legacy code.) Well, that's what I meant by "back something better", Alan : I know nothing about LaTeX, but it looks as if it /might/ be possible ... ** Phil. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
On Jul 28, 2010, at 11:56 AM, Arthur Reutenauer wrote: I know the definition for the IPA environment isn't correct; what I want is characters inside that environment to be interpreted in the same way that they are within the \textipa command provided by xunicode. What you want is a mapping from tipa's transliteration system to the corresponding Unicode values for IPA characters; you can do that with TECkit: it generates a file that XeTeX knows how to use. Arthur Yes, that's probably the best solution (I proposed it myself to someone else a while ago.) I was wondering if there's was a quicker (and probably dirtier) way to do it, given that xunicode has already done much of the work. Maybe I'll just bite the bullet and make the mapping file. (But I'll still take suggestions for a quick and dirty solution.) Thanks Alan -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
Am Wed, 28 Jul 2010 11:25:30 -0400 schrieb Alan Munn:
> Hi
>
> The xunicode package provides a textipa command which recognizes (most
> of?) the commands from the tipa package. This is very useful, since
> it allows one to convert legacy documents containing IPA to xelatex
> with minimal trouble. However, the tipa package also provided an IPA
> environment. This is not supplied by xunicode. Is there a way to
> emulate that too? Here's a minimal document:
>
> I know the definition for the IPA environment isn't correct; what I
> want is characters inside that environment to be interpreted in the
> same way that they are within the \textipa command provided by xunicode.
You must use a name with small letters for your environment (tipa
activates the others)
\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\ipafont}{Doulos SIL}
\def\useTIPAfont{\ipafont}
\newenvironment{ipa}{%
\let\stone\TIPAstonebar
\let\tone\TIPAtonebar
\setTIPAcatcodes\activatetipa
\csname useTIPAfont\endcsname
}{}
\begin{document}
\textipa{RPAQIOE} % This will give you correct phonetic characters
\begin{ipa}
RPAQIOE
\end{ipa}
\end{document}
--
Ulrike Fischer
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
[XeTeX] pstricks and dvi output in xelatex
Is it possible to use pstricks in xelatex and get a dvi output so I can use the auto-updating feature of yap? I have a document that uses pstricks and diagrams don't show up correctly after compiling with xelatex because of the conversion to pdf. If I save to xdv then I can't view the file with yap to check if it rendered correctly. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
On Jul 28, 2010, at 2:03 PM, Ulrike Fischer wrote:
Am Wed, 28 Jul 2010 11:25:30 -0400 schrieb Alan Munn:
Hi
The xunicode package provides a textipa command which recognizes
(most
of?) the commands from the tipa package. This is very useful, since
it allows one to convert legacy documents containing IPA to xelatex
with minimal trouble. However, the tipa package also provided an IPA
environment. This is not supplied by xunicode. Is there a way to
emulate that too? Here's a minimal document:
I know the definition for the IPA environment isn't correct; what I
want is characters inside that environment to be interpreted in the
same way that they are within the \textipa command provided by
xunicode.
You must use a name with small letters for your environment (tipa
activates the others)
\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\ipafont}{Doulos SIL}
\def\useTIPAfont{\ipafont}
\newenvironment{ipa}{%
\let\stone\TIPAstonebar
\let\tone\TIPAtonebar
\setTIPAcatcodes\activatetipa
\csname useTIPAfont\endcsname
}{}
\begin{document}
\textipa{RPAQIOE} % This will give you correct phonetic characters
\begin{ipa}
RPAQIOE
\end{ipa}
\end{document}
Perfect. Thanks a lot, Ulrike. It's not a big deal to change the IPA
environments in the legacy source documents to ipa environments.
Is this documented anywhere? Also, would this environment be
something that it would make sense to add to xunicode?
Alan
--
Alan Munn
am...@gmx.com
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Pipes in XeTeX
Am 28.07.2010 um 14:40 schrieb Florian Gilcher: Now, I would try my theory if i could just get XeTeX (or, more specifically, the bundled ICU) to build from sources on Snow Leopard... You could try to build a 32-bit binary... -- Mit friedvollen Grüßen Pete Der Unterschied zwischen Theorie und Praxis ist in der Praxis meist größer als in der Theorie -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] problem with flashcards, polyglossia and RTL-languages
Hi,
using flashcards class in combination with polyglossia and RTL languages
I met a problem that wasn't there 6 months ago or so:
As soon as I add just a line of
\setotherlanguage{arabic-or-farsi-or-hebrew-or-syriac}
(no arabic etc. text is required for this effect), the text on both
sides jumps to the top of the resulting cards.
This happens with MiKTeX 2.8, updated today and MSWindows 2000;
in flashcards.cls the line
\RequirePackage{geometry}
is replaced with
\RequirePackage[paper=a4paper]{geometry}
and
twosideshift=\oddevenshift,
is commented out.
A minimal example:
%\TeXXeTstate=1
\documentclass[avery5371,frame,grid]{flashcards}
\usepackage{polyglossia}
\usepackage{xltxtra}
\setmainlanguage{english}
\setotherlanguage{german}
\setotherlanguage{arabic}
\usepackage{fontspec,xunicode}
\begin{document}
\begin{flashcard}{texttexttext}
texttexttext
\end{flashcard}
\end{document}
Without "\setotherlanguage{arabic}" all text on the cards is centered as
it was last year.
Is there any solution ?
Many thanks
Fabian Rieger
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
Hi Ulrike and Alan,
On 29/07/2010, at 4:03 AM, Ulrike Fischer wrote:
>> I know the definition for the IPA environment isn't correct; what I
>> want is characters inside that environment to be interpreted in the
>> same way that they are within the \textipa command provided by xunicode.
>
> You must use a name with small letters for your environment (tipa
> activates the others)
>
> \documentclass{article}
> \usepackage{xltxtra}
> \newfontfamily{\ipafont}{Doulos SIL}
> \def\useTIPAfont{\ipafont}
> \newenvironment{ipa}{%
> \let\stone\TIPAstonebar
> \let\tone\TIPAtonebar
> \setTIPAcatcodes\activatetipa
> \csname useTIPAfont\endcsname
> }{}
> \begin{document}
> \textipa{RPAQIOE} % This will give you correct phonetic characters
> \begin{ipa}
> RPAQIOE
> \end{ipa}
>
> \end{document}
You can take the extra step to be able to use
\begin{IPA}
...
\end{IPA}
viz.
>>> \documentclass{article}
>>> \usepackage{xltxtra}
>>> \newfontfamily{\ipafont}{Doulos SIL}
>>> \def\useTIPAfont{\ipafont}
>>> \newenvironment{ipa}{%
>>> \let\stone\TIPAstonebar
>>> \let\tone\TIPAtonebar
>>> \setTIPAcatcodes\activatetipa
>>> \useTIPAfont % no need for \csname here
>>> }{}
>>> \let\realend\end
>>> \let\endIPA\endipa
>>> \def\IPA{\let\end\ipaspecialend\ipa}% change how \end works inside IPA envs
>>> \def\endendipa{\end{IPA}}
>>> {\catcode`I = \active \catcode`P = \active \catcode`A= \active
>>> \gdef\foundendipa{IPA}%
>>> \gdef\ipaspecialend#1{\def\testforipa{#1}%
>>>\ifx \testforipa \foundendipa\expandafter\endendipa
>>>\else\realend{#1}%
>>>\fi}%
>>> }% end of \catcode changes
>>>
>>> \begin{document}
>>> \textipa{RPAQIOE} % This will give you correct phonetic characters
>>> \begin{ipa}
>>> RPAQIOE
>>> \end{ipa}
>>>
>>> RPAQIOE
>>>
>>> \begin{IPA}% So will this!
>>> RPAQIOE
>>> \end{IPA}
>>>
>>> \end{document}
But do *not* try to nest these environments.
If you have macros expanding to use such environments,
then there is no guarantee that these will work properly.
I think they will, since the definitions will have been
made with non-active letters, but have not tested it.
Writing out IPA environments into auxiliary files is
almost certain to *not* work.
But test it, if you need this kind of feature.
> --
> Ulrike Fischer
Hope this helps,
Ross
Ross Moore ross.mo...@mq.edu.au
Mathematics Department office: E7A-419
Macquarie University tel: +61 (0)2 9850 8955
Sydney, Australia 2109 fax: +61 (0)2 9850 8114
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
On Jul 28, 2010, at 5:37 PM, Ross Moore wrote:
Hi Ulrike and Alan,
On 29/07/2010, at 4:03 AM, Ulrike Fischer wrote:
I know the definition for the IPA environment isn't correct; what I
want is characters inside that environment to be interpreted in the
same way that they are within the \textipa command provided by
xunicode.
You must use a name with small letters for your environment (tipa
activates the others)
\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\ipafont}{Doulos SIL}
\def\useTIPAfont{\ipafont}
\newenvironment{ipa}{%
\let\stone\TIPAstonebar
\let\tone\TIPAtonebar
\setTIPAcatcodes\activatetipa
\csname useTIPAfont\endcsname
}{}
\begin{document}
\textipa{RPAQIOE} % This will give you correct phonetic characters
\begin{ipa}
RPAQIOE
\end{ipa}
\end{document}
You can take the extra step to be able to use
\begin{IPA}
...
\end{IPA}
viz.
\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\ipafont}{Doulos SIL}
\def\useTIPAfont{\ipafont}
\newenvironment{ipa}{%
\let\stone\TIPAstonebar
\let\tone\TIPAtonebar
\setTIPAcatcodes\activatetipa
\useTIPAfont % no need for \csname here
}{}
\let\realend\end
\let\endIPA\endipa
\def\IPA{\let\end\ipaspecialend\ipa}% change how \end works
inside IPA envs
\def\endendipa{\end{IPA}}
{\catcode`I = \active \catcode`P = \active \catcode`A= \active
\gdef\foundendipa{IPA}%
\gdef\ipaspecialend#1{\def\testforipa{#1}%
\ifx \testforipa \foundendipa\expandafter\endendipa
\else\realend{#1}%
\fi}%
}% end of \catcode changes
\begin{document}
\textipa{RPAQIOE} % This will give you correct phonetic characters
\begin{ipa}
RPAQIOE
\end{ipa}
RPAQIOE
\begin{IPA}% So will this!
RPAQIOE
\end{IPA}
\end{document}
But do *not* try to nest these environments.
If you have macros expanding to use such environments,
then there is no guarantee that these will work properly.
I think they will, since the definitions will have been
made with non-active letters, but have not tested it.
Writing out IPA environments into auxiliary files is
almost certain to *not* work.
But test it, if you need this kind of feature.
Thanks, Ross. What I'm mainly looking for is a fairly simple way of
using legacy TIPA code, and I don't know whether this would cause any
problems or not. I also don't quite know how much xunicode itself
emulates TIPA and how much it doesn't. Right now there are various
things that don't work, but I don't know enough about how xunicode
works (and probably the relevant fonts themselves) to make a new
package that would make the emulation more complete.
For example, (and not surprisingly) the following commands are defined
in TIPA, but don't work with xunicode:
\* depending on produces the turned version of for
{fkrtw} or a specific other character for {jnhlz} else a non-IPA
version of
\; produces a small caps version for {EJAHLUBGNR}
\: produces a retroflex version for {dlnrRstz}
etc.
These commands are defined in the following way in tipa.sty
\DeclareTextCommand{\:}{T3}[1]{#1}
\DeclareTextAccentDefault{\:}{T3}
\DeclareTextComposite{\:}{T3}{d}{227}
etc.
If I were to do the same thing using xunicode how would I do it?
Also (and more suprisingly) \c{c} doesn't seem to work, but gives
Undefined control sequence \realLaTeXcedilla
Anyway, I'd be happy to do some of the work, but I'm somewhat in the
dark as to how to start.
Thanks
Alan
--
Alan Munn
am...@gmx.com
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] problem with flashcards, polyglossia and RTL-languages
having
\documentclass[avery5371,frame,grid]{flashcards}
\begin{document}
\begin{flashcard}{texttexttext}
texttexttext
\end{flashcard}
\end{document}
as my document and running either pdflatex or xelatex, I get this error:
! Package geometry Error: \paperwidth (0.0pt) too short.
See the geometry package documentation for explanation.
Type H for immediate help.
...
l.989 \...@process
I am using pretest TL10. Sorry but your example should run smoothly so that
I can understand what is wrong.
?
--
Best wishes,
Vafa Khalighi
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] xunicode and TIPA
Hi Alan,
On 29/07/2010, at 8:34 AM, Alan Munn wrote:
> Thanks, Ross. What I'm mainly looking for is a fairly simple way of using
> legacy TIPA code, and I don't know whether this would cause any problems or
> not. I also don't quite know how much xunicode itself emulates TIPA and how
> much it doesn't. Right now there are various things that don't work, but I
> don't know enough about how xunicode works (and probably the relevant fonts
> themselves) to make a new package that would make the emulation more complete.
>
> For example, (and not surprisingly) the following commands are defined in
> TIPA, but don't work with xunicode:
>
> \* depending on produces the turned version of for
> {fkrtw} or a specific other character for {jnhlz} else a non-IPA version of
>
>
> \; produces a small caps version for {EJAHLUBGNR}
> \: produces a retroflex version for {dlnrRstz}
The problem is that these macros are already defined in TeX,
at least in math-mode.
Look at the results of the following to confirm this.
\show\* \show\: \show\;
I need explicit examples of how TIPA uses these, to try to
design the best way to support them in Xunicode.
If we can guarantee that they will only be used
within {ipa} {IPA} environments, or \textipa{...}
then support can be added within Xunicode.
If you want them outside such environments, then you'll need
to do it with an extra package (that can require Xunicode).
>
> etc.
How many others are there in this 'etc.' ?
>
> These commands are defined in the following way in tipa.sty
>
> \DeclareTextCommand{\:}{T3}[1]{#1}
> \DeclareTextAccentDefault{\:}{T3}
> \DeclareTextComposite{\:}{T3}{d}{227}
Clearly these are specific to T3 encoding, which is now not
relevant. So I really need to see example usages, to work
out what is needed, and to supply examples for testing.
>
> etc.
>
> If I were to do the same thing using xunicode how would I do it?
>
> Also (and more suprisingly) \c{c} doesn't seem to work, but gives
>
> Undefined control sequence \realLaTeXcedilla
Hmm. Not sure why this happens.
Can you send a LaTeX preamble, and simple example.
>
> Anyway, I'd be happy to do some of the work, but I'm somewhat in the dark as
> to how to start.
It's not as easy as you might think it ought to be.
This is because you want the definitions to be compatible
with other usages of the macro-name, and have flexibility
for different possible encodings.
>
> Thanks
>
> Alan
>
>
>
> --
> Alan Munn
> am...@gmx.com
Hope this helps,
Ross
Ross Moore ross.mo...@mq.edu.au
Mathematics Department office: E7A-419
Macquarie University tel: +61 (0)2 9850 8955
Sydney, Australia 2109 fax: +61 (0)2 9850 8114
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
