Am 18.08.2010 um 16:07 schrieb tegi...@bluewin.ch:
\setmainfont{Adobe Garamond Pro}
When you comment this line (that Latin Modern gets used), does it
still fail to create the desired look? How does it work with the
starred form, i.e., 2\textsuperscript*{ème}?
Did you try 'texdoc xltxtr
Am 18.08.2010 um 18:07 schrieb Ron Aaron:
How can I find out exactly what "pdf" specials are available in xetex?
By reading what 'texdoc dvipdfm' shows.
--
Greetings
Pete
Cabbage, n. A familiar kitchen-garden vegetable about as large and
wise as a man's head.
-
Am 18.08.2010 um 17:10 schrieb Lomky:
Are there other ways to convert it to utf8?
GNU Emacs, the recode utility, using a backup of the original
unchanged file...
--
Greetings
Pete
"Debugging? Klingons do not debug. Our software does not coddle the
weak."
---
Am 27.08.2010 um 21:01 schrieb Jens Bakker:
Also putting the command "sudo texhash" into the Terminal does not
have any effect, the Terminal gives the answer "command not found".
Try
sudo /usr/texbin/texhash
The hint to use /usr/texbin/ before the TeX related command's name has
b
Am 28.08.2010 um 21:13 schrieb Mike Maxwell:
But what is this "command line template" the -D option wants?
See here: /usr/local/texlive/2010/texmf/dvipdfmx/dvipdfmx.cfg (or /usr/
local/texlive/2010/texmf-dist/doc/latex/cjk/doc/pdfhowto/examples/
dvipdfmx.cfg)!
--
Greetings
Pete
Rain i
Am 29.08.2010 um 18:17 schrieb Alan Munn:
Is there a way to check whether a font is present in a user's system?
Font Book?
Locate?
Find?
Lsbom?
Ftxinstalledfonts?
Fc-list or fc-match?
Spottlight?
--
Greetings
Pete
There is no worse tyranny than to force a man to pay for what he do
Am 30.08.2010 um 06:56 schrieb Wilfred van Rooijen:
In fact, I have had to copy some of the Adobe fonts to my
$HOME/.fonts to do some testing.
You can edit the file fonts.conf (for example in /etc/fonts or /usr/
X11/lib/X11/fontconfig) or ~/.fonts.conf, your personal copy that
fonts are
Am 31.08.2010 um 11:31 schrieb Marcin Grotomirski:
I want to set a different font for differnt environment.
Re-write these environments. The fontspec documentation shows how to
create a whole family of differently coloured fonts.
--
Greetings
Pete
What is this talk of 'release?' Klin
Am 01.09.2010 um 19:24 schrieb Marcin Grotomirski:
\renewcommand{\footnote}{{\addfontfeature{Color=66}}}
\footnote is no font specifier from the fontspec package, but a mighty
command from the article CLS file. So \addfontfeature{} won't work on
it.
You'll have to re-write a lot of
Am 01.09.2010 um 21:20 schrieb Marcin Grotomirski:
How do you create xetex documents that don't look like classic LaTeX
document.
Strong imagination, good plan, some endurance – and no Computer or
Latin Modern font.
--
Greetings
Pete
War springs from unseen and generally insignifica
Am 01.09.2010 um 22:28 schrieb Marcin Grotomirski:
I am asking about technical side of this process.
Reading? Programming a text and code or text only or code only
generator? Using GNU Emacs? Studying some art before starting?
--
Greetings
Pete
Sorry my terrible Eng
Am 05.09.2010 um 05:55 schrieb Mike Maxwell:
I'm trying out some fonts for the Dhivehi language, which has a
unique script.
Thaana, U+0780-U+07BF, can also be found in Code2000, FreeSerif, TITUS
Cyberbit.
The cause is that your code is faulty:
\newfontinstance\dhivehifontA{Mv Elaaf Nor
Am 16.09.2010 um 10:50 schrieb Pierre Morel:
What do you suggest for an elegant fix to this problem ?
Bibliography in English?
--
Greetings
Pete
(This space left blank for technical reasons.)
--
Subscriptions, Archive, an
Am 16.09.2010 um 11:22 schrieb Pierre Morel:
The problems arise when I cite a paper in the French text, such as
"french french french \citep{Author:year} french french french". I
could surround each \citep command by \selectlanguage{english}...
\selectlanguage{french}, but it's certainly no
Am 16.09.2010 um 15:44 schrieb Heiko Oberdiek:
* The only way I know is using
"xetex -no-pdf", followed by "xdvipdfmx -V ".
"xdvipdfmx --help" shows:
This is more efficient:
xetex -output-driver='xdvipdfmx -V '
The xdvipdfmx binaries in TL '09 and '10 pretest work fine... (even
Am 16.09.2010 um 19:56 schrieb David Cottenden:
Is it possible to set things up so that Greek appears in Minion and
Latin (and everything else) appears in Garamond?
See the XeTeX Companion here: http://xml.web.cern.ch/XML/lgc2/xetexmain.pdf
. \XeTeXinterchartoks allows to "bind" a particul
Am 16.09.2010 um 22:01 schrieb Heiko Oberdiek:
I thought you could simply edit dvipdfmx.cfg?
If I would have known it ;-)
I couldn't find any docu about it.
And this route is bug-free?
--
Mit friedvollen Grüßen
Pete
We are usually convinced more easily by reasons we have found
oursel
Am 19.09.2010 um 13:39 schrieb Manfred Lotz:
I tried it in TeXworks under Linux. For instance uktvaa in Devanagari
which has a ligature in it connecting k, t and v shows up correctly in
(out of the box) TeXworks. Both in gvim and emacs Devanagari will be
shown but not correctly (at least in cas
Am 19.09.2010 um 21:12 schrieb Manfred Lotz:
texworks isn't a text processor either and it works in texworks.
And how is the font you are using? Did you try the same font in GNU
Emacs and gvim? What are the results? Which tables/features of the
font get used?
--
Mit friedvollen Grüßen
Am 20.09.2010 um 16:42 schrieb Paolo Matteucci:
I’ve updated my TexLive distribution today, and started noticing
that, if you invoke the tipa package with xltxtra (and hence
fontspec and
xunicode) loaded, you get an extra trailing space just before the
end of the
\textipa environment.
Y
Am 20.09.2010 um 20:44 schrieb Gareth Hughes:
I'm asking for a more useful implementation that checks whether a
certain font is in use now
Wouldn't it be sufficient to check what \{rm,sf,tt}default are set to?
--
Greetings
Pete
When in doubt, use brute force.
Am 25.09.2010 um 18:44 schrieb Axel Kielhorn:
Some weeks ago I suggested getting information about XeTeX into
lshort.
Well, here is the first draft.
The correct Xe(La)TeX logos can be produced with metalogo or hologo
(HO = Heiko Oberdiek) packages. The logos in xltxtra, in fontspec v. 2
Am 26.09.2010 um 15:56 schrieb Axel Kielhorn:
I have to disagree, Vim and emacs (or should that be Emacs?) are
available on Windows as well. (Maybe not used that often.)
It's actually GNU Emacs and XEmacs. There are also specialised
variants, based on GNU Emacs, like NTEmacs, Carbon Emacs,
Am 26.09.2010 um 15:56 schrieb Axel Kielhorn:
GNU Emacs offers input methods. One of them, always available, is C-
q , and the number can be octal, decimal, or
hexadecimal.
You just have to memorize the Unicodecode:-)
You never were tortured by MS-DOS etc. with its Alt- to draw a
frame
Am 26.09.2010 um 19:33 schrieb Philip Taylor (Webmaster, Ret'd):
Many of us also use WinEDT, though its lack of support for Unicode
(even in its V6 guise, which some love and others hate) makes
it unsuitable as an editor for most Xe[La]TeX use.
Philip,
have you tried to use TPU-edt mode ins
Am 27.09.2010 um 22:44 schrieb Talal Al-Azem:
Could Khaled, Vafa, or anyone else perhaps inform me of what I need
to do in order to get an overline over RTL text, when that text runs
for more than a single line?
If no proper solution comes up: split the text, in a final step, in as
many
Am 27.09.2010 um 18:23 schrieb Andréa Loyer:
I am unable to use bold change size of the text as I did before in
the toc and section titles, use smallcaps and change colors...
Update once more and hope that fontspec 2.1a will come!
--
Greetings
Pete
A lot of people mistake a short memory
Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
Can we now come back to the beginning problem:
Which way of creating unicode-encoded .tex-documents to propose in
lshort?
Using GNU Emacs 23.x – the Unicode Emacs (and any of its variants) –
with its AUCTeX extension. One can either set all TE
Am 28.09.2010 um 22:44 schrieb Philipp Stephani:
Am 28.09.2010 um 21:16 schrieb Peter Dyballa:
Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
Can we now come back to the beginning problem:
Which way of creating unicode-encoded .tex-documents to propose in
lshort?
Using GNU Emacs 23.x
Am 29.09.2010 um 00:02 schrieb David J. Perry:
Windoof user have to be hardened by ugly UI.
What about "losedos"?
I am (mostly) a Windows user but am neither stupid nor a loser. All
OSs have their imperfections, people have different reasons for what
they use, so let's stay on task he
Am 29.09.2010 um 13:38 schrieb António Fernandes:
After updating unicode-math to the most recent version I'm
experiencing an unwanted behavior which seems to be related with the
keys "script-features" and "sscript-features".
António,
could you start to learn how to create a new thread? I
Am 29.09.2010 um 05:39 schrieb msk...@ansuz.sooke.bc.ca:
The two lines should be the same length, but they aren't.
I'm only testing with the TeX Live 2010 pretest release and I can see
that pdfLaTeX and LuaLaTeX produce correct output (two spaces) while
XeLaTeX with fontspec v. 1 fails.
Am 29.09.2010 um 23:40 schrieb Philipp Stephani:
reality is approximately as follows: Users who read beginner
documents such as lshort don't want to use TeX, but are forced to do
so by their advisor. They don't want to read discussions about the
pros and cons of various text editors or why
Am 30.09.2010 um 00:42 schrieb Alan Munn:
And I deal with a broad range of students at a major US research
university.
U.S. American students are not a gauge for Earth's youth. (Their
number is also too small.) And indeed I more often interact with much
younger people.
--
Greetings
Am 01.10.2010 um 15:55 schrieb Axel Kielhorn:
Do you have a guide that explains how to turn a pdflatex document
into a xelatex document?
Something like this preamble?
\documentclass[11pt,final]{article}
\usepackage{ifpdf,ifxetex}
\usepackage{graphicx} %[dvipdfmx]
\usepackage[nger
Am 02.10.2010 um 17:02 schrieb Drébon:
Now, I am just searching for a replacement police for helvet that
support smallcaps (and to understand what was I intending to do with
the problematic \renewcommand*\sfdefault{ugq})
This should not be too complicated...
\ifxetex
Am 03.10.2010 um 11:23 schrieb Drébon:
My current problem is that the Tex Gyre *** fonts have no small caps.
I think the PUA (Private Use Area) has some small glyphs (for whatever
use), even a lot accented ones. (Helvetica is a font without Small
Caps. By definition/character/look/visual
Am 05.10.2010 um 12:46 schrieb Dominik Wujastyk:
This is completely wrong, and anachronistic. SGML was born long
after TeX
and LaTeX.
You probably mean that ISO standard on SGML from 1986 (8879). There is
none for any TeX dialect...
William W. Tunnicliffe had the idea of SGML at least
Am 10.10.2010 um 22:26 schrieb David Perry:
he LaTeX command \fontsize{60}{66pt} does not work
Did you add \selectfont?
--
Greetings
Pete
What's the difference between OS X and Vista?
Microsoft employees are excited about OS X…
--
Sub
Am 10.10.2010 um 21:48 schrieb Vadim Radionov:
What can be done to investigate and fix it?
Instead of citing the whole old message it could have been interesting
to see the different sources which lead to so different outputs...
BTW, \listfiles can be a nice part of a preamble.
It also
Am 11.10.2010 um 00:29 schrieb Vadim Radionov:
\textsc{та}
Do Cyrillic small capital letters exist? I would have thought they're
typical Latin...
--
Greetings
Pete
It isn't pollution that's harming the environment. It's the impurities
in our air and water that are doing it.
---
Am 11.10.2010 um 00:29 schrieb Vadim Radionov:
I compiled the same source with 2 instances of xelatex, the one from
texlive 2010 works not as i expected
I don't have fontspec version 2.x around, but Will wrote that he
changed many things, in xltxtra as well. Could you compare the
definiti
Am 11.10.2010 um 05:10 schrieb Alan Munn:
Theoretically either argument could have any other kind of unit.
Right! It works well with mm or a mixture of units. TeX points are a
reliable fall-back default.
--
Greetings
Pete
One cannot live by television, video games, top ten CDs, and du
Am 12.10.2010 um 14:08 schrieb Vadim Radionov:
What could be the next step?
You could run pdffonts on the PDF files and invoke xdvipdfmx with more
verbosity/debug information. See 'xdvipdfmx --help'!
Vadim
PS. There's also strange difference in A4 paper size.
I presume that each sin
Am 12.10.2010 um 20:24 schrieb Khaled Hosny:
So \قسم, \अनुभाग, \אָפּטיילונג are fine,
too?
Is this really correct? I thought it should read قسم/,
अनुभाग/, אָפּטיילונג/...
--
Greetings
Pete
(This space left blank for technical reasons.)
-
Am 12.10.2010 um 14:30 schrieb Vadim Radionov:
xdvipdfmx -vv for both cases
Both logs look OK. You could avoid one annoyance, the use of cmr10, by
adding \pagestyle{empty} or
\thispagestyle{empty} that no page numbers or such are output.
IMO it looks like some bug somewhere. This could be
Am 12.10.2010 um 21:06 schrieb Steve Peter:
Nagari (the middle one) is read left-to-right.
Yes, I thought so, but I also thought it would be more funny when I
showed my complete ignorance...
--
Greetings
Pete
Isn't vi that text editor with two modes... one that beeps and one
that co
Am 12.10.2010 um 21:09 schrieb Vadim Radionov:
I did this and found nothing suspicious (logs attached), except for
TEXMFHOME which points to 2 directories (I used to think that setting
variable in texlive//texmf.cnf overrides
texlive//texmf/web2c/texmf.cnf, but their values both are use
Am 13.10.2010 um 14:41 schrieb Vadim Radionov:
It is stated in the second paragraph of
texlive/2010/texmf/web2c/texmf.cnf that any changes should be done in
texlive/2010/texmf.cnf. The output of xetex with -kpathsea-debug=3
show in my case
kdebug:hash_lookup(TEXMFHOME) => ~/texmf-texlive-2010
Am 14.10.2010 um 12:39 schrieb Keith J. Schultz:
This would be a good idea, but the original thought was also
for using localized units and such.
I don't think there are so many "localised" units at this size
(presumingly they start around 25 mm and reach a few km [Russian
Am 14.10.2010 um 13:48 schrieb William Adams:
(but still need to understand where I put the resulting .fmt file
and make it active)
FMT file is in /usr/local/texlive/2010/texmf-var/web2c/xetex. Because
XeTeX based.
Best is to edit fmtutil.cnf (/usr/local/texlive/2010/texmf-var/web2c/
fm
Am 14.10.2010 um 12:39 schrieb Keith J. Schultz:
the original thought was also for using localized units and such.
Thinking of this again, ex and em cannot be translated into Greek! Who
would now how wide a Latin x or m can span? And using ηξ and ημ
instead would make much difference beca
Am 14.10.2010 um 13:01 schrieb Marc van Dongen:
Any suggestions for solutions would be more than welcome.
Is your version of XeTeX HZ-enabled? If it is, you can achieve even
character protrusion – without the microtype package. It's specific
for pdfTeX.
See also here: http://xetex.tk/me
Am 17.10.2010 um 00:11 schrieb Roland Kuhn:
What's up?
In the TL '10 test distribution it was contained...
--
Mit friedvollen Grüßen
Pete
Seelsorge statt Krankenkasse: das ist neu und liberal, die wähl' ich!
--
Subscriptions, Archive, a
Am 17.10.2010 um 10:09 schrieb Roland Kuhn:
BTW: does anyone know a “terminal” which can use proportional fonts?
That would be a nice compromise between Turing-complete language and
intra-paragraph-WYSIWYG (I’m sorry to say that I’m basically married
to vim).
Xterm, uxterm, ...
--
Mit
Am 17.10.2010 um 11:22 schrieb Roland Kuhn:
Well, konsole can do that, too, but all of them (AFAIK) put each
nice and variable-width glyph at their assumed monospace location,
which is the worst possible solution to my mind (and eyes).
GNU Emacs has an ANSI compliant terminal emulation. Mo
Am 17.10.2010 um 23:34 schrieb Arthur Reutenauer:
But the overwhelming majority of users still type in the ASCII quote
sign and this situation has to be taken in account
They're presumingly pdfTeX users. With LuaTeX and XeTeX, and that's
probably the target of UTF-8 based hyphenation files
Am 18.10.2010 um 15:53 schrieb Apostolos Syropoulos:
Use
http://www.ctan.org/tex-archive/fonts/umtypewriter/
Instead of the real (old) Computer Modern fonts it's also possible to
use Latin Modern, its successor. Another option is to use the TeX Gyre
fonts (Curso is Courier), which at lea
Am 21.10.2010 um 17:45 schrieb Philip Taylor (Webmaster, Ret'd):
A document written in code page X could not
be differentiated from a document written in
code page Y as far as I know, whereas in my
putative "Omni-code [tm]" the code page would
be implicit in the encoding of each character.
T
Am 21.10.2010 um 19:20 schrieb William Adams:
Is there something else I should try?
Look here? /usr/local/texlive/2010/texmf-dist/tex/latex/latexconfig/
xelatex.ini
--
Mit friedvollen Grüßen
Pete
Well begun is half done.
– Optimist.
Half done is well begun.
Am 23.10.2010 um 06:22 schrieb Kamal Abdali:
I would like to try persian.xdy, but can't find
it. On my updated TeXLIve2010/MacTeX, it is neither in xepersian
files nor
in xindy files.
In Tex Live 2008 and 2009 the file existed: /usr/local/texlive/200[89]/
texmf-dist/doc/xelatex/xepersian
Am 23.10.2010 um 10:53 schrieb André Bellaïche:
1. Is it possible to replace unicode by applemac encoding? What are
the commands in this case?
If you want to continue typing in applemac input encoding you better
stay with the much more developed pdfTeX. All packages work with
pdfTeX, an
Am 23.10.2010 um 11:46 schrieb André Bellaïche:
Yes, but it does not seem that the Postscript name is the one you
type in the command \setromanfont.
The family name should be OK since it does not restrict the font to
one variant (roman, italic, bold, a mixture). Look into Font Book
(Livr
Am 23.10.2010 um 18:14 schrieb Ulrike Fischer:
So why not tell them that there is a choice?
Because you need to record each file's particular encoding in order to
share its contents with other users – or editors/TeX front-ends/TeX
engines.
--
Mit friedvollen Grüßen
Pete
There's no
Am 23.10.2010 um 17:30 schrieb Ulrike Fischer:
Am Sat, 23 Oct 2010 11:27:46 +0200 schrieb Peter Dyballa:
1. Is it possible to replace unicode by applemac encoding? What are
the commands in this case?
If you want to continue typing in applemac input encoding you better
stay with the much
Am 25.10.2010 um 13:13 schrieb Pander:
Regular, bold, italic and bold italic offered by the 4 Vollkorn OTF
files do work in OpenOffice 3.2.1.
Fc-cat lists a TrueType font file...
The fontspec documentation describes how to set up a "font family"
from individual files or variants. Maybe it
Am 25.10.2010 um 13:06 schrieb Vafa Khalighi:
Is there a way to recover this tex file?
I know only one useful algorithm for these more than 128 K ASCII NUL
characters: convert them all to one. Or none. Which is better. Because
then no backup programme would try to save this useless and e
Am 25.10.2010 um 17:17 schrieb Pander:
Fc-cat lists a TrueType font file...
Get the newer OTF files from the link in the initial post.
Honestly, me, I don't want these files. But maybe you want to clean
your system from having more than one version of the font.
The fontspec documenta
Am 26.10.2010 um 16:19 schrieb Pander:
Now that this is reproducable on both Linux and OSX, what is the
next step
to take to solve this?
Ask the fonts creator.
Ask an independent fonts expert.
Try to "repair" it in FontForge and save it with modified font names.
Then include the set in
Am 26.10.2010 um 16:22 schrieb Pander:
Is it possible to have more information printed to command line and
log
file for where this error originates?
Invoke xdvipdfmx with -v or -vv or -vvv or ... or invoke xelatex as
"xelatex -output-driver='xdvipdfmx -vv'" etc.
You could also invest a
Am 26.10.2010 um 18:57 schrieb Pander:
It would be nice to also print the name of the font so the searching
is
easier.
You can always construct a minimal example with not more than one font
used (well, I do can). And you can always ask XeTeX to trace the fonts
it uses. And you can also
Am 27.10.2010 um 01:27 schrieb houda araj:
When I put HUGE in front of
\HUGE{این اولین نمایه این متن است که برای
امتحان آورده شده است} .
xelatex does not recognize it.
Since \HUGE is defined only rarely you can use NFSS2 (New Font
Selection Scheme) to set a font's size:
\fontsi
Am 29.10.2010 um 18:30 schrieb André Bellaïche:
Is this normal?
Yes. With
%%!TEX encoding = UTF-8 Unicode
you tell TeXShop how the file's encoding is. The preference you set is
just a default for *new* files or for old files *without* that
encoding declaration. This declaration
Am 29.10.2010 um 23:51 schrieb André Bellaïche:
I have looked into changebar.sty, and it does not seems to be easy
to replace the Postscript commands by a simple command drawing an
hrule or a vrule.
André,
if you need to compare two XeLaTeX files, then you don't need the
fancy XeLaTeX
Am 30.10.2010 um 12:38 schrieb André Bellaïche:
I have also find a `frutiger' package for LaTeX:
http://www.ctan.org/tex-archive/fonts/truetypemetrics/frutiger/
Get the archive and unzip it for example somewhere in /tmp. Change
directory (cd, pushd) on the command line into that directory.
Am 30.10.2010 um 17:42 schrieb Peter Dyballa:
Get the archive and unzip it for example somewhere in /tmp.
Actually I think it's much easier to save the archive somewhere, say,
in the download folder or in /tmp, and then to cd to /usr/local/
texlive/texmf-local. There, on the command
Am 31.10.2010 um 19:14 schrieb Pierre Morel:
And this only for the font for which margin kerning is activated.
Try another font! Maybe your font has a substitution table active. For
a try you could use Latin Modern.
Another option is to invoke xelatex like this:
xelatex -output-
Am 01.11.2010 um 10:46 schrieb Pierre Morel:
Package hyperref Warning: Token not allowed in a PDF string (Unicode):
Could be it helps to load hyperref with the unicode option...
--
Greetings
Pete
Well done is better than well said.
– Benjamin Franklin
Am 06.11.2010 um 20:08 schrieb BPJ:
Is it an optical illusion, or is the size of \textsuperscript and
\textsubscript rather like \tiny than like \scriptsize?
Sometimes is neither this nor that but a decision of the font designer
– some fonts have subscript and superscript glyphs!
--
Gree
Am 10.11.2010 um 13:10 schrieb John Was:
--papersize=a5
I wouldn't use this command line option. I'd use a
\special{papersize=...} which also records these dimensions in the XDV
output file, helping xdvipdfmx to choose the proper paper format.
--
Greetings
Pete
No project was ever c
Am 10.11.2010 um 15:45 schrieb Kai Hendry:
No file letter.aux.
[1
! I can't write on file `letter.pdf'.
(Press Enter to retry, or Control-D to exit; default file extension
is `.pdf')
Please type another file name for output:
! Emergency stop.
\endgroup \...@typeset@protect
It looks OK... no further guess yet! Maybe the webconverger runs on
its platform, the host, with its identity while on the other systems
it is *your* guest with *your* permissions...
--
Greetings
Pete
If it does exist, it's out of date.
– Arnold's Second
Am 11.11.2010 um 00:25 schrieb Wilfred van Rooijen:
Although I may not really understand the question, if you take a
look at the manual of the memoir class, it is precisely explained
how (La)TeX treats the page size. Also, the geometry package lets
you select any page size you want.
Wil
Am 10.11.2010 um 22:33 schrieb Ross Moore:
On 11/11/2010, at 3:10 AM, Peter Dyballa wrote:
It looks OK... no further guess yet! Maybe the webconverger runs on
its platform, the host, with its identity while on the other
systems it is *your* guest with *your* permissions...
Yes, that
Am 11.11.2010 um 12:53 schrieb Kai Hendry:
I've spent hours debugging it.
Did you ever compare the two LOG files, that from the client with that
from the server?
--
Greetings
Pete <\
_\ O _
|o \ _\\_/-\='
_(_)|-(_) (_)__
Am 11.11.2010 um 11:24 schrieb Christian Schmidt:
I don't know how to use the \listfiles command
Just put it into the preamble, just like setting the page style to
empty, or defining some new macro or command.
--
Mit friedvollen Grüßen
Pete
There are two major products that come out o
Am 17.11.2010 um 21:19 schrieb Pander:
XeLaTeX has a problem with Delicious font
This cannot be true, because there are two of them: Mac (Type1) and PC
(OpenType). Which one did you download? And how did you install it?
--
Greetings
Pete
The future will be much better tomorrow.
Am 19.11.2010 um 01:39 schrieb Pander:
I simply put them somewhere fontconfig is finding them.
This is not sufficient. You need to update fontconfig's caches. The
command is: fc-cache. LuaTeX has its own font mechanisms and
automatisms, which might explain your observations.
--
Greetin
Am 17.11.2010 um 21:19 schrieb Pander:
XeLaTeX has a problem with Delicious font
Which I can easily share! The Small Caps variant has these glyphs
where usually the standard glyphs are! Quite unconventional...
These fonts contain just 220 glyphs. They're too problematic to keep
them – I
Am 17.11.2010 um 21:19 schrieb Pander:
XeLaTeX has a problem with Delicious font
Just as Herb I can't reproduce your problem. Maybe I was doing things
incorrectly, since I first installed the the traditional font variants
and added then the heavy and small caps variants, the only thing I
Am 20.11.2010 um 12:07 schrieb Jean-Claude Raoult:
I am not fond of diving into metafont.
John already mentioned that some automatic ligatures are activated by
using the tex-text mapping when loading the font. The fonts XeTeX uses
are better not METAFONT based! These simple fonts have no
Am 20.11.2010 um 12:07 schrieb Jean-Claude Raoult:
and what about st and ct
In case they exist in some fonts you could make them available when
loading any of these fonts with special options. Here are some:
+smcp = small caps
+liga = common ligatures (on by default for L
Am 20.11.2010 um 16:35 schrieb Takayuki YATO (ZR):
I understand your explanation and admit it's logical. But from the
grammar of XeTeX I have the impression that XeTeX treats a font with
some feature enabled as different from the original font; that is,
there are two distinct fonts \tgpNorm and
Am 20.11.2010 um 23:29 schrieb Petr Tomasek:
Is there anything that can be done?
Define these variable types in some C header file!
You can look into Fedora 14's installed C header files and check
whether such type names are used there.
"char16_t" obviously is a 16 bit signed "wide" cha
Am 20.11.2010 um 22:24 schrieb A u:
now I have a question can I change the thickness of
line that gets created using \xrightarrow{}
Use a completely different font, use an artificially emboldened font.
--
Mit friedvollen Grüßen
Pete
Almost anything is easier to get into than out of.
Am 22.11.2010 um 15:40 schrieb Alexander:
After upgrade to TL 2010 these commands not work.
I see in my console log:
(/usr/local/texlive/2010/texmf-dist/tex/xelatex/polyglossia/gloss-
russian.ldf
Package polyglossia Warning: No hyphenation patterns were loaded for
`Russian'
(
Am 22.11.2010 um 17:33 schrieb Petr Tomasek:
I'll see when I'll have time to dig more deeply in
Maybe it's best to start with the configure step. You have it's output
in one window and in other windows you can examine the configure shell
scripts and their LOG files. Commonly configure sh
Am 22.11.2010 um 18:19 schrieb Petr Tomasek:
Even though there is a libicu available on both F12 and F14
I would bet XeTeX uses it's own ICU copy. (It did compile one
at least. And on the F14 the libicu-devel package was not
installed first, but even if I installed it, nothing changed with
the
Am 23.11.2010 um 04:32 schrieb Vladimir Lomov:
P.S. Something wrong with your TL setup because here I could compile
the file without such messages. May be you switch off support for some
languages?
Yes, that's true! I did not think of this and assumed a failure in
polyglossia...
--
Greet
Am 24.11.2010 um 10:23 schrieb Ulrike Fischer:
Perhaps you should at first try simply to update the microtype
package to the beta version:
http://xetex.tk/mediawiki/index.php/Microtype_package_(preliminary_version)
Exactly this is necessary to become able to use micro-typography with
XeTeX
101 - 200 of 589 matches
Mail list logo