ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: No \aring?
Date: Sun, 22 Apr 2001 23:58:05 +0200	[thread overview]
Message-ID: <3.0.6.32.20010422235805.009e37f0@server-1> (raw)
In-Reply-To: <20010421182639.3574.qmail@crux.private.off-line>

At 08:26 PM 4/21/01 +0200, Joop Susan wrote:
>
>Hello,
>
>I'm having problems producing the \aring and \Aring glyphs.
>
>I'm using \enableregime[windows].
>
>Neither {\aring} nor the 8-bit character 229 'å' produce the desired 
>result. They just print an 'a' without the ring.

this is because the fall back of \aring is defined as 's', you can patch
enco-def: 

somewhere at the top:

\definecharacter textring          23

lower: 

\definecharacter Aring {\buildtextaccent\textring A}
\definecharacter aring {\buildtextaccent\textring a}
\definecharacter Uring {\buildtextaccent\textring U}
\definecharacter uring {\buildtextaccent\textring u}

>This is pdfeTeX, Version 3.14159-13h-pretest-20010126-2.1 (Web2C 7.3.3.1)

pretty old pdftex

>ConTeXt  ver: 2001.4.9  fmt: 2001.4.16  int: english  mes: english
>
>I have looked in the source and found a file named 'regi-win.tex'. I 
>understand that this is an input mapping of characters. Right? I found one 
>typo in the file, but no solution to my problem.

this is indeed *input* mapping [or sometimes intermediate mapping]

>I created a test file that prints the named glyphs I found in that file 
>(What would I do without 'vi' and regular expressions?). All looks OK 
>except \ccedilla (typo: \cdedille), \ntilde, \Ntilde, \aring and \Aring.

Ok, so we need to add:  

\definecharacter Ntilde {\buildtextaccent\texttilde N}
\definecharacter ntilde {\buildtextaccent\texttilde n}

>Could it be that not the input mapping, but the output mapping is wrong 
>here?

indeed, there is no good fall back defined, thanks for pointing it out

>Hans, any suggestion for a quick patch? I'm lost... I need \aring.

patch enco-def.tex and regenerate the formats

>    character. That was pdfeTeX, Version 3.14159-14f-released-20000525-2.1

this version of context has named glyph definitions instead of the less
readable accent/commans ones; the internals are still the same, except from
some enoding-to-encoding expansion improvements, but i redid the defs and
for sure missed a couple of glyphs, btw, these issues are unrelated to
pdftex [except that unicode searching for eastern european languagesis now
smoother]. 

Hans
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  reply	other threads:[~2001-04-22 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-21 18:26 Joop Susan
2001-04-22 21:58 ` Hans Hagen [this message]
     [not found] <Your message of "Sun, 22 Apr 2001 23:58:05 +0200." <3.0.6.32.20010422235805.009e37f0@server-1>
2001-04-23 15:11 ` Joop Susan
2001-04-24  7:03   ` 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=3.0.6.32.20010422235805.009e37f0@server-1 \
    --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).