[XeTeX] presentation mode in XeTeX-ConTeXt
Dalyoung
haksan at mac.com
Fri Apr 1 02:54:35 CEST 2005
I have changed all " " with ( ) in typescriptfile and have tested
files containing it. It does't make any problem except \startitemize[1]
doesn't produce small dot for \item.
And then I run "texexec --xtx conf-pre-main.tex".
This time I got different error as follows(it didn't complain about the
font name):
...
system : mark Nopicnumber defined [titlenumber]
system : mark Subject defined [section]
system : mark Subjectnumber defined [sectionnumber]
) (./conf-pre-main.tuo)
Runaway argument?
{^^G^^[⻊\twopassentry {list}{1}{1:2}\twopassentry
{subpage}{1}{1}\twopassentr
y \ETC.
! File ended while scanning use of \thisisbytesequence.
<inserted text>
\par
<to be read again>
\relax
\dodoreadfile ...normalinput \readfilename \relax
\the
\everyafterreadfile
\doutilities ...textension }\donothing \donothing
\the
\everyafterutilityrea...
<argument> ...pass }\jobname \empty \relax \relax
\ifx \twopassdata
\empty \...
\firstofoneargument #1->#1
...
l.36 \starttext
...
Yesterday, I had a complain about the font name. Which does come first,
font error or this type error? If font error come first, then we may
assume that the ( ) method works.
Thank you.
Regards,
Dalyoung
2005. 04. 01, 오전 1:59, Jonathan Kew 작성:
> On 31 Mar 2005, at 4:37 pm, Adam Lindsay wrote:
>
>> Otared Kavian said this at Thu, 31 Mar 2005 17:29:23 +0200:
>>
>>> Can it be that the problem comes from two facts:
>>> 1) XeTeX is set up for a unique paper format A4,
>>
>> True. You can create a work-around, however.
>
> Yes, you just need to pass the -papersize argument. (Sorry, I haven't
> yet implemented a mechanism that can be controlled from within the TeX
> source.)
>
>>> 2) PDF interactions are (seemingly) not supported in XeTeX
>>
>> This is true. I'm eagerly awaiting MacOSX 10.4's PDFKit to see if that
>> will allow embedding JS/PDF literals.
>
> Yup.
>
>> However, the error Dalyoung got was MetaPost-integration related,
>> afaik.
>
> Looked like it was caused by a double-quoted font name used for XeTeX
> getting another set of double-quotes placed around it. I seem to
> remember something along these lines came up previously. One thing I
> think I added in XeTeX was the option to use (...) as an alternative
> to "..." or '...' to quote font names.
>
> Dalyoung, if you change
>
> \definefontsynonym[smMyungjoRegular]["smMyungjoR\space
> W30"][encoding=uc]
>
> to
>
> \definefontsynonym[smMyungjoRegular][(smMyungjoR\space
> W30)][encoding=uc]
>
> (and similarly for other cases with double-quotes), this may help that
> particular problem.
>
> JK
>
> _______________________________________________
> XeTeX mailing list
> postmaster at tug.org
> http://tug.org/mailman/listinfo/xetex
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 3109 bytes
Desc: not available
Url : http://tug.org/pipermail/xetex/attachments/20050401/e28b6593/attachment.bin
More information about the XeTeX
mailing list