At least you can do your macro programming in whatever language you want, in XeLaTeX, just like I do my macro programming only in Persian (which had been my dream for a long time). see attached for an example.
2011/11/3 Danyll Wills <dwi...@netvigator.com>
> Phil, I use XeLaTeX for Chinese, Japanese and Mongolian. I have watched
> the discussion over the past few days and am 100 per cent behind you. I
> started my programming life in the early '80s using 8086 Assembly language.
> Nothing irritates me more than the idea that ASCII is the only way to go.
> Your latest explanation was spot on! Well done.
>
> /Danyll
>
>
>
> Sent from my iPhone
>
> On 3 Nov, 2011, at 18:35, "Philip TAYLOR (Webmaster, Ret'd)" <
> p.tay...@rhul.ac.uk> wrote:
>
> > Dear Arthur, Paul, Heiko, Ross, others --
> >
> >> Please stop. I am serious. Just stop.
> >
> > I was serious too (even when speaking of nominating Heiko
> > for the non-existent position of vice-Grand-Wizard of TeX :
> > that was a genuine expression of respect for his quite remarkable
> > solution to the problem of ascertaining whether a given control
> > word was, or was not, a TeX primitive). I was also very serious
> > when I sought to defend the right of someone who wished to use
> >
> >> \hyperlink {rAsociaci¨®n}{APLT (1988)}
> >>
> >> with
> >>
> >> \hypertarget {rAsociaci¨®n}{Asociaci¨®n para la Promoci¨®n de
> Lecto-Escritura Tlapaneca. 1988.}
> >
> > There is no reason at all why someone using \hyperlink and \hypertarget
> > should need to know anything about AdobeStandardEncoding, byte strings,
> > UTF-16, or any of the other deeply technical considerations that
> > prevent "rAsociaci¨®n" from being used /directly/ as a Name string;
> > whatever massaging that is necessary to convert from "rAsociaci¨®n"
> > to a derived byte string in AdobeStandardEncoding (or whatever)
> > should be the responsibility of the intervening software layer
> > that implements \hyperlink and \hypertarget. It surely /cannot/
> > be acceptable in the 21st century to tell such an author "Don't use
> > non-ASCII characters in the link" unless such a statement is qualified
> > with the words "until such time as the intervening software layer is
> > updated to allow such things".
> >
> > /This/ was the point that I was seeking to make, and if I made it
> > badly, then I apologise : all messages sent over the last few days have
> > been sent in conditions of extreme difficulty, with one arm completely
> > useless (as a result of a tendon injury) and considerable pain (for
> > the same reason).
> >
> > Very sincerely :
> > ** Phil.
> >
> >
> > --------------------------------------------------
> > Subscriptions, Archive, and List information, etc.:
> > http://tug.org/mailman/listinfo/xetex
>
>
>
> --------------------------------------------------
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
khat-zakhimtar-dar-vasat-example.tex
Description: TeX document
-------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
