Hi all:
If I compile this file:
\documentclass{article}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
$2×2±2$
\end{document}
all goes well; the result is a document which contains 2×2±2. However,
if I add the line
\usepackage[utopia]{mathdesign}
before
Excellent - does this mean that custom kerning from within XeTeX is moving
up the 'to-do' list? It seems to me to be in the same general area
(aesthetically though perhaps not technically): one wants to fine-tune the
spacing behaviour of specific characters from within the program rather
On 5/3/2010 2:00 AM, John Was wrote:
Excellent - does this mean that custom kerning from within XeTeX is
moving up the 'to-do' list? It seems to me to be in the same
general area (aesthetically though perhaps not technically): one
wants to fine-tune the spacing behaviour of specific
Hi all,
If I compile this file:
\documentclass{article}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
\'n
\end{document}
then I get a PDF file which, besides the page number, only contains the
diacritic «ń». That's what I would expect.
However, if I add
On Sat, May 1, 2010 at 12:01 PM, Michiel Kamermans
po...@nihongoresources.com wrote:
Ulrike,
Well most of the graphics on my pc have either no dpi entry or 72,
but I found one with 300dpi and this too is larger (x4) when used
with xelatex. (it is not a graphic I can share so we can't test if
Now, I am not surprised by the fact that that specific font doesn't have
that specific character, but shouldn't it be able to create one just by
putting an acute accent over the letter _n_?
The problem you have here is the result of xunicode's action: it
explicitely replaces the sequence
2010/5/3 Barry MacKichan barry.mackic...@mackichan.com:
Now that that has sunk in ;-) can I ask about the other feature of
PDFTeX, namely the ability to improve line breaking by (to my eye)
undetectable changes in the font size for a paragraph? Is there any plan
to port this to XeTeX?
IMHO
On 03-05-2010 11:35, Arthur Reutenauer wrote:
Now, I am not surprised by the fact that that specific font doesn't have
that specific character, but shouldn't it be able to create one just by
putting an acute accent over the letter _n_?
The problem you have here is the result of xunicode's
Hi,
The ICU library included in texlive 2010 is of version 4.4,
which seems to have a bug compared to that of texlive 2009.
For instance,
\font\juni=[Junicode-Regular]:+calt at 24pt \juni
fīð% f, imacron, eth
\bye
with this tex file, I get different result from between tl2009 and tl2010.
On 5/3/2010 4:02 AM, José Carlos Santos wrote:
Then I will have to work without the xunicode and xltxtra packages. I
hope that that will not create new problems.
You could, but what's stopping you from using the actual letter ń?
Incidentally, you only have to load the xltxtra package, not
On Sun, May 02, 2010 at 10:06:31PM -0400, David J. Perry wrote:
Jonathan,
This is great news--thank you! There is also an OpenType feature
called Optical Bounds that is designed to do exactly this. My
understanding is that very few, if any, page layout programs support
this feature.
Am Mon, 03 May 2010 11:26:32 +0100 schrieb José Carlos Santos:
Hi all,
If I compile this file:
\documentclass{article}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
\'n
\end{document}
then I get a PDF file which, besides the page number, only
On 03-05-2010 12:45, Michiel Kamermans wrote:
Then I will have to work without the xunicode and xltxtra packages. I
hope that that will not create new problems.
You could, but what's stopping you from using the actual letter ń?
Within the tex file? Because I don't know how to get it from
I got the microtype version of xetex, and the build process seemed to go well
until the very last few lines. Is this a fatal error? If so, how do I fix it?
%%==%%
sers/sgm/xetex/texk/web2c/xetexdir/XeTeXLayoutInterface.cpp:867: error:
‘ATSUGetAttribute’ was not declared in this scope
On 03-05-2010 13:24, Ulrike Fischer wrote:
If I compile this file:
\documentclass{article}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
\'n
\end{document}
then I get a PDF file which, besides the page number, only contains the
diacritic «ń». That's what I
I would love to try this out, but i work using miktex2.8 on a windows 7(64)
where are instructions how to compile this (or even better download a build)
on the MS platform ?
Avi
On Mon, May 3, 2010 at 2:12 AM, Jonathan Kew jonat...@jfkew.plus.comwrote:
For those who like to live on the
On 03-05-2010 13:40, Ulrike Fischer wrote:
If I compile this file:
\documentclass{article}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
$2×2±2$
\end{document}
all goes well; the result is a document which contains 2×2±2. However,
if I add the line
On 3 May 2010, at 13:47, Stephen Moye wrote:
I got the microtype version of xetex, and the build process seemed to go well
until the very last few lines. Is this a fatal error?
Well, it prevented the compilation finishing, so you got no binary that
seems fairly fatal! :)
If so, how do
José Carlos Santos wrote:
Thanks, but that does not work. What I get is just the letter n.
Besides, the log file then says Missing character: There is no ́ in
font DTL Unico ST/ICU:mapping=tex-text,!
Hi José:
Maybe you could use a font like DTL Unico (I don't have it here) that
/does/
Am Mon, 03 May 2010 13:48:50 +0100 schrieb José Carlos Santos:
On 03-05-2010 13:24, Ulrike Fischer wrote:
If I compile this file:
\documentclass{article}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
\'n
\end{document}
then I get a PDF file which,
That worked. Thank you. However it has been some time since I built and
installed xetex from source. My notes say that the final step is to run sudo
./install-xetex but there is no file install-xetex. What do i do now?
Stephen
On May 3, 2010, at 9:02 AM, Jonathan Kew wrote:
On 3 May 2010,
That won't help sometimes: Word unhelpfully substitutes unavailable
characters from some font which does include it, without warning.
On 3 May 2010 23:18, Ulrike Fischer ne...@nililand.de wrote:
Are you able to get the accent in this font e.g. in Word or a
similar application?
On 03-05-2010 14:48, Ulrike Fischer wrote:
Try this (I can't test as I don't have your font):
\documentclass{article}
\usepackage{xltxtra}
\setmainfont[Mapping=tex-text]{DTLUnicoST}
\UndeclareUTFcomposite[\UTFencname]{x0144}{\'}{n}
\begin{document}
\'n
\end{document}
Thanks, but that does
Am Mon, 03 May 2010 15:32:27 +0100 schrieb José Carlos Santos:
Are you able to get the accent in this font e.g. in Word or a
similar application?
No. I tried it with Word and also with Wordpad, but all I got was ´n.
But you get an accent. The main questions are is this accent in the
font,
Actually, I have just found a older xetex source directory that has the
install-xetex and rebuild-formats. The rebuild-xetex script looks ok as-is. I
**think** the only change necessary for the install-xetex script would be to
change references to the Work directory to the build-xetex
Am 03.05.2010 um 16:43 schrieb Ulrike Fischer:
Am Mon, 03 May 2010 15:32:27 +0100 schrieb José Carlos Santos:
Are you able to get the accent in this font e.g. in Word or a
similar application?
No. I tried it with Word and also with Wordpad, but all I got was ´n.
But you get an accent.
Success -- everything is working perfectly. Many thanks. Now I just
have to be patient whilst microtype and friends are updated.
SGM
Sent from my iPhone
On May 3, 2010, at 10:49 AM, Jonathan Kew jfkth...@googlemail.com
wrote:
On 3 May 2010, at 14:56, Stephen Moye wrote:
That worked.
You can find all the characters included in a font in the «character map».
In Linux, type in the terminal 'charmap'. If you are in Windows, I think it
is in 'Accesories→System Tools→Character Map'. In the character map you can
find precombined characters and combinable diacritical marks.
If you
This is the same kind of issue as one of the earlier ones: the whole
point of XeTeX is that one simply types what one wants into a Unicode
editor (i.e., if you want an em-dash, you simply type an em-dash, and
there is no need any more for TeX conventions like ---, \a, etc. etc.).
Even if
José Carlos Santos wrote:
I repeat: if I compile this file:
\documentclass{article}
\usepackage{xltxtra}
\setmainfont[Mapping=tex-text]{DTLUnicoST}
\begin{document}
ń
\end{document}
I get nothing.
Hi José:
Try this:
\documentclass{article}
\usepackage{xltxtra}
On 03-05-2010 22:43, Fr. Michael Gilmary wrote:
I repeat: if I compile this file:
\documentclass{article}
\usepackage{xltxtra}
\setmainfont[Mapping=tex-text]{DTLUnicoST}
\begin{document}
ń
\end{document}
I get nothing.
Try this:
\documentclass{article}
\usepackage{xltxtra}
On 03-05-2010 22:41, Ross Moore wrote:
Thanks. Now I know that, yes, DTLUnicoST has an acute accent; its
position is 0301.
But I think that in TeX, LaTeX, XeTeX this shouldn't be a problem if you
are using this
|[Mapping=tex-text]
But I am using it. I repeat: if I compile this file:
Hi Jonathan,
On Mon, May 3, 2010 at 9:02 PM, Jonathan Kew jfkth...@googlemail.com wrote:
I'm guessing that you're building on a Snow Leopard system, and so the Apple
tools are defaulting to a 64-bit build, which is not supported for xetex on
OS X.
If that's the case, try the following:
33 matches
Mail list logo
