ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texnansi encoding.
Date: Sat, 14 Sep 2013 20:06:54 +0200	[thread overview]
Message-ID: <64F4D228-5D9E-4001-88D9-4116B1180685@gmail.com> (raw)
In-Reply-To: <20130914131645.70143e77@localb.wexfordpress.net>


[-- Attachment #1.1: Type: text/plain, Size: 1755 bytes --]


Am 14.09.2013 um 19:16 schrieb john Culleton <John@wexfordpress.com>:

> On Sat, 14 Sep 2013 17:42:42 +0200
> Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
> 
>> 
>> Am 14.09.2013 um 15:34 schrieb john Culleton <John@wexfordpress.com>:
>> 
>>> Excellent! Now in MKIV how would I encode an opening quote mark
>>> American style? In previous TeX programs it was always ``. The MKIV
>>> substitute \quotation{foo} 
>>> is not practical for my application, where the raw input code
>>> may use the ditto mark " for both opening and closing quotes. I am
>>> looking for something in MKIV equivalent to \char92 in plain TeX. On
>>> the unicode table I find the hex value 008013 but I don't know how
>>> to plug that in to a macro that redefines the first occurrence of "
>>> to be that character, and the second occurrence to be hex 000814
>>> etc. I can write the macro, I just need the expression equivalent
>>> to \char that gives me such characters in MKIV.
>> 
>> Are you sure these are the correct values?
>> 
>> http://www.fileformat.info/info/unicode/char/8013/index.htm
>> 
>> 
>> What’s wrong with \char?
>> 
>> \starttext
>> 
>> \char"201C TEXT\char"201D
>> 
>> \utfchar{"201C}TEXT\utfchar{"201D}
>> 
>> \fontchar{quotedblleft}TEXT\fontchar{quotedblright}
>> 
>> \stoptext
>> 
>> Wolfgang
> 
> Well you answered my question. The chart I read for unicode characters 
> gave the values I quoted. I guess I was reading the wrong chart. What
> chart do you use?

- http://www.unicode.org/charts/
- http://www.unicode.org/charts/PDF/U2000.pdf
- http://www.decodeunicode.org/
- http://www.decodeunicode.org/u+201C
- http://www.typografie.de/product_info.php?products_id=1409&language=en

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2702 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2013-09-14 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 20:05 john Culleton
2013-09-13  0:41 ` Hans Hagen
2013-09-14 13:34   ` john Culleton
2013-09-14 15:42     ` Wolfgang Schuster
2013-09-14 17:16       ` john Culleton
2013-09-14 18:06         ` Wolfgang Schuster [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=64F4D228-5D9E-4001-88D9-4116B1180685@gmail.com \
    --to=schuster.wolfgang@gmail.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).