[XeTeX] cannot produce labels with non-Latin text when using asymptote with polyglossia, and xelatex
I am having problems trying to produce labels containing non-Latin text by
the Asymptote program. (Not having gotten any help so far from the
Asymptote help forum,) I'm trying my luck here, since the problem also
involves xetex and polyglossia
For putting Arabic script text in labels, Asymptote works well with
arabtex+latex calls. But because of some arabtex limitations, I am trying
to use asymptote with the polyglossia+xelatex combination. Here is my
problematic foo.asy code, run via
asy -tex xelatex foo.asy
usepackge("color");
usepackage("polyglossia");
texpreamble("\setmainlanguage{english}\setotherlanguage{urdu}\newfontfamily\urdufont[Script=Arabic]{Times
New Roman}");
//import unicode; //Not needed since polyglossia works with utf8
pair A=(0,5);
dot(A);
label("${abcd}$",A,N); // Latin text displays OK
//label("$\texturdu{ابجد}$",A,S); // program fails when this line is
uncommented
I'm getting all sort of error messages. The arabxeteX+xelatex combination
produces similar errors. The trouble seems to be in Asymptote's handling of
non-Latin text in xelatex.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] cannot produce labels with non-Latin text when using asymptote with polyglossia, and xelatex
On Fri, May 17, 2013 at 7:42 PM, Arthur Reutenauer <
arthur.reutena...@normalesup.org> wrote:
> > //label("$\texturdu{ابجد}$",A,S); // program fails when this line is
> uncommented
>
> Why on Earth do you want to type the label text in math mode?
No reason, just bad force of habit (:-).
Just remove the dollar signs and you'll be fine.
>
> Arthur
Can't thank you enough, Arthur.
Kamal
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] cannot produce labels with non-Latin text when using asymptote with polyglossia, and xelatex
Thanks, Khalid. In the example in which Arthur pointed out my error, the
label was not part of a math formula. But in some other figures, the labels
do indeed have a little math. I tried your suggestion in one of these, and
it worked. Again I appreciate the prompt solutions.
Kamal
On Fri, May 17, 2013 at 9:33 PM, Khaled Hosny wrote:
> On Sat, May 18, 2013 at 12:42:05AM +0100, Arthur Reutenauer wrote:
> > > //label("$\texturdu{ابجد}$",A,S); // program fails when this line is
> uncommented
> >
> > Why on Earth do you want to type the label text in math mode? Just
> > remove the dollar signs and you'll be fine.
>
> Because it is part of larger math formula in this is just a MWE?
>
> If math mode is really desired, then wrapping \texturdu in an \hbox or
> amsmath's \text should do the trick.
>
> Regards,
> Khaled
>
>
> --
> 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] texlive13/harfbuzz problem with nastaleeq font
Thanks, Khaled, On Sat, Jun 22, 2013 at 6:09 PM, Khaled Hosny wrote: What happens if you omit the WordSpace option? No improvement. >Either way, the font is needed for any meaningful testing. > The links to the fonts are: XB Zar:http://irmug.com/downloads/dl.php?id=21 Jameel Noori Nastaleeq: http://sdrv.ms/186V2rd Best, Kamal -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] texlive13/harfbuzz problem with nastaleeq font
On Sat, Jun 22, 2013 at 6:52 PM, Khaled Hosny wrote: > ... > > ... The font has a ‘ccmp’ feature for Arabic script > that maps the space glyph to a 5-units wide glyph (that is practically > the same as zero), I guess following the traditional practice of > omitting word space in Arabic calligraphy. For some reason the feature > was not applied before so the normal space was used, so it was a bug > that had desirable effect (for some people at least). > > Since the font does not use ‘ccmp’ feature for anything else, it is safe > to just disable it to get the old behaviour, or you can setup things to > allow for looser interword spacing (which will not be that looser than > the old behaviour, after all). > Amazing! When a feature was ignored, it had the desirable effect, and caused frustration when properly taken into account. Thanks for diagnosing the problem, Khaled. Adding RawFeature=-ccmp option in the font family command (I don't know how else to do it) restored the happy state of ignorance. The new output is at least as good as the one generated from TL12 before. Kamal -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] texlive13/harfbuzz problem with nastaleeq font
Hi Akira, As I mentioned in my previous response to Khaled, "-ccmp" does improve the output. It makes the word spacing a bit too generous, but additional adjustment is then possible with WordSpace. Thanks for your attention. Kamal On Sat, Jun 22, 2013 at 8:14 PM, Akira Kakuto wrote: > Hi, > > No improvement. >> > > Is the attached test.pdf made with -ccmp still bad? > > Best regards, > Akira KAKUTO > > > -- > 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] arabic diacritics breaking words in Linux xelatex
Normally any letter that gets joined to the next letter in a word does so
whether or not it bears a diacritic. But Tex Live 2013 on SUSE Linux is
causing such a letter to be printed in its independent rather than
connected form when there is a diacritic on it. This is my first attempt to
use xetex on a Linux machine to process a document in the Arabic script. I
have never seen such an error on Windows or MacOS.
If this forum is not the right place to report the problem, perhaps some
member can kindly direct me to the proper place. An example is the
following:
=
%xelatex
\documentclass{minimal}
\usepackage{fontspec,bidi}
\newfontfamily\a[Script=Arabic]{Amiri}
\begin{document}
\setRTL
\a
قلم قَلَم قلَم قندیل قِندِیل قلوب قُلُوب قُلوب
\end{document}
The TeX output is equivalent to:
قلم قَ لَ م قلَ م قندیل قِ ندِیل قلوب قُ لُ وب قُ لوب
Kamal Abdali
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] arabic diacritics breaking words in Linux xelatex
Nicholas,
Thanks for testing the file. Another member, who wrote directly to me, also
got correct output from TEX Live 2013 under a slightly older version of
Open SUSE.
Not knowing what else to do, I uninstalled TeXLive 13 and installed TeXLive
14. The latter is not pre-packaged on Open SUSE 13.2, so I had to install
it from the TeXLive 14 DVD. This was a desperate step, but that other
version version of TeX did solve the problem.
Incidentally, the TeX Live ISO doesn't contain a binary of Texworks for
Linux. Open SUSE does, of course, have Texworks as a package. But in Open
SUSE the package dependencies are such that when you ask it to install
Texworks, it wants to install the whole TeXLive 13 again! So I had to
download Texworks sources and make it from scratch.
Thanks for your help.
Kamal
On Thu, Feb 12, 2015 at 11:47 PM, heer wrote:
> Kamal,
>
> I'm using Tex Live 2013 on Ubuntu 14.04 and your file works
> perfectly. All the letters are properly connected.
>
> Nicholas
>
>
> On Thu, 12 Feb 2015, Kamal Abdali wrote:
>
> Normally any letter that gets joined to the next letter in a word does so
>> whether or not it bears a diacritic. But Tex Live 2013 on SUSE Linux is
>> causing such a letter to be printed in its independent rather than
>> connected
>> form when there is a diacritic on it. This is my first attempt to use
>> xetex
>> on a Linux machine to process a document in the Arabic script. I have
>> never
>> seen such an error on Windows or MacOS.
>>
>> If this forum is not the right place to report the problem, perhaps some
>> member can kindly direct me to the proper place. An example is the
>> following:
>> =
>> %xelatex
>>
>> \documentclass{minimal}
>>
>> \usepackage{fontspec,bidi}
>>
>> \newfontfamily\a[Script=Arabic]{Amiri}
>>
>> \begin{document}
>>
>> \setRTL
>>
>> \a
>>
>> قلم قَلَم قلَم قندیل قِندِیل قلوب قُلُوب قُلوب
>>
>> \end{document}
>>
>>
>> The TeX output is equivalent to:
>>
>> قلم قَ لَ م قلَ م قندیل قِ ندِیل قلوب قُ لُ وب قُ لوب
>>
>>
>> Kamal Abdali
>>
>>
>
>
> --
> 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] arabic diacritics breaking words in Linux xelatex
Hi Zdeněk,
With TexLive 2014 installed from DVD and Texworks built from sources per
https://code.google.com/p/texworks/wiki/Building, the bizarre unconnected
letter problem has gone away. It seems specific to the texlive 2013 package
collection that comes with OpenSUSE 13.2. I'll take your advice and report
the problem to HarfBuzz. Thanks for your attention.
Kamal
On Sat, Feb 14, 2015 at 5:13 AM, Zdenek Wagner
wrote:
> 2015-02-14 6:40 GMT+01:00 Kamal Abdali :
> > Nicholas,
> >
> > Thanks for testing the file. Another member, who wrote directly to me,
> also
> > got correct output from TEX Live 2013 under a slightly older version of
> Open
> > SUSE.
> >
> In such a case it looks like a bug in HarfBuzz and you should report
> it. I have just tried your file with all versions of TeX Live from
> 2009 to 2014 and it works fine (up to 2012 ICU was used, since 2013
> HarfBuzz is used).
>
> > Not knowing what else to do, I uninstalled TeXLive 13 and installed
> TeXLive
> > 14. The latter is not pre-packaged on Open SUSE 13.2, so I had to
> install it
> > from the TeXLive 14 DVD. This was a desperate step, but that other
> version
> > version of TeX did solve the problem.
> >
> > Incidentally, the TeX Live ISO doesn't contain a binary of Texworks for
> > Linux. Open SUSE does, of course, have Texworks as a package. But in Open
> > SUSE the package dependencies are such that when you ask it to install
> > Texworks, it wants to install the whole TeXLive 13 again! So I had to
> > download Texworks sources and make it from scratch.
> >
> Yes, such dependencies exist probably in all Linux distributions.
> Debian offers equivalence package so that these dependencies are
> satisfied with TeX Live installed from TUG. I have enough space on
> disk thus I accepted TeX from the Fedora distribution but installed
> TeX Live in addition. It is sufficient to have the TeX Live binaries
> listed at the beginning of PATH and do not create symlinks. I have all
> TeX Live versions from 2007 to 2014 and can switch between them just
> by changing PATH. There may be ther dependencies so it is better to do
> it this way, otherwise on day TeX from SuSU may be instaled. If you
> have TeX Live's binary at the beginning of PATH, such installation
> will not break your setup, it will just eat some disk space.
>
> > Thanks for your help.
> >
> > Kamal
> >
>
> Zdeněk Wagner
> http://hroch486.icpf.cas.cz/wagner/
> http://icebearsoft.euweb.cz
>
>
>
> > On Thu, Feb 12, 2015 at 11:47 PM, heer wrote:
> >>
> >> Kamal,
> >>
> >> I'm using Tex Live 2013 on Ubuntu 14.04 and your file works
> >> perfectly. All the letters are properly connected.
> >>
> >> Nicholas
> >>
> >>
> >> On Thu, 12 Feb 2015, Kamal Abdali wrote:
> >>
> >>> Normally any letter that gets joined to the next letter in a word does
> so
> >>> whether or not it bears a diacritic. But Tex Live 2013 on SUSE Linux is
> >>> causing such a letter to be printed in its independent rather than
> >>> connected
> >>> form when there is a diacritic on it. This is my first attempt to use
> >>> xetex
> >>> on a Linux machine to process a document in the Arabic script. I have
> >>> never
> >>> seen such an error on Windows or MacOS.
> >>>
> >>> If this forum is not the right place to report the problem, perhaps
> some
> >>> member can kindly direct me to the proper place. An example is the
> >>> following:
> >>> =
> >>> %xelatex
> >>>
> >>> \documentclass{minimal}
> >>>
> >>> \usepackage{fontspec,bidi}
> >>>
> >>> \newfontfamily\a[Script=Arabic]{Amiri}
> >>>
> >>> \begin{document}
> >>>
> >>> \setRTL
> >>>
> >>> \a
> >>>
> >>> قلم قَلَم قلَم قندیل قِندِیل قلوب قُلُوب قُلوب
> >>>
> >>> \end{document}
> >>>
> >>>
> >>> The TeX output is equivalent to:
> >>>
> >>> قلم قَ لَ م قلَ م قندیل قِ ندِیل قلوب قُ لُ وب قُ لوب
> >>>
> >>>
> >>> Kamal Abdali
> >>>
> >>
> >>
> >>
> >> --
> >> 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] New feature planned for xetex
On Thu, Feb 18, 2016 at 7:38 PM, Zdenek Wagner wrote: > I have compared both and personally I like Jonathan's version. Of course, > I am not an expert. I do not have any collection of high quality Urdu > documents. I have only seen Mirza Ghalib's manuscript in his museum in New > Delhi and some Urdu documents in the museum in LaL Qila. My knowledge of > Urdu is very weak. Spoken Urdu is basically the same language as Hindi so > that I can listen to BBC Urdu and understand almost everything but reading > is difficult for me and I know nothing about calligraphy. It will take me > hours to read the sample text, I can only recognize from the title that it > is the Universal Declaration of Human Rights. Anyway, the larger interword > spaces do not help me toread the text. > > As an example I am attaching the text from the Jama Masjid in New Delhi. > Look at the beginning of the first line. There is a considerable space > between آ and پ although آپ is a single word. The interword space between > آپ and جامع is smalle that the space in the middle of جامع and there is > almost no space between جامع and مسجد. There is no space between پر and > زیارت but I still can see the words. In the third line the largest space is > in the middle of پرکشش. Of course, it helped me to see the same text in > Devanagari, I would probably be unable to read the Urdu text without it. Zdeněk, If each word in Urdu (or in any language written using Arabic characters) formed a connected figure, then any amount of interword space (including zero) would be OK. But since some letters connect with the next letter and some do not, words often consist of two or more separate figures. Having interword spaces then helps to delimit each word. Stringing words together without any space between them is an incessant source of ambiguities and problems. That's why all scripts for the Arabic alphabet other than Nastaleeq now use interword spaces. This forum is not a place to go into more details, so I'll just give you two examples in the form of entertaining puzzles. Without interword spaces, you can read a certain Urdu text (word string) as: EITHER "He is eighty-four years old." OR "That thief is eighty years old." Another one can be read EITHER "Jamaloo was defeated." OR "Jumma went to Lahore." (Jamaloo and Jumma are both common nicknames.) New learners are constantly frustrated because the printed shapes in front of them provide no visual help in separating the words. Basically, the script assumes that you already know what you're trying to learn by reading! Again, I am not calling for a ban on tight kerning, but I am asking Jonathan to be flexible about interword spaces for anyone who wants it. At present most Urdu word processors make it very difficult to overcome interword space suppression in Nastaleeq fonts. Kamal Abdali -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] New feature planned for xetex
Hi Zdeněk, Kudos! You figured one out correctly, and got only close on the second one because I gave you the wrong clue! Sorry. The two word-separated parsings of the second text are: جمالو ہار گیا۔ جما لوہار گیا۔ meaning: " Jamaloo was defeated" and "The ironsmith Jumma has left". While we are on fun and games, it's worth mentioning an embarrassment related to the same Nastaleeq ambiguity that a Pakistani TV channel suffered recently. An announcer pronounced the Urdu transliteration of the English phrase "motor vehicle" as "MoTroo Haikal", most likely thinking of it as a proper noun. Kamal Abdali On Fri, Feb 19, 2016 at 5:18 AM, Zdenek Wagner wrote: > 2016-02-19 4:25 GMT+01:00 Kamal Abdali : > >> >> On Thu, Feb 18, 2016 at 7:38 PM, Zdenek Wagner >> wrote: >> >>> I have compared both and personally I like Jonathan's version. Of >>> course, I am not an expert. I do not have any collection of high quality >>> Urdu documents. I have only seen Mirza Ghalib's manuscript in his museum in >>> New Delhi and some Urdu documents in the museum in LaL Qila. My knowledge >>> of Urdu is very weak. Spoken Urdu is basically the same language as Hindi >>> so that I can listen to BBC Urdu and understand almost everything but >>> reading is difficult for me and I know nothing about calligraphy. It will >>> take me hours to read the sample text, I can only recognize from the title >>> that it is the Universal Declaration of Human Rights. Anyway, the larger >>> interword spaces do not help me toread the text. >>> >>> As an example I am attaching the text from the Jama Masjid in New Delhi. >>> Look at the beginning of the first line. There is a considerable space >>> between آ and پ although آپ is a single word. The interword space between >>> آپ and جامع is smalle that the space in the middle of جامع and there is >>> almost no space between جامع and مسجد. There is no space between پر and >>> زیارت but I still can see the words. In the third line the largest space is >>> in the middle of پرکشش. Of course, it helped me to see the same text in >>> Devanagari, I would probably be unable to read the Urdu text without it. >> >> >> >> Zdeněk, >> >> If each word in Urdu (or in any language written using Arabic characters) >> formed a connected figure, then any amount of interword space (including >> zero) would be OK. But since some letters connect with the next letter and >> some do not, words often consist of two or more separate figures. Having >> interword spaces then helps to delimit each word. Stringing words together >> without any space between them is an incessant source of ambiguities and >> problems. That's why all scripts for the Arabic alphabet other than >> Nastaleeq now use interword spaces. This forum is not a place to go into >> more details, so I'll just give you two examples in the form of >> entertaining puzzles. Without interword spaces, you can read a certain Urdu >> text (word string) as: >> >> EITHER "He is eighty-four years old." >> OR "That thief is eighty years old." >> >> Another one can be read >> >> EITHER "Jamaloo was defeated." >> OR "Jumma went to Lahore." >> >> (Jamaloo and Jumma are both common nicknames.) New learners are >> constantly frustrated because the printed shapes in front of them provide >> no visual help in separating the words. Basically, the script assumes that >> you already know what you're trying to learn by reading! >> >> Again, I am not calling for a ban on tight kerning, but I am asking >> Jonathan to be flexible about interword spaces for anyone who wants it. At >> present most Urdu word processors make it very difficult to overcome >> interword space suppression in Nastaleeq fonts. >> >> Kamal Abdali >> > > Hi Kamal, > > thank you for examples, I see the problem of چوراسی and چور اسی without > and with the interword space. The spaces will be needed especially in > textbooks of Urdu and in dictionaries. > > Could you, please, send me the second example in Urdu? It is interesting > to me. I can guess that the second sentece ends with حلاحور گیا and by > similarity with Hindi I could imagine verb حارنا but then the first > sentence would end with حار گیا > The ending is thus different (حار versus حور) but as I wrote, I may be > mistaken. > > I hope the first example in full is: > وہ چوراسی سال کا ہے، > وہ چور اسی سال کا ہے۔ > > Zdeněk Wagner > http://ttsm.icpf.cas.cz/team/wagner.shtml > http://icebearsoft.euweb.cz > > > >> >> >> >> >> -- >> Subscriptions, Archive, and List information, etc.: >> http://tug.org/mailman/listinfo/xetex >> >> > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] unicode-math and ucharcat
When using the package unicode-math, I get the XeLaTex error: File `ucharcat.sty' not found. XeLaTex then asks for a new filename. When I enter an empty filename, XeLaTex proceeds normally. But to do this every time is annoying. The conclusion from some googling was that this error should no longer appear. Specifically, (1) unicode-math requires ucharcat, and (2) XeTeX now incorporates ucharcat. But I am encountering the problem in XeTeX of TeX Live 2016/W32TeX. Any help would be appreciated. Kamal Abdali -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] unicode-math and ucharcat
David, Thank you for the solution. My texlive 2016 must have been missing ucharcat for some mysterious reason, so your suggestion of doing "tlmgr install ucharcat" fixed the problem! I also notice that you are the author of ucharcat for XeTeX. Kamal On Wed, Feb 8, 2017 at 4:49 PM, David Carlisle wrote: > ucharcat.sty isn't needed for xetex as it's already a primitive but if > you have texlive 2016 you should have ucharcat.sty (or tlmgr install > ucharcat should install it if for some reason it isn't installed > already). That said unicode-matth could move the luatex-specific part, > but really there's no reason not to have ucharcat installed. > > David > > > > > On 8 February 2017 at 21:38, Kamal Abdali wrote: > > When using the package unicode-math, I get the XeLaTex error: > > File `ucharcat.sty' not found. > > > > XeLaTex then asks for a new filename. When I enter an empty filename, > > XeLaTex proceeds normally. But to do this every time is annoying. > > > > The conclusion from some googling was that this error should no longer > > appear. Specifically, (1) unicode-math requires ucharcat, and (2) XeTeX > now > > incorporates ucharcat. > > > > But I am encountering the problem in XeTeX of TeX Live 2016/W32TeX. Any > help > > would be appreciated. > > > > Kamal Abdali > > > > > > > > > > > > > > > > -- > > 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
[XeTeX] "typeset by bidi" message
My xelatex-processed document has this message on the title page of the document: *"Typeset by the bidi package."* ** I understand that bidi is being called by polyglossia which I am using. I hadn't seen such a message before. Is there a way to avoid getting this message? Kamal Abdali -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Spam (7.421):Re: "typeset by bidi" message
On Thu, Jan 25, 2018 at 9:50 PM, Bruno Le Floch wrote:
> Hello Kamal,
>
> On 01/25/2018 09:10 PM, Kamal Abdali wrote:
> > My xelatex-processed document has this message on the title page of the
> > document: *"Typeset by the bidi package."*
> ...
>
> After loading the polyglossia package (but before selecting a language
> that reads right-to-left) try adding
>
> \usepackage[logo=off]{bidi}
>
> Strangely the default is logo=on and the option is not documented.
>
>
Thank you, Bruno, for your prompt message. You have solved my problem!
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Spam (7.421):Re: "typeset by bidi" message
Thanks, Gildas, for your suggestions. I'll try turning off pdfinfo() but I
need to first learn how to do it without the hyperref package which I'm not
using at this time.
I'm also an admirer of Vafa Kalighi's contribution which I use all the time.
On Thu, Jan 25, 2018 at 11:16 PM, Gildas Hamel wrote:
> * Skriv a reas Gildas Hamel n'eus ket pell (Thu Jan
> 25, 2018):
> |>
> |> You may also choose to turn off pdfinfo which is turned on by
> default. If left on, it shows up in the pdf's attributes as:
> |> Content Creator: The bidi package, v32.4, 2018/01/23
> |> PDF Producer: The bidi package, etc.
> |> --Gildas Hamel
>
> I forgot to add that the way I try to recognize the amazing work done over
> so many years by the undefatigable creator and maintainer of the bidi
> package, Vafa Khalighi, is to mention it in the preamble, via the
> hypersetup of the hyperref package:
>
> \hypersetup{
> pdfkeywords={key1, key2},%
> pdfcreator={XeLaTeX and the bidi package}
> }
> I do not know if this is sufficient. If there is a better way of
> recognizing the role of the bidi package, please let me know.
> --Gildas
>
>
> --
> 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] Spam (8.243):Re: Spam (7.421):Re: "typeset by bidi" message
Thanks again, Bruno, for your concise, precise, and effective answer!
On Thu, Jan 25, 2018 at 11:41 PM, Bruno Le Floch wrote:
> \usepackage[logo=off,pdfinfo=off]{bidi}
>
> On 01/25/2018 11:29 PM, Kamal Abdali wrote:
> >
> > Thanks, Gildas, for your suggestions. I'll try turning off pdfinfo() but
> > I need to first learn how to do it without the hyperref package which
> > I'm not using at this time.
> >
> > I'm also an admirer of Vafa Kalighi's contribution which I use all the
> time.
> >
> > On Thu, Jan 25, 2018 at 11:16 PM, Gildas Hamel > <mailto:gwel...@ucsc.edu>> wrote:
> >
> > * Skriv a reas Gildas Hamel > <mailto:gwel...@ucsc.edu>> n'eus ket pell (Thu Jan 25, 2018):
> > |>
> > |> You may also choose to turn off pdfinfo which is turned on by
> > default. If left on, it shows up in the pdf's attributes as:
> > |> Content Creator: The bidi package, v32.4, 2018/01/23
> > |> PDF Producer: The bidi package, etc.
> > |> --Gildas Hamel
> >
> > I forgot to add that the way I try to recognize the amazing work
> > done over so many years by the undefatigable creator and maintainer
> > of the bidi package, Vafa Khalighi, is to mention it in the
> > preamble, via the hypersetup of the hyperref package:
> >
> > \hypersetup{
> > pdfkeywords={key1, key2},%
> > pdfcreator={XeLaTeX and the bidi package}
> > }
> > I do not know if this is sufficient. If there is a better way of
> > recognizing the role of the bidi package, please let me know.
> > --Gildas
> >
> >
> > --
> > Subscriptions, Archive, and List information, etc.:
> > http://tug.org/mailman/listinfo/xetex
> > <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
[XeTeX] index not showing up as an entry in the table of contents
To get the index listed in the table of contents, I include these two lines
in the preamble of a xelatex+polyglossia+bidi program:
\usepackage[imakeidx]
\makeindex[intoc]
My problem is that while the index does get produced it doesn’t get listed
in the TOC. The trouble can be reproduced in this small program:
%%%
\documentclass{book}
\usepackage{imakeidx}
\makeindex[intoc]
\usepackage{polyglossia}
\usepackage{bidi} %
\setmainlanguage{english}
\title{Facts}
\author{Aleck}
\date{}
\begin{document}
\maketitle
\tableofcontents
\chapter{Stars}
Sirius, the brightest star in the night sky, is actually a double star.
\index{Sirius}
\printindex
\end{document}
The above program produces the index without listing it in the TOC.
However, if you comment out the \usepackage{bidi} line, the index IS
produced and listed in TOC as expected.
Note that the above program doesn’t really need bidi as all of its output
text is in the Latin script. But I do need the bidi feature in the actual
document that I need to process.
Any help will be appreciated.
Kamal Abdali
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] index not showing up as an entry in the table of contents
Thanks, Zdeněk. I found the problem and a solution for it discussed here:
https://tex.stackexchange.com/questions/263696/polyglossias-setotherlanguage-blocks-imakeindexs-indexprologue.
The solution did work for me.
Briefly, the problem is attributed to bidi's restoring the book definition
of the theindex environment for no apparent reason. The solution is to
insert the following lines between the \usepackage{imakeindex} and
\makeindex[intoc] lines:
% nullify bidi redefinition
% this should go after polyglossia and imakeidx have been loaded
\let\imakeidxtheindex\theindex
\let\imakeidxendtheindex\endtheindex
\AtBeginDocument{%
\let\theindex\imakeidxtheindex
\let\endtheindex\imakeidxendtheindex
}
Kamal Abdali
On Wed, Apr 25, 2018 at 4:25 AM, Zdenek Wagner
wrote:
> You have to redefine the header, it automatically inserts
> \chapter*{Index}. You have to remove the asterisk. I do not remember the
> details, I would have to search in the documentatin but it is written there.
>
>
> Zdeněk Wagner
> http://ttsm.icpf.cas.cz/team/wagner.shtml
> http://icebearsoft.euweb.cz
>
> 2018-04-24 23:09 GMT+02:00 Kamal Abdali :
>
>> To get the index listed in the table of contents, I include these two
>> lines in the preamble of a xelatex+polyglossia+bidi program:
>>
>> \usepackage[imakeidx]
>> \makeindex[intoc]
>>
>> My problem is that while the index does get produced it doesn’t get
>> listed in the TOC. The trouble can be reproduced in this small program:
>>
>> %%%
>> \documentclass{book}
>>
>> \usepackage{imakeidx}
>> \makeindex[intoc]
>>
>> \usepackage{polyglossia}
>> \usepackage{bidi} %
>> \setmainlanguage{english}
>>
>> \title{Facts}
>> \author{Aleck}
>> \date{}
>>
>> \begin{document}
>> \maketitle
>> \tableofcontents
>> \chapter{Stars}
>> Sirius, the brightest star in the night sky, is actually a double star.
>> \index{Sirius}
>> \printindex
>> \end{document}
>>
>>
>> The above program produces the index without listing it in the TOC.
>> However, if you comment out the \usepackage{bidi} line, the index IS
>> produced and listed in TOC as expected.
>>
>> Note that the above program doesn’t really need bidi as all of its output
>> text is in the Latin script. But I do need the bidi feature in the actual
>> document that I need to process.
>>
>> Any help will be appreciated.
>>
>> Kamal Abdali
>>
>>
>>
>>
>> --
>> 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
[XeTeX] how to customize sorting order of characters in index
I'm using polyglossia and imakeindex to produce an Urdu document. The sorting order of letters in the index is wrong. The order is according to Arabic, but Urdu has about 9 more letters which are being pushed after the Arabic letters in the index. I couldn't find an option to fix this in the imakeindex style file. It probably should be specified in polyglossia but I don't see a way there either. Any suggestions please? Kamal Abdali -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] how to customize sorting order of characters in index
Zdeněk, Thanks for responding promptly and offering to help. The Urdu letters, in their sorting order, are as follows: آ ا ب پ ت ٹ ث ج چ ح خ د ڈ ذ ر ڑ ز ژ س ش ص ض ط ظ ع غ ف ق ک گ ل م ن ں و ہ ھ ء ی ے As you mentioned the following letters never start a word: ھ ء ے And ں occurs only at the end of a word. (Urdu is working hard to create more challenges for its learners -:) ). But all the letters need to be included in the sorting order. T hanks in advance, Kamal Abdali On Sun, May 13, 2018 at 7:30 PM, Zdenek Wagner wrote: > I do not know how to do it in imakeindex but I could do it in xindy. I > have an Urdu-Hindi dictionary so I can find the sort oder of most > characters but I do not know where to put bari yeh (ے), dochashmee he (ھ) > and maybe a few more characters that never appear at the beginning of the > word. This is not too much work, if you give me the correct order of all > characters (including alif maqsura which appears in words like موسی), I can > make it (but it may take a few days, I am currently quite busy). > > > Zdeněk Wagner > http://ttsm.icpf.cas.cz/team/wagner.shtml > http://icebearsoft.euweb.cz > > 2018-05-14 1:04 GMT+02:00 Kamal Abdali : > >> I'm using polyglossia and imakeindex to produce an Urdu document. The >> sorting order of letters in the index is wrong. The order is according to >> Arabic, but Urdu has about 9 more letters which are being pushed after the >> Arabic letters in the index. I couldn't find an option to fix this in the >> imakeindex style file. It probably should be specified in polyglossia but I >> don't see a way there either. Any suggestions please? >> >> Kamal Abdali >> >> >> >> -- >> 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] how to customize sorting order of characters in index
Thanks, Dominik. I had seen your https://cikitsa.blogspot.ca/
2016/07/getting-xindy-to-work-for-iast-encoded.html before during a Web
searching. But a member of this group has kindly promised to write a xindy
piece for Urdu. So instead of trying to do the same also on my own, I am
trying to still make imakeidx/makeindex work. As far as I understand,
Makeindex sorts non-Latin characters in the order of their Unicode
numerical code. The following approach, awful and artificial though it is,
seems to sort Urdu index entries correctly, essentially by using the
makeindex command \index{string1@string2} where string2 is the actual Urdu
index entry and string1 is its representation described below:
Urdu letters
appear in the Arabic script Unicode block 0600-06FF. For about 12 letters,
the utf8 numerical order differs from their Urdu alphabetic order. For
example, in the Urdu alphabet the letter "peh" comes between the letters
"beh" and "teh", but in the Unicode table the utf8 of "peh" is larger than
that of "teh". So what I am doing is to represent "peh" by two characters,
"beh" followed by another one with utf8 larger than of all Urdu letters.
Actually, for these extra characters I use the so-called "Eastern Arabic
Digits" 0,1,2, ... which I can type on my keyboard and don't need
otherwise. Also if two or more Urdu letters come alphabetically between two
adjacent utf-8 positions, then for representing them this way with properly
ordered representations, digits serve as convenient and easily rememberable
extra characters.
Here, for example, is an \index command to get the Urdu word "ناکارگی"
(pronounced as nākāragī" and meaning "entropy" in English) show up in
its correct position in index:
\index{
ناق۰ارق۵ی
@
ناکارگی
{
Doing such extra work for many entries in the index is too cumbersome. But
at least the index is prepared correctly. And my priority for the moment is
to get something (in which the index is the only unfinished part) finished
and delivered, before worrying about elegant solutions! Thanks to everyone
who offered suggestions in response to my inquiries.
Kamal Abdali
On Wed, May 16, 2018 at 3:27 PM, Dominik Wujastyk
wrote:
> A while back, I had a similar issue, and I made some notes about how I got
> the sorting I needed. See here:
>
>- https://cikitsa.blogspot.ca/2016/07/getting-xindy-to-work-
>for-iast-encoded.html
>
>
>
> --
> Professor Dominik Wujastyk <http://ualberta.academia.edu/DominikWujastyk>
> ,
>
> Singhmar Chair in Classical Indian Society and Polity
> ,
>
> Department of History and Classics
> <http://historyandclassics.ualberta.ca/>
> ,
> University of Alberta, Canada
> .
>
> South Asia at the U of A:
>
> sas.ualberta.ca
>
>
>
> On 13 May 2018 at 17:04, Kamal Abdali wrote:
>
>> I'm using polyglossia and imakeindex to produce an Urdu document. The
>> sorting order of letters in the index is wrong. The order is according to
>> Arabic, but Urdu has about 9 more letters which are being pushed after the
>> Arabic letters in the index. I couldn't find an option to fix this in the
>> imakeindex style file. It probably should be specified in polyglossia but I
>> don't see a way there either. Any suggestions please?
>>
>> Kamal Abdali
>>
>>
>>
>> --
>> 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] how to customize sorting order of characters in index
On Fri, May 18, 2018 at 4:38 AM, Zdenek Wagner wrote: > ... > Being engaged in thermodynamics it is nice to know how entropy is said > in Urdu. My former boss has a large collection of "vapour-liquid > equilibrium" translated into many languages. How is it in Urdu? > ... (Taking a brief thermodynamical break on this group :-) ), the equivalent Urdu term would be بخارمائع تعادل (pronounced "bukẖār-māʾiʿ taʿādul"). ...There are many other problems. The Persion module is a good > startbecause Persian also makes use of a few non-Arabic letters > ... > > ... > > Zdeněk Wagner > http://ttsm.icpf.cas.cz/team/wagner.shtml > http://icebearsoft.euweb.cz > > I have several comments about what your suggestions. Let me write them carefully and send those to you a bit later. Thanks, Kamal -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] xelatex not connecting letters in awami nastaliq font
XeLaTeX (in combination with Polyglossia) is not rendering the Awami
Nastaliq font properly. The letters in this font are being displayed
without being connected together. I haven't encountered this problem with
any other nastaleeq font. Nor have I seen this problem when using Awami in
word processors.
%demo.tex
\documentclass[letterpaper]{article}
\usepackage{polyglossia}
\setmainlanguage{urdu}
\newfontfamily\urdufont[Script=Arabic]{Awami Nastaliq}
\newfontfamily\altnast[Script=Arabic]{Jameel Noori Nastaleeq} % or any
other nastaliq font
\setlength\parindent{0pt}
\begin{document}
عوامی نستعلیق\\
\altnast{جمیل نوری نستعلیق}
\end{document}
demo.pdf attached.
Kamal Abdali
awamiTest.pdf
Description: Adobe PDF document
Re: [XeTeX] xelatex not connecting letters in awami nastaliq font
Thank you Lorna and Jonathan for solving the problem.
Jonathan, I almost always need fontspec options like
[Script=Arabic,Scale=xx,WordSpace=yy] because different nastaliq fonts seem
to have very different letter sizes and word spacing behaviors. Moreover,
for some reason the Noto Nastaliq Urdu font doesn't connect letters if the
Script=Arabic option is omitted.
Kamal Abdali
On Sun, Feb 21, 2021 at 5:33 AM Jonathan Kew wrote:
> On 21/02/2021 03:27, Lorna Evans wrote:
> > Awami Nastaliq is a Graphite font. In XeTeX you would need to say "Awami
> > Nastaliq/GR". I'm not sure if that syntax would work in XeLaTeX, but
> > somehow you have to indicate Graphite.
> >
>
> The xelatex/fontspec way to say this would be
>
>\newfontfamily\urdufont[Renderer=Graphite]{Awami Nastaliq}
>
> (You might also want to add the option
>
>\XeTeXinterwordspaceshaping=1
>
> to your document, for better word spacing results.)
>
> JK
>
> > On Sat, Feb 20, 2021, 6:24 PM Kamal Abdali > <mailto:kabd...@gmail.com>> wrote:
> >
> > XeLaTeX (in combination with Polyglossia) is not rendering the Awami
> > Nastaliq font properly. The letters in this font are being displayed
> > without being connected together. I haven't encountered this problem
> > with any other nastaleeq font. Nor have I seen this problem when
> > using Awami in word processors.
> >
> > %demo.tex
> > \documentclass[letterpaper]{article}
> > \usepackage{polyglossia}
> > \setmainlanguage{urdu}
> > \newfontfamily\urdufont[Script=Arabic]{Awami Nastaliq}
> > \newfontfamily\altnast[Script=Arabic]{Jameel Noori Nastaleeq} % or
> > any other nastaliq font
> > \setlength\parindent{0pt}
> > \begin{document}
> > عوامی نستعلیق\\
> > \altnast{جمیل نوری نستعلیق}
> > \end{document}
> >
> > demo.pdf attached.
> >
> > Kamal Abdali
> >
>
>
Re: [XeTeX] xelatex not connecting letters in awami nastaliq font
>
> ... (The default
> word spacing in Awami should generally be quite good, especially if you
> use the \XeTeXinterwordspaceshaping=1 setting, but I assume it would
> still work to adjust it if you wish.)
>
The default works well. I'm glad XeTeX and fontspec have options to control
word spacing. Some people, including myself, prefer spacing between words
for readability as opposed to the true nastaliq enthusiasts who like words
kerned together.
Kamal
On Sun, Feb 21, 2021 at 1:30 PM Jonathan Kew wrote:
> On 21/02/2021 14:55, Kamal Abdali wrote:
> > Thank you Lorna and Jonathan for solving the problem.
> >
> > Jonathan, I almost always need fontspec options like
> > [Script=Arabic,Scale=xx,WordSpace=yy] because different nastaliq fonts
> > seem to have very different letter sizes and word spacing behaviors.
> > Moreover, for some reason the Noto Nastaliq Urdu font doesn't connect
> > letters if the Script=Arabic option is omitted.
>
> Noto Nastaliq Urdu is an OpenType font; OpenType requires that the
> correct script is specified so that it knows what shaping engine to use.
> (There's a default "generic" shaper that is used for Latin & other
> simple scripts, so in that case nothing needs to be explicitly
> specified, but Arabic and other "complex" scripts require the script to
> be specified so that script-specific rules can be applied.)
>
> Awami Nastaliq is a Graphite font; no script option is required as the
> shaping behavior is encoded entirely within the font; the engine is
> script-independent.
>
> So the Script option is not relevant for Awami, but you do need the
> Renderer=Graphite option to use the proper font engine. (The default
> word spacing in Awami should generally be quite good, especially if you
> use the \XeTeXinterwordspaceshaping=1 setting, but I assume it would
> still work to adjust it if you wish.)
>
> JK
>
> >
> > Kamal Abdali
> >
> > On Sun, Feb 21, 2021 at 5:33 AM Jonathan Kew > <mailto:jfkth...@gmail.com>> wrote:
> >
> > On 21/02/2021 03:27, Lorna Evans wrote:
> > > Awami Nastaliq is a Graphite font. In XeTeX you would need to say
> > "Awami
> > > Nastaliq/GR". I'm not sure if that syntax would work in XeLaTeX,
> but
> > > somehow you have to indicate Graphite.
> > >
> >
> > The xelatex/fontspec way to say this would be
> >
> > \newfontfamily\urdufont[Renderer=Graphite]{Awami Nastaliq}
> >
> > (You might also want to add the option
> >
> > \XeTeXinterwordspaceshaping=1
> >
> > to your document, for better word spacing results.)
> >
> > JK
> >
> > > On Sat, Feb 20, 2021, 6:24 PM Kamal Abdali > <mailto:kabd...@gmail.com>
> > > <mailto:kabd...@gmail.com <mailto:kabd...@gmail.com>>> wrote:
> > >
> > > XeLaTeX (in combination with Polyglossia) is not rendering
> > the Awami
> > > Nastaliq font properly. The letters in this font are being
> > displayed
> > > without being connected together. I haven't encountered this
> > problem
> > > with any other nastaleeq font. Nor have I seen this problem
> when
> > > using Awami in word processors.
> > >
> > > %demo.tex
> > > \documentclass[letterpaper]{article}
> > > \usepackage{polyglossia}
> > > \setmainlanguage{urdu}
> > > \newfontfamily\urdufont[Script=Arabic]{Awami Nastaliq}
> > > \newfontfamily\altnast[Script=Arabic]{Jameel Noori Nastaleeq}
> > % or
> > > any other nastaliq font
> > > \setlength\parindent{0pt}
> > > \begin{document}
> > > عوامی نستعلیق\\
> > > \altnast{جمیل نوری نستعلیق}
> > > \end{document}
> > >
> > > demo.pdf attached.
> > >
> > > Kamal Abdali
> > >
> >
>
>
Re: [XeTeX] Arabic fonts and ligatures after migrating machine
Hi Manuel,
I tried your file and it worked as expected. Attached is the resulting pdf.
I think that for default font lookup any downloaded fonts should be copied
into either /Library/Fonts or ~/Library/Fonts. FontBook "installs" fonts in
the latter directory. But "font installation" is nothing more than copying,
so manually copying the fonts is OK too.
Kamal Abdali
2010/4/29 Manuel Souto Pico
> Dear all,
>
> After migranting to a new machine and copying all files and installing
> Tex Live again, I find that when I try to typeset (in
> TexShop) some documents that I had in Arabic, ligatures stop working.
> I use Mac OS X 10.6.3.
>
> The font I use is Scheherazade. I copied the file
> ScheherazadeRegAAT.ttf in /System/Library/Fonts (although it doesn't
> appear in the Font Book, I don't know why).
>
> My minimal example is:
>
> %!TEX TS-program = xelatex-xdvipdfmx
> %!TEX encoding = UTF-8 Unicode
>
> \documentclass[a4paper]{article}
> \usepackage{polyglossia}
> \setmainlanguage{arabic}
> \setotherlanguage{galician}
> \newfontfamily\arabicfont[Scale=1.5,Script=Arabic]{Scheherazade}
>
> \title{السلام عليكم}
>
> \begin{document}
> \maketitle
> وعليكم السلام
> \end{document}
>
> and the log says:
>
> (...)
> ! Font \...@tempfontb=scheherazade/ICU at 10.0pt not loadable: Metric
> (TFM) file or installed font not found.
>
> and something else but I can't copy and paste. In any case, the
> document is not compiled.
>
> If I replace Scheherazade with Scheherazade-AAT or with other fonts
> (Times New Roman, Geeza Pro, etc.), the document is compiled but the
> ligatures don't work.
>
> Has anyone had this issue? Any clue about how to solve it? I probably
> need to teak some setting that I did long ago in my former computer.
>
> Cheers, Manuel
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
pico.pdf
Description: Adobe PDF document
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Position of kasra when used together with tashdid in Arabic
While the problem is with fonts, I think it is really caused by language differences. In Urdu, the convention for the tashdid-kasra combination is to put tashdid above and kasra below the letter. This convention applies even to Arabic texts (e.g., the Qurans) published in countries like Pakistan and India with large numbers of Urdu speakers. The Qurans published in Arab countries place kasra below the tashdid symbol, of course. Incidentally, there are several other orthographic differences in the Qurans published in Pakistan and India and those published in Arab countries. This variation is unfortunate because it limits the use of many fonts across different languages. Below is the image of a Mac TextEdit window with the tashdid-kasra combination in three different Urdu fonts. Kamal Abdali [image: tashdid-kasra-urdu.jpg] On Thu, Jul 8, 2010 at 15:02, Andy Lin wrote: > > The best thing is to try a font which does not have this kind of issue. > > I've attached a pdf file of various Arabic fonts (most of them are > included with newer versions of Windows). The string is input with > tashdid before kasra. The first column has the script set to Arabic, > the second column has the language set to Urdu (the SIL fonts behave > differently here!), and the third has the language set to Farsi. > > Hope this helps, > Andy > > > > -- > 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] Prime + Unicode-math
Here's a related problem.
The math symbols in XITS seem rather small. When trying to increase XITS
character size with the Scale option, I noticed that math accents get
amplified too much, and get placed too far from the subject symbols. The
example below shows that by comparing XITS and Asana math fonts.
\documentclass{article}
\usepackage{fontspec}
\usepackage{xltxtra}
\usepackage{unicode-math}
\begin{document}
\setmathfont[Scale=2.5]{XITS}
$P'''$
\setmathfont[Scale=1.5]{Asana Math}
$P'''$
\end{document}
Kamal Abdali
On Sun, Oct 3, 2010 at 14:11, Khaled Hosny wrote:
> On Sun, Oct 03, 2010 at 06:26:51PM +0100, José Carlos Santos wrote:
> > Hi all,
> >
> > If I compile this file:
> >
> > \documentclass{article}
> > \usepackage{fontspec}
> > \usepackage{xltxtra}
> > \usepackage{unicode-math}
> > \begin{document}
> > $P'$
> > \end{document}
> >
> > I get this error message:
> >
> > ! Undefined control sequence.
> > \um_prime_single_mchar
> >
> > l.6 $P'$
>
> You need to use a Unicode math font as well, TeXLive have XITS and
> Asana Math. There is no point in loading unicode-math without using a
> Unicode math font. I thin unicode-math package should handle this
> though, like issuing a warning or something.
>
> --
> 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
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Prime + Unicode-math
Thanks Will and Khaled for explaining the problem. Kamal On Tue, Oct 5, 2010 at 04:12, Khaled Hosny wrote: > On Mon, Oct 04, 2010 at 06:37:07PM -0400, Kamal Abdali wrote: > > Here's a related problem. > > > > The math symbols in XITS seem rather small. > > Because you are using the text font; XITS, not the math font; XITS Math, > the former will give you primes that are suitable for text since they > are already reduced in size and raised to superscript position, while > the math font have large primes since the engine does *scripting on its > own. > > 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 > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] polyglossia/bidi -- footnote rule alignment
I'm using the package polyglossia to typeset documents in Urdu, a
right-to-left language. Polyglossia uses the bidi package whose
documentation implies that the footnote rule is right-aligned when the
footnote is in the middle of some right-to-left text. But the footnote rule
is appearing aligned to the left anyway.
Here is an example:
\documentclass{article}
\usepackage{polyglossia}
\setmainlanguage{urdu}
\newfontfamily\urdufont[Script=Arabic,Scale=1.7]{Lateef}
%\rightfootnoterule %force footnote rule to right
\begin{document}
افلاطون
\footnote{یونانی فلسفی}
\end{document}
Unless the commented statement is uncommented, the footnote rule shows up on
the left.
Kamal Abdali
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] polyglossia/bidi -- footnote rule alignment
Dear Gareth,
Thanks for pointing out the better polyglossia style (\setmainfont).
As to the main problem, Vafa Khalighi has kindly explained that for the
footnoterule to be aligned correctly, the RTLdocument or rldocument option
of bidi has to be activated. Apparently, this has not been done by
polyglossia.
He has also recommended \autofootnoterule instead \rightfootnoterule.
That takes care of the problem. It is too easily fixed to require any change
in polyglossia or its language-specific files.
Kamal Abdali
==
On Thu, Oct 14, 2010 at 07:58, Gareth Hughes wrote:
> Kamal Abdali wrote:
> > I'm using the package polyglossia to typeset documents in Urdu, a
> > right-to-left language. Polyglossia uses the bidi package whose
> > documentation implies that the footnote rule is right-aligned when the
> > footnote is in the middle of some right-to-left text. But the footnote
> rule
> > is appearing aligned to the left anyway.
> >
> > Here is an example:
> >
> > \documentclass{article}
> > \usepackage{polyglossia}
> > \setmainlanguage{urdu}
> > \newfontfamily\urdufont[Script=Arabic,Scale=1.7]{Lateef}
> > %\rightfootnoterule %force footnote rule to right
> > \begin{document}
> > افلاطون
> > \footnote{یونانی فلسفی}
> > \end{document}
> >
> >
> > Unless the commented statement is uncommented, the footnote rule shows up
> on
> > the left.
> >
> > Kamal Abdali
>
> Dear Kamal,
>
> I can confirm that the footnote rule is wrongly positioned in your file.
> I thought that changing \newfontfamily\urdufont for \setmainfont might
> make a difference, but it doesn't (I think this replacement might be
> considered more correct in polyglossia). As you say, the footnote rule
> needs to be forced to be placed correctly.
>
> Gareth.
>
>
> --
> 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] arabic
Hi Ross,
On Wed, Oct 20, 2010 at 19:12, Ross Moore wrote:
> ...
> To find out what needs updating, put \listfiles
> in the preamble (e.g., after \makeindex )
> Then compare the list of package dates to those for what I'm using:
> viz.
>
> *File List*
>book.cls2007/10/19 v1.4h Standard LaTeX document class
>bk10.clo2007/10/19 v1.4h Standard LaTeX file (size option)
> ...
>
I compared, and saw that some of your files (e.g., *l3* files, xltxtra)
need updating -:) .
But here's a serious problem. My suggestion to Houda was that it might be
worthwhile to try xepersian or polyglossia, since these will use the Persian
words for "chapter", "contents", etc. But running the polyglossia code, I
notice that an index is generated only if the language declaration specifies
that Western numerals be used. That is,
\setmainlanguage[numerals=western]{farsi}
The same problem occurs with Arabic and Urdu. Here is a cut down variant of
Houda's code that will illustrate the complaint.
=
\documentclass{book}%
\usepackage{polyglossia}
\setmainlanguage{farsi}%[numerals=western]{farsi}
\setmainfont[Script=Arabic,Scale=1.3]{Scheherazade}%
\usepackage{makeidx}
\makeindex
\title{روش تولید نمایه توسط زیلاتک}
\author{مهدی امیدعلی}
\begin{document}
\maketitle
\chapter{ امتحان }
این اولین نمایه این متن است که برای امتحان آورده شده است.
\index{نمایہ }
\printindex
\end{document}
=
If the western numerals are not specified, this is what Makeindex says:
Scanning input file xetexQ5.idx...done (0 entries accepted, 1 rejected).
Nothing written in xetexQ5.ind.
Makeindex reads the idx file for sorting the indices. Probably, it finds the
non-Western numerals undecipherable.
Kamal Abdali
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] arabic
On Thu, Oct 21, 2010 at 03:17, Ulrike Fischer wrote:
> Am Thu, 21 Oct 2010 00:20:47 -0400 schrieb Kamal Abdali:
> >...
>
> Makeindex reads the idx file for sorting the indices. Probably, it finds
> the
> > non-Western numerals undecipherable.
>
> Yes, makeindex needs to understand numbers to be able to build page
> ranges and sort the page numbers. As default it understands the
> standard digits, alphabetic and roman page numbers.
>
> If you would redefine \thepage to e.g. \renewcommand\thepage{Page
> \arabic{page}} you would run into problems in an english document
> too.
>
> I would suggest that you try xindy.
>
>
Thanks, Ulrike, for the xindy recommendation. A recent tendency in Urdu
publications (which concern me most) is to use Western numerals, so
Makeindex will work partially. But in general xindy will be unavoidable.
Kamal Abdali
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] arabic
HI Houda and Ross,
Ross is of the opinion that the job of indexing in Arabic can be done with
makeindex. I did a little search and reading, and concluded that the job is
not one that can be done in an afternoon (or two). At least not without some
hints from Ross (and others).
For the xindy route, there are files that accompany the xepersian package.
Since the Persian alphabet is a superset of the Arabic one, those files
should suffice without change to create an Arabic index (assuming that they
work properly in Persian). Since the Urdu alphabet is a superset of the
Persian one, the Persian xindy still needs to be generalized somewhat. Sorry
to keep inserting Urdu in the discussion, but that concerns me most these
days. Moreover, a solution for Urdu should also work for Arabic. As I've
never used xindy before, the task again seems much more complex than an
afternoon's hacking :-).
The 2-column format is standard for indexing via makeindex.
Kamal
On Fri, Oct 22, 2010 at 10:02, houda araj wrote:
> Hello Kamal
>
> Could you give me more instruction on how to define an ist file. A working
> example would be fine.
> I have to create two columns index.
>
> Thanks
>
> Houda
>
>
> > From: ross.mo...@mq.edu.au
> > Date: Fri, 22 Oct 2010 16:01:54 +1100
>
> > To: xetex@tug.org
> > Subject: Re: [XeTeX] arabic
> >
> > Hello Kamal,
> >
> > On 22/10/2010, at 12:39 PM, Kamal Abdali wrote:
> >
> > > On Thu, Oct 21, 2010 at 03:17, Ulrike Fischer
> wrote:
> > > Am Thu, 21 Oct 2010 00:20:47 -0400 schrieb Kamal Abdali:
> > > >...
> > > > Makeindex reads the idx file for sorting the indices. Probably, it
> finds the
> > > > non-Western numerals undecipherable.
> > >
> > > Yes, makeindex needs to understand numbers to be able to build page
> > > ranges and sort the page numbers. As default it understands the
> > > standard digits, alphabetic and roman page numbers.
> > >
> > > If you would redefine \thepage to e.g. \renewcommand\thepage{Page
> > > \arabic{page}} you would run into problems in an english document
> > > too.
> > >
> > > I would suggest that you try xindy.
> > >
> > >
> > > Thanks, Ulrike, for the xindy recommendation. A recent tendency in Urdu
> publications (which concern me most) is to use Western numerals, so
> Makeindex will work partially. But in general xindy will be unavoidable.
> >
> > Well, I don't think it is unavoidable at all.
> >
> > You can define your own .ist (index-style) file for use
> > with makeindex .
> > Then you can ensure that a LaTeX macro reads the page-number
> > and converts it into the language form that you desire.
> >
> > Makeindex is extremely flexible, just as is Xindy.
> > You may need a bit of experience writing the correct LaTeX
> > macro to use, and have it applied appropriately, just as you'll
> > need to gain experience using Xindy, if you go down that path.
> >
> >
> > >
> > > Kamal Abdali
> >
> >
> > Hope this helps,
> >
> > Ross
> >
> >
> > Ross Moore ross.mo...@mq.edu.au
> > Mathematics Department office: E7A-419
> > Macquarie University tel: +61 (0)2 9850 8955
> > Sydney, Australia 2109 fax: +61 (0)2 9850 8114
> >
> >
> >
> >
> >
> >
> >
> > --
> > 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] arabic
Good to hear from you, Vafa. I would like to try persian.xdy, but can't find it. On my updated TeXLIve2010/MacTeX, it is neither in xepersian files nor in xindy files. Kamal On Fri, Oct 22, 2010 at 22:43, Vafa Khalighi wrote: > I disagree. If makeindex was so perfect, why would someone spends lots of > time inventing a new system. > > For languages like Persian, Urdu, and other complex scripts, makeindex is > not suitable and you have got to use xindy. > > > -- > بسی رنج بردم در این سال سی عَجَم زنده کردم بدین پارسی > > > > > > -- > 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] arabic
Dear Khaled, You are absolutely correct that collation is language-dependent. In fact, at least in Urdu there seems some disagreement about the place of at least two letters and a vagueness about defining the order for vocalized words (i.e., after inserting the short vowels that are generally omitted). But my hope was that once we have one standard table for a large alphabet and make it work with some indexing program, we could worry about the ordering variations. Kamal Abdali On Sat, Oct 23, 2010 at 05:32, Khaled Hosny wrote: > On Fri, Oct 22, 2010 at 08:47:04PM -0400, Kamal Abdali wrote: > > HI Houda and Ross, > > > > Ross is of the opinion that the job of indexing in Arabic can be done > with > > makeindex. I did a little search and reading, and concluded that the job > is not > > one that can be done in an afternoon (or two). At least not without some > hints > > from Ross (and others). > > > > For the xindy route, there are files that accompany the xepersian > package. > > Since the Persian alphabet is a superset of the Arabic one, those files > should > > suffice without change to create an Arabic index (assuming that they work > > properly in Persian). Since the Urdu alphabet is a superset of the > Persian > > one, the Persian xindy still needs to be generalized somewhat. Sorry to > keep > > inserting Urdu in the discussion, but that concerns me most these days. > > Moreover, a solution for Urdu should also work for Arabic. As I've never > used > > xindy before, the task again seems much more complex than an afternoon's > > hacking :-). > > I think collation rules are language dependant, some letters get > different sort order in Arabic and Persian, so the files should be > checked carefully before use in other languages. Some, if not most > depending on the field, Arabic authors will prefer Abjadi order which is > totally different from Alphabetical order. > > 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 > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] arabic
Thanks, Ross, for your effort to tame makeindex for the Arabic script.
I also came across an interesting Persian sample that uses xepersian and
makeindex. The pdf and tex source are at
http://www.parsilatex.com/joomla/attachments/vahid-seminar.pdf
http://www.parsilatex.com/joomla/attachments/vahid-seminar.tex
Missing some of the source components, I couldn't reproduce the pdf exactly.
But lo and behold, the index was generated without fuss and in the desired
order of entries. I am still mystified why the letters are disconnected in
the text, but that's another debugging chore.
Kamal Abdali
On Sat, Oct 23, 2010 at 18:30, Ross Moore wrote:
> Hi Vafa, Houda, Kamal, Ulrike and others,
>
>
> On 23/10/2010, at 1:43 PM, Vafa Khalighi wrote:
>
> > I disagree. If makeindex was so perfect, why would someone spends lots of
> time inventing a new system.
>
> Nobody said makeindex was perfect, just that it may be
> sufficient for the job at hand.
>
> If the only problem is in representing the page-numbers using
> other than western digits, then this is certainly achievable.
> (See below for the kind of configuration that is needed.)
>
> On the other hand, Makeindex would have difficulty sorting
> the index entries automatically, according to rules
> for non-latin scripts, unless there were extra sorting
> tags provided with \index instances of the form
> \index{...@.}
>
>
> >
> > For languages like Persian, Urdu, and other complex scripts, makeindex is
> not suitable and you have got to use xindy.
>
> Until you have defined exactly what tasks are needed,
> and how they need to fit with the workflow being employed,
> how can you presume to say what is suitable and what is not?
>
> >
> >
> > --
> > بسی رنج بردم در این سال سی عَجَم زنده کردم بدین پارسی
> >
>
> If the *only* problem is to deal with the page numbers
> in the .ind file, such as the OP gets using the defaults
> for Makeindex; viz.
>
> >>> \begin{theindex}
> >>>
> >>> \item test, 5
> >>>
> >>> \indexspace
> >>>
> >>> \item نمایه, 5
> >>>
> >>> \end{theindex}
>
> (Beware the RTL text may be confusing the appearance
> of the actual byte order here.)
>
> You can configure to get the following instead:
>
> >>> \begin{theindex}
> >>>
> >>> \item test, \pagenumstyled 5
> >>>
> >>> \indexspace
> >>>
> >>> \item نمایه, \pagenumstyled 5
> >>>
> >>> \end{theindex}
>
>
> Now all that is needed is to define \pagenumstyled
> appropriately, to "read ahead" and adjust how the
> page number is to be displayed.
> Here is example (La)TeX coding that does this:
>
> \RequirePackage{arabicnumbers}
> \newcount\pageindcnt
> \def\pagenumstyled{\afterassignment\dopagenumstyle\pageindcnt}
> \def\dopagenumstyle{\arabicdigits{\number\pageindcnt}}
>
>
>
> So how is the configuration achieved?
>
> Use a customised .ist file.
> The following is minimal. It can be easily extended to cope
> with nested entries and headings for letter-ranges, etc.
>
> >>> start of file myind.ist %%%
> >>> preamble
> >>> "\\begin{theindex} \n "
> >>> postamble
> >>> "\n\n \\end{theindex}\n"
> >>> delim_0 ", \\pagenumstyled "
> >>> end of myind.ist %%%
>
>
> To use this the call to Makeindex needs to be include
> extra parameters; e.g.
>
> makeindex -s ./myind.ist -o test-arabe1.ind test-arabe1.idx
>
> for a document named test-arabe1.tex
> This will load the customised .ist file from
> the same directory as the document source.
>
> Of course you could put it in another loaction that
> Makeindex will find, or you could adjust the TeXshop
> command for Makeindex, or use a shell script, or ...
>
> Do whatever fits best with your workflow.
>
>
> Here is a neat way, using \write18 that keeps all of
> the coding together in your LaTeX document's preamble:
>
>
> >>> \usepackage{makeidx}
> >>> \RequirePackage{arabicnumbers}
> >>> \newcount\pageindcnt
> >>> \def\pagenumstyled{\afterassignment\dopagenumstyle\pageindcnt}
> >>> \def\dopagenumstyle{\arabicdigits{\number\pageindcnt}}
> >>> \immediate\write18{makeindex -s ./myind.ist -o test-arabe1.ind
> test-arabe1.idx}
> >>> \makeindex
>
>
>
> Note that the call to 'makeindex' must come *before* the \makeindex ,
> >
>
> so that it u
Re: [XeTeX] arabic
Hi Houda, Ross, and others,
In the previous message, I had mentioned Vahid Damanafshan's sample
mathematical document in Persian that uses makeindex with xepersian. With
some trivial improvisation, the TeX source ran successfully and almost
duplicated the original pdf. The index generation seems satisfactory.
Houda: This may be the kind of example code you were looking for. It
illustrates not just the index but a lot of other features of a scholarly
document. If you don't want to substitute any fonts, the ones needed can be
downloaded from http://wiki.irmug.org/index.php/X_Series_2. The order of
index entries is alphabetical, not abjadi. If you insist on the latter, then
some options and tables have to be changed.
Ross: The steps in TeXShop were exactly the same as needed with an English
document: TeX engine command twice; Makeindex command once; TeX engine
command once again. TeXShop has built-in keys and menus for both. MakeIndex
worked without any options, hints, additional collation tables, extra
scripts, etc. Perhaps xepersian provides the support that makeindex needs.
Kamal Abdali
On Sun, Oct 24, 2010 at 15:05, Kamal Abdali wrote:
> Thanks, Ross, for your effort to tame makeindex for the Arabic script.
>
> I also came across an interesting Persian sample that uses xepersian and
> makeindex. The pdf and tex source are at
> http://www.parsilatex.com/joomla/attachments/vahid-seminar.pdf
> http://www.parsilatex.com/joomla/attachments/vahid-seminar.tex
> Missing some of the source components, I couldn't reproduce the pdf
> exactly. But lo and behold, the index was generated without fuss and in the
> desired order of entries. I am still mystified why the letters are
> disconnected in the text, but that's another debugging chore.
>
> Kamal Abdali
>
> On Sat, Oct 23, 2010 at 18:30, Ross Moore wrote:
>
>> Hi Vafa, Houda, Kamal, Ulrike and others,
>>
>>
>> On 23/10/2010, at 1:43 PM, Vafa Khalighi wrote:
>>
>> > I disagree. If makeindex was so perfect, why would someone spends lots
>> of time inventing a new system.
>>
>> Nobody said makeindex was perfect, just that it may be
>> sufficient for the job at hand.
>>
>> If the only problem is in representing the page-numbers using
>> other than western digits, then this is certainly achievable.
>> (See below for the kind of configuration that is needed.)
>>
>> On the other hand, Makeindex would have difficulty sorting
>> the index entries automatically, according to rules
>> for non-latin scripts, unless there were extra sorting
>> tags provided with \index instances of the form
>> \index{...@.}
>>
>>
>> >
>> > For languages like Persian, Urdu, and other complex scripts, makeindex
>> is not suitable and you have got to use xindy.
>>
>> Until you have defined exactly what tasks are needed,
>> and how they need to fit with the workflow being employed,
>> how can you presume to say what is suitable and what is not?
>>
>> >
>> >
>> > --
>> > بسی رنج بردم در این سال سی عَجَم زنده کردم بدین پارسی
>> >
>>
>> If the *only* problem is to deal with the page numbers
>> in the .ind file, such as the OP gets using the defaults
>> for Makeindex; viz.
>>
>> >>> \begin{theindex}
>> >>>
>> >>> \item test, 5
>> >>>
>> >>> \indexspace
>> >>>
>> >>> \item نمایه, 5
>> >>>
>> >>> \end{theindex}
>>
>> (Beware the RTL text may be confusing the appearance
>> of the actual byte order here.)
>>
>> You can configure to get the following instead:
>>
>> >>> \begin{theindex}
>> >>>
>> >>> \item test, \pagenumstyled 5
>> >>>
>> >>> \indexspace
>> >>>
>> >>> \item نمایه, \pagenumstyled 5
>> >>>
>> >>> \end{theindex}
>>
>>
>> Now all that is needed is to define \pagenumstyled
>> appropriately, to "read ahead" and adjust how the
>> page number is to be displayed.
>> Here is example (La)TeX coding that does this:
>>
>> \RequirePackage{arabicnumbers}
>> \newcount\pageindcnt
>> \def\pagenumstyled{\afterassignment\dopagenumstyle\pageindcnt}
>> \def\dopagenumstyle{\arabicdigits{\number\pageindcnt}}
>>
>>
>>
>> So how is the configuration achieved?
>>
>> Use a customised .ist file.
>> The following is minimal. It can be easily extended to cope
>> with nested entries and headings for letter-ranges, etc.
>
Re: [XeTeX] Persian verus Farsi
Thanks, Vafa, for the link to Suren-Pahlav's very informative and interesting article. I was struck by the quote in it from Frances Pritchett that the use of the word "Farsi" was further promoted by Urdu-speakers. I wonder whether she is referring to her conversations with her Urdu-speaking colleagues in Urdu or in English. I, an Urdu speaker by birth, learned in childhood that the same language is called "Persian" in English and "Farsi" in Urdu (sometimes "Parsi", specially in poetry.) For example, that's how the Persian language class was listed differently in school schedules depending on whether the schedule was posted in Urdu or English. Different English and Urdu names also applied to many other languages, countries, and people. Urdu books often refer to English, French, Spanish, and Dutch languages, respectively, as "Angrezi", "Faransesi", "Hispanvi", and "Volandezi". This is consistent with different names used in different languages to refer to the same language. What is called "Deutsch" in its own language is called "German" in English, "Allemagne" in French, "Tedesco" in Italian, etc. The word "Farsi" seems to have been used in Arabic for a long time to refer to Persian, even by writers of Persian origin. For example, in the Introduction of the Arabic version of the famous book on complete quadrilaterals by the great 13th century Persian scientist Tusi, I see the statement that the author originally wrote the book in "Farsi" but then translated it into "Arabi" on the request of some of his scholarly friends. There doesn't seem much to worry about Persian (or any other language) being called differently in different languages. The cause for alarm is if a particular language is suddenly and deliberately renamed by some group. In English the subject language has been called "Persian" for centuries. So it should be of concern that the Foreign Language School administered by the US State Department calls it "Farsi"! Kamal Abdali = On Fri, Jun 10, 2011 at 08:48, Vafa Khalighi wrote: > A while ago, I insisted on using the word "Persian" instead "Farsi". My > friend, Shapour * *Suren-Pahlav from the circle of ancient Iranian studies > has written an article about this. You can see his article here: > http://www.cais-soas.com/CAIS/Languages/persian_not_farsi.htm* > * > > > > -- > 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] Persian verus Farsi
Petr, There is nothing wrong with names changing gradually as words in every language change over time. But one is naturally concerned if the renaming is needless, sudden, and suspected to be politically motivated, e.g., by the decision of foreign governments or groups. Names are a very sensitive matter. Just look at the large number of countries and cities that have been renamed in the last 30 or so years: Burma -> Myanmar, Ceylon -> Sri Lanka, Rhodesia -> Zimbabwe, Basutoland -> Lesotho, Bombay -> Mumbai, Madras -> Chennai. The new names were adopted by popular demand because the older names were thought to have been introduced by colonizers, occupiers, ruling elites, etc. Kamal Abdali On Sun, Jun 12, 2011 at 18:14, Petr Tomasek wrote: > > There doesn't seem much to worry about Persian (or any other language) > being > > called differently in different languages. The cause for alarm is if a > > particular language is suddenly and deliberately renamed by some group. > In > > English the subject language has been called "Persian" for centuries. So > it > > should be of concern that the Foreign Language School administered by the > US > > State Department calls it "Farsi"! > > > > Kamal Abdali > > What's wrong with it? It's natural that names do change and there > doesn't have to be any "political" reason for that... > > -- > Petr Tomasek <http://www.etf.cuni.cz/~tomasek> > Jabber: but...@jabbim.cz > > > EA 355:001 DU DU DU DU > EA 355:002 TU TU TU TU > EA 355:003 NU NU NU NU NU NU NU > EA 355:004 NA NA NA NA NA > > > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] genotype
Here's a suggestion:
\newcommand\gen[2]{ %genotype
$
\left( \mathop{{}_{\overline{\overline{#2}}}^{#1}}\right)
$
}
The double bar will be sized for the bottom symbol. So if the top symbol
has a different size, the result won't look nice.
On Sun, Jan 1, 2012 at 13:46, Jean-Louis Cordonnier wrote:
> In order to write genetics, I need something like $\frac{A}{a}$ but with
> a double horizontal bar -- and left( and right)
> I tried this, but there is too much white around it.
>
> \newcommand\gen[2]{ %genotype
>
> $
>
> \left(
>
> \begin{array}{c} #1 \\
>
> \hline \hline #2\\
>
> \end{array}
>
> \right)
>
> $
>
>
>
>
> --
> 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] Problems beginning typesetting arabic text
On Sat, Feb 25, 2012 at 14:49, Tobias Schoel wrote: > Hello to all, > > Finally, a little question concerning Arabic typesetting in General: > > The above line in Arabic shall be a headline for instructions, so it > should be heavily emphasised. In Latin script, I would typeset it larger > and with a bold face. In Arabic, this seems to be wrong as the usual Arabic > fonts don't include bold faces. So how is heavy and attention drawing > emphasis done in Arabic script? > > > The X Series 2 (http://wiki.irmug.com/index.php/X_Series_2) is a nice set of fonts (with families named XB Zar, etc.) with bold, italic, and bold italic variants. Some families also have the "oblique" face variant in which the slanting direction is opposite to the one in italic. Kamal Abdali > -- > Tobias Schoel > Europaschule Kairo > www.europaschulekairo.com > > > --** > Subscriptions, Archive, and List information, etc.: > > http://tug.org/mailman/**listinfo/xetex<http://tug.org/mailman/listinfo/xetex> > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] arabic
With XeTeX, there seems less need of language-specific packages because the
characters of various alphabets can be directly typed. So this produces the
same output as Nathan's program:
\documentclass[12pt]{article}
\usepackage{fontspec}
\newfontfamily\A[Script=Arabic,Scale=1.4,WordSpace=2]{Amiri} % Scheherazade
\begin{document}
\begin{tabular}{c c}
{\A
مثلث
} & {\A
١٢٣٤
}
\end{tabular}
\end{document}
=
On Sun, Apr 1, 2012 at 11:15, Nathan Sidoli wrote:
> This works for me:
> --
> \documentclass[12pt,a4paper]{**article}
>
> \usepackage{fontspec}
>
> \usepackage[novoc,fdf2noalif]{**arabxetex} %
> \newfontfamily\arabicfont[**Script=Arabic,Scale=1.4,**WordSpace=2]{Amiri}
> % Scheherazade
> \newcommand{\A}{\textarabic} % Tag for all Arabic text
>
> \begin{document}
>
> \begin{tabular}{c c}
> {\A{m_tl_t}} & {\A{1234}}
> \end{tabular}
>
> \end{document}
>
>
>
>
> On 12/04/01 23:37, Jean-Louis Cordonnier wrote:
>
>> My tex file works properly with text only but gives an error if I want
>> to use tabular :
>>
>> \begin{tabular}[l]
>> \textarab[voc]{`arabI}
>> \end{tabular}
>>
>>
>> Le 18/01/2012 18:55, Zdenek Wagner a écrit :
>>
>>> 2012/1/18 Jean-Louis Cordonnier**:
>>>
I try to write a few word in arabic ;
I get this error message :
Package bidi Error: Oops! you have loaded package xunicode before bidi
packag
e. Please load package xunicode after bidi package, and then try to run
xelatex
on your document again.
Load arabxetex before xltxtra. Arabxetex loads bidi, xltxtra loads
>>> xunicode.
>>>
>>> I dont understand why (where in bidi documentation ?)
My file
|\documentclass{article}
\usepackage{xltxtra}
\newfontfamily{\arabicfont}[**Script=Arabic,Scale=1.5]{**Traditional
Arabic}
\usepackage{arabxetex}
\begin{document}
\section{\textarab[utf]{**العربية}}
\textarab[utf]{السلم عليكم و رحمت الله و بركته}
\section{Legacy syntax}
When he goes---``Salamun alaykum!''\\
She replies—“Wa alaykumus-salam, dear!”
\end{document}|
--**
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] arabic
My point was that some of the functionality of language-specific packages
is already built-in into XeTeX. Facility for inputting the text is one
such. ArabTeX has special Tex commands for representing individual Arabic
letters, and for turning vocalization on or off. These are redundant in
XeTeX. We can just type the text, adding vowel marks to any letter if
needed. Below is a (trivial) modification of the previous (trivial) program
to illustrate this (for those who are new to typesetting Arabic with TeX).
Of course, for advanced editing, you are better off using special packages.
Personally I am quite happy at present with the package polyglossia. It has
support for several languages, including most of the languages that use the
Arabic script. The nice thing is that you can mix texts from as many
languages and alphabets as you need. For the text direction control,
polyglossia has the bidi package loaded already.
\documentclass[12pt]{article}
\usepackage{fontspec}
\newfontfamily\A[Script=Arabic,Scale=1.4,WordSpace=2]{Amiri} % Scheherazade
\begin{document}
\begin{tabular}{c c c}
{\A
مُثَلَّث
}& {\A
١٢٣٤
}&
Triangle
\end{tabular}
\end{document}
=
=
On Wed, Apr 4, 2012 at 06:09, Zdenek Wagner wrote:
> 2012/4/3 Kamal Abdali :
> > With XeTeX, there seems less need of language-specific packages because
> the
> > characters of various alphabets can be directly typed. So this produces
> the
> > same output as Nathan's program:
> >
> In such a trivial case you certainly do not need other packages but
> for real use with an Arabic script you need at least the bidi package.
>
> > \documentclass[12pt]{article}
> > \usepackage{fontspec}
> > \newfontfamily\A[Script=Arabic,Scale=1.4,WordSpace=2]{Amiri} %
> Scheherazade
> >
> > \begin{document}
> > \begin{tabular}{c c}
> > {\A
> > مثلث
> > } & {\A
> > ١٢٣٤
> > }
> > \end{tabular}
> >
> > \end{document}
> > =
> >
> > On Sun, Apr 1, 2012 at 11:15, Nathan Sidoli
> > wrote:
> >>
> >> This works for me:
> >> --
> >> \documentclass[12pt,a4paper]{article}
> >>
> >> \usepackage{fontspec}
> >>
> >> \usepackage[novoc,fdf2noalif]{arabxetex} %
> >> \newfontfamily\arabicfont[Script=Arabic,Scale=1.4,WordSpace=2]{Amiri} %
> >> Scheherazade
> >> \newcommand{\A}{\textarabic} % Tag for all Arabic text
> >>
> >> \begin{document}
> >>
> >> \begin{tabular}{c c}
> >> {\A{m_tl_t}} & {\A{1234}}
> >> \end{tabular}
> >>
> >> \end{document}
> >>
> >>
> >>
> >>
> >> On 12/04/01 23:37, Jean-Louis Cordonnier wrote:
> >>>
> >>> My tex file works properly with text only but gives an error if I want
> >>> to use tabular :
> >>>
> >>> \begin{tabular}[l]
> >>> \textarab[voc]{`arabI}
> >>> \end{tabular}
> >>>
> >>>
> >>> Le 18/01/2012 18:55, Zdenek Wagner a écrit :
> >>>>
> >>>> 2012/1/18 Jean-Louis Cordonnier:
> >>>>>
> >>>>> I try to write a few word in arabic ;
> >>>>> I get this error message :
> >>>>> Package bidi Error: Oops! you have loaded package xunicode before
> bidi
> >>>>> packag
> >>>>> e. Please load package xunicode after bidi package, and then try to
> run
> >>>>> xelatex
> >>>>> on your document again.
> >>>>>
> >>>> Load arabxetex before xltxtra. Arabxetex loads bidi, xltxtra loads
> >>>> xunicode.
> >>>>
> >>>>> I dont understand why (where in bidi documentation ?)
> >>>>>
> >>>>> My file
> >>>>>
> >>>>> |\documentclass{article}
> >>>>> \usepackage{xltxtra}
> >>>>> \newfontfamily{\arabicfont}[Script=Arabic,Scale=1.5]{Traditional
> >>>>> Arabic}
> >>>>> \usepackage{arabxetex}
> >>>>>
> >>>>> \begin{document}
> >>>>> \section{\textarab[utf]{العربية}}
> >>>>> \textarab[utf]{السلم عليكم و رحمت الله و بركته}
> >>>>>
> >>>>> \section{Legacy syntax}
> >>>>> When he goes---``Salamun alaykum!''\\
> >>>>> She replies—“Wa alaykumus-salam, dear!”
> >>>>> \end{document}|
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> 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
> >
>
>
>
> --
> Zdeněk Wagner
> http://hroch486.icpf.cas.cz/wagner/
> http://icebearsoft.euweb.cz
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
