[XeTeX] Xelatex+Tamil+English

[Sengottuvel]

Dear all,

  I was create the Tamil document using xelatex. I got the output.   In that
Tamil document some of the words are English in that words are comes
boxes,how to solve this problem.
 Which font should use for both Tamil and English.,.,


with regards,
T.Sengottuvel


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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Shrisha Rao]

El dic 20, 2010, a las 8:52 p.m., Dominik Wujastyk escribió:

> I fail to understand your point.  Pre-modern mathematics from South Asia is 
> almost all written in Sanskrit.  

But not written in modern algebraic/arithmetic/set-theoretic notation; it 
contains Sanskrit equivalents of statements like "the square on the hypotenuse 
is equal to the sum of the squares on the other two sides."

> If you edit and publish one of these works - as many do - you need the math 
> capabilities of TeX.  Hayashi's edition of the Bakhshali MS contains both an 
> edition of the Sanskrit text from the codex unicus and a translation of it 
> into English.  Both parts of Hayashi's work used TeX's math capabilities 
> extensively.  Most editions are like this.

These would count as contemporary translations of Sanskrit works, or 
presentations of math from Sanskrit works, which I already mentioned.

Regards,

Shrisha Rao

> D
> 
> On 20 December 2010 15:43, Shrisha Rao  wrote:
> El dic 20, 2010, a las 8:02 p.m., Dominik Wujastyk escribió:
> 
> > Actually, the famous edition of the Sanskrit Bakhshali manuscript, on 
> > medieval Indian mathematics, by Takao Hayashi was typset entirely in TeX.  
> > So was the recent book, History of Indian Mathematics, by Kim Plofker.
> 
> I did not know that, but it makes sense.
> 
> > In fact, TeX is the tool of choice for most people working at the forefront 
> > of the history of Indian mathematics.
> 
> TeX is most common for people writing any kind of mathematics, including 
> engineers, physicists, and computer scientists.  However, my point was 
> slightly different -- in a text that is almost entirely in Sanskrit (not a 
> contemporary translation of a Sanskrit work or a work presented mathematics 
> originally found in a Sanskrit text), there is unlikely to be much use for 
> math notation.
> 
> Regards,
> 
> Shrisha Rao
> 
> > Dominik
> >
> >
> > On 20 December 2010 15:28, Shrisha Rao  wrote:
> > El dic 20, 2010, a las 5:05 p.m., Ulrike Fischer escribió:
> >
> > > Am Mon, 20 Dec 2010 16:55:07 +0530 schrieb Shrisha Rao:
> > >
> > >> I tried inserting the \catcode`\^=11, etc., right after
> > >> \begin{document} and that seems to work.
> > >
> > > As long as you don't use ^ in math. In general it is better to keep
> > > such changes local.
> >
> > Not very likely that math mode superscript/power notation will need to be 
> > used in Sanskrit texts, but I see your point.
> >
> > Regards,
> >
> > Shrisha Rao
> >
> > > Ulrike Fischer
> >
> >
> >
> >
> > --
> > Subscriptions, Archive, and List information, etc.:
> >  http://tug.org/mailman/listinfo/xetex
> >
> >
> >
> > --
> > Subscriptions, Archive, and List information, etc.:
> >  http://tug.org/mailman/listinfo/xetex
> 
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
> 
> 
> 
> --
> 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] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Shrisha Rao]

El dic 20, 2010, a las 9:26 p.m., A u escribió:

> thats about the best I can tell. People reading Sanskrit in Roman script is 
> the main source of mispronunciation.

Even if we condemn use of the Roman script for the sake of argument (which 
itself is a serious stretch, IMHO), there is plenty of mispronunciation by 
people who read and write Devanagari and Kannada also -- for instance, a 
Devanagari reader (whose native language may be Hindi) is likely to take out 
the final ह्रस्व vowel at the end of the word, so that राम is mispronounced as 
राम् as with Hindi words.  A Kannada reader is likely to insert a दीर्घ vowel 
in place of the ह्रस्व in many cases; in fact because such reading of final 
ह्रस्व as दीर्घ is common, many words that actually need a final दीर्घ are 
incorrectly spelled without it, e.g., ತಾರಾ (तारा) is written as ತಾರ (तार) 
instead.  

> anyway it's individuals choice. 

In a sense, it is not just an individual choice to present Sanskrit in scripts 
other than Devanagari -- the quantity of Sanskrit published in other scripts 
(either historically or just in the present day) is not small.

> Thats why गङ्गे is read as Ganges (गन्जिस) 

Such distortions occur with other scripts also.  I don't think IAST in 
particular is any worse for this than any other system.

> Good luck

Thanks.

Regards,

Shrisha Rao




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

[XeTeX] pdf_link_obj(): passed invalid object.

[Jérôme Etévé]

Hello xetex experts :)

I'm sure It's not the first time you see that, but here we go again:

I use xetex (xelatex) to generate document that can include other pdf
files (using the package pdfpages) and when I include some documents,
the rendering of my latex file crashes with an error like that:

** WARNING ** Could not find any valid object.
** WARNING ** Could not find a value in dictionary object.
** WARNING ** Didn't find "endobj".
** ERROR ** pdf_link_obj(): passed invalid object.

I tried rendering first the xdv file, then rendering it in pdf
specifying a more recent version of pdf:

$ xelatex -no-pdf latexdoc.tex
# Then
$ xdvipdfmx -V5 latexdoc.xdv

But it didn't solve the issue.

Unfortunately I cannot quality control the pdf's entering the
application, and there will always be some dodgy ones around, so it'd
be great if there's a way to make xdvipdfmx more robust against crap
user pdf's.

Thanks for any help!

Jerome.

-- 
Jerome Eteve.

http://libsquare.net


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

Re: [XeTeX] Auto Font and Language Package in XeTeX

[Michiel Kamermans]

On 12/20/2010 8:13 AM, Yves Codet wrote:

Hello.

I couldn't try your package, both links seem to be broken but I found the 
documentation here:
http://projects.nihongoresources.com/downloadables/ucharclasses.pdf
According to what I read, if I want to use polyglossia to load hyphenation 
patterns, I can say:
\setTransitions{Devanagari}{\begin{sanskrit}}{\end{sanskrit}}
But how can I do if I want to use the \textsanskrit{one_word_in_Sanskrit} 
command?
   


You can disable ucharclass for a stretch of text with \uccoff and \uccon

- Mike


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

Re: [XeTeX] Externalizing PGF graphics - page size incorrect

[Alan Munn]

On Dec 20, 2010, at 1:59 PM, Wesley Griffin wrote:


I am trying to externalize PGF graphics and it does not appear that
xelatex sets the page size correctly. The following code works (i.e.
creates a PDF sized to the graphic):

% pdflatex --jobname=fig1 pgf.tex

while using xelatex gives the following warning and creates a full  
8.5x11 PDF:


% xelatex --jobname=fig1 pgf.tex

Package pgf Warning: Your graphic driver pgfsys-xetex.def does not
support papersize. This warning is given only once on input line 14.

Is there anything I can do?


Update your distribution?  I don't get the warning, and both files are  
image-sized.


Here's the output of \listfiles

-Alan


 *File List*
 article.cls2007/10/19 v1.4h Standard LaTeX document class
  size10.clo2007/10/19 v1.4h Standard LaTeX file (size option)
tikz.sty2010/10/13 v2.10 (rcs-revision 1.76)
 pgf.sty2008/01/15 v2.10 (rcs-revision 1.12)
  pgfrcs.sty2010/10/25 v2.10 (rcs-revision 1.24)
everyshi.sty2001/05/15 v3.00 EveryShipout Package (MS)
  pgfrcs.code.tex
 pgfcore.sty2010/04/11 v2.10 (rcs-revision 1.7)
graphicx.sty1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR)
  keyval.sty1999/03/16 v1.13 key=value parser (DPC)
graphics.sty2009/02/05 v1.0o Standard LaTeX Graphics (DPC,SPQR)
trig.sty1999/03/16 v1.09 sin cos tan (DPC)
graphics.cfg2010/04/23 v1.9 graphics configuration of TeX Live
   xetex.def2009/11/22 v0.94 LaTeX color/graphics driver for  
XeTeX (RRM/JK)


  pgfsys.sty2010/06/30 v2.10 (rcs-revision 1.37)
  pgfsys.code.tex
pgfsyssoftpath.code.tex2008/07/18  (rcs-revision 1.7)
pgfsysprotocol.code.tex2006/10/16  (rcs-revision 1.4)
  xcolor.sty2007/01/21 v2.11 LaTeX color extensions (UK)
   color.cfg2007/01/18 v1.5 color configuration of teTeX/TeXLive
 pgfcore.code.tex
pgfcomp-version-0-65.sty2007/07/03 v2.10 (rcs-revision 1.7)
pgfcomp-version-1-18.sty2007/07/23 v2.10 (rcs-revision 1.1)
  pgffor.sty2010/03/23 v2.10 (rcs-revision 1.18)
 pgfkeys.sty
 pgfkeys.code.tex
  pgffor.code.tex
tikz.code.tex



Thanks,
Wes

-

\documentclass{article}
\usepackage{tikz}

\pgfrealjobname{pgf}
\begin{document}

\beginpgfgraphicnamed{fig1}
\begin{tikzpicture}
\fill (0,0) circle (1cm);
\end{tikzpicture}
\endpgfgraphicnamed

\end{document}


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


--
Alan Munn
am...@gmx.com






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

[XeTeX] Externalizing PGF graphics - page size incorrect

[Wesley Griffin]

I am trying to externalize PGF graphics and it does not appear that
xelatex sets the page size correctly. The following code works (i.e.
creates a PDF sized to the graphic):

% pdflatex --jobname=fig1 pgf.tex

while using xelatex gives the following warning and creates a full 8.5x11 PDF:

% xelatex --jobname=fig1 pgf.tex

Package pgf Warning: Your graphic driver pgfsys-xetex.def does not
support papersize. This warning is given only once on input line 14.

Is there anything I can do?

Thanks,
Wes

-

\documentclass{article}
\usepackage{tikz}

\pgfrealjobname{pgf}
\begin{document}

\beginpgfgraphicnamed{fig1}
\begin{tikzpicture}
\fill (0,0) circle (1cm);
\end{tikzpicture}
\endpgfgraphicnamed

\end{document}


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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Dominik Wujastyk]

>
> Thats why गङ्गे is read as Ganges (गन्जिस)
>

This has nothing to do with contemporary systems of transliteration, and
everything to do with historical phonology and language interaction from the
17th onwards (see the OED).

Reading Sanskrit from Latin transliteration can be a problem, but needn't
be.  It just depends on how well the students are taught.  My students move
between scripts comfortably, and their pronunciation is quite good.   Some
of the most incomprehensible Sanskrit pronunciation I've ever heard has been
by pandits from Bengal, where Bengali-language pronunciation of vowels,
sibilants and some other consonants (j), is very hard for non-Bengalis to
decipher.  This again has little to do with script, but is a phonological
phenomenon.

DW


On 20 December 2010 16:56, A u  wrote:

> thats about the best I can tell. People reading Sanskrit in Roman script is
> the main source of mispronunciation. anyway it's individuals choice.
> Thats why गङ्गे is read as Ganges (गन्जिस)
> Good luck
>
> On Mon, Dec 20, 2010 at 9:21 AM, Shrisha Rao  wrote:
>
>> El dic 20, 2010, a las 7:08 p.m., A u escribió:
>>
>> > I don't know why are you using itrans, typing in Hindi or anyother
>> language directly works just fine. I use ubuntu and TeXworks, and it allows
>> me to directly
>> > type in Hindi using itranks encoder and XeLaTeX.
>> >
>> > I am attaching a sample document i Hope this helps.
>>
>> Thank you, but there are a few good reasons not to do it that way:
>>
>> (1) there are many existing documents coded using ITRANS that would need
>> to be recoded using UTF-8;
>>
>> (2) many people are not comfortable entering or viewing UTF-8, and prefer
>> ASCII; and
>>
>> (3) it is easy to produce outputs in multiple scripts from the same base
>> coding, by doing it my way (there is actually great demand for this, as many
>> people want to read Sanskrit texts in Kannada or IAST/Roman scripts rather
>> than in Devanagari as one might presume) -- not so if a particular script
>> has already been used to enter the text.
>>
>> Regards,
>>
>> Shrisha Rao
>>
>> > Aku
>>
>>
>>
>>
>>
>> --
>> Subscriptions, Archive, and List information, etc.:
>>  http://tug.org/mailman/listinfo/xetex
>>
>
>
>
>
> --
> 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] Auto Font and Language Package in XeTeX

[Khaled Hosny]

On Mon, Dec 20, 2010 at 07:45:21AM -0800, Michiel Kamermans wrote:
> 
> >I long had that on my todo list, but I'm yet to figure out a proper user
> >interface for it; one needs to take care of different font styles,
> >optical sizes etc. e.g. English ARABIC {\it english ARABIC} should work
> >and get the Arabic text assigned the proper italic font and so on.
> >
> >The code at lua end is quit trivial, once the script->font mapping is
> >defined which is actually the tricky part.
> 
> Hmm... that sounds much more narrow than what you can do with
> XeTeX's intercharclass behaviour, and much more like just
> font-switching.

I'm not sure what XeTeX's intercharclass can do (I never understood it
to be honest, it just looked too limited to me).

> I would imagine that something like what XeTeX
> offers makes it much easier to say "if arabic character from non
> arabic, RTL and font switch (and whatever else is requested by the
> user)".

Actually Jonathan said before intercharclass can't be used to do
bidirectional switching, while in luatex you have direct access to node
list and I actually have an implementation of Unicode bidi algorithm
written entirely in lua[1] (I usually use it with ConTeXt, so the LaTeX
part is not very well tested at the moment).

> But perhaps LuaTeX wants to do these two things separately,
> which would of course be equally fine, just requiring a different
> approach in terms of packageness

Font switching and text directionality are two separate issues and even
and can't be done in one step; bidi is very tricky and not just
Arabic==RTL and English==LTR, even font switching can be a bit tricky
when you consider characters that don't belong to specific script (like
most punctuation marks).

[1] http://github.com/khaledhosny/luadirections

Regards,
 Khaled

-- 
 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer


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

Re: [XeTeX] Auto Font and Language Package in XeTeX

[Yves Codet]

Hello.

I couldn't try your package, both links seem to be broken but I found the 
documentation here:
http://projects.nihongoresources.com/downloadables/ucharclasses.pdf
According to what I read, if I want to use polyglossia to load hyphenation 
patterns, I can say:
\setTransitions{Devanagari}{\begin{sanskrit}}{\end{sanskrit}}
But how can I do if I want to use the \textsanskrit{one_word_in_Sanskrit} 
command?

Kind regards,

Yves

Le 20 déc. 2010 à 12:17, Michiel Kamermans a écrit :

> 
> Alright, I finished the ucharclasses package at least to a functional degree, 
> with the project page for it at 
> http://projects.nihongoresources.com/xelatex/ucharclasses (it's been 
> submitted to CTAN, so once it's in the listing it'll be nice and easy to 
> grab).
> 
> If anyone has any improvement requests (either functionally or codewise), I'm 
> all ears. Or eyes. whichever works best, really.
> 
> Incidentally, does anyone know whether there is a LuaTeX version of the 
> XeTeXintercharclass behaviour that would let this package be rewritten for 
> LuaTeX with minimal effort?
> 
> - Mike "Pomax" Kamermans
> nihongoresources.com
> 
> 
> --
> 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] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[A u]

thats about the best I can tell. People reading Sanskrit in Roman script is
the main source of mispronunciation. anyway it's individuals choice.
Thats why गङ्गे is read as Ganges (गन्जिस)
Good luck

On Mon, Dec 20, 2010 at 9:21 AM, Shrisha Rao  wrote:

> El dic 20, 2010, a las 7:08 p.m., A u escribió:
>
> > I don't know why are you using itrans, typing in Hindi or anyother
> language directly works just fine. I use ubuntu and TeXworks, and it allows
> me to directly
> > type in Hindi using itranks encoder and XeLaTeX.
> >
> > I am attaching a sample document i Hope this helps.
>
> Thank you, but there are a few good reasons not to do it that way:
>
> (1) there are many existing documents coded using ITRANS that would need to
> be recoded using UTF-8;
>
> (2) many people are not comfortable entering or viewing UTF-8, and prefer
> ASCII; and
>
> (3) it is easy to produce outputs in multiple scripts from the same base
> coding, by doing it my way (there is actually great demand for this, as many
> people want to read Sanskrit texts in Kannada or IAST/Roman scripts rather
> than in Devanagari as one might presume) -- not so if a particular script
> has already been used to enter the text.
>
> Regards,
>
> Shrisha Rao
>
> > Aku
>
>
>
>
> --
> 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] Auto Font and Language Package in XeTeX

[Michiel Kamermans]

I long had that on my todo list, but I'm yet to figure out a proper user
interface for it; one needs to take care of different font styles,
optical sizes etc. e.g. English ARABIC {\it english ARABIC} should work
and get the Arabic text assigned the proper italic font and so on.

The code at lua end is quit trivial, once the script->font mapping is
defined which is actually the tricky part.
   


Hmm... that sounds much more narrow than what you can do with XeTeX's 
intercharclass behaviour, and much more like just font-switching. I 
would imagine that something like what XeTeX offers makes it much easier 
to say "if arabic character from non arabic, RTL and font switch (and 
whatever else is requested by the user)". But perhaps LuaTeX wants to do 
these two things separately, which would of course be equally fine, just 
requiring a different approach in terms of packageness


- Mike


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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Dominik Wujastyk]

I fail to understand your point.  Pre-modern mathematics from South Asia is
almost all written in Sanskrit.  If you edit and publish one of these works
- as many do - you need the math capabilities of TeX.  Hayashi's edition of
the Bakhshali MS contains both an edition of the Sanskrit text from the
codex unicus and a translation of it into English.  Both parts of Hayashi's
work used TeX's math capabilities extensively.  Most editions are like this.

D

On 20 December 2010 15:43, Shrisha Rao  wrote:

> El dic 20, 2010, a las 8:02 p.m., Dominik Wujastyk escribió:
>
> > Actually, the famous edition of the Sanskrit Bakhshali manuscript, on
> medieval Indian mathematics, by Takao Hayashi was typset entirely in TeX.
>  So was the recent book, History of Indian Mathematics, by Kim Plofker.
>
> I did not know that, but it makes sense.
>
> > In fact, TeX is the tool of choice for most people working at the
> forefront of the history of Indian mathematics.
>
> TeX is most common for people writing any kind of mathematics, including
> engineers, physicists, and computer scientists.  However, my point was
> slightly different -- in a text that is almost entirely in Sanskrit (not a
> contemporary translation of a Sanskrit work or a work presented mathematics
> originally found in a Sanskrit text), there is unlikely to be much use for
> math notation.
>
> Regards,
>
> Shrisha Rao
>
> > Dominik
> >
> >
> > On 20 December 2010 15:28, Shrisha Rao  wrote:
> > El dic 20, 2010, a las 5:05 p.m., Ulrike Fischer escribió:
> >
> > > Am Mon, 20 Dec 2010 16:55:07 +0530 schrieb Shrisha Rao:
> > >
> > >> I tried inserting the \catcode`\^=11, etc., right after
> > >> \begin{document} and that seems to work.
> > >
> > > As long as you don't use ^ in math. In general it is better to keep
> > > such changes local.
> >
> > Not very likely that math mode superscript/power notation will need to be
> used in Sanskrit texts, but I see your point.
> >
> > Regards,
> >
> > Shrisha Rao
> >
> > > Ulrike Fischer
> >
> >
> >
> >
> > --
> > Subscriptions, Archive, and List information, etc.:
> >  http://tug.org/mailman/listinfo/xetex
> >
> >
> >
> > --
> > Subscriptions, Archive, and List information, etc.:
> >  http://tug.org/mailman/listinfo/xetex
>
>
>
>
> --
> 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] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Ulrike Fischer]

