From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Making necessary OpenType features on by default
Date: Tue, 24 Feb 2009 00:23:59 +0100 [thread overview]
Message-ID: <49A3300F.2060407@wxs.nl> (raw)
In-Reply-To: <20090223165605.GA7160@khaled-laptop>
Khaled Hosny wrote:
> On Mon, Feb 23, 2009 at 01:28:23PM +0100, Hans Hagen wrote:
>> Thomas A. Schmitz wrote:
>>> On Feb 23, 2009, at 1:09 PM, Khaled Hosny wrote:
>>>
>>>> For scaling, we can specify a size, some thing like:
>>>>
>>>> \setupbodyfont[arabic=foo,20pt,latin=bar,18pt]
>>>>
>>>> or so.
>>> I don't know Arabic, but I've done similar things for Greek, and that
>>> is not a good interface. You want a scaling factor, so users won't have
>>> to worry about scaling in footnotes, titles, etc., an absolute size is
>>> not a viable alternative.
>> indeed.
>>
>> btw, i have no problem with a bunch of predefined combinations (using
>> the fallbacks mechanism) so that users can quickly initialize a typeface
>>
>> \usetypescript[fancyarabicwithgreekandtraditionallatin]
>> \setupbodyfont[fancyarabicwithgreekandtraditionallatin,13pt]
>>
>> or so, collected in some type-* file, but that's as far as we can go; we
>> need to guard at least some minimal quality
>>
>> a quick start but with bad output is not the way to go
>
> I was about to forget why I didn't like font fallbacks in the first
> place, the current font fallback mechanism assigns fonts per Unicode
> characters, this is fine until we come to common characters like numbers
> or brackets: you can only assign it to one font, which isn't usually
> desirable. Think of this sentence:
>
> عربي 1234 عربي (English 1234 English (English) English) عربي.
>
> Here, the outer most parentheses and first numbers should use the same
> font of the Arabic text, while the inner ones should use the font of the
> English text, font fallback can't do this. Instead we need to segment
> the text per script and apply fonts on whole segments, the Unicode
> Script Property annex describes a way to handle this, see
> http://www.unicode.org/reports/tr24/#Script_Names_in_Rendering.
Sure but that can be done by using explicit switches to another
'environment' i.e. explicitly marking sections
I'm not that sure if i want to add some fuzzy automatism which then
needs to handle all kind of exceptions too
proper markup is a good solution
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-23 23:23 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 18:39 Khaled Hosny
2009-02-20 18:57 ` Hans Hagen
2009-02-20 19:31 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-20 21:02 ` Khaled Hosny
2009-02-20 21:23 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-20 22:10 ` Hans Hagen
2009-02-20 22:26 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-21 23:53 ` Karl Berry
2009-02-20 20:23 ` Khaled Hosny
2009-02-20 22:07 ` Hans Hagen
2009-02-20 22:49 ` Khaled Hosny
2009-02-21 15:58 ` Ilda Khaki
2009-02-23 10:58 ` Hans Hagen
2009-02-21 13:05 ` Otared Kavian
2009-02-22 21:03 ` Khaled Hosny
2009-02-22 22:44 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-23 12:02 ` Khaled Hosny
2009-02-23 13:00 ` Hans Hagen
2009-02-23 15:34 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-23 17:15 ` Khaled Hosny
2009-02-23 17:56 ` Idris Samawi Hamid
2009-02-23 22:51 ` Khaled Hosny
2009-02-23 23:19 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-24 20:41 ` Khaled Hosny
2009-02-25 2:30 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-23 10:53 ` Hans Hagen
2009-02-23 12:09 ` Khaled Hosny
2009-02-23 12:17 ` Thomas A. Schmitz
2009-02-23 12:28 ` Hans Hagen
2009-02-23 16:56 ` Khaled Hosny
2009-02-23 17:01 ` Taco Hoekwater
2009-02-23 17:04 ` Taco Hoekwater
2009-02-23 17:49 ` Khaled Hosny
2009-02-23 23:23 ` Hans Hagen [this message]
2009-02-24 15:49 ` Idris Samawi Hamid
2009-02-24 16:03 ` Hans Hagen
2009-02-23 12:36 ` Khaled Hosny
2009-02-22 22:54 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-22 23:35 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-21 21:14 ` Otared Kavian
2009-02-23 10:42 ` Hans Hagen
2009-02-23 12:25 ` Khaled Hosny
2009-02-23 12:46 ` Khaled Hosny
2009-02-23 12:56 ` Hans Hagen
2009-02-20 18:58 ` Hans Hagen
2009-02-20 20:27 ` Khaled Hosny
2009-02-20 22:09 ` Hans Hagen
2009-02-20 22:46 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-21 11:41 ` Hans Hagen
2009-02-22 20:54 ` Khaled Hosny
2009-02-22 23:08 ` Idris Samawi Hamid ادريس سماوي حامد
2009-02-22 13:51 ` 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=49A3300F.2060407@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).