Aleph queries

older
t-bib and hyperlinkded references?

Duncan Hothersall

15 Jun 2006 15 Jun '06

10:30 a.m.

Hello all (especially Idris :-) ) Using the fantastic resources from Idris' messages on this list, and the Aleph page on the Wiki, I have managed to start producing Arabic PDF output directly from UTF-8 sources using Aleph and dvipdfmx. This is great, thanks so much. I have just one or two queries and things I wasn't able to make work. I hope someone can help. My test file is here: http://www.capdm.com/public/context/omarab-queries1.tex And the output it generates is here: http://www.capdm.com/public/context/omarab-queries1.pdf First question - how do I get italic text? The first three paragraphs in the test are identical content, but the second has {\it ...} around it and the third has {\bf ...} around it. The third para comes out perfectly in bold, but the second para looks the same as the first. How can I get italics? Second question - that same first para contains 5 ligatures. They don't seem to match the rest of the font. Is this a set-up issue, or is it the way the font is designed? If it is a set-up issue, is there a way to fix it? Third and final question - I inserted a section and two subsections to demonstrate that the numbering of subsections is left-to-right. How can I make it right-to-left? (Explanation: the PDF shows section "1", and then subsections "1-1" and "1-2"; reading the numbers from right-to-left, I need it to show as section "1" and then subsections "1-1" and "2-1". In the subsection the "1" should come first when reading rtl.) Thanks very much for any help. Bests, Duncan

Show replies by date

Idris Samawi Hamid

15 Jun 15 Jun

6:28 p.m.

Hi Duncan, On Thu, 15 Jun 2006 02:30:15 -0600, Duncan Hothersall wrote:

...

Using the fantastic resources from Idris' messages on this list, and the Aleph page on the Wiki, I have managed to start producing Arabic PDF output directly from UTF-8 sources using Aleph and dvipdfmx. This is great, thanks so much.

Glad you liked it:-)

...

I have just one or two queries and things I wasn't able to make work. I hope someone can help.

My test file is here: http://www.capdm.com/public/context/omarab-queries1.tex And the output it generates is here: http://www.capdm.com/public/context/omarab-queries1.pdf

First question - how do I get italic text? The first three paragraphs in the test are identical content, but the second has {\it ...} around it and the third has {\bf ...} around it. The third para comes out perfectly in bold, but the second para looks the same as the first. How can I get italics?

There is no italic font, only regular and bold, so \it just maps to the default regular font.

...

Second question - that same first para contains 5 ligatures. They don't seem to match the rest of the font. Is this a set-up issue, or is it the way the font is designed? If it is a set-up issue, is there a way to fix it?

Both :-) You could edit the cuni2oar otp (and recompile it) so that it ignores the ligatures you don't like, or you could put a kashidah between the two letters whose ligature you want to break. Better is to define an "empty" kashidah so that you can manually break the ligature without stretching the word. I'll look into this in the next few days (busy right now) if you remind me-)

...

Third and final question - I inserted a section and two subsections to demonstrate that the numbering of subsections is left-to-right. How can I make it right-to-left? (Explanation: the PDF shows section "1", and then subsections "1-1" and "1-2"; reading the numbers from right-to-left, I need it to show as section "1" and then subsections "1-1" and "2-1". In the subsection the "1" should come first when reading rtl.)

Add \reversesectionnumberstrue to your Arabic definition: \def\ArabicUTF{\ArabicDirGlobal\usefiltersequence[UTFArabic] \reversesectionnumberstrue\switchtobodyfont[omarb]} Ideally when one selects global RL this should happen automatically. This is being planned for the future :-) Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Duncan Hothersall

21 Jun 21 Jun

5:37 p.m.

Idris Samawi Hamid (15/06/2006 17:28) said:

...

You could edit the cuni2oar otp (and recompile it) so that it ignores the ligatures you don't like, or you could put a kashidah between the two letters whose ligature you want to break. Better is to define an "empty" kashidah so that you can manually break the ligature without stretching the word. I'll look into this in the next few days (busy right now) if you remind me-)

