Duncan Hothersall wrote:
I agree the above works, but when I use Arabic fonts and content it
doesn't seem to.
still puzzling
things like this (imo) conform that the ability to typeset in multiple
directions not means that one claim to have a multilingual tex
the problem is that there's
Duncan Hothersall wrote:
Idris wrote:
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]
Hi,
Hans Hagen wrote:
figure [num1] . [num2] . [num3]
should come out as
[num3] . [num2] . [num1] erugif
We discovered that the arabic contextual analyzation OTP assumes
that any sequence of [0-9.+-]+ is a single number and should be
typeset in TLT mode.
For figure numbers and
Taco Hoekwater wrote:
Hi,
Hans Hagen wrote:
figure [num1] . [num2] . [num3]
should come out as
[num3] . [num2] . [num1] erugif
We discovered that the arabic contextual analyzation OTP assumes
that any sequence of [0-9.+-]+ is a single number and should be
typeset in TLT
A trick (?) is to change the separator such that the number
parsing in the otp see separate numbers as well:
\setupcaptions[separator={{.}}]
\setupheads [separator={{.}}]
\setupcaptions[separator={{.}}]
this still gives problems with refering to a graphic but for that we need
more
\setupheads [separator={{.}}]
\setupcaptions[separator={{.}}]
this still gives problems with refering to a graphic but for that we
need more hackery
Also, probably because it uses the same cross-referencing mechanism,
this leaves the section numbers in tables of contents the other way
Hmm, I did not get the parent(s) to this email; was it off-list?
Idris
On Fri, 23 Jun 2006 06:10:57 -0600, Duncan Hothersall [EMAIL PROTECTED] wrote:
A trick (?) is to change the separator such that the number
parsing in the otp see separate numbers as well:
\setupcaptions[separator={{.}}]
Idris Samawi Hamid wrote:
Hmm, I did not get the parent(s) to this email; was it off-list?
yes, taco and i skyped a bit -)
anyhow, it looks like we need some low level support for this kind of
things; playing with that now (not much time today)
Hans
Idris wrote:
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
Duncan Hothersall wrote:
I agree the above works, but when I use Arabic fonts and content it
doesn't seem to.
I have new tex and pdf files at:
http://www.capdm.com/public/context/figtest.tex
and
http://www.capdm.com/public/context/figtest.pdf
hm, some weird interaction between opt's
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
On Wed, 21 Jun 2006 09:37:50 -0600, Duncan Hothersall [EMAIL PROTECTED] 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
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
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
On Wed, 21 Jun 2006 10:11:06 -0600, Duncan Hothersall [EMAIL PROTECTED] 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
On Wed, 21 Jun 2006 10:35:14 -0600, Hans Hagen [EMAIL PROTECTED] 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
Idris Samawi Hamid wrote:
On Wed, 21 Jun 2006 10:35:14 -0600, Hans Hagen [EMAIL PROTECTED] 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
On Wed, 21 Jun 2006 11:05:43 -0600, Hans Hagen [EMAIL PROTECTED] wrote:
Idris Samawi Hamid wrote:
In Latin we write
Figure 1.2
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
Idris Samawi Hamid wrote:
On Wed, 21 Jun 2006 11:05:43 -0600, Hans Hagen [EMAIL PROTECTED] wrote:
Idris Samawi Hamid wrote:
In Latin we write
Figure 1.2
in Arabic we want the equivalent of
2.1 erugiF
but Duncan seems to be getting
1.2 erugiF
even with global Arabic
On Wed, 21 Jun 2006 21:16:40 +0200, Hans Hagen [EMAIL PROTECTED] 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
Hi Duncan,
On Thu, 15 Jun 2006 02:30:15 -0600, Duncan Hothersall [EMAIL PROTECTED] 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.
21 matches
Mail list logo
