ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Subject: 8r vs. ec vs. texnansi
Date: Tue, 18 Mar 2003 23:39:15 +0100	[thread overview]
Message-ID: <87wuiwti3w.fsf_-_@gundla.ch> (raw)
In-Reply-To: <20030318184827.1399fd6e.morawski@gmx.net> (Jens-Uwe Morawski's message of "Tue, 18 Mar 2003 18:48:27 +0100")

Jens-Uwe Morawski <morawski@gmx.net> writes:

Hello Jens and others,

>> \setupencoding[default=8r]
>
> what is the advantage of using 8r instead of ec or texnansi?

It is a matter of taste and the characters you need. There is no big
difference for my german and english texts.

texnansi does not work with the preinstalled (psnfss) fonts from
teTeX. So this leaves my preferred coding system to 8r or ec.

Sometimes I need glyphs that are encoded in 8r but not in ec (euro sign
for example). I never use glyphs that are encoded in ec but not in
8r. 

Patrick

  reply	other threads:[~2003-03-18 22:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5.1.0.14.0.20030220182954.0234dfc0@server-1>
     [not found] ` <20030220163139.GA25234@idi.ntnu.no>
     [not found]   ` <5.1.0.14.0.20030221092916.029ff530@server-1>
2003-03-15 17:05     ` Font and index trouble (was Re: mathpple-a-like for ConTeXt?) Magnus Lie Hetland
     [not found]   ` <20030317205042.GA14658@idi.ntnu.no>
2003-03-18  7:45     ` Hans Hagen
     [not found] ` <20030318131323.GB12151@idi.ntnu.no>
2003-03-18 15:11   ` mathpple-a-like for ConTeXt? Patrick Gundlach
2003-03-18 17:48     ` Jens-Uwe Morawski
2003-03-18 22:39       ` Patrick Gundlach [this message]
2003-03-19  9:14         ` 8r vs. ec vs. texnansi Maarten Sneep
2003-03-19  9:54           ` Patrick Gundlach
2003-03-19 17:30             ` Hans Hagen
2003-03-19 13:51         ` Jens-Uwe Morawski
2003-03-19 13:58           ` Patrick Gundlach
2003-03-19 16:08             ` Jens-Uwe Morawski
2003-03-19 12:56     ` Re: mathpple-a-like for ConTeXt? Magnus Lie Hetland
2003-03-20  9:03       ` adobekb.tex Patrick Gundlach
2003-03-21 21:23         ` adobekb.tex Guo Yang
2003-03-21 21:33           ` adobekb.tex Patrick Gundlach
     [not found]       ` <87el53eck8.fsf@gundla.ch>
     [not found]         ` <20030319181205.GA11531@idi.ntnu.no>
     [not found]           ` <87llzbcixi.fsf@gundla.ch>
     [not found]             ` <20030319195106.GA17157@idi.ntnu.no>
     [not found]               ` <87vfyfvw8f.fsf@gundla.ch>
     [not found]                 ` <20030320003148.GA2051@idi.ntnu.no>
     [not found]                   ` <87he9y5u7h.fsf_-_@gundla.ch>
2003-03-20 10:39                     ` colors Magnus Lie Hetland
     [not found]             ` <20030319235209.GA29226@idi.ntnu.no>
     [not found]               ` <87znnq4djb.fsf_-_@gundla.ch>
     [not found]                 ` <20030320104502.GB7979@idi.ntnu.no>
     [not found]                   ` <87isue489u.fsf@gundla.ch>
     [not found]                     ` <20030320122729.GC14561@idi.ntnu.no>
     [not found]                       ` <874r5y434p.fsf@gundla.ch>
2003-03-20 13:37                         ` foonotes Magnus Lie Hetland

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=87wuiwti3w.fsf_-_@gundla.ch \
    --to=pg@levana.de \
    --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).