Am Mon, 20 Dec 2010 20:13:56 +0530 schrieb Shrisha Rao:


> However, my point was slightly different -- in a text that is
> almost entirely in Sanskrit (not a contemporary translation of a
> Sanskrit work or a work presented mathematics originally found in
> a Sanskrit text), there is unlikely to be much use for math
> notation.

^ is also often used for superscripts (e.g. for footnotemarks). And
your example also changed the catcode of ~, which is used to insert
non-breaking space. But as long as only you use your code and you
pay attention to the possible conflicts, I don't see much of a
problem if you change the catcode globally.  

-- 
Ulrike Fischer 



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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Shrisha Rao]

El dic 20, 2010, a las 8:02 p.m., Dominik Wujastyk escribió:

> Actually, the famous edition of the Sanskrit Bakhshali manuscript, on 
> medieval Indian mathematics, by Takao Hayashi was typset entirely in TeX.  So 
> was the recent book, History of Indian Mathematics, by Kim Plofker.  

I did not know that, but it makes sense.

> In fact, TeX is the tool of choice for most people working at the forefront 
> of the history of Indian mathematics.

TeX is most common for people writing any kind of mathematics, including 
engineers, physicists, and computer scientists.  However, my point was slightly 
different -- in a text that is almost entirely in Sanskrit (not a contemporary 
translation of a Sanskrit work or a work presented mathematics originally found 
in a Sanskrit text), there is unlikely to be much use for math notation.

