From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Passing unicode characters
Date: Mon, 28 Jul 2008 16:37:41 +0200 [thread overview]
Message-ID: <488DD9B5.4080103@wxs.nl> (raw)
In-Reply-To: <6faad9f00807221421n1f956817j451ad0ff30479e63@mail.gmail.com>
Mojca Miklavec wrote:
> On Tue, Jul 22, 2008 at 9:39 PM, Mehdi Omidali wrote:
>> Dear Mojca,
>> Thanks for your complete answer. In fact, in persian (and maybe
>> arabic) documents, we need every digit be in persian,
>
> But when you write, you probably write numbers in persian already?
>
>> like chapter,
>> section,
>
> \chapter and \section are a bit buggy as far as numbering is
> concerned, but you can use
> \setuphead
> [section]
> [conversion=arabicnumerals]
the section numbering has to take too many things into account (there
are sveral places where one can hook in conversion commands);
complications are for instance in supporting chinese (left/right stuff)
and separators; one problem is that the number needs to be expanded when
it is written to lists; separator handlign (esp replacement) then can
become rather hairy too
concerning left/right handling ... there has been added some trickery
when idris needed it and was still using otp's but since otp's were
error prone, this can easily interfere with other things
anyhow, in mkiv there will be a more flexible mechanism with more data
being carried around so that in various stages one can tweak things like
conversions, separators, prefixes is much more detail (which then of
course will lead to more demands)
Hans
(btw, you really don't want to know what numbering we have to use in our
projects; it hardly fits a model)
-----------------------------------------------------------------
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-07-28 14:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 14:48 Mehdi Omidali
2008-07-22 15:23 ` Idris Samawi Hamid ادريس سماوي حامد
2008-07-22 16:31 ` Mehdi Omidali
2008-07-22 18:14 ` Mehdi Omidali
2008-07-22 18:40 ` Idris Samawi Hamid
2008-07-22 19:24 ` Mehdi Omidali
2008-07-22 19:42 ` Aditya Mahajan
2008-07-22 20:50 ` Mehdi Omidali
2008-07-23 6:37 ` Wolfgang Schuster
2008-07-27 21:25 ` Khaled Hosny
2008-07-27 22:38 ` Mehdi Omidali
2008-07-28 14:41 ` Hans Hagen
2008-07-22 18:10 ` Mojca Miklavec
2008-07-22 19:39 ` Mehdi Omidali
2008-07-22 21:21 ` Mojca Miklavec
2008-07-23 17:52 ` Mehdi Omidali
2008-07-27 12:39 ` Taco Hoekwater
2008-07-28 14:37 ` Hans Hagen [this message]
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=488DD9B5.4080103@wxs.nl \
--to=pragma@wxs.nl \
--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).