On Dec 6, 2007 5:09 PM, Steffen Wolfrum wrote:
Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
The general approach would be something like:
\definefontfeature[mine][smcp=yes]
\definefontsynonym[a][name:Warnock Pro][features=mine]
\showfont[a]
(grep the sources for
I ran sudo ctxtools --updatecontext about one hour ago and all this
that you write here can't be found (s-pre-63.tex is the latest) ...
Where did you mean should I grep the sources for definefontfeature ??
Steffen
Am 06.12.2007 um 17:35 schrieb Mojca Miklavec:
On Dec 6, 2007 5:09 PM,
\setfontfeature
{disableoldstyle} 789
\stoptext
you mean typeset with Lua, right? with XeTeX it yields
! Undefined control sequence.
l.20 \setfontfeature!
This is a new feature introduced only for LuaTeX, not XeTeX
and allows you to choose a different fontfeature in your document.
Could be used
2007/12/6, Mojca Miklavec [EMAIL PROTECTED]:
On Dec 6, 2007 5:09 PM, Steffen Wolfrum wrote:
Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
The general approach would be something like:
\definefontfeature[mine][smcp=yes]
\definefontsynonym[a][name:Warnock Pro][features=mine]
Wolfgang Schuster wrote:
2007/12/6, Mojca Miklavec [EMAIL PROTECTED]:
On Dec 6, 2007 5:09 PM, Steffen Wolfrum wrote:
Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
The general approach would be something like:
\definefontfeature[mine][smcp=yes]
\definefontsynonym[a][name:Warnock
{disableoldstyle} 789
\stoptext
you mean typeset with Lua, right? with XeTeX it yields
! Undefined control sequence.
l.20 \setfontfeature!
This is a new feature introduced only for LuaTeX, not XeTeX
and allows you to choose a different fontfeature in your document.
Could be used
Am 06.12.2007 um 18:55 schrieb Hans Hagen:
something like that ...
keep in mind that you don't need to define a font then,
{\setfontfeature{smallcaps}Some Text}
will automatically give you that featureset so in practice we can do
with only a few real font definitions; mkiv keeps track of
Steffen Wolfrum wrote:
Am 06.12.2007 um 18:55 schrieb Hans Hagen:
something like that ...
keep in mind that you don't need to define a font then,
{\setfontfeature{smallcaps}Some Text}
will automatically give you that featureset so in practice we can do
with only a few real font
:50:01 MEZ
An: Unicode-based TeX for Mac OS X and other platforms [EMAIL PROTECTED]
Betreff: Re: [XeTeX] Redefining the footnotes in XeTeX
Antwort an: Unicode-based TeX for Mac OS X and other platforms
[EMAIL PROTECTED]
On 21/11/2007, at 1:02 AM, Brian Anderson wrote:
I'd like to find a way
Steffen Wolfrum wrote:
BTW: are the benefit's of David's work also available for ConTeXters?
i've never looked into it, but because latex and context are set up
completely different it probably would mean more refactoring than i'm
willing to do
concerning multiple footnotes, it's been there
to do
concerning multiple footnotes, it's been there for a while
What Brian, starting that thread on XeTeX-list, ment was this:
Am 20.11.2007 um 15:32 schrieb Brian Anderson:
What I'm trying to do is change the footnotes at the bottom of the
page from this:
1) first note
2) second note
Steffen Wolfrum wrote:
Hans, can you build a routine upon this for ConTeXt?
(Just in case it's not too weird!!!)
not today -)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat
with every option you need.
Thank you VERY much Mojca and Wolfgang! With XeTeX now I can use the
oldstyle numerals with my system-installed OpenType fonts. :-) I'm
very, very happy with that. I really thought I had to wait for LuaTeX
for that.
Now, to push the features topic further on, before
On Nov 10, 2007 9:23 PM, Mojca Miklavec [EMAIL PROTECTED] wrote:
You can say (features=default is optional)
\definefontsynonym[SomeFont][name:Font Name][features=default]
which means that XeTeX will call the font
\font\somefont=FontName;mapping=tex-text,... (tex-text is
implied
On Nov 12, 2007 4:12 PM, Jeff Smith wrote:
On Nov 10, 2007 9:23 PM, Mojca Miklavec wrote:
You can say (features=default is optional)
\definefontsynonym[SomeFont][name:Font Name][features=default]
which means that XeTeX will call the font
\font\somefont=FontName;mapping=tex-text
2007/11/12, Jeff Smith [EMAIL PROTECTED]:
On Nov 10, 2007 9:23 PM, Mojca Miklavec [EMAIL PROTECTED] wrote:
You can say (features=default is optional)
\definefontsynonym[SomeFont][name:Font Name][features=default]
which means that XeTeX will call the font
\font\somefont=FontName
and Wolfgang! With XeTeX now I can use the
oldstyle numerals with my system-installed OpenType fonts. :-) I'm
very, very happy with that. I really thought I had to wait for LuaTeX
for that.
Now, to push the features topic further on, before experimenting a bit
I'd like to ask... does XeTeX support
Am 05.11.2007 um 09:30 schrieb Dalyoung Jeong:
Mon Nov 5 16:56:15 graph.ssu.ac.kr xdv2pdf[21489] Error:
WARNING: Type1 font data returned by OFAStreamPSDownload isn't in
the correct format required by the Adobe Type 1Font Format
specification.
...
Output written on test-font.pdf (1
To all XeTeX enthusiasts,
I have just figured out (after Jonathan's post on the XeTeX mailing
list) that the new XeTeX supports some interesting features. You can
check it out (it might be that it only works with ConTeXt 2007.09.28
and XeTeX 0.997):
\definefontfeature
[slantedandextended
Dear all MikTeX fans,
Just to let you know: MikTeX 2.7 beta 3 should work OK with ConTeXt
XeTeX (with yesterday's ConTeXt update).
I have experienced some problems with fontconfig admin rights, but
in general it could or should be OK (I didn't try the very latest
version). If you experience
(Thanks Hans)
On 15 Sep 2007, at 18:43, Hans Hagen wrote:
Andrea Valle wrote:
\enableregime[utf]
this one is not needed, xetex is utf
Ok. I read some infos on the wiki but I was a bit confused.
So:
- if I encode in utf-8 I don't have to specify regime \enableregime[utf]
- if I encode
I was happy with old install, with bugs and xetex low level commands :-)
So, er, which strategy you gurus suggest?
Reinstall from scratch (old) TeXLive 2007 waiting for a new release?
I have that project of typesetting our journal which will start in a
month.
(I'd like to use system fonts
On 9/16/07, Andrea Valle wrote:
On 15 Sep 2007, at 18:43, Hans Hagen wrote:
\enableregime[utf]
this one is not needed, xetex is utf
Ok. I read some infos on the wiki but I was a bit confused.
So:
- if I encode in utf-8 I don't have to specify regime \enableregime[utf]
- if I encode
On 9/16/07, Andrea Valle wrote:
I was happy with old install, with bugs and xetex low level commands :-)
So, er, which strategy you gurus suggest?
Reinstall from scratch (old) TeXLive 2007 waiting for a new release?
That's one possibility, of course.
You can also download any ConTeXt
Really thanks a lot Mojca for the help.
I replaced the two files, I found two copies of font-ini.tex and
replaced them all.
Then:
texexec --make --all
texexec --make --all --xetex
(I guess the first is useless if I execute the second, isn't it?)
YES!
Alleluja, alleluja, it works
On 9/16/07, Andrea Valle wrote:
Then:
texexec --make --all
texexec --make --all --xetex
(I guess the first is useless if I execute the second, isn't it?)
You need the first one for pdfTeX and the second one for XeTeX. (If
you only work with XeTeX, then you don't need the first one
Andrea Valle wrote:
(Thanks Hans)
On 15 Sep 2007, at 18:43, Hans Hagen wrote:
Andrea Valle wrote:
\enableregime[utf]
this one is not needed, xetex is utf
Ok. I read some infos on the wiki but I was a bit confused.
So:
- if I encode in utf-8 I don't have to specify regime
Mojca Miklavec wrote:
Another possibility would be to use LuaTeX. It should work OK, but
again, there is no 100% guarantee (I created some newspaper with it
back in June and besides all the problems I had every now and then, it
was pre-alpha after all, our color laser at university still
Andrea Valle wrote:
Thanks Hans
texexec --xetex myfile.tex
is broken too:
** WARNING ** Invalid CMap
** ERROR ** pdf_ref_obj(): passed invalid object.
(what's the difference between --xtx and --xetex?)
depends on theversion of texexec; nowadays we always use dvipdfmx so
' licensed
font **
]
** WARNING ** Invalid CMap
** ERROR ** pdf_ref_obj(): passed invalid object.
(I take care of removing other aux files)
-a-
On 15 Sep 2007, at 13:25, Hans Hagen wrote:
Andrea Valle wrote:
Thanks Hans
texexec --xetex myfile.tex
is broken too:
** WARNING ** Invalid CMap
Andrea Valle wrote:
\enableregime[utf]
this one is not needed, xetex is utf
\starttext
\startitemize
\item nome dell'insegnamento (es. $\to$ Storia del cinema)
\item settore scientifico-disciplinare (SSD, es. $\to$ l-art/06)
\item numero di crediti (cfu, es. $\to$ 10)
\stopitemize
La
for the default LM) is that
font loading in ConTeXt+XeTeX now does the following:
if (FontName is a valid font) then
use FontName
else
use [FontName]
end
And that one forgets the third possibility: about the old tfm fonts
which should be loaded without any quotes, for example rm-lmr12
\font
Mojca Miklavec wrote:
PS: to be honest, I'm still using the XeTeX version from TeXLive 2007
which is a bit old. I remember that Jonathan has promissed to look
into the problem described above some time ago (\font\a=rm-lmr12 vs.
\font\a=rm-lmr12 at 12pt), but I have no idea about what has
(besides being quite slow for the default LM) is that
font loading in ConTeXt+XeTeX now does the following:
if (FontName is a valid font) then
use FontName
else
use [FontName]
end
And that one forgets the third possibility: about the old tfm fonts
which should be loaded without
Thanks Mojca,
Yes, having the standard mactex I had an old ConTeXt version.
On 13 Sep 2007, at 14:47, Mojca Miklavec wrote:
ctxtools --updatecontext
Done it. Now I'm using:
texexec --version
TeXExec | version 6.2.0 - 1997-2006
texec --check
2007.09.13 21:15
I've made also:
texexec
FilesVersion: 2007.09.13 21:15
?
Many thanks
Hi Andrea,
you have to generate extra formats for XeTeX, you should type
texexec --make --all --xetex before you can run ConTeXt.
Wolfgang
___
If your question
need to apologise for blaming ConTeXt for wrong stretching of
included figures (I had some problems with figures in XeTeX in ConTeXt
already before, so I falsely assumed that it was yet another one in
the series). It turned out it has been a XeTeX bug, which popped up
only for some very specific
the base files!
FormatVersion : 2007.01.12 15:56 MKII
FilesVersion: 2007.09.13 21:15
?
also run
texexec --make --xetex --all
Best wishes,
Taco
___
If your question is of interest to others as well
On 14 Sep 2007, at 11:45, Mojca Miklavec wrote:
Great! Do you still experience any speed problems now? (I have a
feeling that Hans has removed dependency on ImageMagic, but I didn't
try to uninstall it to check if that was true.)
(I'm surely having ImageMagick in my path, don't kwon if it's a
/local/texlive/2007/../texmf-local/tex/context/base/cont-new.tex
FatalError : Your format does not match the base files!
FormatVersion : 2007.01.12 15:56 MKII
FilesVersion: 2007.09.13 21:15
?
also run
texexec --make --xetex --all
Best wishes,
Taco
Hmmm,
after updating I'm able to solve problems related to figures in XeTeX.
In any case, my graphical project (involving jpgs and pdf inclusion,
also in alyers) does not compile anymore.
I'm having this
** WARNING ** Invalid CMap
** ERROR ** pdf_ref_obj(): passed invalid object.
Output
Le 14 septembre à 11:51:43 Andrea Valle [EMAIL PROTECTED] écrit notamment:
| I'm having this
| ** WARNING ** Invalid CMap
| ** ERROR ** pdf_ref_obj(): passed invalid object.
I had the same until I updated metapost to version 1.000 and regenerated
some formats (metafun). Now it has disappeared
Many thanks
and how do I update Metapost?
I supposed that
ctxtools --updatecontext
would have update all
Best
-a-
On 14 Sep 2007, at 15:36, Jean Magnan de Bornier wrote:
Le 14 septembre à 11:51:43 Andrea Valle [EMAIL PROTECTED] écrit
notamment:
| I'm having this
| ** WARNING **
Andrea Valle wrote:
Many thanks
and how do I update Metapost?
I supposed that
ctxtools --updatecontext
would have update all
this only updates the context files (tex, mp, etc) not binaries
(soon it will be possible to do this from the garden)
Hans
Andrea Valle wrote:
Thanks Hans,
So, how can I update binaries?
depends on the platform ... debian ships intermediate updates, at
akira's site there are fresh win binaries, osx distributions have good
updaters, and for luatex there is luatex.org and fabrice's gforge repos
Hans
Thanks Hans,
So, how can I update binaries?
Best
-a-
On 14 Sep 2007, at 15:59, Hans Hagen wrote:
Andrea Valle wrote:
Many thanks
and how do I update Metapost?
I supposed that
ctxtools --updatecontext
would have update all
this only updates the context files (tex, mp, etc) not binaries
Le 14 septembre à 15:46:05 Andrea Valle [EMAIL PROTECTED] écrit notamment:
| Many thanks
| and how do I update Metapost?
| I supposed that
| ctxtools --updatecontext
| would have update all
| Best
Here:
http://foundry.supelec.fr/frs/?group_id=13release_id=224
--
Jean
Brief investigation and summary:
After
1. updating with macTeX package on macOSX 10.4.9
2. even if I have update ConTeXt and regenerate formats (all, also
with xetex)
my normal ConTeXt (texexec) is ok, my XeConTeX (texexec --xtx) is
broken
This is a test code (saved as utf-8
, then I did
texexec --make --all
texexec --make --all --xetex
ConTeXt works but it doesn't change anything with respect to the:
| ** WARNING ** Invalid CMap
| ** ERROR ** pdf_ref_obj(): passed invalid object.
message (which makes the compilation fail in the case of my
photoBooklet).
Any
--updatecontext
But I did it the same, then I did
texexec --make --all
texexec --make --all --xetex
ConTeXt works but it doesn't change anything with respect to the:
| ** WARNING ** Invalid CMap
| ** ERROR ** pdf_ref_obj(): passed invalid object.
message (which makes the compilation fail
Andrea Valle wrote:
Brief investigation and summary:
After
1. updating with macTeX package on macOSX 10.4.9
2. even if I have update ConTeXt and regenerate formats (all, also with
xetex)
my normal ConTeXt (texexec) is ok, my XeConTeX (texexec --xtx) is broken
--xetex too
Thanks Hans
texexec --xetex myfile.tex
is broken too:
** WARNING ** Invalid CMap
** ERROR ** pdf_ref_obj(): passed invalid object.
(what's the difference between --xtx and --xetex?)
Best
-a-
On 14 Sep 2007, at 20:28, Hans Hagen wrote:
Andrea Valle wrote:
Brief investigation and summary
On 9/5/07, Andrea Valle wrote:
Hi,
I'm experimenting with xetex as suggested. All ok up to know.
But I'm having a strange problem with figures.
Typically I create my diagrams with Omnigraffle, export them in pdf (default
setting) and reimport them in ConTeXt. Always fine.
Using texexec
Thanks Mojca,
I'll send it to you privately.
I've rewritten the wiki entry related to figure specifying that the
use of low level command is just a workaround.
Best
-a-
On 13 Sep 2007, at 13:00, Mojca Miklavec wrote:
On 9/5/07, Andrea Valle wrote:
Hi,
I'm experimenting with xetex
On 9/12/07, Andrea Valle wrote:
PS: I wikified some of the previous xetex infos. Please someone check I
didn't write silly stuff...
The information that \externalfigure should be replaced by
\XeTeXpicfile is misleading. It is a temporary solution for the bug (I
didn't test recently, but I had
On 12 Sep 2007, at 09:22, Mojca Miklavec wrote:
The information that \externalfigure should be replaced by
\XeTeXpicfile is misleading. It is a temporary solution for the bug (I
didn't test recently, but I had serious prolems with inclusion of
binary figures and newer PDF file versions), but
Mojca Miklavec wrote:
On 9/12/07, Andrea Valle wrote:
PS: I wikified some of the previous xetex infos. Please someone check I
didn't write silly stuff...
The information that \externalfigure should be replaced by
\XeTeXpicfile is misleading. It is a temporary solution for the bug (I
didn't
Thanks
I edited ~/.bash_profile
adding
On 10 Sep 2007, at 19:26, Henning Hraban Ramm wrote:
export PATH='$PATH:/usr/texbin'
alias texetex='texexec --xtx'
calling from Terminal
texetex /test/xetest.tex
I'm having
env: ruby: No such file or directory
Best
-a-
I'm having
env: ruby: No such file or directory
You should surround the PATH line with double quotes (), not simple
ones (').
___
If your question is of interest to others as well, please add an entry to the
You should surround the PATH line with double quotes (), not simple
ones (').
Ok, works as an alias from terminal.
BTW a texetex command already exists, so I used xecontext
But Hraban, how do I then set up TeXShop?
Thanks
-a-
Am 2007-09-11 um 12:44 schrieb Arthur Reutenauer:
I'm having
env: ruby: No such file or directory
You should surround the PATH line with double quotes (), not simple
ones (').
Sorry, I'm used to write Python (where or ' doesn't matter) or PHP
(where I normally use 's)...
Never post
Sorry, I'm used to write Python (where or ' doesn't matter)
(me too :) )
Does that work? (If I ever use TeXshop, then I run texexec in a
separate Terminal...)
Hmm, no, (AFA I can say)
Thanks
Best
-a-
PS: I wikified some of the previous xetex infos. Please someone check
I didn't write
Hi Andrea,
I saw that many tmp .rli files are generated. Apart form the
increasing compiling time, the first problem is that I had to run
several times texexec --xtx in order to generate them all. Is it normal?
This (many .rli files) is normal if you use \externalfigure in an older
version
Many thanks Jelle,
I'm solving also following some previous emails in the list.
I have to say that I'm not really fond of changing commands for
figure control depending on the engine
Best
-a-
On 10 Sep 2007, at 11:32, Jelle Huisman wrote:
Hi Andrea,
I saw that many tmp .rli files are
Hi,
I was trying to configure teXShop so that it can run texexec --xtx
I was following Otared's suggestions:
http://www.ntg.nl/pipermail/ntg-context/2006/016502.html
I tried a brainless practice, creating the suggested file with
#!/bin/tcsh
set path= ($path
Ok, sorry, I solved adding the infamous blank line suggested by Jelle...
http://article.gmane.org/gmane.comp.tex.macosx/23622/match=xecontext
+texshop
http://article.gmane.org/gmane.comp.tex.macosx/23634/match=xecontext
+texshop
I think I will add some stuff to wiki/xetex
Best
-a-
On 10
Any hints?
Make sure the xetex binary is indeed in
/usr/local/texlive/2007/bin/i386-darwin
or in /usr/texbin, and the XeConTeXt.engine is an executable file
(type chmod 755 ~/Library/TeXShop/Engines/XeConTeXt.engine in Terminal.app)
You can also remove the stand-alone slash after set path
Thanks Arthur
so now my XeConTeXt.engine file contains:
#!/bin/tcsh
set path= ($path /usr/texbin)
texexec --xtx $1
(including a blank line)
It works
Best
-a-
On 10 Sep 2007, at 17:49, Arthur Reutenauer wrote:
Any hints?
Make sure the xetex binary is indeed in /usr/local/texlive
Am 2007-09-10 um 18:18 schrieb Andrea Valle:
so now my XeConTeXt.engine file contains:
#!/bin/tcsh
set path= ($path /usr/texbin)
texexec --xtx $1
(including a blank line)
It works
BTW, for the records:
tcsh is rather exotic (was default on OSX 10.1, though).
I'd suggest:
in your
Hi,
I'm experimenting with xetex as suggested. All ok up to know.
But I'm having a strange problem with figures.
Typically I create my diagrams with Omnigraffle, export them in pdf
(default setting) and reimport them in ConTeXt. Always fine.
Using texexec --xtx I'm having a strange scale
Hello all,
I have fetched mswincontext.zip from 06-Aug-2007. I would like to update it to
the
latest status of ConTeXt and then install the latest (dev.) version 0.997 of
XeTeX
but I miss somehow the procedure on the context/xetex mailing list.
Can somebody help me?
Thanks and regards,
Ardi
Hello all,
1.
I have fetched mswincontext.zip from 06-Aug-2007. I would like to update it to
the
latest status of ConTeXt and then install the latest (dev.) version 0.997 of
XeTeX
but I miss somehow the procedure on the context/xetex mailing list.
Can somebody help me?
2. Is there a procedure
Research Panel today!---BeginMessage---
Hello all,
I have fetched mswincontext.zip from 06-Aug-2007. I would like to update it to
the
latest status of ConTeXt and then install the latest (dev.) version 0.997 of
XeTeX
but I miss somehow the procedure on the context/xetex mailing list.
Can
. This change was introduced
when ConTeXT started supporting the new XeTeX way of specifying a
(non-installed) OpenType font by its filename.
Either this:
[name:Minion Pro\xetexcolon mapping=tex-text;+onum;]
or this:
['Minion Pro\xetexcolon mapping=tex-text;+onum;']
should work (I
Thomas A. Schmitz wrote:
1. The syntax [name:Minion Pro\xetexcolon mapping=tex-text;+onum;]
will only work for installed fonts, not for opentype fonts that are
in the texmf-tree,
correct
My experiments suggest that these can be found via the [file:filename]
mechanism, but I can't
supporting the new XeTeX way of specifying a
(non-installed) OpenType font by its filename.
Either this:
[name:Minion Pro\xetexcolon mapping=tex-text;+onum;]
or this:
['Minion Pro\xetexcolon mapping=tex-text;+onum;']
should work (I defined \xetexcolon in type-xtx.tex).
Yes
On Aug 2, 2007, at 4:24 PM, Taco Hoekwater wrote:
definately correct.
Best wishes,
Taco
Thanks for the clarification Taco!
All best
Thomas
___
If your question is of interest to others as well, please add an
In ver: 2007.01.12, a typescript like this works fine:
\starttypescript[serif][minion][uc]
\definefontsynonym [MinionRegular] ['Minion Pro:mapping=tex-text;
+onum;'][encoding=uc]
\stoptypescript
We get Minion Pro, mapping TeX markup to unicode characters and
Hi all,
if i use the metafun macro externalfigure with xetex, there is a printed
number
(first externafigure prints a 1, the second a 2 right after the 1 and
so on)
in the lower left corner of the picture; the picture itself is shifted to
the upper right,
out of the bounding box.
I have
Hi all,
if i use the metafun macro externalfigure with xetex, there is a printed
number
(first externafigure prints a 1, the second a 2 right after the 1 and
so on)
in the lower left corner of the picture; the picture itself is shifted to
the upper right
out of the bounding box.
I have
Hello Hans,
I've updated original TeXLive2007 distribution to the latest cont-tmf beta, by
copying \web2c into TeXLive2007\texmf folder and every other stuff into
TeXLive2007\texmf-dist folder. Then I rebuilded the format files for both
context and xetex (texexec --make en, then texexec --xtx
Vyatcheslav Yatskovsky wrote:
Hello Hans,
I've updated original TeXLive2007 distribution to the latest cont-tmf
beta, by copying \web2c into TeXLive2007\texmf folder and every other
stuff into TeXLive2007\texmf-dist folder. Then I rebuilded the format
files for both context and xetex (texexec
Hello,
Taco and Hans, thank you both very much. You are not less but genius. :)
The patch from Taco runs smoothly. Now all system fonts I'm using are found
without complaints. (BTW, I've never considered TeX seriously without XeTeX.
System font support is Must Have for a Windows-minded user
Hello,
I've found a bug in XeTeX image handling. Once it has created a .rli file for
an image, it doesn't recalculate dimensions after the image is changed.
I tested it with .png image, 1-bit (black-and-white). When I crop the image,
both its size and datetime attribs are updated. Nevertheless
Hello,
Just to let you all know: ConTeXt with pdfTeX creates PDF version 1.5
by default, and xdvipdfmx driver of XeTeX (which became the default
one) isn't capable to handle those files. It handles PDF 1.4 OK, so if
you have some PDFs with a too recent version, you should convert them
to a lower
Hi,
I can't use opentype font features with XeTeX, e.g. Palatino
Linotype:+smcp for small caps. It works with plain XeTeX or ConTeXt
with \font, e.g.
\font\PALA=Palatino Linotype:+smcp at 12pt
\PALA some text...
but not with typescripts, like
\starttypescript[serif][PalatinoLinotype][uc
On 4/23/07, Mojca Miklavec [EMAIL PROTECTED] wrote:
Hello,
Just to let you all know: ConTeXt with pdfTeX creates PDF version 1.5
by default, and xdvipdfmx driver of XeTeX (which became the default
one) isn't capable to handle those files. It handles PDF 1.4 OK, so if
you have some PDFs
I have read this thread in the mailing list
(http://archive.contextgarden.net/message/20070413.171025.c375278f.en.html)
and understood the problem.
Sorry for the noise.
Ricard
___
If your question is of interest to
On 4/24/07, Ricard Roca [EMAIL PROTECTED] wrote:
I have read this thread in the mailing list
(http://archive.contextgarden.net/message/20070413.171025.c375278f.en.html)
and understood the problem.
See
http://archive.contextgarden.net/message/20070326.110622.842543c2.en.html
Mojca
Vyatcheslav Yatskovsky wrote:
Hello
Unfortunately, I get dummy boxes instead of .pdf figures in the
XeteXed document. I know, it has been discussed already in the list. However,
I downloaded and installed the fresh
version of TexLive2007 today, and no problems from updating shouldn't arise.
Hello,
I have some progress with XeTeX already (with the version included in TeXLive
distribution).
1a) Including external graphics really requires ImageMagic to be installed.
1b) PDF pictures refuse to be inserted for unknown reason but PNGs are handled
fine.
2) To use Windows encoding
and adjusting other settings don't
help also. Anything created in this Acrobat fails in XeTeX.
And good news: pdf created in Inkscape seems to be valid input for XeTeX!
--
Best regards,
Vyatcheslav Yatskovsky
Well, first try inserting the sample PDF file cow.pdf supplied with
ConTeXt via
Hello
Unfortunately, I get dummy boxes instead of .pdf figures in the
XeteXed document. I know, it has been discussed already in the list. However, I
downloaded and installed the fresh
version of TexLive2007 today, and no problems from updating shouldn't arise.
The log says:
figures :
Hello,
To get rid of dummy boxes instead of figures in XeTeX output, I've decided to
update the stuff (I already has installed fresh latest TeXLive).
I typed
ctxtools --update
then
texexec --xtx --make en
and even recreated format files from TeXLive GUI. After all, I get
(c
of the things undergoing a massive
overhaul these days. Unfortunately this appears to have broken
compatibility with XeTeX. At the Epen conference Hans told me that
he's going to finalize ConTeXt's font interface code for luaTeX first
and then eventually backport everything to XeTeX.
So
Hi,
again, I've been through this a couple of days ago so I'm happy to
share my experience with you ;-)
For me the problem was not having installed ImageMagick in the first
place. But judging from your log this doesn't seem to be the problem.
Let me think ... perhaps your glitch might be
Hello Oliver,
I reinstalled TeXLive2007 from scratch -- fonts work fine, but .pdf images are
replaced by dummy rectangles. (ImageMagik makes no difference.)
After manually updating ConTeXt files to the current release -- font handling
is broken.
So, there is no way to use XeTeX for me
XeTeX, but guessing from the error message, is write18
enabled on your system?
Aditya
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Vyatcheslav Yatskovsky wrote:
Hello Oliver,
I reinstalled TeXLive2007 from scratch -- fonts work fine, but .pdf
images are replaced by dummy rectangles. (ImageMagik makes no
difference.)
This sounds like the command execution extension is turned off.
Whether or not ConTeXt is allowed to
Oliver Buerschaper wrote:
Hi Vyatcheslav,
I encountered the same problem a couple of weeks ago ... and it will
probably not be fixed until luaTeX is out.
It appears to me that reverting back to the situation from three months
ago would already be a step forward from what we have now, yes?
401 - 500 of 700 matches
Mail list logo