Regards,

Shrisha Rao

> Dominik
> 
> 
> On 20 December 2010 15:28, Shrisha Rao  wrote:
> El dic 20, 2010, a las 5:05 p.m., Ulrike Fischer escribió:
> 
> > Am Mon, 20 Dec 2010 16:55:07 +0530 schrieb Shrisha Rao:
> >
> >> I tried inserting the \catcode`\^=11, etc., right after
> >> \begin{document} and that seems to work.
> >
> > As long as you don't use ^ in math. In general it is better to keep
> > such changes local.
> 
> Not very likely that math mode superscript/power notation will need to be 
> used in Sanskrit texts, but I see your point.
> 
> Regards,
> 
> Shrisha Rao
> 
> > Ulrike Fischer
> 
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
> 
> 
> 
> --
> 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] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Dominik Wujastyk]

Actually, the famous edition of the Sanskrit Bakhshali manuscript, on
medieval Indian mathematics, by Takao Hayashi was typset entirely in TeX.
So was the recent book, History of Indian Mathematics, by Kim Plofker.  In
fact, TeX is the tool of choice for most people working at the forefront of
the history of Indian mathematics.

Dominik


On 20 December 2010 15:28, Shrisha Rao  wrote:

> El dic 20, 2010, a las 5:05 p.m., Ulrike Fischer escribió:
>
> > Am Mon, 20 Dec 2010 16:55:07 +0530 schrieb Shrisha Rao:
> >
> >> I tried inserting the \catcode`\^=11, etc., right after
> >> \begin{document} and that seems to work.
> >
> > As long as you don't use ^ in math. In general it is better to keep
> > such changes local.
>
> Not very likely that math mode superscript/power notation will need to be
> used in Sanskrit texts, but I see your point.
>
> Regards,
>
> Shrisha Rao
>
> > Ulrike Fischer
>
>
>
>
> --
> 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] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Shrisha Rao]

