[XeTeX] [Fwd: Re: FreeSerif not working for me in Devanagari]

2012-09-08 Thread Neal Delmonico
I am not sure this made it to the full list.  Therefore, I am forwarding
it.  

My problem with FreeSerif has been solved.  Everything is working now,
even the page headings with the help of FakeSlant.  I think it is the
best font yet for those of us working with Devanagari on a regular
basis.

Best

Neal
---BeginMessage---
2012/9/8 Steve White stevan.wh...@googlemail.com:
 Hi Neal,

 I'm very pleased to hear it's working for you!

 Could you please write to the mailing list, to let them know?  (To
 date, the advice has been don't use FreeFont.)  It would be great to
 see your working examples there, too.

I had some communication with Neal off list so I will summarize now.

1. Devanagari is a script used for several languages. They differ
mainly in the repertoire of ligatures used, the full list being used
in Sanskrit. Up to now, there anre Snaskrit fonts (not usable for
Hindi, Marathi etc. because the users without education in Sanskrit
will be unable to read them), Hindi fonts (not usable for Sanskrit due
to missing ligatures), Marathi fonts (not usable even for Hindi), yet
all of them use the Devanagari script. FreeSerif is the new
generation font because it supplies the Devanagari script and the set
of ligatures are set according to the language. FreeSans does not
contain all Sanskrit ligatures.

2. The Devanagari block is missing in the italic shapes in both
FreeSerif and FreeSans. In order to use them, AutoFakeSlant has to be
specified. The default value is 0.2 if not given.

Written shortly, Neal Delmonico uses Charis SIL as the default font
and FreeSerif as the Sanskrit font. In order to have it work with all
Sanskrit ligatures and italic, the header shouldbe as follows:

\usepackage{xltxtra}
\usepackage{polyglossia}
\setmainfont{Charis SIL}
\newfontfamily\sanskritfont[Script=Devanagari,Mapping=RomDev,Language=Sanskrit,AutoFakeSlant=0.195]{FreeSerif}

Mapping=RomDev is only needed if the text is input in transliteration,
if the text is typed directly in UTF-8, it is not needed.

For those who need more information:
FreeSerif contains the Velthuis glyphs (I hope that the PFB files
hand-tuned by Karel Piska were used). Positions of matras were
precisely adjusted. Some characters with nuktas require different
positions of u and uu matras in order to be readable and the nukta
were visible and Steve made it. Consonants ka and pha need different
position of e and ai matras. All this is done.

FreeSans is derived from Gargi. It seems to me that Gargi was a
Marathi font because unlike Hindi, Marathi does not use characters
with nuktas. The characters with nuktas were present but there half
forms were missing. Thus the font was almost unusable fot Hindi. I
know that nuktas are often omitted in Hindi, ja is often used instead
of za (some people even pronounce jaruur instead of zaruur), pha is
often used instead of fa, qa is almost always replaced with ka. The
correct half forms were added to FreeSans. Nowadays fonts often omit
the classical kra ligatures. I have asked my Indian friends and they
replied that the they would prefare the classical shape. It was
therefore made by Steve. And as with FreeSerif, positions of matras
were precisely tuned.

I forgot to mention positions of anusvaras. They are used in Hindi in
the oblique case in plural and with verbs in plural feminine. The
situation may be quite complex with some words and the position of
anusvaras in all possible cases was tuned in order to make the words
readable.

Indian typographers use larger spacing preceding punctuation. In
Sanskrit only dandas and double dandas are used but nowaday's
languages accept also question and exclamation marks. The same spacing
is expected (a few years ago I read an article written by an Indian
typographer but I am not able to find it now). Majority of Devanagari
fonts do not take it into account. Native users thus tend to enter a
space preceding punctiatiom marks which leads to incorrect line breaks
where punctuation may appear at the beginning of a line. It would be
necessary to enter a fixed-width nonbreakable space but it is not
usually available on a keyboard. FreeFont uses correct spacing. The
same punctuation marks behave properly both in the Latin and
Devanagari scripts (both FreeSans and FreeSerif, tested in a longer
Hindi text).

It was a huge amount of work but now all aspect of typesetting in
Devanagari are properly set. Due to Steve's big care it is now the
most beautiful Devanagari font.

Remember that Unix distributions often come with an older version of
GNU FreeFont. If you want to use the current version as distributed
with TeX Live 2012, you have to delete the system fonts and follow the
post-install actions as given in the TeX Live manual. The new version
of the GNU FreeFont will then be available to the system, no
applications relying on the existence of the font will be broken
(verified by me in four different Linux distributions).

 I still haven't got it going.  Near as I can tell, this tec

Re: [XeTeX] FreeSerif not working for me in Devanagari

2012-09-07 Thread Neal Delmonico
The two problems I mentioned are in the sample I sent yesterday.  I have
attached the same sample as before (and its source file) done this time
successfully with FreeSerif.  Five lines from the the bottom, second
cluster from the right you can see kimaGgAni.  The Gg is the guttural
n + g combination.  It should have the n on top and the g beneath it.
This is pretty standard.  Instead one has the n with a virama stroke
underneath it and the g next to it.  A little earlier in the same line
the same is true when d + g occur in mAnonnAhAdglapayasi.  That is more
complicated because three consonants are involved: d + g + l.  I have
noticed that even Nakula does not try to combine those.  So perhaps that
is not a fault.  Basically, though, anytime I see the virama stroke used
in consonant combinations, I see it as a conjunct failure.  It is not
that it is wrong.  I have seen plenty of printed examples of Devanagari
texts in which it is done, but it always seems like an eyesore and a
cheap alternative to the proper way of doing it.

What concerns me most is that FreeSerif does not appear in the page
headings.  Here is an example of the code I use for that which works
well with Nakula and Sahadeva and even Sanskrit 2003:

\chapter*{The Leading Ladies (\skt{atha nāyikābhedaprakaraam})}
\addcontentsline{toc}{chapter}{The Leading Ladies (\textsanskrit{atha
nāyikābhedaprakaraam})} 
\markboth{Śrī Ujjvala-nīlamai}{The Leading Ladies (\textsanskrit{atha
nāyikābhedaprakaraam})}

Why would this produce little empty boxes at the top of the pages
instead of the Devanagari?

These are just problems I have noticed with a glance.  I have not looked
at FreeSerif in a longer text.

Best 

Neal

On Fri, 2012-09-07 at 10:39 +0200, Zdenek Wagner wrote:
 2012/9/7 Neal Delmonico ndelmon...@sbcglobal.net:
  I am happy to say that I finally got it working.  Those Freefonts were
  installed on my computer no less than four times (not counting texlive).
  Moodle installed them as did Joomla.  I had installed them from the
  ports collection and apparently the system installed them, or perhaps it
  was X-windows.  Anyway, I found them with the X-11 fonts.  When I got
  them all removed XeLaTeX could no longer find FreeSerif.  I don't know
  why the Texlive installation could not find fonts it had installed.
 
 It is explained in the manual in the chapter on post-install actions.
 
  Anyway, I downloaded the most recent version of the Freefonts and placed
  them in the X-11 font directory, ran all the programs so that X could
  find them and voila! suddenly XeLaTeX could find them too.  Sadly, I see
  that FreeSerif does not handle some of the common conjuncts well.
  Guttural n and g do not combine, nor do d and g, for instance.  Also the
 
 Could you, please, prepare a sample documenting that bug? I do not
 know Sanskrit, I made tests just in Hindi where these conjuncts are
 not used. Steve White will certainly fix it if we write him exactly
 what is wrong.
 
  Devanagari was replaced by little empty boxes in my page headings Where
  I put the Sanskrit titles of the chapters along with their English
  translations.  Nakula and Sahadeva and even Sanskrit 2003 could all do
  those things.  FreeSerif is a nice looking Devanagari font, but it is
  still not up to where it needs to be in order for me to use it
  regularly.
 
 Again, prepare a sample. As Steve White wrote a few months ago, he
 cannot fix the bugs if people do not report them.
 
  Thanks for your help, everyone.
 
  Best
 
  Neal
 
 
 
  --
  Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
 
 
 



test.pdf
Description: Adobe PDF document
\input{header}

\begin{document}

\begin{verse}

\skt{

\normalsize 

mohāntasuratakṣamā, yathā

śramajalaniviḍāṃ nimīlitākṣīṃ \\
ślathacikurāmanadhīnabāhuvallīm |\\
muditamanasamasmṛtānyabhāvāṃ\\
ratiśayane niśi gopikāṃ smarāmi|| 31||

māne komalā, yathā

prāṇāstvameva kimiva tvayi gopanīyaṃ\\
mānāya keśimathane sakhi nāsmi śaktā |\\
ehi prayāva ravijātaṭaniṣkuṭāya\\
kalyāṇi phullakusumāvacayacchalena|| 32||

māne karkaśā, yathā vidagdhamādhave (5.30)

mudhā mānonnāhādglapayasi kimaṅgāni kaṭhine\\
ruṣaṃ dhatse kiṃvā priyaparijanābhyarthanavidhau |\\
prakāmaṃ te kuñjālayagṛhapatistāmyati puraḥ \\
kṛpālakṣmīvantaṃ caṭulaya dṛgantaṃ kṣaṇamiha|| 33||\\

\large
tridhāsau mānavṛtteḥ syāddhīrādhīrobhayātmikā|| 34||

}

\end{verse}

\end{document}


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


Re: [XeTeX] FreeSerif not working for me in Devanagari

2012-09-07 Thread Neal Delmonico
I use the RomDev map, so this problem does not affect me.  It also
allows me to easily switch back and forth between Devanagari and Roman
transliteration when I need to.

N

On Fri, 2012-09-07 at 10:48 +0200, François Patte wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Le 07/09/2012 07:28, Neal Delmonico a écrit :
  find them and voila! suddenly XeLaTeX could find them too.
 couic
 
  Sadly, I see that FreeSerif does not handle some of the common
  conjuncts well. Guttural n and g do not combine, nor do d and g, for
  instance.
 
 these two work for me...
 
 But, I think there is some bug in velthuis-sanskrit.map : ~n is not
 taken into account. If you type pa~nca, you get in devanagari: pa nca (I
 think that the space is an unbreakable space).
 
 F.P.
 - -- 
 François Patte
 UFR de mathématiques et informatique
 Laboratoire MAP5 --- UMR CNRS 8145
 Université Paris Descartes
 45, rue des Saints Pères
 F-75270 Paris Cedex 06
 Tél. +33 (0)1 8394 5849
 http://www.math-info.univ-paris5.fr/~patte
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.11 (GNU/Linux)
 Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
 
 iEYEARECAAYFAlBJtO8ACgkQdE6C2dhV2JVfBgCfQHgOZhp6+h3URVE78WA65Uyg
 EaQAn0luH+0aeHZr8Uir3yuDVtSvUpbq
 =ASzi
 -END PGP SIGNATURE-




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


Re: [XeTeX] FreeSerif not working for me in Devanagari

2012-09-07 Thread Neal Delmonico
I guess it was US-ascii.  I have switched to utf-8.  Let's see if that
works better.

\chapter*{The Leading Ladies (\skt{atha nāyikābhedaprakaraṇam})}
\addcontentsline{toc}{chapter}{The Leading Ladies (\textsanskrit{atha
nāyikābhedaprakaraṇam})} 
\markboth{Śrī Ujjvala-nīlamaṇi}{The Leading Ladies (\textsanskrit{atha
nāyikābhedaprakaraṇam})}




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


Re: [XeTeX] FreeSerif not working for me in Devanagari

2012-09-06 Thread Neal Delmonico
I am happy to say that I finally got it working.  Those Freefonts were
installed on my computer no less than four times (not counting texlive).
Moodle installed them as did Joomla.  I had installed them from the
ports collection and apparently the system installed them, or perhaps it
was X-windows.  Anyway, I found them with the X-11 fonts.  When I got
them all removed XeLaTeX could no longer find FreeSerif.  I don't know
why the Texlive installation could not find fonts it had installed.
Anyway, I downloaded the most recent version of the Freefonts and placed
them in the X-11 font directory, ran all the programs so that X could
find them and voila! suddenly XeLaTeX could find them too.  Sadly, I see
that FreeSerif does not handle some of the common conjuncts well.
Guttural n and g do not combine, nor do d and g, for instance.  Also the
Devanagari was replaced by little empty boxes in my page headings Where
I put the Sanskrit titles of the chapters along with their English
translations.  Nakula and Sahadeva and even Sanskrit 2003 could all do
those things.  FreeSerif is a nice looking Devanagari font, but it is
still not up to where it needs to be in order for me to use it
regularly.

Thanks for your help, everyone.

Best

Neal



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


Re: [XeTeX] Difficulty with hypenation in Sanskrit with Devanagari

2012-04-30 Thread Neal Delmonico
Thanks for all your replies and suggestions.  I decided that there was no  
easy solution.  It must be the fact that some of the compound words have  
more than 64 characters that is causing the hyphenation to fail.  I  
decided to hyphenate it manually and came up with something passable.  I  
hope I don't run into too many more passages like this.


Best

Neal

On Wed, 25 Apr 2012 03:48:19 -0500, Zdenek Wagner  
zdenek.wag...@gmail.com wrote:



2012/4/25 Mojca Miklavec mojca.miklavec.li...@gmail.com:

2012/4/24 Zdenek Wagner zdenek.wag...@gmail.com:

However, what I know for sure is that the
very first word of a paragraph can never be hyphenated. If you start a
paragraph with a long word, you have to precede it by \hspace{0pt} in
order to allow hyphenation.


Also words with 64 characters or more have problems and this might
well be the problem in your case. (LuaTeX has a longer limit, but also
not an infinite one.)


However, LuaTeX does not yet support Devanagari :-(


Mojca


--
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] Difficulty with hypenation in Sanskrit with Devanagari

2012-04-30 Thread Neal Delmonico

Greetings Aku,

Sure.  No problem.  I'm glad to help if I can.  Attached is the header  
file I use for that file.  The header is for a purely Sanskrit (i.e., no  
other language) book with a size of 5 x 8.  If you have any questions or  
suggestions, please don't hesitate.


Best wishes,

Neal

On Mon, 30 Apr 2012 12:33:07 -0500, A u akupadhyay...@gmail.com wrote:


Neal,
I am working of Bellamkonda Ramarayakavi's Gita-Bhashya, if you do not  
mind

can you share the header file required to process your attached tex file.
I am using xetex and directly typing in Devanagari, instead of using  
roman
letters. I am new to tex so want to learn how to do the way you are  
doing.

I would really appreciate your help
Aku

On Thu, Apr 26, 2012 at 10:51 AM, Neal Delmonico
ndelmon...@sbcglobal.netwrote:

Thanks for all your replies and suggestions.  I decided that there was  
no

easy solution.  It must be the fact that some of the compound words have
more than 64 characters that is causing the hyphenation to fail.  I  
decided

to hyphenate it manually and came up with something passable.  I hope I
don't run into too many more passages like this.

Best

Neal


On Wed, 25 Apr 2012 03:48:19 -0500, Zdenek Wagner  
zdenek.wag...@gmail.com

wrote:

 2012/4/25 Mojca Miklavec  
mojca.miklavec.lists@gmail.**commojca.miklavec.li...@gmail.com

:


2012/4/24 Zdenek Wagner zdenek.wag...@gmail.com:


However, what I know for sure is that the
very first word of a paragraph can never be hyphenated. If you start  
a

paragraph with a long word, you have to precede it by \hspace{0pt} in
order to allow hyphenation.



Also words with 64 characters or more have problems and this might
well be the problem in your case. (LuaTeX has a longer limit, but also
not an infinite one.)

 However, LuaTeX does not yet support Devanagari :-(


 Mojca



--**
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/**listinfo/xetexhttp://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/xetexhttp://tug.org/mailman/listinfo/xetex




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

header4.tex
Description: TeX document


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


Re: [XeTeX] Odd hyphenations

2011-10-02 Thread NEAL DELMONICO
Thanks.  I tried that and it does solve the English hyphenation.  I was 
wondering if it affected the Sanskrit hyphenation.  Apparently it does.  
Fortunately, I don't have much Sanskrit in this book.  But, there may be 
ramifications for the Hindi (Braj Bhsha) verse in the appendix.  I will look at 
that.  Most are too short for there to be a problem.  Some lines are long and 
may be affected by the lack of hyphenation.  If anyone comes up with a solution 
I would be much obliged.  My internet connection has gone south and therefore 
my 
response time will be slow for the next few days.  I have to go to campus in 
order to get on the internet.

Best wishes,

Neal






From: Dominik Wujastyk wujas...@gmail.com
To: Unicode-based TeX for Mac OS X and other platforms xetex@tug.org
Sent: Sat, October 1, 2011 3:49:18 AM
Subject: Re: [XeTeX] Odd hyphenations

Try removing \setotherlanguage{sanskrit}.

There's probably a lot more going on, but this seemed to fix the hyphenation 
errors in the English.  It looks as if the Sanskrit isn't hyphenating now, 
though.  More thought required.

See attached.

Dominik



On 30 September 2011 19:56, NEAL DELMONICO ndelmon...@sbcglobal.net wrote:

Greetings All,

I am having some problems with hyphenation in English and wonder if I am 
missing 
something important in my header file.  The hyphenation program seems to be 
misfiring since it gives the following hyphenations: n-ear, s-mall, b-lissful, 
s-miling, y-our, and many more like this.  I have been going though and adding 
those words to my \hyphenation{} command and that usually fixes them.  But, as 
I 
go through the book, I find that I find a bad hyphenation every few pages.  
There are a lot of Indic words in the text and hyphenation will often mess 
them 
up.  That is understandable, but the wrong hyphenation of these English words 
is 
puzzling.  Any suggestions?

My header file and log file are attached.  Actually, I can't seem to find the  
log file.  TeXworks says it writes one, but I cannot find it anywhere.

Best wishes,


Neal



--
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] Odd hyphenations

2011-10-02 Thread NEAL DELMONICO
Thanks.  I will try this and uncomment the \setotherlanguage{Sanskrit}.  That 
way if there are any hyphenations in the Hindi verse, they will occur 
correctly.  Am I correct in thinking this?  Or, do I need to put other settings 
in for the Hindi sections?  And after the Hindi section do I put these again?

Best,

Neal






From: Arthur Reutenauer arthur.reutena...@normalesup.org
To: Unicode-based TeX for Mac OS X and other platforms xetex@tug.org
Sent: Sun, October 2, 2011 9:32:35 AM
Subject: Re: [XeTeX] Odd hyphenations

   I have been through the introduction and first 
 chapter correcting the mistaken hyphenations by hand.

  Please don't do that, it is a total waste of your own time.  There is
a bug in Polyglossia.  It needs to be fixed, but for the time being it's
enough if you add the following two lines just before the start of the
English text:

\lefthyphenmin=2
\righthyphenmin=3

  That will prevent XeTeX from trying to hyphenate after the first character
of words, and before the last two characters.

Arthur


--
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] Odd hyphenations

2011-09-30 Thread NEAL DELMONICO
Greetings All,

I am having some problems with hyphenation in English and wonder if I am 
missing 
something important in my header file.  The hyphenation program seems to be 
misfiring since it gives the following hyphenations: n-ear, s-mall, b-lissful, 
s-miling, y-our, and many more like this.  I have been going though and adding 
those words to my \hyphenation{} command and that usually fixes them.  But, as 
I 
go through the book, I find that I find a bad hyphenation every few pages.  
There are a lot of Indic words in the text and hyphenation will often mess them 
up.  That is understandable, but the wrong hyphenation of these English words 
is 
puzzling.  Any suggestions?

My header file and log file are attached.  Actually, I can't seem to find the 
log file.  TeXworks says it writes one, but I cannot find it anywhere.

Best wishes,


Neal


header.tex
Description: TeX document


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


Re: [XeTeX] Odd hyphenations

2011-09-30 Thread Neal Delmonico
How does one do this on a Windows machine?  In Unix it is easy enough, but  
the machine I am working on is Windows 7.


On Fri, 30 Sep 2011 10:39:32 -0500, Peter Dyballa peter_dyba...@web.de  
wrote:




Am 30.09.2011 um 17:26 schrieb NEAL DELMONICO:


I assume the new progs were copied over the old ones.


No, Neal, this does never happen.


 Is that okay, or should I do a clean install and update to 2011?


You should update PATH, MANPATH, INFOPATH instead.

Look at /usr/local/texlive! You'll see a few directory names that  
obviously stand for years, and you'll see the directory texmf-local.  
Adapt the PATH variables I named to the most recent year! (And try  
again.) (You could also check whether you have only i386 or also x86_64  
directories in /usr/local/texlive/year/bin.)


--
Greetings

  Pete

Journalism is printing what someone else does not want printed;  
everything else is public relations.

– George Orwell






--
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] Odd hyphenations

2011-09-30 Thread Neal Delmonico
Oh and I forgot to mention, I checked the texlive directory and only 2009  
is listed.  In my Windows menus I have both TeXlive 2009 and 2010.  The  
only one that has a link to the Texline Manager is the 2009/


best

Neal

On Fri, 30 Sep 2011 10:39:32 -0500, Peter Dyballa peter_dyba...@web.de  
wrote:




Am 30.09.2011 um 17:26 schrieb NEAL DELMONICO:


I assume the new progs were copied over the old ones.


No, Neal, this does never happen.


 Is that okay, or should I do a clean install and update to 2011?


You should update PATH, MANPATH, INFOPATH instead.

Look at /usr/local/texlive! You'll see a few directory names that  
obviously stand for years, and you'll see the directory texmf-local.  
Adapt the PATH variables I named to the most recent year! (And try  
again.) (You could also check whether you have only i386 or also x86_64  
directories in /usr/local/texlive/year/bin.)


--
Greetings

  Pete

Journalism is printing what someone else does not want printed;  
everything else is public relations.

– George Orwell






--
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] Odd hyphenations

2011-09-30 Thread NEAL DELMONICO
Yes, I agree.  Unix is my preferred platform.  I use Windows reluctantly and 
with trepidation.

Best

Neal





From: Peter Dyballa peter_dyba...@web.de
To: Unicode-based TeX for Mac OS X and other platforms xetex@tug.org
Sent: Fri, September 30, 2011 12:38:22 PM
Subject: Re: [XeTeX] Odd hyphenations


Am 30.09.2011 um 19:03 schrieb Neal Delmonico:

 How does one do this on a Windows machine?

I don't know; and I prefer to use other Windows, those I can open and close.

--
Greetings

  Pete

Encryption, n.:
A powerful algorithmic encoding technique employed in the creation of 
computer manuals.




--
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] Hyphenation in Transliterated Sanskrit

2011-09-11 Thread Neal Delmonico
Thanks to both Yves and Zdenek for your suggestions and examples.  The  
hyphenation is working now in both Devanagari and Roman Translit.  I'd  
have never figured it out on my own.  If I were to want to read more on  
this where would I look?


Also Zdenek raises an interesting possibility.  If I were to want to  
typeset Sanskrit, say this very Sanskrit, in Bengali or Telugu script.   
How would I go about that?


Thanks again.

Neal

On Sun, 11 Sep 2011 04:32:59 -0500, Zdenek Wagner  
zdenek.wag...@gmail.com wrote:



2011/9/11 Neal Delmonico ndelmon...@sbcglobal.net:
Thanks!  How would one set it up so that the English portions are  
hyphenated
according to English rules and the transliteration is hyphenated  
according

to Sanskrit rules?


I am sending an example. You can see another nice feature of the
TECkit mapping. The mapping is applied when the text is typeset. You
can thus store the transliterated text in a temporary macro and
typeset it twice.

There is one problem (this is the reason why I am sending a copy to
François). It is requested that Sanskrit text is typeset by a font
with Devanagari characters. However, Sanskrit is also written in other
scripts so that people in other parts of India, who do not know
Devanagari, could read it. Even the Tibetan script contains retroflex
consonants that are not used in the Tibetan language but server for
writing Sanskrit (and recently writing words of English origin).
Polyglossia should not be that demanding.

And just to François: I found two bugs in documentation. Section 5.2
mentions selection between Western and Devanagari numerals, but it
should be Bengali numerals (I am not sure which option is really
implemented). At the introduction, Vafa Khaligi's name is wrong. AFAIK
in Urdu and Farsi, the isolated and final form of YEH are dotless (it
is not a big bug), but in fact the name is written as Khaliql, there
is ق instead of غ


Best

Neal

On Sat, 10 Sep 2011 19:40:51 -0500, Zdenek Wagner  
zdenek.wag...@gmail.com

wrote:


2011/9/11 Neal Delmonico ndelmon...@sbcglobal.net:


Here is the source files for the pdf.  Sorry to take so long to send
them.


Your default language for polygliglossia is defined as English. You
switch to Sanskrit only inside the \skt macro. The text in Devanagari
is therefore hyphenated according to Sanskrit rules but the
transliterated text is hyphenated according to the English rules. You
have to switch the language to Sanskrit also for the transliterated
text.


Best

Neal

On Sat, 10 Sep 2011 17:53:42 -0500, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:


On Sun, Sep 11, 2011 at 00:39, Neal Delmonico wrote:


Here is an example of what I mean in the pdf attached.


Do I get it right that hyphenation is working, it is just that it
misses a lot of valid hyphenation points?

You should talk to Yves Codet, the author of Sanskrit patterns.

But PLEASE: do post example of your code when you ask for help. If  
you

don't send the source, it is not clear whether you are in fact using
Sanskrit patterns or if you are falling back to English when you try
to switch fonst. You could just as well sent us PDF with French
hyphenation enabled and claim that TeX is buggy since it doesn't
hyphenate right.

Mojca


--
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









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


--
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


[XeTeX] Hyphenation in Transliterated Sanskrit

2011-09-10 Thread Neal Delmonico

Greetings,

I have a question.  How does one get the hyphenation to work for  
transliterated Sanskrit as well as it does for Sanskrit in Devenagari.  I  
use the same text in Devanagari and Roman transliteration and yet in the  
Devanagari the hyphenation works fine and in the transliteration it does  
not.  Is there some trick to setting up the transliteration so that the  
hyphenation works?


Thanks.

Neal

--
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] Hyphenation in Transliterated Sanskrit

2011-09-10 Thread Neal Delmonico
How does one do that?  Where are the patterns kept and what format needs  
to be rebuilt.  Sorry for being so clueless about this.


Best

Neal

On Sat, 10 Sep 2011 15:47:38 -0500, Zdenek Wagner  
zdenek.wag...@gmail.com wrote:



2011/9/10 Neal Delmonico ndelmon...@sbcglobal.net:

Greetings,

I have a question.  How does one get the hyphenation to work for
transliterated Sanskrit as well as it does for Sanskrit in Devenagari.  
 I

use the same text in Devanagari and Roman transliteration and yet in the
Devanagari the hyphenation works fine and in the transliteration it does
not.  Is there some trick to setting up the transliteration so that the
hyphenation works?

It is necessary to modify the hyphenation patterns and then rebuild the  
format.



Thanks.

Neal

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


--
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 peter_dyba...@web.de  
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  
ndelmon...@sbcglobal.net 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 peter_dyba...@web.de  
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-13 Thread Neal Delmonico

When the fmtutil file is run it gets several errors.  Here is what it says:


fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
  /usr/local/texlive/2009/texmf-var/web2c
for details.
###

This is a summary of all `failed' messages:
`pdftex -ini  -jobname=amstex -progname=amstex -translate-file=cp227.tcx  
*amstex.ini' failed
`pdftex -ini  -jobname=eplain -progname=eplain -translate-file=cp227.tcx  
*eplain.ini' failed
`pdftex -ini  -jobname=latex -progname=latex -translate-file=cp227.tcx  
*latex.ini' failed
`pdftex -ini  -jobname=pdflatex -progname=pdflatex  
-translate-file=cp227.tcx *pdflatex.ini' failed
`pdftex -ini  -jobname=mex -progname=mex -translate-file=cp227.tcx  
*mex.ini' failed
`pdftex -ini  -jobname=pdfmex -progname=pdfmex -translate-file=cp227.tcx  
*pdfmex.ini' failed

`pdftex -ini  -jobname=utf8mex -progname=utf8mex -enc *utf8mex.ini' failed

I looked at the xelatex.fmt and see that the date on the file is back in  
january.  So it was not touched in the most recent execution of fmtutil.


Any suggestions?

Best

Neal



On Sat, 13 Aug 2011 03:45:07 -0500, Dominik Wujastyk wujas...@gmail.com  
wrote:



have you tried rebuilding the fmt file?


On 13 August 2011 06:08, Neal Delmonico ndelmon...@sbcglobal.net wrote:


Hi,

I am having some trouble with XeTeX suddenly.  I recently updated my
TeXLive using tlmgr and now XeLaTeX no longer works.

Instead I get the following message

---! /usr/local/texlive/2009/texmf-**var/web2c/xetex/xelatex.fmt doesn't
match xetex.pool
(Fatal format file error; I'm stymied)

How do I fix this?  What went wrong.  Usually the update all installed
function wrongs like a charm.

Thanks,

Neal

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


--**
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/**listinfo/xetexhttp://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


[XeTeX] XeLateX problem after updating

2011-08-12 Thread Neal Delmonico

Hi,

I am having some trouble with XeTeX suddenly.  I recently updated my  
TeXLive using tlmgr and now XeLaTeX no longer works.


Instead I get the following message

---! /usr/local/texlive/2009/texmf-var/web2c/xetex/xelatex.fmt doesn't  
match xetex.pool

(Fatal format file error; I'm stymied)

How do I fix this?  What went wrong.  Usually the update all installed  
function wrongs like a charm.


Thanks,

Neal

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


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


[XeTeX] Velthuis to Roman transliteration

2011-02-08 Thread Neal Delmonico

Greetings All,

I just wanted to thank everyone who offered advice and help in resolving  
my Velthuis to transliteration question.  I now have RomDev.map and .tec  
successfully installed and they are working like a charm.  I have two  
routes to conversion of my old velthuis files to unicode: a sed script  
(thanks Dominik) that works well and an emacs script (thanks Francois)  
that works equally well.  Those scripts have helped me resolve some other  
questions I had a had about efficient ways to input Unicode  
transliteration.  I would still like to try create a map that would  
convert velthuis to unicode Roman transliteration, but I will save that  
until I have some free time for that.


Anyway, thanks to all for your patience and help.

Best wishes,

Neal

--
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] Velthuis to Roman translit

2011-02-04 Thread Neal Delmonico
There's the problem.  I apparently don't have RomDev.map and tec  
installed.  Doesn't it come with TeXLive?  If not, how do I get it?


On Fri, 04 Feb 2011 04:56:58 -0600, Dominik Wujastyk wujas...@gmail.com  
wrote:



But I think there's another point.  You've gone through some trouble to
convert Velthuis to UTF8.  But if, in the \newfontfamily statement you  
said

Mapping=velthuis-sanskrit then the Velthuis encoding itself can give
perfectly good Nagari output.


Yes. This is true.  I used this before and still do.  I wanted to see if I  
could get back to Devanagari from the transliterated files.  These texts  
are still under development.  Being able to produce either a Devanagari  
version or a transliterated version from one file would be grand.  I could  
continue to work in velthuis encoding and then when the text is where I  
want it run your script script on it and produce a Romanized version.  It  
is not a big hassle.  It would be nice to just have one file that with the  
change of one code produces either Devanagari or transliteration.


Thanks for your help.

Best wishes,

Neal

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] Velthuis to Roman translit

2011-02-03 Thread Neal Delmonico

Thanks Dominik,

I tried the sed file and it works wonderfully, in fact a little too well.   
My files tend to be mixed Sanskrit and translation in which I use the  
standard LaTeX diacritic codes.  \~n gets picked up by the sed file and  
converted and then XeLaTeX chokes on it.  Is there a way around this?  I  
can, of course, search and replace those unwanted conversions, but it is a  
little less convenient.


What is involved in writing a XeTeX TEC file?  I've looked at the map  
files.  Is it mostly a matter of substituting the Unicode codes with other  
Unicode codes to produce Romanized output instead of Devanagari?  Is it  
possible for a semi-computer literate person like myself to do that?   
Where would I start?


Thanks again for your help.

Best

Neal

On Thu, 03 Feb 2011 06:05:51 -0600, Dominik Wujastyk wujas...@gmail.com  
wrote:


I tend to do this just with a sed script, for the file as a whole (sed  
file
attached, originally from Richard Mahoney, but edited by me).  It  
wouldn't

be that hard to write a xetex TEC file to do this, but I'm not aware of
anyone actually having done it yet.  It would be nice to have, I agree.
Dominik
https://www.dropbox.com/referrals/NTIzNzI2MTY5


On 2 February 2011 23:34, Neal Delmonico ndelmon...@sbcglobal.net  
wrote:



Hi All,

Is there any easy way to get from Velthuis Devanagari encoding to Roman
transliteration?  I have lots of documents in Velthuis that I would  
like to

switch to Roman transliteration sometimes without having to type them in
again.  If there is a way to just substitute some LaTex codes, that  
would be

tremendous.

Thanks,

Neal

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


--
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] Velthuis to Roman translit

2011-02-03 Thread Neal Delmonico
Yes.  I am using Emacs.  How does your system work?  I already use the  
,emacs file for shortcut keys.  Adding more should not be a problem.


Thanks,

Neal

On Thu, 03 Feb 2011 09:00:36 -0600, François Patte  
francois.pa...@mi.parisdescartes.fr wrote:



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le 02/02/2011 23:34, Neal Delmonico a écrit :

Hi All,

Is there any easy way to get from Velthuis Devanagari encoding to Roman
transliteration?  I have lots of documents in Velthuis that I would like
to switch to Roman transliteration sometimes without having to type them
in again.


Are you using emacs? I can send you the code to put in your .emacs file.

- --
François Patte
UFR de mathématiques et informatique
Université Paris Descartes
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk1KwxMACgkQdE6C2dhV2JXI0gCcCMvO0kVlf9A94cpMULOWXpF4
Fu8Ani/yG4f9p5XbZcupjumZBJTUjskq
=9zCN
-END PGP SIGNATURE-


--
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] Velthuis to Roman translit

2011-02-03 Thread Neal Delmonico

Thanks for the suggestions.  See below.

On Thu, 03 Feb 2011 12:31:26 -0600, Dominik Wujastyk wujas...@gmail.com  
wrote:


Wait a minute.  Reading your note more carefully, I think the sed script  
is
giving you English text with unwanted \ñ strings here and there. Is  
that

right?  If so, you could just add a last line to the sed script to right
that wrong (s/\\ñ/ñ/g).


Yes.  This worked.  It turns out that there are only two occasions when  
the script overreaches.  \~n and \.n  Following your advice I added  
lines to the end of the script that turned the mistaken conversions back.   
So far I have not found any other problems.




Yes, you are right about TEC/map files.  I think you should use the  
existing

velthuis map files and replace the Devanagari character codes for output
with Latin, just as you say.  Once you get to understand the conjunct
consonants coding, it can be stripped out.  Etc.  I don't know where the
documentation for TEC files is, but probably on the SIL website.


I will look into this and see if I can make the appropriate changes.

One small question more.  Now that I have the files in Unicode encoding,  
how do I go from that to Devanagari?  Using the RomDev mapping just gives  
me more Romanized diacritics.   Here is what I am using:


\documentclass[10pt,titlepage]{book}
\usepackage{xltxtra}
\usepackage{polyglossia}
\setmainfont{Charis SIL}
\defaultfontfeatures{Mapping=tex-text}
\newfontfamily\sanskritfont[Script=Devanagari,Mapping=RomDev]{Sahadeva}
\newcommand{\skt}[1]{{\sanskritfont\textsanskrit{#1}}}

Thanks.

Neal

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



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