ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: substitutions
Date: Wed, 08 Oct 2008 06:41:05 -0600	[thread overview]
Message-ID: <op.uiphirc5fkrasx@your-b27fb1c401> (raw)
In-Reply-To: <48EBA78A.8040209@wxs.nl>

On Tue, 07 Oct 2008 12:16:42 -0600, Hans Hagen <pragma@wxs.nl> wrote:

>> Hans and Taco can probably tell you more.
> it all depends on what we want to achieve ...

> - we can have font fixers (dynamically extend fonts with features, but
> this demands knowledge of the font)
> - we can have replacements in the node list (attribute driven,
> relatively easy to implement)
> so before i start looking into this, we need to investigate what is
> needed (and what for)

For things like my journal, I get lots of inconsistent transliterations,  
and we are not yet at the stage where we can enforce behavior on authors.  
I would like to be able to do things like

Mohamed -> Muḥammad

which would save me a lot of time in proofreading, editing, etc. Getting  
the transliteration for the entire journal consistent is a tedious pain,  
and eventually I can have a nice database that will cover most cases. This  
is also much more convenient than using control-sequence definitions and  
watching out for spaces etc.

> (only mkiv)

Indeed ;-)

Best wishes
Idris

-- 
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2008-10-08 12:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-05 23:57 substitutions Idris Samawi Hamid ادريس سماوي حامد
2008-10-07 10:53 ` substitutions Mojca Miklavec
2008-10-07 18:16   ` substitutions Hans Hagen
2008-10-08 12:41     ` Idris Samawi Hamid ادريس سماوي حامد [this message]
2008-10-08 14:46       ` substitutions Mojca Miklavec
2008-10-08 15:43         ` substitutions Idris Samawi Hamid
2008-10-08 22:53       ` substitutions Mojca Miklavec
2009-03-27 12:05         ` substitutions Khaled Hosny
2009-03-29  1:27           ` substitutions: can i send this? Idris Samawi Hamid ادريس سماوي حامد
2009-03-29 17:25             ` Khaled Hosny
2009-03-29 17:37               ` Hans Hagen
2008-10-08 12:34   ` substitutions Idris Samawi Hamid ادريس سماوي حامد

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=op.uiphirc5fkrasx@your-b27fb1c401 \
    --to=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).