Thanks very much for this, but unfortunately as an Arabic typesetting novice I can't quite follow it (the comments on the ligatures came from a proofreader). Am following this up via another route to try to better understand what to do, but if you really did want a reminder about this - here it is :-)

...

Add \reversesectionnumberstrue to your Arabic definition:

Ah, great, perfect. Now I have a follow-up to that one: I also would like figure and table numbering to have the chapternumber in the right order and use - as a separator. In other words, in English I use \in{Figure}[figref0102] to generate "Figure 1.2" and in Arabic I'd like to use \in{رسم بياني }[figref0102] to generate "رسم بياني 1-2" Any advice for that? (I had a search for other \reverse type commands but no luck :-( Many thanks again. Duncan PS. Apologies if the UTF-8 content there doesn't show up correctly.

Idris Samawi Hamid

5:55 p.m.

On Wed, 21 Jun 2006 09:37:50 -0600, Duncan Hothersall wrote:

...

Idris Samawi Hamid (15/06/2006 17:28) said:

...
You could edit the cuni2oar otp (and recompile it) so that it ignores the ligatures you don't like, or you could put a kashidah between the two letters whose ligature you want to break. Better is to define an "empty" kashidah so that you can manually break the ligature without stretching the word. I'll look into this in the next few days (busy right now) if you remind me-)

Thanks very much for this, but unfortunately as an Arabic typesetting novice I can't quite follow it (the comments on the ligatures came from a proofreader).

...

Am following this up via another route to try to better understand what to do, but if you really did want a reminder about this - here it is :-)

Well, I don't know which ligatures the proofreader liked/did not like so...

...

...
Add \reversesectionnumberstrue to your Arabic definition:

Ah, great, perfect.

Now I have a follow-up to that one: I also would like figure and table numbering to have the chapternumber in the right order and use - as a separator. In other words, in English I use

\in{Figure}[figref0102]

to generate

"Figure 1.2"

and in Arabic I'd like to use

\in{رسم بياني }[figref0102]

to generate

"رسم بياني 1-2"

Any advice for that? (I had a search for other \reverse type commands but no luck :-(

Hans, can you do a \reverse macro for this? Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Duncan Hothersall

6:11 p.m.

...

...
Am following this up via another route to try to better understand what to do, but if you really did want a reminder about this - here it is :-)

Well, I don't know which ligatures the proofreader liked/did not like so...

Sorry, I realise that was a bit stupid of me... Thanks for your patience. :-) Duncan

Idris Samawi Hamid

6:44 p.m.

On Wed, 21 Jun 2006 10:11:06 -0600, Duncan Hothersall wrote:

...

...
Well, I don't know which ligatures the proofreader liked/did not like so...

Sorry, I realise that was a bit stupid of me... Thanks for your patience. :-)

I suspect it may be that the lam-yaa ligature appears to collide with the preceding yaa. My suggestion: instead of getting rid of the ligature do a global replace of يلي by يـلي and the like (placing the kashidah before the ligature). I could tell the otp to do this as well but that would take some testing etc. and I'm just swamped at the moment. Let me know what you would prefer and I'll get to it as soon as I can :-) Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Hans Hagen

6:35 p.m.

Idris Samawi Hamid wrote:

...

...
and in Arabic I'd like to use

\in{رسم بياني }[figref0102]

to generate

"رسم بياني 1-2"

