ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \char"xxxx not working as I expected
Date: Wed, 25 Feb 2009 15:41:15 +0100	[thread overview]
Message-ID: <D86DFA72-48E7-465A-B085-05910EFF0AEA@gmail.com> (raw)
In-Reply-To: <go3kns$qff$1@ger.gmane.org>


Am 25.02.2009 um 15:31 schrieb Maurí cio:

> I did check the font in 'gucharmap' and it does contain
> all codes I'm using (U+2019, U+2610, U+226b, U+2115). But
> the result is a blank (U+2610 and U+2115) or wrong
> (U+226b) character. (U+2019 is shown properly.)
>
> The test alternates lines where a unicode character is
> inserted directly (using emacs 'ucs' input method) and
> then insert the same character using '\char'. (So, if you
> see strange chars in the code, it's because it does
> contain utf-8 characters.) It's intersting that u+226b
> is shown properly when typed, but not when using '\char'.
>
> Am I doing something wrong?

1. You need a font with the chars, e.g. Arial Unicode
2. Use uppercase letters for hex numbers (lowercase is used for ^^..)

Wolfgang

___________________________________________________________________________________
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:[~2009-02-25 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 14:31 Maurí­cio
2009-02-25 14:41 ` Wolfgang Schuster [this message]
2009-02-25 14:42 ` Taco Hoekwater
2009-02-25 14:54 ` 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=D86DFA72-48E7-465A-B085-05910EFF0AEA@gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).