date:20110922

Re: [XeTeX] Difference between XeLaTeX and LaTeX

2011-09-22 Thread Suresh Avvarulakshmi, Integra-PDY, IN

Thank you for valuable suggestions. 
Suresh

-Original Message-
From: xetex-boun...@tug.org [mailto:xetex-boun...@tug.org] On Behalf Of Zdenek 
Wagner
Sent: Thursday, September 22, 2011 3:24 PM
To: Unicode-based TeX for Mac OS X and other platforms
Subject: Re: [XeTeX] Difference between XeLaTeX and LaTeX

2011/9/21 Suresh Avvarulakshmi, Integra-PDY, IN
:
> Hi All,
>
>
>
> Are they any comparisons documents, which shows the difference between
> XeLaTeX and LaTeX typesettings?
>
I do not know but it can be said quite simply. In any case, it is
Lamport's LaTeX with extensions. The macrolanguage is the same. The
differences stem from the differences in extensions:

1. Output driver, XeLaTeX cannot create dvi, thus dvips and similar
programs cannot be used. It is important to know when including
graphics.

2. XeLaTeX cannot use microtypographical extensions but it may change
in the future. Currently pdflatex or lualatex is needed.

3. Classical LaTeX cannot work in UTF-8, only 8bit encodings are
supported. Although the inputenc package offers input in Unicode by
means of active characters, the character is composed from a series of
bytes during macro expansion. This may break certain macros. XeLaTeX
work in UTF-8 where a character is a character.

4. Classical LaTeX has no direct support for non-latin scripts.
Preprocessors are usually needed. I am aware of a preprocessor for
Velthuis encoding for Davanagari, Gurmukhi and Bengali. I am not aware
of any support for Dravidian scripts. On the contrary, XeLaTeX works
with these scripts directly.

5. Classical LaTeX can only work with TeX fonts. If you buy a font,
you have to create TFM and FD, you have to select an encoding known by
LateX. If it is an OpenType font, you have to convert it to (possibly
a searies of) type1 fonts, OpenType features will be unavailable. With
XeLaTeX or lualatex you just install the font in your OS and it can be
used as such, Opentype features can be utiized.

6. Since non-TeX fonts can be used and vendors do not care on
portability, it no longer holds that the same source document will be
typeset exactly the same way anywhere in the world or at any time. It
can be a problem if you have to share and store documents (unless you
are sure that exactly the same version of fonts is used) but you need
not care if you just want to produce PDF once and it will never change
in the future. (This is the philosophy of the Prague Bulletin of
Mathematical Linguistics, per definition the right PDF is that typeset
by the editors, they after reviews and proofs create a PDF, have it
printed, put it to the web and this is the final version that will
never change).

Most packages deal with macros, not with the particular engine/output
driver. You can use them no matter whether you use pdflatex, lualatex,
classical LaTeX with dvips or XeLaTeX. Other packages are able to
detect the engine/driver and adapt itself. Thus the only difference
from the user's point of view is the font/script issue.

Hope this helps.
>
>
> Thanks,
>
> Suresh
>
> This email and any accompanying attachments is for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. Any unauthorized review, use, disclosure, distribution, or
> copying is strictly prohibited. If you are not the intended recipient of
> this communication or received the email by mistake, please notify the
> sender and destroy all copies. Integra Software Services Pvt Ltd. reserves
> the right, subject to applicable local law, to monitor and review the
> content of any electronic message or information sent to or from its company
> allotted employee email address/ID without informing the sender or recipient
> of the message.
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>
>

-- 
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz

--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

2011-09-22 Thread Nathan Sidoli

Yes, of course you are right. However, many of the older LaTeX packages 
are not being developed very actively any more (or not at all in some 
cases) so it makes it difficult to decide what to use when one need the 
functionality of some of the older packages but also wants to work with 
unicode, etc.


Anyway, you have certainly done a great deal to make bidi very 
functional and I am very grateful for that.



On 11/09/23 12:09, VAFA KHALIGHI wrote:



For how long have bidi and ednotes been incompatible? François
Charette , who maintains arabxetex and works on polyglossia, wrote
an example file showing how to use arabxetex + bidi with ednotes
to produce critical editions, so I assumed there would be some
effort to keep the packages compatible.



