From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: using `` '' the output is wrong.
Date: Thu, 4 Mar 2010 20:19:55 +0200 [thread overview]
Message-ID: <20100304181955.GA5398@khaled-laptop> (raw)
In-Reply-To: <6faad9f01001191131l7a924bf6wf98998c6c13af0a8@mail.gmail.com>
On Tue, Jan 19, 2010 at 08:31:22PM +0100, Mojca Miklavec wrote:
> - The deciding moment when some of these ugly tricks have been thrown
> away was when we realized that if you do add those tricks, there is no
> way to print the grave accent. (Grave accent will be automatically
> converted to the same "comma" that you get in quotation marks.) In
> good old TeX the grave accent (`) and the character that you get when
> you type ` are at two different slots. In Unicode-encoded fonts that's
> not doable. This means that if one wants to enable the `` trick then
> there's no way to allow composite characters with grave accent or the
> character ` in typewriter font. In most cases that is not a problem
> since Unicode fonts usually support a wide range of characters, but I
> already had to use a character not present in Unicode. And that was
> not doable until the hack has been removed.
Now, I feel there is some thing wrong here, (`) is not an accent
(despite it misleading Unicode name), but rather a spacing character, so
typing n` to get ǹ is wrong; you should use (̀ ) instead (this is
U+0300), since the later is the combining grave accent while the former
is a spacing character.
Regards,
Khaled
--
Khaled Hosny
Arabic localiser and member of Arabeyes.org team
Free font developer
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-03-04 18:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 12:34 views63
2010-01-18 12:50 ` Taco Hoekwater
2010-01-18 13:11 ` views63
2010-01-18 13:15 ` Alan BRASLAU
2010-01-18 13:47 ` Henning Hraban Ramm
2010-01-18 13:53 ` Hans Hagen
2010-01-19 19:31 ` Mojca Miklavec
2010-01-19 20:04 ` Aditya Mahajan
2010-01-19 20:10 ` Alan BRASLAU
2010-01-19 20:23 ` Wolfgang Schuster
2010-01-19 20:26 ` Aditya Mahajan
2010-01-19 20:34 ` Wolfgang Schuster
2010-01-19 20:44 ` Aditya Mahajan
2010-02-03 13:56 ` Wolfgang Schuster
2010-01-19 20:28 ` Aditya Mahajan
2010-01-19 21:01 ` Hans Hagen
2010-01-19 21:02 ` Mojca Miklavec
2010-01-20 7:04 ` Taco Hoekwater
2010-01-20 7:28 ` Alan BRASLAU
2010-01-20 7:52 ` Peter Münster
2010-01-20 9:10 ` Hans Hagen
2010-01-20 9:58 ` Alan BRASLAU
2010-01-20 10:39 ` Taco Hoekwater
2010-01-20 14:42 ` Mojca Miklavec
2010-03-04 18:41 ` Khaled Hosny
2010-03-04 18:31 ` Khaled Hosny
2010-01-20 9:03 ` Hans Hagen
2010-01-19 22:08 ` Peter Münster
2010-03-04 18:19 ` Khaled Hosny [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=20100304181955.GA5398@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).