El dic 20, 2010, a las 5:05 p.m., Ulrike Fischer escribió:

> Am Mon, 20 Dec 2010 16:55:07 +0530 schrieb Shrisha Rao:
> 
>> I tried inserting the \catcode`\^=11, etc., right after
>> \begin{document} and that seems to work.
> 
> As long as you don't use ^ in math. In general it is better to keep
> such changes local. 

Not very likely that math mode superscript/power notation will need to be used 
in Sanskrit texts, but I see your point.

Regards,

Shrisha Rao

> Ulrike Fischer 




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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Shrisha Rao]

El dic 20, 2010, a las 7:08 p.m., A u escribió:

> I don't know why are you using itrans, typing in Hindi or anyother language 
> directly works just fine. I use ubuntu and TeXworks, and it allows me to 
> directly 
> type in Hindi using itranks encoder and XeLaTeX. 
> 
> I am attaching a sample document i Hope this helps. 

Thank you, but there are a few good reasons not to do it that way:

(1) there are many existing documents coded using ITRANS that would need to be 
recoded using UTF-8;

(2) many people are not comfortable entering or viewing UTF-8, and prefer 
ASCII; and

(3) it is easy to produce outputs in multiple scripts from the same base 
coding, by doing it my way (there is actually great demand for this, as many 
people want to read Sanskrit texts in Kannada or IAST/Roman scripts rather than 
in Devanagari as one might presume) -- not so if a particular script has 
already been used to enter the text.

Regards,

Shrisha Rao

> Aku




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

Re: [XeTeX] Auto Font and Language Package in XeTeX

[Khaled Hosny]

On Mon, Dec 20, 2010 at 12:59:45PM +0100, Paul Isambert wrote:
> Selon Arthur Reutenauer :
> 
> > > Incidentally, does anyone know whether there is a LuaTeX version of the
> > > XeTeXintercharclass behaviour that would let this package be rewritten
> > > for LuaTeX with minimal effort?
> >
> >   Paul Isambert has written code to that effect, but I'm not sure he has
> > made it into a package yet.
> 
> 
> I haven't indeed. It's quite low on my priority list, all the more as 
> mimicking
> interchartoks isn't totally possible in LuaTeX, although the most significant
> part of the mechanism can be reproduced.
> 
> Anyway judging from what I understand Michiel's package does, an
> interchartoks-like code in LuaTeX won't work, because it'll really be an
> ``inter-node'' mechanism, and (glyph) nodes already have their fonts attached 
> to
> them, whereas the package is supposed to change fonts.
> 
> The solution would rather be: get the nodes as soon as possible, e.g. in the
> ligaturing callback, and set the font number for each node according to its
> unicode value. That means no such thing as "\fontspec{A font}" is usable here;
> instead, you must go low-level and grab the fonts by their numbers. Such 
> numbers
> can be retrieved from the control sequences passed to the \font primitive with
> Lua's font.id(). An extension to fontspec would be infinitely simpler 
> than
> an independent package.

I long had that on my todo list, but I'm yet to figure out a proper user
interface for it; one needs to take care of different font styles,
optical sizes etc. e.g. English ARABIC {\it english ARABIC} should work
and get the Arabic text assigned the proper italic font and so on.

The code at lua end is quit trivial, once the script->font mapping is
defined which is actually the tricky part.

Regards,
 Khaled

-- 
 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer


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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[A u]

I don't know why are you using itrans, typing in Hindi or anyother language
directly works just fine. I use ubuntu and TeXworks, and it allows me to
directly
type in Hindi using itranks encoder and XeLaTeX.

I am attaching a sample document i Hope this helps.
Aku

On Mon, Dec 20, 2010 at 6:25 AM, Shrisha Rao  wrote:

> El dic 20, 2010, a las 4:18 p.m., Shrisha Rao escribió:
>
> > El dic 20, 2010, a las 3:56 p.m., Ulrike Fischer escribió:
> >
> >> Your problem has nothing to do with fontspec. Your commands \dev etc
> >> change catcodes. But when you use them in the argument of a command
> >> this changes are too late. The catcodes are already fixed.
> >>
> >> Change the catcodes before the \chapter* command.
> >
> > Thanks, but the only way to do that would be to have \chapter*, enclosed
> in \dev{...}, which does not seem to work (already tried that with no
> success).  So I'm not sure what you mean.  What precisely would you do
> instead?
>
> I tried inserting the \catcode`\^=11, etc., right after \begin{document}
> and that seems to work.  Thanks again.
>
> Regards,
>
> Shrisha Rao
>
> > Regards,
> >
> > Shrisha Rao
> >
> >> Ulrike Fischer
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>


