On 11/5/07, Dalyoung Jeong wrote:
> Dear Mojca,
>
> Thank you for the reply. As you did, I send my problem to the list. I
> think that I am a problem maker.
>
> I wonder why the output of XeTeX+ConTeXt was changed after the upgrade
> to Leopard.
> I didn't change anything in TeX system. I just upgr
Dear Mojca,
Thank you for the reply. As you did, I send my problem to the list. I
think that I am a problem maker.
I wonder why the output of XeTeX+ConTeXt was changed after the upgrade
to Leopard.
I didn't change anything in TeX system. I just upgraded the OSX.
But nicely working XeTeX+Co
Mojca Miklavec wrote:
> On 3/9/07, Akira Kakuto wrote:
>
>> Hi Mojca,
>>
>>
>>> Well, OK, that's understandable. That's just an accidental mix-up with
>>> otf files in ConTeXt. Line 73 of font-ini.mkii should read
>>> \def\fontfilesome#1{"#1"}
>>> instead of
>>> \def\fontfilesome#1{
On 3/9/07, Akira Kakuto wrote:
> Hi Mojca,
>
> > Well, OK, that's understandable. That's just an accidental mix-up with
> > otf files in ConTeXt. Line 73 of font-ini.mkii should read
> > \def\fontfilesome#1{"#1"}
> > instead of
> > \def\fontfilesome#1{"[#1]"}
>
> Please check my previous ma
Hmmm ... perhaps the problem is not only in XeTeX. After reinstalling
ConTeXt (version: 2007.02.21), I now get
(/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-spe.tex)
(/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-akb.tex))
bodyfont: 12pt rm is loaded
kpathsea: Illegal fontname `cm
Hello,
Here's the same error report that has been discussed on(off?) the list
already, but there has been no resolution so far. Should I ask the
XeTeX mailing list?
With texexec --xtx whatever I get:
(/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-akb.tex)
(/usr/local/gwTeX/texmf.pkgs/tex/co
