Re: [XeTeX] XeLateX problem after updating

2011-08-14 Thread Neal Delmonico
Never mind.  I think I have figured it out.  There is one unicode  
candrabindu code for the Devanagari (0910) and another for the Roman  
(0310).  The Roman code does not work in the Devanagari.


Best

Neal

On Sun, 14 Aug 2011 12:46:28 -0500, Neal Delmonico  
 wrote:


As an addendum to my last message, here is the code I am working with  
that produces the flawed output.  It is from the Bhagavadgita 4.39:



\skt{\large śraddhāvā̐llabhate jñānaṃ tatparaḥ saṃyatendriyaḥ|}\\
\skt{\large jñānaṃ labdhvā parāṃ śāntimacireṇādhigacchati|| 39||}

śraddhāvā̐l labhate jñānaṃ tatparaḥ saṃyatendriyaḥ|\\
jñānaṃ labdhvā parāṃ śāntim acireṇādhigacchati|| 39||


Thanks.

Neal


On Sun, 14 Aug 2011 12:25:25 -0500, Neal Delmonico  
 wrote:


Thanks.  I scrapped the old system (it seems like 2011 files had been  
written to that 2009 directory somehow in my previous tlmgr updates)  
and downloaded and installed the new 2011 one (into  
/usr/local/texlive/2011).  Everything seems to be working now.


I have one more question for the Sanskritists on the list.  How does  
one get the candra-bindu to work with a preceding long a? I inserted  
the unicode character for candrabindu into its proper place in the  
Roman transliteration but when that gets converted into Devanagari by  
RomDev a blank square appears in place where candrabindu should be.   
What am I doing wrong?


Thanks again.

best

Neal

On Sat, 13 Aug 2011 13:40:23 -0500, Peter Dyballa  
 wrote:




Am 13.08.2011 um 20:01 schrieb Neal Delmonico:


Any suggestions?


Please use the updated version! Not the old stuff from 2009.

--
Greetings

  Pete

When you meet a master swordsman,
show him your sword.
When you meet a man who is not a poet,
do not show him your poem.
– Rinzai, ninth century Zen master




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









--
Using Opera's revolutionary email client: http://www.opera.com/mail/



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


Re: [XeTeX] XeLateX problem after updating

2011-08-14 Thread Neal Delmonico
As an addendum to my last message, here is the code I am working with that  
produces the flawed output.  It is from the Bhagavadgita 4.39:



\skt{\large śraddhāvā̐llabhate jñānaṃ tatparaḥ saṃyatendriyaḥ|}\\
\skt{\large jñānaṃ labdhvā parāṃ śāntimacireṇādhigacchati|| 39||}

śraddhāvā̐l labhate jñānaṃ tatparaḥ saṃyatendriyaḥ|\\
jñānaṃ labdhvā parāṃ śāntim acireṇādhigacchati|| 39||


Thanks.

Neal


On Sun, 14 Aug 2011 12:25:25 -0500, Neal Delmonico  
 wrote:


Thanks.  I scrapped the old system (it seems like 2011 files had been  
written to that 2009 directory somehow in my previous tlmgr updates) and  
downloaded and installed the new 2011 one (into  
/usr/local/texlive/2011).  Everything seems to be working now.


I have one more question for the Sanskritists on the list.  How does one  
get the candra-bindu to work with a preceding long a? I inserted the  
unicode character for candrabindu into its proper place in the Roman  
transliteration but when that gets converted into Devanagari by RomDev a  
blank square appears in place where candrabindu should be.  What am I  
doing wrong?


Thanks again.

best

Neal

On Sat, 13 Aug 2011 13:40:23 -0500, Peter Dyballa   
wrote:




Am 13.08.2011 um 20:01 schrieb Neal Delmonico:


Any suggestions?


Please use the updated version! Not the old stuff from 2009.

--
Greetings

  Pete

When you meet a master swordsman,
show him your sword.
When you meet a man who is not a poet,
do not show him your poem.
– Rinzai, ninth century Zen master




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






--
Using Opera's revolutionary email client: http://www.opera.com/mail/



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


Re: [XeTeX] XeLateX problem after updating

2011-08-14 Thread Neal Delmonico
Thanks.  I scrapped the old system (it seems like 2011 files had been  
written to that 2009 directory somehow in my previous tlmgr updates) and  
downloaded and installed the new 2011 one (into /usr/local/texlive/2011).   
Everything seems to be working now.


I have one more question for the Sanskritists on the list.  How does one  
get the candra-bindu to work with a preceding long a? I inserted the  
unicode character for candrabindu into its proper place in the Roman  
transliteration but when that gets converted into Devanagari by RomDev a  
blank square appears in place where candrabindu should be.  What am I  
doing wrong?


Thanks again.

best

Neal

On Sat, 13 Aug 2011 13:40:23 -0500, Peter Dyballa   
wrote:




Am 13.08.2011 um 20:01 schrieb Neal Delmonico:


Any suggestions?


Please use the updated version! Not the old stuff from 2009.

--
Greetings

  Pete

When you meet a master swordsman,
show him your sword.
When you meet a man who is not a poet,
do not show him your poem.
– Rinzai, ninth century Zen master




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



--
Using Opera's revolutionary email client: http://www.opera.com/mail/



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


Re: [XeTeX] Trouble with the new Xetex

2011-08-14 Thread Ulrike Fischer
Am Sat, 13 Aug 2011 19:56:33 +0200 schrieb Mojca Miklavec:


>> My guess is that it used to use the combining diacritic with the y,
>> and now it only looks for the precomposed character. I'm not sure how
>> you'd go about solving your problem though.
 
> I don't know the details, but I also think that one package A (maybe
> fontspec or xltxtra?) now loads the other package B (maybe xunicode?)
> automatically.
 
> Most probably xunicode tries to use the proper accent even if you use
> \=, but I have no idea how to fix that in XeLaTeX. If you were using
> proper letter ȳ, you could just make that letter active and redefine
> it to create a composite character.
 
> Maybe xunicode has some sequence to revert its magic?

It has. But I didn't see previously the error message ("** ERROR **
Invalid glyph index (gid 1329)") in this context and the only
"proof" for the claim that the source of the problem is the \=y is a
log-file of a 70 page document. 

Without a small complete ("minimal") example it is impossible to
investigate in a sensible way.



-- 
Ulrike Fischer 



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