How 2 Create Boxes.tex
Description: TeX document


How 2 Create Boxes.pdf
Description: Adobe PDF document


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

Re: [XeTeX] Auto Font and Language Package in XeTeX

[Paul Isambert]

Selon Arthur Reutenauer :

> > Incidentally, does anyone know whether there is a LuaTeX version of the
> > XeTeXintercharclass behaviour that would let this package be rewritten
> > for LuaTeX with minimal effort?
>
>   Paul Isambert has written code to that effect, but I'm not sure he has
> made it into a package yet.


I haven't indeed. It's quite low on my priority list, all the more as mimicking
interchartoks isn't totally possible in LuaTeX, although the most significant
part of the mechanism can be reproduced.

Anyway judging from what I understand Michiel's package does, an
interchartoks-like code in LuaTeX won't work, because it'll really be an
``inter-node'' mechanism, and (glyph) nodes already have their fonts attached to
them, whereas the package is supposed to change fonts.

The solution would rather be: get the nodes as soon as possible, e.g. in the
ligaturing callback, and set the font number for each node according to its
unicode value. That means no such thing as "\fontspec{A font}" is usable here;
instead, you must go low-level and grab the fonts by their numbers. Such numbers
can be retrieved from the control sequences passed to the \font primitive with
Lua's font.id(). An extension to fontspec would be infinitely simpler than
an independent package.

