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 that Mac users can typeset in ConTeXt with OpenType fonts. Is it possible on Windows platform? (either in MiKTeX or TeXLive?)

The easiest way to use OpenType fonts is to use XeTeX (luaTeX will support them as well, but you would need to wait a bit before it comes out). You can also use pdfTeX, but it's a bit painful to set up everything properly.

TeXLive 2007 includes XeTeX, MikTeX will include it in version 2.7 (currently it's still at version 2.5 and 2.6 beta), so TeXLive (or standalone ConTeXt with some additional settings) is currently the best choice.

See http://wiki.contextgarden.net/Fonts_in_XeTeX (but please note that some high-level interface is currently broken if you install the latest ConTeXt; the version from TeXLive should be OK).

You can use any font in the texmf tree or any font installed on the system. You might need to run fc-cache (and perhaps edit font.conf).

Mojca _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

-------------------------------------------------- Andrea Valle -------------------------------------------------- CIRMA - DAMS Università degli Studi di Torino --> http://www.cirma.unito.it/andrea/ --> andrea.valle@unito.it --------------------------------------------------

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 language, the one Knuth described in the _TeXBook_. But they have slight differences. For example, TeX produces DVI output. eTeX does too but it adds a few more commands ('primitives') to the macro language. PDFTeX produces PDF directly (or can produce DVI) and has, relative to regular TeX, new macro commands to support features of PDF; for example, \pdfpagewidth is new to PDFTeX. Regular TeX doesn't have an equivalent because the DVI format does not include a notion of page size. PDFTeX, from v1.40, also incorporates those eTeX commands. And XeTeX has commands to support OpenType, which is the new standard font format. LaTeX and ConTeXt are large programs ('macro packages') written on top of the engine. Namely, the program -- whether LaTeX or ConTeXt -- is written in the macro language of the engine. Most of the program is independent of the engine, but there are a few changes needed; the program usually detects which engine is being used underneath it and adjusts what it does accordingly. For LaTeX, you choose the engine by the name of the program you run: * latex -- uses regular TeX (actually, now it uses PDFTeX pretending to be regular TeX) * pdflatex -- uses PDFTeX * xelatex -- uses XeTeX For ConTeXt, you choose the engine by the '--engine' option to texexec. For example: "texexec --engine=pdftex file.tex" will make you file.pdf. But as the manual entry now says, you usually do not need to specify the engine: --engine=texengine Specify the program to do the hard work of typesetting. Currently either pdftex (the default), xetex, or aleph. The luatex value is experimental. The --engine option is not usually needed. Instead, let texexec figure out the setting based on other command-line information. See for example the --xetex or --pdf switches. So * "texexec --xetex file.tex" : uses XeTeX * "texexec --pdf file.tex" : uses PDFTeX * "texexec file.tex" : also uses PDFTeX (the --pdf option is now the default to texexec) I hope this explanation clarifies. If so, you can Wikify (on wikipedia and/or the ConTeXt wiki)! -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien)

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 this? Use the fonts in the source? Add a special command? Thanks a lot Best -a- On 5 Apr 2007, at 15:23, Sanjoy Mahajan 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 the engine. They all understand basically the same macro language, the one Knuth described in the _TeXBook_.

But they have slight differences. For example, TeX produces DVI output. eTeX does too but it adds a few more commands ('primitives') to the macro language. PDFTeX produces PDF directly (or can produce DVI) and has, relative to regular TeX, new macro commands to support features of PDF; for example, \pdfpagewidth is new to PDFTeX. Regular TeX doesn't have an equivalent because the DVI format does not include a notion of page size. PDFTeX, from v1.40, also incorporates those eTeX commands. And XeTeX has commands to support OpenType, which is the new standard font format.

LaTeX and ConTeXt are large programs ('macro packages') written on top of the engine. Namely, the program -- whether LaTeX or ConTeXt -- is written in the macro language of the engine. Most of the program is independent of the engine, but there are a few changes needed; the program usually detects which engine is being used underneath it and adjusts what it does accordingly.

For LaTeX, you choose the engine by the name of the program you run:

* latex -- uses regular TeX (actually, now it uses PDFTeX pretending to be regular TeX) * pdflatex -- uses PDFTeX * xelatex -- uses XeTeX

For ConTeXt, you choose the engine by the '--engine' option to texexec. For example: "texexec --engine=pdftex file.tex" will make you file.pdf. But as the manual entry now says, you usually do not need to specify the engine:

--engine=texengine Specify the program to do the hard work of typesetting. Currently either pdftex (the default), xetex, or aleph. The luatex value is experimental. The --engine option is not usually needed. Instead, let texexec figure out the setting based on other command-line information. See for example the --xetex or --pdf switches.

So * "texexec --xetex file.tex" : uses XeTeX * "texexec --pdf file.tex" : uses PDFTeX * "texexec file.tex" : also uses PDFTeX (the --pdf option is now the default to texexec)

I hope this explanation clarifies. If so, you can Wikify (on wikipedia and/or the ConTeXt wiki)!

-Sanjoy

`Not all those who wander are lost.' (J.R.R. Tolkien) _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

-------------------------------------------------- Andrea Valle -------------------------------------------------- CIRMA - DAMS Università degli Studi di Torino --> http://www.cirma.unito.it/andrea/ --> andrea.valle@unito.it -------------------------------------------------- I did this interview where I just mentioned that I read Foucault. Who doesn't in university, right? I was in this strip club giving this guy a lap dance and all he wanted to do was to discuss Foucault with me. Well, I can stand naked and do my little dance, or I can discuss Foucault, but not at the same time; too much information. (Annabel Chong)