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?
As far as fonts are concerned ...
Hello,
Taco and Anita, you are geniuses! shell_escape was set to false, indeed.
However, it fails further. My ch6.pdf output file isn't created at all whenever
I insert \externalfigure[f01.pdf].
The log says
...
systems : begin file ch6 at line 10
[EMAIL
Hi,
I'm a bit confused. Still can't have a clear frame of -TeX stuff.
What does this exactly mean (from wikipedia)?
XeTeX works well with both LaTeX and ConTeXt.
Many thanks
Best
-a-
On 5 Apr 2007, at 12:18, Mojca Miklavec wrote:
On 4/5/07, Vyatcheslav Yatskovsky wrote:
Hello,
I heard
On 4/5/07, Andrea Valle [EMAIL PROTECTED] wrote:
I'm a bit confused. Still can't have a clear frame of -TeX stuff.
What does this exactly mean (from wikipedia)?
XeTeX works well with both LaTeX and ConTeXt.
In the beginning there was tex, a program. I know people who create
documents
What does this exactly mean (from wikipedia)?
XeTeX works well with both LaTeX and ConTeXt.
XeTeX, PDFTeX, eTeX, and TeX (Knuth's original TeX) are conceptually
at the same level. The ConTeXt documents (and kpathsea) call this
level the engine. They all understand basically the same macro
On 4/5/07, Sanjoy Mahajan [EMAIL PROTECTED] wrote:
What does this exactly mean (from wikipedia)?
XeTeX works well with both LaTeX and ConTeXt.
XeTeX, PDFTeX, eTeX, and TeX (Knuth's original TeX) are conceptually
at the same level. The ConTeXt documents (and kpathsea) call this
level
Thanks Sanjoy for the exhaustive infos.
I knew the relations among Tex, LaTeX and ConTeXt but couldn't
understand at which level XeTeX was positioned.
So, I was interested in XeTeX because (if I understood clearly) I can
use resident fonts. Is it true?
What I have to do in order to do
Hi,
[xetex on linux, esp. on contextgarden.net]
/etc/fonts/local.conf, I guess... as far as the fontconfig side of the
Force is concerned, this is the right location to add “local” font
directories (say
/usr/local/texlive/2007/texmf-dist/fonts/opentype/public/iwona)
That is the secret
On 4/1/07, Patrick Gundlach wrote:
Hi,
[xetex on linux, esp. on contextgarden.net]
/etc/fonts/local.conf, I guess... as far as the fontconfig side of the
Force is concerned, this is the right location to add local font
directories (say
/usr/local/texlive/2007/texmf-dist/fonts
Hmmm ... there must be a few additional lines somewhere in fontconfig.
/etc/fonts/local.conf, I guess... as far as the fontconfig side of the
Force is concerned, this is the right location to add “local” font
directories (say /usr/local/texlive/2007/texmf-dist/fonts/opentype/public/iwona)
but
Just find a distraction for Arthur and
you'll be on the safe side ;)
Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Hello out there,
I feel stupid: the following file runs fine on live.contextgarden.net
(xetex engine)
\font\myfont=Iwona-Regular
\myfont
\starttext
Hello world!
\stoptext
but not on my local installation:
texmfstart texexec --xtx simple
TeXExec | processing document 'simple'
TeXExec | no ctx
Any clue what could cause the trouble?
Your font is probably only in the texmf tree, it should be installed;
that is, on Mac OS X, simply double-click on the font and select
“Install”. It will be put in ~/Library/Fonts (probably) and some caching
utilities will be run so that in can be found
to sleep at all, just in case I could
miss important changes (like switching to xetex at 4:44 a.m) :-))
Merci beaucoup,
Patrick
--
ConTeXt wiki and more: http://contextgarden.net
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman
Next ConTeXt meeting I won't go to sleep at all, just in case I could
miss important changes (like switching to xetex at 4:44 a.m) :-))
That's probably the best choice. 24 hours a day are hardly enough anyway :-)
___
ntg-context mailing list
ntg
to sleep at all, just in case I could
miss important changes (like switching to xetex at 4:44 a.m) :-))
Don't worry, Patrick ... I guess that I won't have any sleep in the
last two weeks before the meeting, so you'll have to lock my account
for safety reasons anyway ;) Just find a distraction
Hello,
While waiting for the train in Köln (just back from one of the best
ConTeXt meetings ever ;), I decided to post this warning/explanation
to the mailing list (before Hans gets back and blocks my account ;)
For those who rely on (complex) XeTeX typescripts, please don't
upgrade ConTeXt
Dear Hans,
I got the same problem with new ConTeXt update.
! Font \*12ptrmtfrm*=[ec-lmr12] not loadable: Metric (TFM) file or
installed fo
nt not found.
to be read again
\relax
\xxdododefinefont ...tspec {#4}\newfontidentifier
On 3/1/07, Jeong Dalyoung [EMAIL PROTECTED] wrote:
Dear Hans,
I got the same problem with new ConTeXt update.
! Font \*12ptrmtfrm*=[ec-lmr12] not loadable: Metric (TFM) file or
installed fo
nt not found.
to be read again
\relax
\xxdododefinefont ...tspec
not that strange ... just install the latest latin roman .. it's
what the message says
Font \*7ptmmmrrm*=[rm-lmr7] not loadable: Metric (TFM) file or
installed font
not found.
Well, then perhaps I need a bit of advice because I have the
impression that my TeXLive 2007 installation
Mojca Miklavec wrote:
On 2/26/07, Oliver Buerschaper wrote:
Dear folks,
I'm afraid I'm facing the XeTeX problem again after I updated ConTeXt
to version 2007.02.21 :-(
On a freshly installed MacTeX-2007 (which is TeXLive 2007 up to minor
modifications) everything is fine. The ConTeXt
Dear folks,
I'm afraid I'm facing the XeTeX problem again after I updated ConTeXt
to version 2007.02.21 :-(
On a freshly installed MacTeX-2007 (which is TeXLive 2007 up to minor
modifications) everything is fine. The ConTeXt version is 2007.01.12.
Then I ran ctxtools which installed
On 2/26/07, Oliver Buerschaper wrote:
Dear folks,
I'm afraid I'm facing the XeTeX problem again after I updated ConTeXt
to version 2007.02.21 :-(
On a freshly installed MacTeX-2007 (which is TeXLive 2007 up to minor
modifications) everything is fine. The ConTeXt version is 2007.01.12
Henning Haeske wrote:
Thanks,
it is working after I copied the relevant files from my texmf-fonts/ into
the texmf-local/ folder.
The disjunction into the different texmf-... folders:
texmf/
texmf-local/...
texmf-font/
texmf-extra/...
texmf-linux/
is a little bit
Thanks,
it is working after I copied the relevant files from my texmf-fonts/ into
the texmf-local/ folder.
The disjunction into the different texmf-... folders:
texmf/
texmf-local/...
texmf-font/
texmf-extra/...
texmf-linux/
is a little bit confusing to me. Is this
Hello,
I started this night the installation-instruction from:
http://wiki.contextgarden.net/Linux_User_Installation
and then i continued with: http://wiki.contextgarden.net/XeTeX
texexec --pdf first.tex is working fine, but the xetex is not working:
fonts : using map file: t5
Hi,
Henning Haeske wrote:
I also tried fixing this with this note:
http://archive.contextgarden.net/message/20070130.082837.4bc51f61.en.html
Make sure you also read:
http://archive.contextgarden.net/message/20070130.145856.ffeabcfc.en.html
Best wishes,
Taco
Hi all,
there seems to be a problem with the XeTeX engine and the
mapping:tex-text feature for OpenType fonts. Try this:
---
\usetypescriptfile[type-minion]
\usetypescript[minion][uc]
\setupbodyfont[minion,13pt]
\starttext
There is --- without any doubt --- a tiny problem.
\stoptext
Oliver Buerschaper wrote:
Hi all,
there seems to be a problem with the XeTeX engine and the
mapping:tex-text feature for OpenType fonts. Try this:
---
\usetypescriptfile[type-minion]
\usetypescript[minion][uc]
\setupbodyfont[minion,13pt]
\starttext
There is --- without any doubt
Hi all,
there seems to be a problem with the XeTeX engine and the
mapping:tex-text feature for OpenType fonts. Try this:
---
\usetypescriptfile[type-minion]
\usetypescript[minion][uc]
\setupbodyfont[minion,13pt]
\starttext
There is --- without any doubt --- a tiny problem.
\stoptext
As I ran into the same problem I followed your instructions ...
running the ctxtools command doesn't resolve it I'm afraid.
$ kpsewhich lm-math.map
/usr/local/gwTeX/texmf.texlive/fonts/map/dvips/lm/lm-math.map
You should try that with --engine=dvipdfm , because dvipdfmx
will find different
Oliver Buerschaper wrote:
No, didn't copy anything. Should I've done that? I'm lost ...
Yes, you should have. Same original thread, second message
(I forgot to mention that in the original message)
Taco
___
ntg-context mailing list
Problem solved.. Thanks so much for all of your input!!
Helin
On 2/7/07, Oliver Buerschaper [EMAIL PROTECTED] wrote:
No, didn't copy anything. Should I've done that? I'm lost ...
Yes, you should have. Same original thread, second message
(I forgot to mention that in the original message)
Hi Taco,
I got a new problem after upgrading to the new ConTeXt.
When I compile a document with the xetex engine, during the xdvipdfmx
processing, I got the following message, and all the math symbols are
missing:
Please see this thread:
http://archive.contextgarden.net/message
with the xetex engine, during the xdvipdfmx
processing, I got the following message, and all the math symbols are
missing:
Please see this thread:
http://archive.contextgarden.net/message/
20070130.082837.4bc51f61.en.html
As I ran into the same problem I followed your instructions
after upgrading to the new ConTeXt.
When I compile a document with the xetex engine, during the xdvipdfmx
processing, I got the following message, and all the math symbols are
missing:
Please see this thread:
http://archive.contextgarden.net/message/
20070130.082837.4bc51f61.en.html
Hi all,
I got a new problem after upgrading to the new ConTeXt.
When I compile a document with the xetex engine, during the xdvipdfmx
processing, I got the following message, and all the math symbols are
missing:
** WARNING ** This .map file looks like a dvips format fotmap file.
** WARNING
Helin Gai wrote:
Hi all,
I got a new problem after upgrading to the new ConTeXt.
When I compile a document with the xetex engine, during the xdvipdfmx
processing, I got the following message, and all the math symbols are
missing:
Please see this thread:
http://archive.contextgarden.net
Mojca Miklavec wrote:
... much much text .. begging for []'s ...
How about this ... no quotes in specs, only file: or name: in front of
the name, and for xetex we default to filenames using file:
It means that existing defs need to be adapted, but this syntax is
better than funny [ ] etc
On 2/2/07, Hans Hagen wrote:
Mojca Miklavec wrote:
... much much text .. begging for []'s ...
How about this ... no quotes in specs, only file: or name: in front of
the name, and for xetex we default to filenames using file:
I would default to name:
It means that existing defs need
Mojca Miklavec wrote:
On 2/2/07, Hans Hagen wrote:
Mojca Miklavec wrote:
... much much text .. begging for []'s ...
How about this ... no quotes in specs, only file: or name: in front of
the name, and for xetex we default to filenames using file:
I would default
On 2/2/07, Hans Hagen wrote:
Mojca Miklavec wrote:
On 2/2/07, Hans Hagen wrote:
Mojca Miklavec wrote:
... much much text .. begging for []'s ...
How about this ... no quotes in specs, only file: or name: in front of
the name, and for xetex we default to filenames using file
Dear Mojca,
As you told me, I changed outputdriver in tex.rb from xdvipdfmx to
xdv2pdf and run it.
There is no delay at all, but the output pdf lost color and mp stuffs.
I think that it is better to use xdvipdfmx even though it took more
times.
During the test, I found a strange result.
separately. Support for metapost has been
improved on the first day when XeTeX for linux came out, but support
for xdv2pdf will most probably never be available unless one of the
users would be willing to write it. (Also, more and more features are
now only available for xdvipdfmx. It might
Dear all,
Recently I updated TeXlive and ConTeXt. After that the compiling time
of a file under ConTeXt+XeTeX became longer than before. However,
there is no change when I compiled the files using ConTeXt.
I tested the same file using the previous ConTeXt version in the
another Mac
On 2/1/07, Jeong Dalyoung wrote:
Dear all,
Recently I updated TeXlive and ConTeXt. After that the compiling time of a
file under ConTeXt+XeTeX became longer than before. However, there is no
change when I compiled the files using ConTeXt.
I tested the same file using the previous ConTeXt
On 1 Feb 2007, at 1:51 pm, Mojca Miklavec wrote:
If you have someone to blame, please blame me. I asked Hans if he
could add an additional switch -output-driver=xdvipdfmx when running
XeTeX. This means that the files are now converted to pdf with
xdvipdfmx instead of xdv2pdf. Without
Jonathan Kew wrote:
It may be that older ConTeXt scripts didn't run an xdv-to-pdf
converter at all until the last of several passes; if you call xetex
with the -no-pdf switch on all the preliminary runs, it will skip the
conversion and therefore be faster. But I'm not sure exactly how
Mojca Miklavec wrote:
Hello,
Since there are serious problems with XeTeX on non-TeXLive
distributions anyway: why not mess it up properly this time?
The attached file seems to work OK, although kpathsea complains a bit
(but these are only warnings - no serious problems; perhaps other
On 1/31/07, Hans Hagen wrote:
Mojca Miklavec wrote:
Hello,
Since there are serious problems with XeTeX on non-TeXLive
distributions anyway: why not mess it up properly this time?
The attached file seems to work OK, although kpathsea complains a bit
(but these are only warnings
On 31 Jan 2007, at 4:58 pm, Mojca Miklavec wrote:
hm, i'm still wondering why xetex needs the extra [] ; is this
somewhere documented? is it something new? why not {}
having an extra series of defs for xetex is a bad idea, so i'd
rather fix that 'automatically'
Using OpenType fonts
filename stuff i can probably just feed the [] deep down
in context to the xetex font command
will think of something
please forward to jonathan since his mailer an dmy mail server don;t
like each other -)
Hans
Hello,
Since there are serious problems with XeTeX on non-TeXLive
distributions anyway: why not mess it up properly this time?
The attached file seems to work OK, although kpathsea complains a bit
(but these are only warnings - no serious problems; perhaps other
macros could or should
Taco Hoekwater wrote:
Thomas A. Schmitz wrote:
2. When generating the formats, texexec complained about unknow
control sequence because of lines 25 and 26 in syst-xtx.tex
\setcclcuc 201C 201C 201C
\setcclcuc 201D 201D 201D
I had to comment out these lines to generate the formats (this
when you don;t use those []'s?
It would be nicer if XeTeX would support TeX-style braces as well.
This is much less bizarre:
\definedfont[{GFSDidot} at 20pt]
Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg
Thomas A. Schmitz wrote:
Well don't laugh: I tried your suggestion and found that this works:
\definedfont[{{[GFSDidot] at 20pt}}]
the two pairs of braces seem to be needed. Not a pretty sight, though...
[GFSDidot]
is not a prettu sight anyway; does it fail when you don;t use those
On Jan 22, 2007, at 12:17 AM, Hans Hagen wrote:
fonts is more than definitions; esp a the level of supporting
features and runtime manipulating fonts, xetex and luatex will
undoubtely differ; also, xetex uses external font libraries, while
luatex does things internaly and under user
). It was a headache. (I needed
external figures and I didn't know that using them was possible in
XeTeX.)
OK, I see where XeTeX has its strong points. And I can certainly
agree: if you want unusual glyphs that are not part of a more-or-less
standard encoding, that can be a PITA.
Two other reasons
On Jan 22, 2007, at 10:41 AM, Hans Hagen wrote:
[GFSDidot]
is not a prettu sight anyway; does it fail when you don;t use those
[]'s?
Hans
Yes, it breaks without the [].
Just came back from a day of excruciatingly boring meetings...
Thanks
Thomas
I'm trying (once again) to find out if learning something about XeTeX
is worth the trouble. So far, I haven't seen any compelling reason,
but I'd like to experiment a bit more. Here are two questions I have
run into:
1. in the wiki pages Talk:XeTeX, there's this anonymous piece of
wisdom
Thomas A. Schmitz wrote:
2. When generating the formats, texexec complained about unknow
control sequence because of lines 25 and 26 in syst-xtx.tex
\setcclcuc 201C 201C 201C
\setcclcuc 201D 201D 201D
I had to comment out these lines to generate the formats (this is
with a
Uhm, maybe I wasn't quite clear: the entire TeX foundation is the
current texlive head; I last sync'd on Jan 17. ConTeXt version is
2007.01.18. A look at the log doesn't reveal anything unusual, here's
the beginning and end of the log file:
This is XeTeXk, Version 3.141592-2.2-0.996 (Web2C
On 1/21/07, Thomas A. Schmitz wrote:
I'm trying (once again) to find out if learning something about XeTeX
is worth the trouble. So far, I haven't seen any compelling reason,
but I'd like to experiment a bit more. Here are two questions I have
run into:
1. in the wiki pages Talk:XeTeX
Thomas A. Schmitz wrote:
Uhm, maybe I wasn't quite clear: the entire TeX foundation is the
current texlive head; I last sync'd on Jan 17. ConTeXt version is
2007.01.18. A look at the log doesn't reveal anything unusual, here's
the beginning and end of the log file:
ConTeXt ver:
Mojca Miklavec wrote:
But one would also need \definedfont[[KalligraphiaLTStd] at 40pt] or
a similar command (double brackets look ugly anyway) to pass the same
Have you tried
\definedfont[{[KalligraphiaLTStd] at 40pt}]
yet? Sorry, I have simply no time to toy around with XeTeX myself
Mojca Miklavec wrote:
But one would also need \definedfont[[KalligraphiaLTStd] at 40pt] or
a similar command (double brackets look ugly anyway) to pass the same
Have you tried
\definedfont[{[KalligraphiaLTStd] at 40pt}]
yet? Sorry, I have simply no time to toy around with XeTeX myself
On Jan 21, 2007, at 5:51 PM, Mojca Miklavec wrote:
I requested that feature in XeTeX and yet: it's now implemented in
LaTeX, but not in ConTeXt. (When Adam became a father, sad times have
started for fonts in ConTeXt ;)
Oh that's where Adam has been hanging out lately! I was wondering
it ;)
Thanks a lot! (Why on earth haven't I thought about that before?)
That basically means that now I can finally try to add a bunch of
(although ugly, but at least working) definitions to get the OpenType
version of LM version used by default when launching XeTeX. (I tried
it already
Taco Hoekwater wrote:
Thomas A. Schmitz wrote:
Uhm, maybe I wasn't quite clear: the entire TeX foundation is the
current texlive head; I last sync'd on Jan 17. ConTeXt version is
2007.01.18. A look at the log doesn't reveal anything unusual, here's
the beginning and end of the log
to toy around with XeTeX myself.
or
\def\xetexfontspec#1{[#1]}
(or maybe \unexpanded\def\xetexfontspec#1{[#1]})
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH
Thomas A. Schmitz wrote:
But since I know that you've done a lot of work on XeTeX in ConTeXt,
I'd really like to know: what exactly can XeTeX do that would make me
want to take a more thorough look at it? After a sometimes painful
learning curve, I find it nowadays relatively easy
[{[KalligraphiaLTStd] at 40pt}]
yet? Sorry, I have simply no time to toy around with XeTeX myself.
Best, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Mojca Miklavec wrote:
Hmmm ... you can use OpenType fonts in XeTeX in a plain-TeX-way like that:
\font\a=[KalligraphiaLTStd] \a
hm, weird syntax
But there's no high level interface for it yet. The relevant pieces
are in font-ini.tex:
%D For \XETEX\ we need to support a bit more:
%D
%D
a bunch of
(although ugly, but at least working) definitions to get the OpenType
version of LM version used by default when launching XeTeX. (I tried
it already and it seems to work OK, but it has to be completed and
cleaned a bit first.)
are these [] really needed?
Now I only have to figure
On 1/10/07, Peter Münster wrote:
Hello,
what is needed to get LM working with XeTeX?
I've no success with such a minimal file (imagine utf8 encoding, which is
not the case in this email):
\startext
à è ö € œ ±
\stoptext
Just to answer what you have been asking for:
\font\f=[lmroman12
On 1/10/07, Peter Münster wrote:
Hello,
what is needed to get LM working with XeTeX?
\font\f=[lmroman12-regular] \f
You can take a look at my naive example (I just replaced everything
that came to my mind, but that's wrong). Of course, it doesn't work.
It seems that low-level macros need some
Hello,
what is needed to get LM working with XeTeX?
I've no success with such a minimal file (imagine utf8 encoding, which is
not the case in this email):
\startext
à è ö € œ ±
\stoptext
Cheers, Peter
--
http://pmrb.free.fr/contact/
___
ntg-context
Hi,
I'm trying to learn about using XeTeX in ConTeXt. The problem is that
when I compile a file using texexec --xtx filename.tex, I get the
following error message
*** fontmap psfonts.map not found; texmf.cnf may be broken
*** font ec-lmtt10 not found in psfonts.map or host system
Helin Gai wrote:
Hi,
I'm trying to learn about using XeTeX in ConTeXt. The problem is that
when I compile a file using texexec --xtx filename.tex, I get the
following error message
*** fontmap psfonts.map not found; texmf.cnf may be broken
*** font ec-lmtt10 not found in psfonts.map
Thanks for the reply.
I solved the problem eventually by commenting out the line
$ENV{'TEXFONTMAPS'} = '.;$TEXMF/fonts/map/{xetex,pdftex,dvips,}//' ;
in texexec.pl.
Thanks again!
Sincerely,
Helin
On 1/8/07, Hans Hagen [EMAIL PROTECTED] wrote:
Helin Gai wrote:
Hi,
I'm trying to learn
On Mon, 8 Jan 2007, Helin Gai wrote:
Thanks for the reply.
I solved the problem eventually by commenting out the line
$ENV{'TEXFONTMAPS'} = '.;$TEXMF/fonts/map/{xetex,pdftex,dvips,}//' ;
in texexec.pl.
texexec.pl is no longer supported. About a year ago, ConTeXt moved to
the ruby
by commenting out the line
$ENV{'TEXFONTMAPS'} = '.;$TEXMF/fonts/map/{xetex,pdftex,dvips,}//' ;
in texexec.pl.
texexec.pl is no longer supported. About a year ago, ConTeXt moved to
the ruby version texexec.rb. Try your code with
texmfstart texexec --xetex filename
Aditya
Hello,
with XeTeX 3.141592-0.996 (Web2C 7.5.6) and ConTeXt-2007.1.2 I get the
following error when issuing texexec --make --xtx en:
) (/opt/TeX-live/texmf-context/tex/context/base/enco-pfr.tex
loading : Context Encoding Macros (pdf)
! Undefined control sequence.
l.63 \ifcase
� wrote:
Hello,
with XeTeX 3.141592-0.996 (Web2C 7.5.6) and ConTeXt-2007.1.2 I get the
following error when issuing texexec --make --xtx en:
) (/opt/TeX-live/texmf-context/tex/context/base/enco-pfr.tex
loading : Context Encoding Macros (pdf)
! Undefined control sequence.
l.63
| www.pragma-pod.nl
-
---BeginMessage---
Hi,
i installed the XeTeX on a Debian Linux system and could use the xetex
commad to create a sample file
in persian language, very thing seems to be OK
http://www.linuxiha.com
On 12/12/06, Hans Hagen [EMAIL PROTECTED] wrote:
you can use context with xetex
Ok, but to make a pdf we must convert from dvi, right ?
Is it good or pdfetex has something more ? (Actually , I mean)
luigi
___
ntg-context mailing list
ntg-context
luigi scarso wrote:
On 12/12/06, Hans Hagen [EMAIL PROTECTED] wrote:
you can use context with xetex
Ok, but to make a pdf we must convert from dvi, right ?
indeed
Is it good or pdfetex has something more ? (Actually , I mean)
luatex (pdftex 2) probably will have more (esp
On 12/12/06, Hans Hagen wrote:
Mojca Miklavec wrote:
Hello,
I'm probaby misusing the feature (most robably because I just didn't
take time to study how to do it properly), but it behaves really
strange.
In XeTeX I first did
\font\f='Some Name' \f
which worked OK. But when I
I'm a little bit confused about extex (www.extex.org) and
xetex (scripts.sil.org/cms/scripts/page.php?site_id=nrsiid=xetex)
How do they relate with Context ?
luigi
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg
luigi scarso wrote:
I'm a little bit confused about extex (www.extex.org) and
xetex (scripts.sil.org/cms/scripts/page.php?site_id=nrsiid=xetex)
How do they relate with Context ?
you can use context with xetex; i know nothing of extex apart from that
it is a java based tex variant
Hans
Hello,
I'm probaby misusing the feature (most robably because I just didn't
take time to study how to do it properly), but it behaves really
strange.
In XeTeX I first did
\font\f='Some Name' \f
which worked OK. But when I tried the same with
\definedfont['Some Name']
it resulted
On 12/12/06, luigi scarso wrote:
I'm a little bit confused about extex (www.extex.org) and
xetex (scripts.sil.org/cms/scripts/page.php?site_id=nrsiid=xetex)
How do they relate with Context ?
XeTeX is reasonably well supported in ConTeXt (font stuff is better
supported in LaTeX for the time
Mojca Miklavec wrote:
Hello,
I'm probaby misusing the feature (most robably because I just didn't
take time to study how to do it properly), but it behaves really
strange.
In XeTeX I first did
\font\f='Some Name' \f
which worked OK. But when I tried the same with
\definedfont
Mojca Miklavec wrote:
XeTeX is reasonably well supported in ConTeXt (font stuff is better
supported in LaTeX for the time being, hopefully this will change).
I will cook up a decent open type font model for luatex and backport to
xetex for as far as possible.
Hans
that the issues with XeTeX and papersize
have been already solved.
When producing bookmarks with XeConTeXt, for some strange reason
destinations change the page view to /Fit. Is there any way to avoid this?
Bookmarks are generated fine in UTF-8, but surprisingly (at least for
me) the file info is wrong
Hi,
I have a question regarding ConTeXt, XeTeX and the use of Unicode fonts
with diacritic characters which I use quite a lot. (Note also that I'm
a novice user.) Consider the following extreme example (using Gentium
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsiid=gentium
Philipp Reichmuth wrote:
- character[ range]s which get passed directly to the underlying engine
(useful mainly with XeTeX and possibly with Aleph/Omega)
- character[ range]s which get constructed from accents
- character[ range]s which get used from a different typescript; for
example if I
Hi,
is there a first-line comment directive or a \setupoutput[] parameter to
force usage of XeTeX just like the --xtx commandline switch?
Consider the following document:
--
% ??? = xetex???
\starttext
This is a piece of text
\stoptext
--
I just
.
\XeTeXinputencoding bytes
\enableregime[utf]
Ṯḥíş ıš ā pìėçẹ ȯf ṭēxt.
\XeTeXinputencoding utf-8
Ṯḥíş ıš ā pìėçẹ ȯf ṭēxt.
\stoptext
which doesn't work. I experimented around with commenting out the XeTeX
section in base/regi-uni.tex, but that doesn't do anything
Philipp Reichmuth wrote:
Hans Hagen schrieb:
Philipp Reichmuth wrote:
- character[ range]s which get passed directly to the underlying engine
(useful mainly with XeTeX and possibly with Aleph/Omega)
- character[ range]s which get constructed from accents
- character[ range]s which
501 - 600 of 700 matches
Mail list logo