Best,
Paul


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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Ulrike Fischer]

Am Mon, 20 Dec 2010 16:55:07 +0530 schrieb Shrisha Rao:


> I tried inserting the \catcode`\^=11, etc., right after
> \begin{document} and that seems to work.

As long as you don't use ^ in math. In general it is better to keep
such changes local. 


-- 
Ulrike Fischer 



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

Re: [XeTeX] Auto Font and Language Package in XeTeX

[Arthur Reutenauer]

> Incidentally, does anyone know whether there is a LuaTeX version of the  
> XeTeXintercharclass behaviour that would let this package be rewritten  
> for LuaTeX with minimal effort?

  Paul Isambert has written code to that effect, but I'm not sure he has
made it into a package yet.

Arthur


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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Shrisha Rao]

El dic 20, 2010, a las 4:18 p.m., Shrisha Rao escribió:

> El dic 20, 2010, a las 3:56 p.m., Ulrike Fischer escribió:
> 
>> Your problem has nothing to do with fontspec. Your commands \dev etc
>> change catcodes. But when you use them in the argument of a command
>> this changes are too late. The catcodes are already fixed. 
>> 
>> Change the catcodes before the \chapter* command. 
> 
> Thanks, but the only way to do that would be to have \chapter*, enclosed in 
> \dev{...}, which does not seem to work (already tried that with no success).  
> So I'm not sure what you mean.  What precisely would you do instead?

I tried inserting the \catcode`\^=11, etc., right after \begin{document} and 
that seems to work.  Thanks again.

