From: Duncan Hothersall <dh@capdm.com>
Cc: Idris Samawi Hamid <ishamid@colostate.edu>
Subject: Re: Aleph queries
Date: Wed, 21 Jun 2006 16:37:50 +0100 [thread overview]
Message-ID: <449967CE.1070004@capdm.com> (raw)
In-Reply-To: <op.ta6300hnnx1yh1@walayah-main>
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.
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-06-21 15:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 8:30 Duncan Hothersall
2006-06-15 16:28 ` Idris Samawi Hamid
2006-06-21 15:37 ` Duncan Hothersall [this message]
2006-06-21 15:55 ` Idris Samawi Hamid
2006-06-21 16:11 ` Duncan Hothersall
2006-06-21 16:44 ` Idris Samawi Hamid
2006-06-21 16:35 ` Hans Hagen
2006-06-21 16:54 ` Idris Samawi Hamid
2006-06-21 17:05 ` Hans Hagen
2006-06-21 18:04 ` Idris Samawi Hamid
2006-06-21 19:16 ` Hans Hagen
2006-06-21 21:07 ` Idris Samawi Hamid
[not found] <mailman.119.1150925775.1824.ntg-context@ntg.nl>
2006-06-22 7:57 ` Duncan Hothersall
2006-06-22 15:44 ` Hans Hagen
2006-06-23 8:35 ` Hans Hagen
2006-06-23 9:32 ` Taco Hoekwater
2006-06-23 11:08 ` Hans Hagen
2006-06-23 8:55 ` Hans Hagen
[not found] <mailman.3.1151056802.10220.ntg-context@ntg.nl>
2006-06-23 12:10 ` Duncan Hothersall
2006-06-23 15:46 ` Idris Samawi Hamid
2006-06-23 16:24 ` Hans Hagen
2006-06-23 14:13 ` Duncan Hothersall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=449967CE.1070004@capdm.com \
--to=dh@capdm.com \
--cc=ishamid@colostate.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).