ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: h h extern <pragma@wxs.nl>
Subject: encoding problem
Date: Thu, 24 Feb 2005 22:59:32 +0100	[thread overview]
Message-ID: <421E4E44.1080506@wxs.nl> (raw)

Was this problem solved? If not, the problem may be in not loading a map file; 
typescripts take care of this.

btw, one you see the light, typescripts are not that hard, see examples in wiki, 
  Bill M's font page and Adam L's myways.

Hans



 >>>>>>

Hello,

I'm working on some XSL stylesheets for translating XML documents into
Context. Although I've read the document "Fonts in Context" and
understood that one could use typescripts for managing fonts, in the
context of my stylesheets I'd rather like to stick to the
\definebodyfont command, because so far it works and I'm a bit confused
about all those indirections one has to use when defining typescripts.
The only thing which doesn't seem to work are font encodings. Please,
take a look at the following document:

%--------------------------------------------
\enableregime[il1]
\mainlanguage[de]
\language[de]
\setupencoding[default=texnansi]

\definefontsynonym[NewCenturySchoolbook][pncr8r][encoding=texnansi]

\definebodyfont[4pt,5pt,6pt,7pt,8pt,9pt,10pt,11pt,12pt,14.4pt,17.3pt][rm]
   [tf=NewCenturySchoolbook sa 1]

\definefont[nctr][NewCenturySchoolbook at 10pt]

\setupbodyfont[10pt]

\starttext
{\nctr \showcharacters}
{\showcharacters}
\stoptext
%--------------------------------------------

Defining the font "directly" with \definefont leads to a
texnansi-encoded table of characters, so that I could use the special
German umlaut characters (which is my intention, of course). The
definition of the font with \definebodyfont produces a default-encoded
table with characters, which are *not* texnansi-encoded, because all the
umlaut characters are missing. At least using Windows XP, TexLive 2004
distribution (MikTeX). I don't understand why this happens for two reasons:

1. Both commands (\definebodyfont and \definefont) use the same synonym
for the font, with an explicitely defined texnansi-encoding.

2. The default encoding of the whole document was set to texnansi.

It is getting even more disturbing when I'm setting the body font size
to 12pt. (Using the command \setupbodyfont[12pt]). Then both tables are
showing a texnansi-encoded font. What has font size to do with encodings?

Since I don't want to use a body font size of 12pt in all of my
documents, only to be able to use German umlaut characters, any hints to
what I'm doing wrong here would be appreciated very much.

Thanks in advance,
Stefan Ohletz


_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context




-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

                 reply	other threads:[~2005-02-24 21:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=421E4E44.1080506@wxs.nl \
    --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).