From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: seeking 'hello world' example for Arabic typesetting with conTeXt
Date: Tue, 30 Nov 2010 12:50:58 +0100 [thread overview]
Message-ID: <AANLkTi=+sjQ_Yh3o6A1d=sa2pvmUpCpTo=t2jN-uG1Rh@mail.gmail.com> (raw)
In-Reply-To: <op.vmx446i760pfzx@ihamidnb.libarts.colostate.edu>
2010/11/29 Idris Samawi Hamid ادريس سماوي حامد wrote:
> On Mon, 29 Nov 2010 11:03:06 -0700, Khaled Hosny wrote:
>
> OK: In that case, let's include the standard Scheharezade as is in the
> minimals until another unicode-complete font comes along. It has an Open
> Font License so should be no problem.
>
> Mojca: Till then, where do you suggest placing Scheharezade in the tree?
If we make some font the default one ... it makes sense to put it on
CTAN and include it in TeX Live as well, right?
Mojca
But then ... I somehow find it a bit weird to have Arabic fallback
inside Latin Modern unless a user requests that explicitely and also
says which font he wants to use. That it: I would suggest to have some
setting that would tell exactly which glyphs to replace in the main
font, which features to use ... but then the user would say that this
font needs to be added.
That is: are we also going to add Chinese, Japanese, Korean, Ethiopic,
... etc. scripts, all inside the one default font?
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-30 11:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 21:48 Jon Crump
2010-11-29 4:47 ` Idris Samawi Hamid ادريس سماوي حامد
2010-11-29 5:14 ` Idris Samawi Hamid ادريس سماوي حامد
2010-11-29 18:30 ` Hans Hagen
2010-11-29 18:03 ` Khaled Hosny
2010-11-29 19:16 ` Idris Samawi Hamid ادريس سماوي حامد
2010-11-29 19:23 ` luigi scarso
2010-11-29 19:28 ` Hans Hagen
2010-11-30 11:50 ` Mojca Miklavec [this message]
2010-11-30 12:06 ` Hans Hagen
2010-11-30 14:46 ` Idris Samawi Hamid ادريس سماوي حامد
2010-12-01 9:48 ` luigi scarso
2010-12-01 17:53 ` Idris Samawi Hamid ادريس سماوي حامد
2010-11-29 20:18 ` Jon Crump
2010-11-29 18:11 ` Khaled Hosny
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='AANLkTi=+sjQ_Yh3o6A1d=sa2pvmUpCpTo=t2jN-uG1Rh@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.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).