From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Non-printable Unicode control characters
Date: Fri, 15 Aug 2008 22:23:08 +0300 [thread overview]
Message-ID: <20080815192308.GB5667@khaled-laptop> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
Unicode has many "control characters" that only control text behaviour
and shouldn't be rendered visually in the text, such as Bidi_Control and
Join_Control chars (see
http://www.unicode.org/Public/5.1.0/ucd/PropList.txt and
http://unicode.org/Public/UNIDATA/UCD.html)
Currently, ConTeXt handles ZWJ and ZWNJ, but other characters get
rendered if the font has glyphs for them or make no effect at all if the
font has no glyphs for them. I think that the optimum behaviour is to
make those characters affect text formatting while not visually rendered
whether the font has glyphs for them or not.
It might be also useful if we can enable rendering those characters
manually, for drafts and such.
Regards,
Khaled
--
Khaled Hosny
Arabic localizer and member of Arabeyes.org team
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2008-08-15 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 19:23 Khaled Hosny [this message]
2008-08-16 7:53 ` Hans Hagen
2008-08-17 2:37 ` Idris Samawi Hamid ادريس سماوي حامد
2008-08-17 12:46 ` Hans Hagen
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=20080815192308.GB5667@khaled-laptop \
--to=khaledhosny@eglug.org \
--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).