Well, certainly bidi can not support every single package on CTAN, one 
would need unlimited resources to be able to do that. bidi itself is 
now too big, it supports around 100 packages. Unfortunately the 
concept is misunderstood, it is not the duty of bidi package to add 
support for other packages but other packages themselves have to add 
bidi support. bidi should only support standard LaTeX and considering 
this, I have done heaps more than I ought to do. So it makes sense if 
you contact the author of ednotes package and ask him for bidi support 
in his package.




--
Subscriptions, Archive, and List information, etc.:
   http://tug.org/mailman/listinfo/xetex




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

2011-09-22 Thread VAFA KHALIGHI

>
> For how long have bidi and ednotes been incompatible? François Charette ,
> who maintains arabxetex and works on polyglossia, wrote an example file
> showing how to use arabxetex + bidi with ednotes to produce critical
> editions, so I assumed there would be some effort to keep the packages
> compatible.
>
>
>
Well, certainly bidi can not support every single package on CTAN, one would
need unlimited resources to be able to do that. bidi itself is now too big,
it supports around 100 packages. Unfortunately the concept is misunderstood,
it is not the duty of bidi package to add support for other packages but
other packages themselves have to add bidi support. bidi should only support
standard LaTeX and considering this, I have done heaps more than I ought to
do. So it makes sense if you contact the author of ednotes package and ask
him for bidi support in his package.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Problem using bidi with hyperref and amsart

2011-09-22 Thread VAFA KHALIGHI

This is a bug of bidi package however I do not think "claim" is a polite
word. I fix it today and upload the new version to CTAN.

On Thu, Sep 22, 2011 at 6:49 PM, Ari Meir Brodsky
wrote:

> Hello,
>
> I've been using LaTeX to typeset math for years, but just recently I
> decided
> to upgrade to XeLaTeX in order to include Hebrew.  I've come across the
> following problem.  Chapter 2 of the bidi package document (version 1.3.0,
> page 15) claims that the bidi package supports the hyperref package as well
> as the amsart class.  However, when I use all three together --- amsart,
> hyperref, bidi --- the XeTeX engine goes into an infinite loop at the
> \makefile command, and exceeds the input stack size capacity.  Here is a
> small example:
>
> ---
> % !TeX encoding = UTF-8
> % !TeX program = xelatex
> % test_bidi_hyperref.tex
> \documentclass{amsart}
> \usepackage{hyperref}
> \usepackage{bidi}
> \title{This is a test file}
> \author{Ari Meir Brodsky}
> \begin{document}
> \maketitle
>
> Hi, this is just a test.
> \end{document}
> ---
>
> Some (hopefully relevant) excerpted lines from the log file are:
>
> -
> This is XeTeX, Version 3.1415926-2.3-0.9997.5 (MiKTeX 2.9) (preloaded
> format=xelatex 2011.9.20)
> entering extended mode
> **test_bidi_hyperref.tex
>
> LaTeX2e <2011/06/27>
> Document Class: amsart 2009/07/02 v2.20.1
> Package: hyperref 2011/08/19 v6.82h Hypertext links for LaTeX
> Package hyperref Message: Driver (autodetected): hxetex.
> File: hxetex.def 2011/08/19 v6.82h Hyperref driver for XeTeX
> Package: bidi 2011/10/01 v1.3.0 Bidirectional typesetting in plain TeX and
> LaTeX
> File: xetex-bidi.def 2011/07/25 v0.9 bidi adaptations for XeTeX engine
> File: amsart-xetex-bidi.def 2011/08/26 v0.6 bidi adaptations for amsart
> class for XeTeX engine
> File: amsthm-xetex-bidi.def 2010/07/25 v0.1 bidi adaptations for amsthm
> package for XeTeX engine
> File: hyperref-xetex-bidi.def 2010/07/25 v0.4 bidi adaptations for hyperref
> package for XeTeX engine
> File: umsa.fd 2009/06/22 v3.00 AMS symbols A
> File: umsb.fd 2009/06/22 v3.00 AMS symbols B
> Package: nameref 2010/04/30 v2.40 Cross-referencing by name of section
>
> ! TeX capacity exceeded, sorry [input stack size=5000].
> \@ifnextchar #1#2#3->\let \reserved@d =#1
> \def \reserved@a {#2}\def
> \reserved...
> l.11
>
> If you really absolutely need more capacity,
> you can ask a wizard to enlarge me.
>
> Here is how much of TeX's memory you used:
>  7077 strings out of 429156
>  96081 string characters out of 3168943
>  193729 words of memory out of 300
>  10145 multiletter control sequences out of 15000+20
>  7385 words of font info for 29 fonts, out of 300 for 9000
>  947 hyphenation exceptions out of 8191
>  5000i,3n,26p,313b,130s stack positions out of
> 5000i,500n,1p,20b,5s
> No pages of output.
>
> ---
>
> Any ideas how to fix this?
>
> Thanks,
> -Ari
>
> ---
> Ari M. Brodsky
> ari.brod...@utoronto.ca
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Xelatex crash on OpenSolaris

2011-09-22 Thread rhino64

Hi All,
  Xelatex (texlive 2011) crash on OpenSolaris as soon the command 
«\setmainfont» is used.
The problem does not arise with Xelatex from texlive 2010 nor if the command
«\setmainfont» is commented out and the default font is used.

By googling the web, I suppose this could be a problem with gcc libs of 
different versions.

Any ideas ?

Thanks for the help,

---Transcript of example, xelatex 2010, xelatex 2011-
Script started on 22 septembre 2011 22:03:07 CEST
xx:test1 101> cat example.tex

\documentclass{article}









   \usepackage{fontspec}

  %Traitement des ligatures classiques de TeX

  \defaultfontfeatures{Mapping=tex-text}

   \fontspec[%

Extension=.otf,

UprightFont = *,

BoldFont=*Bold,

ItalicFont=*Italic,

BoldItalicFont=*BoldItalic]{GFSDidot}

   \setmainfont{GFS Didot}



\usepackage{fontspec}

\begin{document}

A simple example with math: $e^{ip}+1=0$.

\end{document}



xx:test1 102> xelatex example.tex

This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010)
 restricted \write18 enabled.