Regards,

Shrisha Rao

> Regards,
> 
> Shrisha Rao
> 
>> Ulrike Fischer 




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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Ulrike Fischer]

Am Mon, 20 Dec 2010 16:18:14 +0530 schrieb Shrisha Rao:

> El dic 20, 2010, a las 3:56 p.m., Ulrike Fischer escribió:
> 
>> Your problem has nothing to do with fontspec. Your commands \dev etc
>> change catcodes. But when you use them in the argument of a command
>> this changes are too late. The catcodes are already fixed. 
>> 
>> Change the catcodes before the \chapter* command. 
 
> Thanks, but the only way to do that would be to have \chapter*,
> enclosed in \dev{...}, which does not seem to work (already tried
> that with no success).  So I'm not sure what you mean.  What
> precisely would you do instead?

\begingroup
\catcode ..=.. %(or simply  \dev
\chapter ...
\addcontentsline ...

\endgroup 

or

\begingroup
\dev
\gdef\myarg{kR^ishhNaM vande jagadgurum.h}
\endgroup

\chapter*{\dev myarg}

-- 
Ulrike Fischer 



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

Re: [XeTeX] Auto Font and Language Package in XeTeX

[Michiel Kamermans]

Alright, I finished the ucharclasses package at least to a functional 
degree, with the project page for it at 
http://projects.nihongoresources.com/xelatex/ucharclasses (it's been 
submitted to CTAN, so once it's in the listing it'll be nice and easy to 
grab).


