Am 11.06.2011 um 16:23 schrieb Vafa Khalighi:
Further homosexuality originated from Greece.
That's so silly that you better return to kindergarten!
Homosexuality exists world-wide as a natural phenomenon, as is the
colour of eyes (or the language or the script). Some cultures are
great
Am 12.06.2011 um 22:26 schrieb Pander:
I have discovered a problem with ocrb10.otf the ligatures are not
workig
correctly in xelatex.
/usr/local/texlive/2010/texmf-dist/fonts/opentype/public/ocr-b-outline/
ocrb10.otf *of course* does not have the f* ligatures. (You can check
this easily
Am 06.06.2011 um 09:33 schrieb Tobias Schoel:
3. xdvipmx and xdv2pdf convert TikZ's \special{}s into pdf
transparency on all systems.
Xdv2pdf seems to produce some strange PDF output on my system (Mac OS
X 10.5.8, PPC). The disdvi utility of TeX Live 2011 is able to
disassemble an XDV f
Am 18.06.2011 um 23:20 schrieb Blake Wentworth:
I would be delighted to know where the source of the initial problem
lies
You could specify the renderer engine! Fontspec allows
\fontspec[Renderer=AAT]{font}
(other options are ICU, usable for most fonts, and Graphite, usable
for j
Am 19.06.2011 um 13:53 schrieb Philip TAYLOR (Webmaster, Ret'd):
Is this meaningfully true for all platforms ?
Of course not. But Blake used Apple Mail to send his message and he
also mentions Mac OS X as the OS he uses, where his problems occur. So
I tried to use my brain and mentioned t
Am 19.06.2011 um 15:14 schrieb Philip TAYLOR (Webmaster, Ret'd):
Yes, but your mail will be read by others (such as myself)
who are unaware of either of these facts, and will then be
misled into believing that it should work in their platform.
The term "AAT" stands for "Apple Advanced Typogra
Am 19.06.2011 um 15:58 schrieb Philip TAYLOR (Webmaster, Ret'd):
I am not complaining : I am asking for precision, which
is another matter entirely.
So, here is precision: AAT is a proprietary Mac OS X font technology
from Apple (maybe doomed to die). It started as QuickDraw GX, on which
Am 19.06.2011 um 23:40 schrieb Tobias Schoel:
m I the OP? (I don't know that abbreviation and therefore I am
confused.)
*O*riginal *P*oster. (I hope this posting looks original as well.)
Unicode has codepoints for the roman numerals from 1 to 12 (why 12?).
So should CXV be stored as an id
Am 20.06.2011 um 16:59 schrieb Tobias Schoel:
Are months written with roman numerals?
Ask your granddad! (In other languages, for example Polish, Hungarian,
Romanian, Bulgarian, the month is written in Roman numerals, sometimes
with over- and under-strokes, in France and Spain the same wa
Am 23.06.2011 um 19:11 schrieb Peter Baker:
I can't reproduce the problem, but I'm using the CVS version of
Junicode.
This could be true! Believe me that I could reproduce the problem (in
a XeLaTeX file, with Unicode font and text encoding). I then switched
from Junicode to other fonts.
Am 05.07.2011 um 06:56 schrieb Le Farfadet Spatial:
. First, it seems that the font Linux Libertine does not have any
bold italic characters.
First, Michael Niedermair wrote three weeks ago to include into your
LaTeX document the line
\usepackage{libertine}
and it's meant to al
Am 05.07.2011 um 10:36 schrieb le.farfadet.spat...@free.fr:
Are you sure you are not mistaking me with someone else?
Yes, I am. In the footer of the mails of this list you can find a link
to the list's archive. In the middle of June a thread about some too
heavy Libertine face started. Re
Am 15.07.2011 um 00:57 schrieb Michael Joyner:
I am trying to use the epsdice package from inside LyX, and when I
switch to
using xelatex as the formatting engine, the package malfunctions.
This packages is a bit old and meant to be used with the pdfTeX
engine. With XeTeX you can:
Am 16.07.2011 um 09:38 schrieb Michael Joyner:
> As a sort of an aside (could tie into this) Is there a way to specify a
> "fallback" font for tetex to use when a glyph is not present in the current
> active font?
The results of finding in some other font the character would not satisfy the
use
Am 16.07.2011 um 10:55 schrieb Michael Joyner:
> Here is the current results attached as a single page PDF.
I'm missing the use of IPA – how do you pronounce these words?
--
Greetings
Pete
Almost anything is easier to get into than out of.
– Allen's Law
-
Am 16.07.2011 um 18:04 schrieb Michael Joyner:
Am 16.07.2011 um 09:38 schrieb Michael Joyner:
As a sort of an aside (could tie into this) Is there a way to
specify a
"fallback" font for tetex to use when a glyph is not present in the
current
active font?
The results of finding in some o
Am 16.07.2011 um 22:30 schrieb msk...@ansuz.sooke.bc.ca:
Bear in mind that the audience for his project is not
linguists who might already know IPA, but language learners.
Probably British learners, so they would know how "Hee" is pronounced
in English. In German it might me transcribed as
Am 16.07.2011 um 23:32 schrieb Michael Joyner:
How would one leverage that to handle my font defines of (below) for
only a fixed range of unicode?
You either use a loop to activate the up to 128 characters or you use
a font with Cherokee script and characters support to type Cherokee.
Or
Am 17.07.2011 um 00:42 schrieb Michael Joyner:
The font definition I posted has Cherokee glyphs, but I have to fake
bold,
etc.
Try GNU FreeSerif and FreeSans! (My FreeMono has only one Cherokee
type face.)
--
Greetings
Pete
Some day we may discover how to make magnets that can poin
Am 17.07.2011 um 16:21 schrieb Michael Joyner:
> If I wanted to redefine
> the UNICODE range for Cherokee Glyphs to match the below, so that I could
> leave the rest using standard fonts, by using the \def approach, how would
> you do it?
Maybe this (untested) works:
\newfontfamily\Che
Am 17.07.2011 um 17:58 schrieb Petr Tomasek:
> are the microtype fetures already merged into XeTeX SVN TRUNK,
I think they are, but the TeX Live 2010 distribution does not have the new
microtype package. The update is available via tlmgr (or TLU on Mac OS X) from
the repository http://tlcontri
Am 17.07.2011 um 22:59 schrieb Philip TAYLOR (Webmaster, Rettet):
> Peter Dyballa wrote:
>
>>\def\n{\Cher\n}
>
> Can't see that working : won't the expansion of
> \n involve the expansion of \n, which will involve
> the ... (you get the idea).
Yes,
Am 18.07.2011 um 11:34 schrieb Susan Dietmar:
> If I understand correctly, he wants to
> construct a loop, where \n contains the loop's counter (and the integer
> representation of the character to be replaced, if I understand correctly),
> so he does not want to define \n, but define whatever \n
>> After searching on google I found the command
>>
>> \special{x:backgroundcolor=color}
Could be this \special{} is meant for the old Mac OS X output driver xdv2pdf...
--
Greetings
Pete
Globalisation – communism from above.
--
Subscriptio
Am 04.08.2011 um 15:02 schrieb Alan Jones:
> ! LaTeX Error: File `xetex.def' not found.
>
> Type X to quit or to proceed,
> or enter new name. (Default extension: def)
Here you could try to invoke, in a second shell, 'sudo texhash' to make your
TeX installation aware of all its files. You can
Am 04.08.2011 um 22:11 schrieb Peter Dyballa:
> Actually it might be possible to use the tlmgr (TeX Live [distribution]
> Manager) script to update your TeX installation.
Doing so today might be a bit dangerous. See this thread:
http://tug.org/pipermail/tex-live/2011-August/02987
Am 10.08.2011 um 10:28 schrieb John Was:
> It's not an intellectually satisfying solution, but could you not yourself be
> the first (dummy) customer each day, offering up a file for PDF conversion so
> that the initial slow processing happens only to you?
It should be easier, and more efficie
Am 13.08.2011 um 06:08 schrieb Neal Delmonico:
> ---! /usr/local/texlive/2009/texmf-var/web2c/xetex/xelatex.fmt doesn't match
> xetex.pool
> (Fatal format file error; I'm stymied)
Did you read the sequence "2 0 0 9"? It tells you that you are *not* using the
updated xelatex.
>
> How do I fix
Am 13.08.2011 um 10:45 schrieb Dominik Wujastyk:
> have you tried rebuilding the fmt file?
Tlmgr usually does this job. (Also updating the MAP files.)
--
Greetings
Pete
Upgraded, adj.:
Didn't work the first time.
--
Subscriptions, A
Am 13.08.2011 um 20:01 schrieb Neal Delmonico:
> Any suggestions?
Please use the updated version! Not the old stuff from 2009.
--
Greetings
Pete
When you meet a master swordsman,
show him your sword.
When you meet a man who is not a poet,
do not show him your poem.
–
Am 23.08.2011 um 15:09 schrieb Wilfred van Rooijen:
> #> locate SIunits
Locate is some non-TeX utility. It is not guaranteed that it will function.
Better use the texdoc utility. The command
texdoc texdoc
should enable you to use texdoc.
--
Greetings
Pete
Without vi there is only
Am 30.08.2011 um 09:53 schrieb Keith J. Schultz:
> The question is if there is an actual need to still support ATSU at all?
This question could probably be answered on some fonts or font technologies
related list. Maybe Apple folks could contribute by answering whether Apple is
going to
Am 30.08.2011 um 12:56 schrieb Chris Yocum:
> I was just wondering what would be necessary to get micro-type into the
> core of XeTeX?
The recent XeTeX versions in TeX Live 2010 and 2011 *are* micro-type enabled.
>
> After looking at the wiki
> (http://xetex.tk/mediawiki/index.php/Microtype_pa
Am 30.08.2011 um 16:43 schrieb Keith J. Schultz:
> ATSU is deprecated and replaced by Core Text for handling unicode as of
> Leopard.
>
> So, xetex has to be refractured or rewritten to use Core Text on the Mac.
Why? XeTeX pioneered in the use of Unicode in TeX. Its development has come to
Am 31.08.2011 um 12:02 schrieb Keith J. Schultz:
> Nothing is considered stable just yet.
The same would be true when you try to port XeTeX from ATSUI to CoreText.
>
> In other words, xe(la)tex would be the way to go. For awhile.
And therefore keep old versions of Mac OS X! Leopard and Snow
Am 31.08.2011 um 16:50 schrieb Jonathan Kew:
> Why, is there a problem with running the current (Intel build of) xetex on
> 10.7? I wasn't aware of this.
And neither me. Because I'm not using Lion (Mac OS X 10.7).
>
> Seems like you're introducing unnecessary complication and confusion
I
Am 31.08.2011 um 20:42 schrieb Rolf Schmolling:
> So what to do?
As Herb mentioned: you need to download and install the "experimental"
microtype package from the TLcontrib site. Tlmgr on all platforms and TLU (TeX
Live Utility) on modern Mac OS X platforms (Snow Leopard, Lion) can perform
th
Am 01.09.2011 um 01:29 schrieb Arthur Reutenauer:
> On a related note, are you aware that you should never talk to a llama
> wearing your socks inside out?
I actually don't care, I prefer to go naked. At least down under.
--
Greetings
Pete
Our enemies are innovative and resourceful, and so
Am 01.09.2011 um 14:27 schrieb Daniel Greenhoe:
> So instead of the \setmathrm giving me the font I requested, I seem to
> be getting a computer modern font. Why would this be???
Because you don't set your maths in \mathrm! The default for maths is a
sans-serif font, because the text usually co
Am 01.09.2011 um 19:44 schrieb Keith J. Schultz:
> Woof!
Wasn't it “Moof”?
Moof.aiff
Description: audio/aiff
--
Greetings
Pete
_oo o o
_<< \\_/\_, \\_ \\_/\_,
(*)/(*) (*) (*) (*) `-(*)
--
Subscr
Am 01.09.2011 um 20:13 schrieb Keith J. Schultz:
> Furthermore I do not know which compilers are used over at MacTeX as this
> does matter
> in ways which are far to complicates to discuss here.
It's not only a question of compilers – you also need SDKs!
If you want to create new binaries whic
Am 01.09.2011 um 21:12 schrieb Keith J. Schultz:
> Are you sure you know what you are talking- er- writing about!!
Yes.
The problem is with libgcc (or libstdc++ or libobjc). You don't need to include
it in the static binary, because the target OS has it. Tiger has only the GCC
4.0.1
Am 02.09.2011 um 03:12 schrieb Keith J. Schultz:
> So If I follow you right I should build a 64-bit xetex for Tiger! ;-)))
Some folks prefer 64-bit applications. Tiger doesn't support that much 64-bit
hardware, starting with Mac OS X 10.4.8. Tiger has working ATSUI, so a 64-bit
XeTeX based o
Am 05.09.2011 um 01:11 schrieb Tschijnmo Tschau:
> kpathsea: Invalid fontname `Gentium Book Basic', contains ' '
This, "kpathsea", indicates that fontspec did not find the font name in the
system's font service and therefore delegated the job of finding the font to
TeX.
It is correct to edit
Am 15.09.2011 um 10:13 schrieb Marc Hohl:
> I used "xdvi" instead of "dvipdfm"
How can you display an XDV (or PDF) file with xdvi?
Dvipdfm is neither able to use an XDV file, the intermediary output format of
XeTeX, which you usually do not see, because it's piped to xdvipdfmx, which
produces
Am 15.09.2011 um 19:07 schrieb Zdenek Wagner:
> Remember that graphics inclusion is not a job of TeX but a job of the
> driver.
I know. XeTeX does not produce such a message. It can easily handle PNG and
others, without needing a BB or XBB file. This line comes from using dvipdfm.
And dvipdfm
Am 16.09.2011 um 22:09 schrieb John Was:
> Not a strictly XeTeX issue, but can anyone recommend a font (preferably
> Unicode compliant but not absolutely essential) that contains the
> astrological symbols (planets, zodiacal signs etc.: mainly Unicode range
> 263D and following) and will look
Am 18.09.2011 um 22:02 schrieb rhin...@postmail.ch:
> This point is quite important, since it is much easier to install a font
> in the system as to install it for TeX.
Either look into the texmf.cnf files for AFM or FONT related variables or
simply invoke:
kpsewhich -engine xetex -sho
> :
>> Hi All,
>>
>>
>>
>> Are they any comparisons documents, which shows the difference between
>> XeLaTeX and LaTeX typesettings?
There can't be any. Both pass the TRIP test.
--
Greetings
Pete
The problem with the French is that they don't have a word for « entrepreneur ».
>>
>> 2. XeLaTeX cannot use microtypographical extensions but it may change
>> in the future. Currently pdflatex or lualatex is needed.
>
> Actually there are already experimental versions of XeTeX lying around
> that have some microtypographical features, see:
> http://xetex.tk/mediawiki/index.
Am 23.09.2011 um 18:32 schrieb Jean-Louis Garcin:
> And the same list of commands when I typesset with latex instead of xelatex
> is succesfull.
PSTricks are written for the pdfTeX engine. XeTeX uses a different engine which
supports some of the PSTricks. You could try LuaTeX...
You could al
Am 24.09.2011 um 21:20 schrieb rhin...@postmail.ch:
> \fontspec[%
>Extension=.otf,
>UprightFont = *,
>BoldFont=*Bold,
>ItalicFont=*Italic,
>BoldItalicFont=*BoldItalic]{GFSDidot}
With XeTeX you certainly don't need this block.
I could get your result onl
Am 25.09.2011 um 10:55 schrieb rhin...@postmail.ch:
> Is this solution possible under Windows ? How to implement it ?
I prefer not to use MS Windows privately. (The setup for fontconfig is
documented, some .CNF files already exist in the distribution.)
--
Greetings
Am 25.09.2011 um 10:55 schrieb rhin...@postmail.ch:
> Yes I would prefer not to install GFS Didot in the font
> directory of Windows and thus not to use the font service
> for this font.
There are two or three possible options…
You could put the fonts into the same directory as the TeX file.
Am 29.09.2011 um 12:34 schrieb peter knezel:
> what is the default font setting for text and for math in xelatex?
For text it's Latin Modern.
You can check the fonts used with the pdffonts utility (from xpdf package).
With given \pagestyle{empty} you can exactly determine which fonts are used
Am 30.09.2011 um 08:48 schrieb peter knezel:
> How should I know which of them supports math fonts and which of them is
> monospaced (like Courier New)?
With the fontconfig package you should have received the file
/usr/X11/share/doc/fontconfig/fontconfig-user.html (or in some similar path).
I
Am 30.09.2011 um 17:26 schrieb NEAL DELMONICO:
> I assume the new progs were copied over the old ones.
No, Neal, this does never happen.
> Is that okay, or should I do a clean install and update to 2011?
You should update PATH, MANPATH, INFOPATH instead.
Look at /usr/local/texlive! You'll se
Am 30.09.2011 um 19:03 schrieb Neal Delmonico:
> How does one do this on a Windows machine?
I don't know; and I prefer to use other Windows, those I can open and close.
--
Greetings
Pete
Encryption, n.:
A powerful algorithmic encoding technique employed in the creation of
computer
Am 04.10.2011 um 12:01 schrieb Vladimir Lomov:
> Don't do that! Please, read carefully l2tabue (search for file
> `l2tabue.pdf' or run 'texdoc l2tabue').
It's "l2tabuen".
--
Greetings
Pete
Time flies like an error – but fruit flies like a banana!
- (almost) G
Am 06.10.2011 um 22:33 schrieb Le Farfadet Spatial:
> Does anybody have an idea to solve this problem?
Don't run fc-cache on the doc(uments) tree but the fonts tree!
(/usr/local/texlive/2011/texmf-dist/fonts)
--
Greetings
Pete
There's no place like ~
– (UNIX Guru)
Am 06.10.2011 um 23:29 schrieb Pander:
> It can also differ to run
> fc-cache -f
> and
> sudo fc-cache -f
> so I'd recommend to run both
At least this system-wide directory was touched:
>> /var/cache/fontconfig: cleaning cache directory
--
Greetings
Pete
Got Mole problems?
Call Avogadro
Am 08.10.2011 um 03:15 schrieb Le Farfadet Spatial:
> I went in the directory, and have run both commands. None of them has given
> any output, but I still get the error with Linux Libertine.
OK! Did you configure fontconfig to scan the libertine directory?
Can you repeat the fc-cache command(
Am 12.10.2011 um 00:10 schrieb Chris Travers:
> texlive-xetex-2007-51.fc13.i686
Now that the 2011 is almost finished you could consider updating to TeX Live
2011…
--
Greetings
Pete
Rain is saved up in cloud banks.
--
Subscriptions, Archiv
Am 12.10.2011 um 16:28 schrieb Hendrik Maryns:
> I want to use some IPA characters in my document
What you also need is to use a font for "printing" these IPA characters that
actually has them! Not all fonts have them. The fontspec default font, Latin
Modern, does not. Linux Libertine O/Linux
Am 12.10.2011 um 17:40 schrieb Tobias Schoel:
> the character seems not to be included in Latin Modern (standard with
> fontspec).
Because it's not IPA (LATIN SMALL LETTER ALPHA, U+0251).
--
Mit friedvollen Grüßen
Pete
The best way to accelerate a PC is 9.8 m/s²
---
Am 13.10.2011 um 18:35 schrieb Tobias Schoel:
> So what component is the source of problems.
Asana Math. It has only a regular face. (Fontspec allows to artificially make a
font bold.)
--
Mit friedvollen Grüßen
Pete
To be is to do.
– I. Kant
To do is to be.
Am 14.10.2011 um 12:03 schrieb Suresh Avvarulakshmi, Integra-PDY, IN:
> I was trying to compile the XMLTeX source files in XeLaTeX application.
OK, you know that these files exist somewhere. Can you tell us where they exist?
--
Greetings
Pete <]
o
Am 18.10.2011 um 10:30 schrieb Chris Travers:
> Is there any way to manually create this file?
TeX Live comes with a utility, fmtutil-sys. It allows to create FMT files for
the *system*. Private FMT files can be created with fmtutil. The former is kind
of a wrapper for the latter, so the only
Am 18.10.2011 um 15:43 schrieb Chris Travers:
> Given that server software that I work with usually has at least a
> five year support cycle, what are those reasonable limits?
For TeX I'd think in decades. And support in the way TeX understands this term
is constant development and constant upd
Am 18.10.2011 um 16:39 schrieb Chris Travers:
> Here's a breakdown of OS support for TexLive versions for anyone interested:
>
> Debian Lenny: TexLive 2007
> Debian Squeeze: TexLive 2009
> Debian Sid: TexLive 2009
> Ubuntu 10.04 LTS: TexLive 2009
> Red Hat Enterprise 6: TexLive 2007
> That
Am 19.10.2011 um 12:19 schrieb Chris Travers:
> If RHEL 6 (released about a year ago) is sticking to TeXLive 2007, we all
> have problems.
The only problem is that of understanding. It's like the fifth wheel or the
tool to change wheels that come with new car. They're not really usable,
they'
Am 19.10.2011 um 16:09 schrieb Chris Travers:
> However, it seems
> to me that this community here doesn't really care about the kinds of
> environments where this sort of document processing occurs.
Or this community knows how to get back to functioning state. Or uses test or
development areas
Am 19.10.2011 um 16:21 schrieb Herbert Schulz:
> I don't think packages in updated TeX Live installations are changed
> arbitrarily but rather in response to bug fixes that others, and possibly not
> all users, have observed.
Indeed! Usually new (possibly bugful) features enter stage when a ne
Am 20.10.2011 um 12:32 schrieb Petr Tomasek:
> This is the best way to hell. Native packages should be used and not some
> stupid external blob!
Can it be that you see stupidity because you can't see tlmgr and that the blob
is similar to any Linux distribution?
What keeps you from installing T
Am 20.10.2011 um 12:53 schrieb Chris Travers:
> However, statically linking things strikes me as even worse from a
> stability/security perspective (which is what is critical with server
> software). It means that if there is a bug in any of the libraries
> you have possibly linked to, you have
Am 20.10.2011 um 13:24 schrieb Chris Travers:
> So if libz needs a security update, I can get it without replacing
> everything else
What do you gain with that? What is the difference between overwriting 5 MB or
50 MB of disk space?
--
Greetings
Pete
Bake pizza not war!
---
Am 20.10.2011 um 13:32 schrieb Susan Dittmar:
> Could you tell me how to do that for openSUSE from the top of your head?
No. I never created the specification for an RPM or DEB package in Linux (I
think I edited a few of them). Once it's created the package manager will build
the package and p
Am 20.10.2011 um 16:12 schrieb Chris Travers:
> Not disturbing other dependencies that production software depends on.
It can't. It does not carry shared libraries, DLLs, or such, that make
ld_config or such go mad. TeX Live is like the universe: it's self-contained.
And expanding...
--
G
Am 20.10.2011 um 16:54 schrieb Chris Travers:
> One of the other commentors talks about documents that don't render on
> all versions of TexLive. If a client of mine is depending on this
> working, upgrading the various stuff from CTAN in order to get a
> security fix in an underlying program is
Am 20.10.2011 um 17:08 schrieb Petr Tomasek:
> And that's exactly what's wrong and what needs to be changed...
Yes, I wouldn't stand the pain when the big rip will happen. This will feel
like the middle ages. Before this we will get very bloated, which should hurt
as well. I also prefer the bi
Am 21.10.2011 um 00:51 schrieb Chris Travers:
> I'm not the one mixing things up. What I am saying is perhaps a bit
> different. If you are tying the .sty upgrades to binary upgrades,
> then an upgrade in a binary requires .sty upgrades, and these can
> break document generation systems.
Neith
Am 21.10.2011 um 01:42 schrieb Chris Travers:
> At the time a large portion of the industry was writing software
> statically linked against zlib
I think it wasn't zlib, it was versions of zlib, presumingly dozens.
>
> If TexLive had been around in 2002 and was statically linking to zlib,
> it
Am 21.10.2011 um 09:40 schrieb Chris Travers:
> Am I reading this wrong?
No, but you you're choosing the wrong candidates, those from the old and
smelling Linux packages.
--
Greetings
Pete
Build a man a fire and he'll be warm for a night, but set a man on fire and
he'll be warm for the re
Am 24.10.2011 um 00:57 schrieb Daniel Greenhoe:
> I am talking about these for example ...
> T ==> theta ('124)
> A ==> script A ('101)
> @ ==> schwa ('100)
> 2 ==> turned V ('062)
> D ==> Eth ('104)
> E ==> epsilon ('105)
> N ==> right-tail n ('357)
> S ==> Esh ('123)
>
Am 25.10.2011 um 20:12 schrieb Andy Lin:
> %These two lines are for xunicode, if you use it instead
> %\newfontface\doulos{Doulos SIL}
> %\def\useTIPAfont{\doulos}
> \newfontface\tipafont[Mapping=xetex-textipa]{Doulos SIL}
And another option is to turn this font declaration (similar to {\rmfamil
Am 27.10.2011 um 10:06 schrieb Daniel Greenhoe:
> If I can do this conversion from the command line, why can't fontspec
> handle it correctly? That is, before fontspec tries to interpret a
> sequence beginning with "\" as a command, why can't it first check to
> see if the sequence is up for repl
Am 28.10.2011 um 13:58 schrieb Mojca Miklavec:
> If nothing else, if nobody adapts
> the code, it might stop working with next version of Mac OS X or a
> version after that.
Mac OS X is not the world. Classic Mac OS was the basis for the first XeTeX
development. When Apple decides to change its
Am 30.10.2011 um 02:12 schrieb Daniel Greenhoe:
> For example the "b" with a small circle under it
> (voiceless b) is quite important in Chinese. Any suggestions for
> typesetting glyphs with diacritics?
With COMBINING RING BELOW, U+0325?
--
Greetings
Pete
Engineer: a mechanism for converti
Am 30.10.2011 um 10:11 schrieb Daniel Greenhoe:
> How do I in general put, for example, U+0325 below U+0062,
> while still maintaining proper alignment (e.g. the bottom of the "b"
> (U+0062) with a ring (U+0325) below it is still aligned with the
> bottom of an adjacent "c" (U+0063) with nothing
Am 31.10.2011 um 19:06 schrieb Andy Lin:
> IIRC (and I might not), Calibri, Meiryo, and Tahoma(Windows Vista or
> later) should have at least partial support of IPA characters. My
> fallback font is Lucida Sans Unicode.
I checked my own font repertoire. The Tahoma I have (Version 5.01.2x) has th
Am 03.11.2011 um 13:46 schrieb A u:
> /usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmappings/
The correct pathname would be:
/usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmapping. Since your
files are local additions to the TeX distribution it's better you save them in
Am 03.11.2011 um 16:57 schrieb Zdenek Wagner:
> doubling "fonts" in texmf-local/fonts/fonts/misc/... will be a problem.
Bad mistake, indeed. Too many interrupts might excuse this faux-pas...
> The output of strace could help.
Mac OS X comes without strace. But it has DTrace...
--
Greetings
Am 03.11.2011 um 23:53 schrieb A u:
> I checked line number 54 and it looks like this "U+092F > U+0C2F"
To me it looks like
U+092E > U+0C2EU
--
Greetings
Pete
Remember: use logout to logout.
--
Subscriptions, Archive, and List inf
Am 04.11.2011 um 00:04 schrieb A u:
> I am attaching the tex file that I am working with along with pdf output and
> log file.
You would have found the cause of the failures if would have looked into the
LOG file...
Firstly you are obviously using TeX Live 2010. So installing the teckit files
Am 04.11.2011 um 01:13 schrieb Zdenek Wagner:
> 2011/11/4 Peter Dyballa :
>>
>> Am 03.11.2011 um 23:53 schrieb A u:
>>
>>> I checked line number 54 and it looks like this "U+092F > U+0C2F"
>>
>> To me it looks like
>>
>>
Am 04.11.2011 um 00:04 schrieb A u:
> I created new map file and it did not give any errors. but I am still
> getting blank pdf.
By using the correct TEC file's name I get something Indic with a Latin page
number 1. The fonts used are, according to pdfinfo:
name
Am 05.11.2011 um 19:06 schrieb Karljurgen Feuerherm:
> Typesets fine... But the output PDF is still letter size
Either set
\pdfpagewidth=176truemm
\pdfpageheight=250truemm
or use the geometry package!
--
Mit friedvollen Grüßen
Pete
I hope to die before I *have* to use Micr
Am 05.11.2011 um 19:06 schrieb Karljurgen Feuerherm:
> Typesets fine... But the output PDF is still letter size
There are two more options, of course, because it's a (well) known problem:
xelatex -papersize=b5 … # don't know by heart what's supported
xdvipdfmx -p b5 … # do
Am 06.11.2011 um 02:15 schrieb Andrew Gollan:
> The Invalid glyph is
> actually the result of a \=V in one place, but the \=y is being printed as
> a spiral in the PDF if that is remove
V with macron does not exist in Unicode (but U with macron does, so it looks
bad, until you invent a good mac
Am 06.11.2011 um 12:41 schrieb Andrew Gollan:
> It used to work.
Yes! I too remember that I could typeset documents in Palatino Linotype with
XeLaTeX.
Actually I still can! Sorry, I'm a bit busy with other things today… But what
I've found is that your use of composed characters with macro
301 - 400 of 589 matches
Mail list logo