Any advice for that? (I had a search for other \reverse type commands but no luck :-(

Hans, can you do a \reverse macro for this? what do you mean with \reverse

bla bla left to right bla bla \in {something arab right left} bla bla i assume that arab always should be reverse so one should either explicitly enable arab or is there something wrong with the \in macro ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Idris Samawi Hamid

6:54 p.m.

On Wed, 21 Jun 2006 10:35:14 -0600, Hans Hagen wrote:

...

...
...
\in{رسم بياني }[figref0102]

to generate

"رسم بياني 1-2"

Any advice for that? (I had a search for other \reverse type commands but no luck :-(

Hans, can you do a \reverse macro for this? what do you mean with \reverse

bla bla left to right bla bla \in {something arab right left} bla bla

i assume that arab always should be reverse so one should either explicitly enable arab or is there something wrong with the \in macro

In Latin we write

in Arabic we want the equivalent of <2.1 erugiF> but Duncan seems to be getting <1.2 erugiF> even with global Arabic settings. In addition Duncan would like to use a dash instead of a period: <2-1 erugiF> Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Hans Hagen

7:05 p.m.

Idris Samawi Hamid wrote:

...

On Wed, 21 Jun 2006 10:35:14 -0600, Hans Hagen wrote:

...
...
...
\in{رسم بياني }[figref0102]

to generate

"رسم بياني 1-2"

Any advice for that? (I had a search for other \reverse type commands but no luck :-(

Hans, can you do a \reverse macro for this?

what do you mean with \reverse

bla bla left to right bla bla \in {something arab right left} bla bla

i assume that arab always should be reverse so one should either explicitly enable arab or is there something wrong with the \in macro

In Latin we write

in Arabic we want the equivalent of

<2.1 erugiF>

but Duncan seems to be getting

<1.2 erugiF>

even with global Arabic settings.

so it's only the number that's wrong?

...

In addition Duncan would like to use a dash instead of a period:

<2-1 erugiF>

that's configurable Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Idris Samawi Hamid

8:04 p.m.

On Wed, 21 Jun 2006 11:05:43 -0600, Hans Hagen wrote:

...

Idris Samawi Hamid wrote:

...
In Latin we write

in Arabic we want the equivalent of

<2.1 erugiF>

but Duncan seems to be getting

<1.2 erugiF>

even with global Arabic settings.

so it's only the number that's wrong?

That's right (though I have not tested it myself, relying on Duncan's description)

...

...
In addition Duncan would like to use a dash instead of a period:

<2-1 erugiF>

that's configurable

I figured as much ;-) Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Hans Hagen

9:16 p.m.

Idris Samawi Hamid wrote:

...

On Wed, 21 Jun 2006 11:05:43 -0600, Hans Hagen wrote:

...
Idris Samawi Hamid wrote:

...
In Latin we write

in Arabic we want the equivalent of

<2.1 erugiF>

but Duncan seems to be getting

<1.2 erugiF>

even with global Arabic settings.

so it's only the number that's wrong?

That's right (though I have not tested it myself, relying on Duncan's description)

hm, so now i need to install arab fonts, otps, etc in my current tree -) i wonder how hard dit is to check it using reversed english (easier for me) .. does Duncan has such a sample? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Idris Samawi Hamid

11:07 p.m.

On Wed, 21 Jun 2006 21:16:40 +0200, Hans Hagen wrote:

...

...
...
so it's only the number that's wrong?

That's right (though I have not tested it myself, relying on Duncan's description)

hm, so now i need to install arab fonts, otps, etc in my current tree -)

Well, it's not that involved ;-) http://wiki.contextgarden.net/Aleph_Guide#Installing

...

i wonder how hard dit is to check it using reversed english (easier for me) .. does Duncan has such a sample?

I doubt it, but something along these lines should do it: ====== % tex=aleph output=dvipdfmx \pagedir TRT \bodydir TRT \pardir TRT \textdir TRT \hoffset=0pt % bug \starttext \chapter{Cow} \section{Dutch Cow} \placefigure [middle] [fig:cow] {This is an example of a cow.} {\externalfigure[cow][width=1.5in]} \section{Another Dutch Cow} \placefigure [middle] [fig:cow] {This is an example of a cow.} {\externalfigure[cow][width=1.5in]} \stoptext ====== Hmm, seems to work here; maybe Duncan did not use \bodydir TRT? Hans: How do we configure the "."=>"-" separator? Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

6760

Age (days ago)

6766

Last active (days ago)

List overview

Download

11 comments

3 participants

participants (3)

Duncan Hothersall
Hans Hagen
Idris Samawi Hamid

Aleph queries

tags

participants (3)