If anyone has any improvement requests (either functionally or 
codewise), I'm all ears. Or eyes. whichever works best, really.


Incidentally, does anyone know whether there is a LuaTeX version of the 
XeTeXintercharclass behaviour that would let this package be rewritten 
for LuaTeX with minimal effort?


- Mike "Pomax" Kamermans
nihongoresources.com


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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Shrisha Rao]

El dic 20, 2010, a las 3:56 p.m., Ulrike Fischer escribió:

> Your problem has nothing to do with fontspec. Your commands \dev etc
> change catcodes. But when you use them in the argument of a command
> this changes are too late. The catcodes are already fixed. 
> 
> Change the catcodes before the \chapter* command. 

Thanks, but the only way to do that would be to have \chapter*, enclosed in 
\dev{...}, which does not seem to work (already tried that with no success).  
So I'm not sure what you mean.  What precisely would you do instead?

Regards,

Shrisha Rao
 
> Ulrike Fischer 




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

Re: [XeTeX] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Dominik Wujastyk]

To call the Velthuis input scheme "faulty" is to misunderstand its purpose.
It is not faulty.   ITRANS too has several merits that are relevant even for
someone who can type using inscript.

The many fonts, input systems, and post-processors used for South Asian
languages all have merits as well as limitations, and are best understood in
the historical context of the computer platforms existing at the time of
their creation.

Dominik



On 20 December 2010 06:28, Duvvuri Venu Gopal <
venugopal_duvv...@rediffmail.com> wrote:

> It appears you already know how to type in Hindi using inscript keyboard.
> Then why using itrans package?
>
> The input method developed originally by Velthuis is faulty. Because of
> that before running TeX it has to be postprocessed - because he used many
> restricted characters for inputing hindi characters.
>
> In this respect the Telugu TeX and Kannada TeX (which is based on Telugu
> TeX) input methods are better as they do not use these characters.
>
> Venu Gopal
>
> I use OpenOffice 3.0!
> Do you!!
>
>
>
>
> 
>
>
> --
> 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] Fontspec mappings causing errors in ToC/chapter-headings in memoir class documents

[Ulrike Fischer]

Am Sun, 19 Dec 2010 15:27:58 +0530 schrieb Shrisha Rao:

> Greetz.
 
> I find that when a Roman-based fontspec mapping is used in a
> chapter title or a ToC entry in a memoir document, it causes an
> error if the input text (not the output) offends (Xe)TeX in some
> way; thus, `kR^ishhNaM vande jagadgurum.h' (which should simply
> be rendered as कृष्णं वन्दे जगद्गुरुम्) causes a problem because
> (Xe)TeX thinks `R^i' can only occur in math mode.  Other input
> texts do not seem to cause such a problem, and the same string
> also causes no problem inside a chapter (only in chapter titles
> and ToC entries).

Your problem has nothing to do with fontspec. Your commands \dev etc
change catcodes. But when you use them in the argument of a command
this changes are too late. The catcodes are already fixed. 

Change the catcodes before the \chapter* command. 

-- 
Ulrike Fischer 



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