entering extended mode
(./example.tex
LaTeX2e <2009/09/24>
Babel  and hyphenation patterns for english, dumylang, nohyphenation, ge
rman-x-2009-06-19, ngerman-x-2009-06-19, ancientgreek, ibycus, arabic, armenian
, basque, bulgarian, catalan, pinyin, coptic, croatian, czech, danish, dutch, u
kenglish, usenglishmax, esperanto, estonian, farsi, finnish, french, galician, 
german, ngerman, swissgerman, monogreek, greek, hungarian, icelandic, assamese,
 bengali, gujarati, hindi, kannada, malayalam, marathi, oriya, panjabi, tamil, 
telugu, indonesian, interlingua, irish, italian, kurmanji, lao, latin, latvian,
 lithuanian, mongolian, mongolianlmc, bokmal, nynorsk, polish, portuguese, roma
nian, russian, sanskrit, serbian, slovak, slovenian, spanish, swedish, turkish,
 turkmen, ukrainian, uppersorbian, welsh, loaded.
(/opt/texlive/2010/texmf-dist/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/opt/texlive/2010/texmf-dist/tex/latex/base/size10.clo))
(/opt/texlive/2010/texmf-dist/tex/latex/fontspec/fontspec.sty
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/expl3.sty
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3names.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/etex-pkg/etex.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3basics.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3expan.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3tl.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3intexpr.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3quark.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3seq.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3toks.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3int.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3prg.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3clist.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3token.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3prop.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3msg.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3io.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3skip.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3box.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3keyval.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3keys.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3precom.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3xref.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3file.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/expl3/l3fp.sty)
(/opt/texlive/2010/texmf-dist/tex/latex/tools/calc.sty))
(/opt/texlive/2010/texmf-dist/tex/latex/xpackages/xbase/xparse.sty)
(/opt/texlive/2010/texmf-dist/tex/generic/kastrup/binhex.tex)
(/opt/texlive/2010/texmf-dist/tex/latex/xkeyval/xkeyval.sty
(/opt/texlive/2010/texmf-dist/tex/generic/xkeyval/xkeyval.tex
(/opt/texlive/2010/texmf-dist/tex/generic/xkeyval/keyval.tex)))
(/opt/texlive/2010/texmf-dist/tex/latex/fontspec/fontspec-patches.sty
(/opt/texlive/2010/texmf-dist/tex/latex/base/fixltx2e.sty))
(/opt/texlive/2010/texmf-dist/tex/latex/base/fontenc.sty
(/opt/texlive/2010/texmf-dist/tex/latex/euenc/eu1enc.def)
(/opt/texlive/2010/texmf-dist/tex/latex/euenc/eu1lmr.fd))
fontspec.cfg loaded.
(/opt/texlive/2010/texmf-dist/tex/latex/fontspec/fontspec.cfg))
(./example.aux) [1] (./example.aux) )
Output written on example.pdf (1 page).
Transcript written on example.log.
xx:test1 103> /opt/texlive/2011/bin/i386-solaris/xelatex 
example.tzex[K[K[Kex

This is XeTeX, Version 3.1415926-2.3-0.9997.5 (TeX Live 2011)
 restricted \write18 enabled.
entering extended mode
(./example.tex
LaTeX2e <2011/06/27>
Babel  and hyphenation patterns for english, dumylang, nohyphenation, ge
rman-x-2011-07-01, ngerman-x-2011-07-01, afrikaans, ancientgreek, ibycus, arabi
c, armenian, basque, bulgarian, catalan, pinyin, coptic, croatian, czech, danis
h, dutc

[XeTeX] Problem using bidi with hyperref and amsart

2011-09-22 Thread Ari Meir Brodsky

Hello,

I've been using LaTeX to typeset math for years, but just recently I decided
to upgrade to XeLaTeX in order to include Hebrew.  I've come across the
following problem.  Chapter 2 of the bidi package document (version 1.3.0,
page 15) claims that the bidi package supports the hyperref package as well
as the amsart class.  However, when I use all three together --- amsart,
hyperref, bidi --- the XeTeX engine goes into an infinite loop at the
\makefile command, and exceeds the input stack size capacity.  Here is a
small example:

---
% !TeX encoding = UTF-8
% !TeX program = xelatex
% test_bidi_hyperref.tex
\documentclass{amsart}
\usepackage{hyperref}
\usepackage{bidi}
\title{This is a test file}
\author{Ari Meir Brodsky}
\begin{document}
\maketitle

Hi, this is just a test.
\end{document}
---

Some (hopefully relevant) excerpted lines from the log file are:

-
This is XeTeX, Version 3.1415926-2.3-0.9997.5 (MiKTeX 2.9) (preloaded
format=xelatex 2011.9.20)  
entering extended mode
**test_bidi_hyperref.tex

LaTeX2e <2011/06/27>
Document Class: amsart 2009/07/02 v2.20.1
Package: hyperref 2011/08/19 v6.82h Hypertext links for LaTeX 
Package hyperref Message: Driver (autodetected): hxetex.
File: hxetex.def 2011/08/19 v6.82h Hyperref driver for XeTeX
Package: bidi 2011/10/01 v1.3.0 Bidirectional typesetting in plain TeX and
LaTeX
File: xetex-bidi.def 2011/07/25 v0.9 bidi adaptations for XeTeX engine
File: amsart-xetex-bidi.def 2011/08/26 v0.6 bidi adaptations for amsart
class for XeTeX engine
File: amsthm-xetex-bidi.def 2010/07/25 v0.1 bidi adaptations for amsthm
package for XeTeX engine
File: hyperref-xetex-bidi.def 2010/07/25 v0.4 bidi adaptations for hyperref
package for XeTeX engine
File: umsa.fd 2009/06/22 v3.00 AMS symbols A
File: umsb.fd 2009/06/22 v3.00 AMS symbols B
Package: nameref 2010/04/30 v2.40 Cross-referencing by name of section

! TeX capacity exceeded, sorry [input stack size=5000]. 
\@ifnextchar #1#2#3->\let \reserved@d =#1
 \def \reserved@a {#2}\def
\reserved... l.11 
 
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

Here is how much of TeX's memory you used:
 7077 strings out of 429156
 96081 string characters out of 3168943
 193729 words of memory out of 300
 10145 multiletter control sequences out of 15000+20
 7385 words of font info for 29 fonts, out of 300 for 9000 
 947 hyphenation exceptions out of 8191 
 5000i,3n,26p,313b,130s stack positions out of
5000i,500n,1p,20b,5s 
No pages of output.

---

Any ideas how to fix this?

Thanks,
-Ari


---
Ari M. Brodsky
ari.brod...@utoronto.ca




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

[XeTeX] Problem using bidi with hyperref and amsart

2011-09-22 Thread Ari Meir Brodsky

Hello,

I've been using LaTeX to typeset math for years, but just recently I decided
to upgrade to XeLaTeX in order to include Hebrew.  I've come across the
following problem.  Chapter 2 of the bidi package document (version 1.3.0,
page 15) claims that the bidi package supports the hyperref package as well
as the amsart class.  However, when I use all three together --- amsart,
hyperref, bidi --- the XeTeX engine goes into an infinite loop at the
\makefile command, and exceeds the input stack size capacity.  Here is a
small example:

---
% !TeX encoding = UTF-8
% !TeX program = xelatex
% test_bidi_hyperref.tex
\documentclass{amsart}
\usepackage{hyperref}
\usepackage{bidi}
\title{This is a test file}
\author{Ari Meir Brodsky}
\begin{document}
\maketitle

Hi, this is just a test.
\end{document}
---

Some (hopefully relevant) excerpted lines from the log file are:

-
This is XeTeX, Version 3.1415926-2.3-0.9997.5 (MiKTeX 2.9) (preloaded
format=xelatex 2011.9.20)  
entering extended mode
**test_bidi_hyperref.tex

LaTeX2e <2011/06/27>
Document Class: amsart 2009/07/02 v2.20.1
Package: hyperref 2011/08/19 v6.82h Hypertext links for LaTeX
Package hyperref Message: Driver (autodetected): hxetex.
File: hxetex.def 2011/08/19 v6.82h Hyperref driver for XeTeX
Package: bidi 2011/10/01 v1.3.0 Bidirectional typesetting in plain TeX and
LaTeX
File: xetex-bidi.def 2011/07/25 v0.9 bidi adaptations for XeTeX engine
File: amsart-xetex-bidi.def 2011/08/26 v0.6 bidi adaptations for amsart
class for XeTeX engine
File: amsthm-xetex-bidi.def 2010/07/25 v0.1 bidi adaptations for amsthm
package for XeTeX engine
File: hyperref-xetex-bidi.def 2010/07/25 v0.4 bidi adaptations for hyperref
package for XeTeX engine
File: umsa.fd 2009/06/22 v3.00 AMS symbols A
File: umsb.fd 2009/06/22 v3.00 AMS symbols B
Package: nameref 2010/04/30 v2.40 Cross-referencing by name of section

! TeX capacity exceeded, sorry [input stack size=5000].
\@ifnextchar #1#2#3->\let \reserved@d =#1
 \def \reserved@a {#2}\def
\reserved...
l.11 
 
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

Here is how much of TeX's memory you used:
 7077 strings out of 429156
 96081 string characters out of 3168943
 193729 words of memory out of 300
 10145 multiletter control sequences out of 15000+20
 7385 words of font info for 29 fonts, out of 300 for 9000
 947 hyphenation exceptions out of 8191
 5000i,3n,26p,313b,130s stack positions out of
5000i,500n,1p,20b,5s
No pages of output.

---

Any ideas how to fix this?

Thanks,
-Ari

---
Ari M. Brodsky
ari.brod...@utoronto.ca




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Difference between XeLaTeX and LaTeX

2011-09-22 Thread Peter Dyballa


>> 
>> 2. XeLaTeX cannot use microtypographical extensions but it may change
>> in the future. Currently pdflatex or lualatex is needed.
> 
> Actually there are already experimental versions of XeTeX lying around
> that have some microtypographical features, see:
> http://xetex.tk/mediawiki/index.php/Main_Page

XeTeX in TeX Live 2010 should have been enabled with this "extension". The 
problem was that the microtype package did not support XeTeX then. On TLcontrib 
(http://tlcontrib.metatex.org/cgi-bin/package.cgi/action=listall) you can find 
the version which supports micro-typography in XeTeX.

--
Greetings

  Pete

Know thyself. Need help, call GOOGLE.




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Difference between XeLaTeX and LaTeX

2011-09-22 Thread Peter Dyballa


> :
>> Hi All,
>> 
>> 
>> 
>> Are they any comparisons documents, which shows the difference between
>> XeLaTeX and LaTeX typesettings?

There can't be any. Both pass the TRIP test.

--
Greetings

  Pete

The problem with the French is that they don't have a word for « entrepreneur ».
– Georges W. Bush




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Difference between XeLaTeX and LaTeX

2011-09-22 Thread Petr Tomasek

> 
> 2. XeLaTeX cannot use microtypographical extensions but it may change
> in the future. Currently pdflatex or lualatex is needed.

Actually there are already experimental versions of XeTeX lying around
that have some microtypographical features, see:
http://xetex.tk/mediawiki/index.php/Main_Page

-- 
Petr Tomasek 
Jabber: but...@jabbim.cz


EA 355:001  DU DU DU DU
EA 355:002  TU TU TU TU
EA 355:003  NU NU NU NU NU NU NU
EA 355:004  NA NA NA NA NA





--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Difference between XeLaTeX and LaTeX

2011-09-22 Thread Zdenek Wagner

2011/9/21 Suresh Avvarulakshmi, Integra-PDY, IN
:
> Hi All,
>
>
>
> Are they any comparisons documents, which shows the difference between
> XeLaTeX and LaTeX typesettings?
>
I do not know but it can be said quite simply. In any case, it is
Lamport's LaTeX with extensions. The macrolanguage is the same. The
differences stem from the differences in extensions:

1. Output driver, XeLaTeX cannot create dvi, thus dvips and similar
programs cannot be used. It is important to know when including
graphics.

2. XeLaTeX cannot use microtypographical extensions but it may change
in the future. Currently pdflatex or lualatex is needed.

3. Classical LaTeX cannot work in UTF-8, only 8bit encodings are
supported. Although the inputenc package offers input in Unicode by
means of active characters, the character is composed from a series of
bytes during macro expansion. This may break certain macros. XeLaTeX
work in UTF-8 where a character is a character.

4. Classical LaTeX has no direct support for non-latin scripts.
Preprocessors are usually needed. I am aware of a preprocessor for
Velthuis encoding for Davanagari, Gurmukhi and Bengali. I am not aware
of any support for Dravidian scripts. On the contrary, XeLaTeX works
with these scripts directly.

5. Classical LaTeX can only work with TeX fonts. If you buy a font,
you have to create TFM and FD, you have to select an encoding known by
LateX. If it is an OpenType font, you have to convert it to (possibly
a searies of) type1 fonts, OpenType features will be unavailable. With
XeLaTeX or lualatex you just install the font in your OS and it can be
used as such, Opentype features can be utiized.

6. Since non-TeX fonts can be used and vendors do not care on
portability, it no longer holds that the same source document will be
typeset exactly the same way anywhere in the world or at any time. It
can be a problem if you have to share and store documents (unless you
are sure that exactly the same version of fonts is used) but you need
not care if you just want to produce PDF once and it will never change
in the future. (This is the philosophy of the Prague Bulletin of
Mathematical Linguistics, per definition the right PDF is that typeset
by the editors, they after reviews and proofs create a PDF, have it
printed, put it to the web and this is the final version that will
never change).

Most packages deal with macros, not with the particular engine/output
driver. You can use them no matter whether you use pdflatex, lualatex,
classical LaTeX with dvips or XeLaTeX. Other packages are able to
detect the engine/driver and adapt itself. Thus the only difference
from the user's point of view is the font/script issue.

Hope this helps.
>
>
> Thanks,
>
> Suresh
>
> This email and any accompanying attachments is for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. Any unauthorized review, use, disclosure, distribution, or
> copying is strictly prohibited. If you are not the intended recipient of
> this communication or received the email by mistake, please notify the
> sender and destroy all copies. Integra Software Services Pvt Ltd. reserves
> the right, subject to applicable local law, to monitor and review the
> content of any electronic message or information sent to or from its company
> allotted employee email address/ID without informing the sender or recipient
> of the message.
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>
>



-- 
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

2011-09-22 Thread VAFA KHALIGHI

By the way, I do not know why you are using ednotes.sty. If it is because of
footnote support, bidi package also allows you to do paragraph footnotes.
For more details, see bidi manual. ednotes is not supported by bidi and its
use together with bidi should be avoided.

On Thu, Sep 22, 2011 at 5:16 PM, VAFA KHALIGHI  wrote:

> I could not be bothered looking through lineno.sty to see what setups they
> have so this is another quick/dirty fix. The problem is that in the
> definition of \MakeLineNo, they use \sbox, \sbox itself uses \s...@color.bidi 
> changes the definition of \set@colorwhen color/xcolor package is loaded such 
> that in the definition of \sbox at
> the beginning of \hbox, you get \beginR, and at the end of \hbox, you get
> \endR, that is, it makes \hbox and consequently \sbox RTL in RTL mode.
> lineno setup for right linenumbers expect that \hbox or \sbox to be an LTR
> one. Well, it can be RTL but you need to reverse the process (putting
> \hskips, etc) I did not have time to look through the whole lineno.sty so
> instead I used \setbox instead \sbox so it fixes the problem. Replace the
> previously given code by this one:
>
> \makeatletter
>
> \@ifpackageloaded{color}{%
>
> \def\MakeLineNo{%
>
> \@LN@maybe@normalLineNumber % v4.31
>
> \boxmaxdepth\maxdimen\setbox\z@\vbox{\unvbox\@cclv}%
>
> \@tempdima\dp\z@ \unvbox\z@
>
> \setbox\@tempboxa=\hbox to \z@{\makeLineNumber}%
>
> \stepLineNumber
>
> \ht\@tempboxa\z@ \@LN@depthbox
>
> \@LN@do@vadjusts
>
> \count@\lastpenalty
>
> \ifnum\outputpenalty=-\linenopenaltypar
>
> \ifnum\count@=\z@ \else
>
> \xdef\@LN@parpgbrk{%
>
> \penalty\the\count@
>
> \global\let\noexpand\@LN@parpgbrk
>
> \noexpand\@LN@screenoff@pen}% v4.4
>
> \fi
>
> \else
>
> \@tempcnta\outputpenalty
>
> \advance\@tempcnta -\linenopenalty
>
> \penalty \ifnum\count@<\@tempcnta \@tempcnta \else \count@ \fi
>
> \fi
>
> }}{}
>
> \makeatother
>
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

2011-09-22 Thread VAFA KHALIGHI

I could not be bothered looking through lineno.sty to see what setups they
have so this is another quick/dirty fix. The problem is that in the
definition of \MakeLineNo, they use \sbox, \sbox itself uses
\s...@color.bidi changes the definition of \set@colorwhen color/xcolor
package is loaded such that in the definition of \sbox at
the beginning of \hbox, you get \beginR, and at the end of \hbox, you get
\endR, that is, it makes \hbox and consequently \sbox RTL in RTL mode.
lineno setup for right linenumbers expect that \hbox or \sbox to be an LTR
one. Well, it can be RTL but you need to reverse the process (putting
\hskips, etc) I did not have time to look through the whole lineno.sty so
instead I used \setbox instead \sbox so it fixes the problem. Replace the
previously given code by this one:

 \makeatletter

\@ifpackageloaded{color}{%

\def\MakeLineNo{%

\@LN@maybe@normalLineNumber % v4.31

\boxmaxdepth\maxdimen\setbox\z@\vbox{\unvbox\@cclv}%

\@tempdima\dp\z@ \unvbox\z@

\setbox\@tempboxa=\hbox to \z@{\makeLineNumber}%

\stepLineNumber

\ht\@tempboxa\z@ \@LN@depthbox

\@LN@do@vadjusts

\count@\lastpenalty

\ifnum\outputpenalty=-\linenopenaltypar

\ifnum\count@=\z@ \else

\xdef\@LN@parpgbrk{%

\penalty\the\count@

\global\let\noexpand\@LN@parpgbrk

\noexpand\@LN@screenoff@pen}% v4.4

\fi

\else

\@tempcnta\outputpenalty

\advance\@tempcnta -\linenopenalty

\penalty \ifnum\count@<\@tempcnta \@tempcnta \else \count@ \fi

\fi

}}{}

\makeatother


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] Difference between XeLaTeX and LaTeX

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

Re: [XeTeX] Problem using bidi with hyperref and amsart

[XeTeX] Xelatex crash on OpenSolaris

[XeTeX] Problem using bidi with hyperref and amsart

[XeTeX] Problem using bidi with hyperref and amsart

Re: [XeTeX] Difference between XeLaTeX and LaTeX

Re: [XeTeX] Difference between XeLaTeX and LaTeX

Re: [XeTeX] Difference between XeLaTeX and LaTeX

Re: [XeTeX] Difference between XeLaTeX and LaTeX

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

Re: [XeTeX] Compatibility issues with ednotes and pstricks or TikZ

13 matches

Site Navigation

Mail list logo

Footer information