ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Re: 8r vs. ec vs. texnansi
Date: Wed, 19 Mar 2003 17:08:18 +0100	[thread overview]
Message-ID: <20030319170818.1b481f12.morawski@gmx.net> (raw)
In-Reply-To: <87wuivcvaf.fsf@gundla.ch>

On Wed, 19 Mar 2003 14:58:48 +0100
Patrick Gundlach <pg@levana.de> wrote:

> Jens-Uwe Morawski <morawski@gmx.net> writes:
> 
> Hello Jens and others,
> 
> > some time ago Hans and me discussed how to make TS1 symbols available.
> > I've never tried it but it sounds interesting since it is an unified
> > way to access the symbols. For example for Palatino
> >
> >
> > add to the typescripts
> >
> > \definefontsynonym [PalatinoSymbols] [<TS1-Font>]
> > \definefontsynonym [PalatinoSymbolsBold] [<TS1-Bold-Font>]
> >
> > \definefontsynonym [SerifSymbols] [PalatinoSymbols]
> > \definefontsynonym [SerifSymbolsBold] [PalatinoSymbolsBold]
> >
> > and define the symbols in a symbol-typescript
> >
> > \definesymbol[textregistered] [{\symbol[\currentencoding-registered]}]
> > \definesymbol[ec-registered][\getglygh{SerifSymbols}{\char123}]
> >
> > this could add the capability that the LaTeX textcomp package provides
> 
> At a quick glance this would fail for example for the euro
> sign/ec. (Not there in ec). Why not access the existing virtual fonts
> or generate new ones if needed? (phvr8c.vf for example - let us not
> fall back to the urw/adobe discussion yet :) 

your glance was too quick. :) The chain is:

starting with texteuro symbol -->
if in ec-encoding it becomes ec-texteuro symbol -->
it takes char 0xBF from the current ...Symbol... font
 (the symbol macro should be able to resolve Serif.., Sans..., Serif...Bold etc
  automatically) -->
the current ...Symbol... font is *NOT* a EC-encoded font but a TS1 (aka 8c)
encoded one that is associated via typescript with the T1 encoded font
(as i have already written above: <TS1-Font>)

This would easily allow for other text encodings to define the usual
symbols, for example for 8r one can declare either

\definesymbol[8r-texteuro][\getglygh{Serif}{\char128}]

or better
\definefontsynonym [SerifSymbols] [Serif]
\definesymbol[8r-texteuro][\getglygh{SerifSymbols}{\char128}]

since in 8r or texnansi there are no special symbol fonts. Thus, when
you switch the encoding in your document from ec to 8r to texnansi
then the euro is from the users view always the symbol texteuro, but
for ec taken from the associated 8c-font and for 8r or texnansi
taken directly from the text-font.

So, we should look if the macro-names from textcomp package conflict
with macro-names already defined in ConTeXT. If there is no conflict
we can define all text-symbols according to 'textcomp' in some
typescripts:

\starttypescript[textsymbols]
  ...
  \definesymbol[texteuro] [{\symbol[\currentencoding-texteuro]}]
  ...
\stoptypescript

\starttypescript[textsymbols][ec]
  ...
  \definesymbol[ec-texteuro] [\getglygh{Textsymbol}{\char191}]
  ...
\stoptypescript

\starttypescript[textsymbols][8r]
  ...
  \definesymbol[8r-texteuro] [\getglygh{Textsymbol}{\char128}]
  ...
\stoptypescript


the font typescripts then have to declare what 'Textsymbol' is:

\starttypescript [serif] [Adobe Times] [name]
  \definefontsynonym [Serif]            [Times-Roman]
  \definefontsynonym [SerifBold]        [Times-Bold]
  \definefontsynonym [SerifItalic]      [Times-Italic]
  \definefontsynonym [SerifSlanted]     [Times-Italic]
  \definefontsynonym [SerifBoldItalic]  [Times-BoldItalic]
  \definefontsynonym [SerifBoldSlanted] [Times-BoldItalic]
  \definefontsynonym [SerifCaps]        [Times-Roman]
  \definefontsynonym [TextsymbolSerif]            [TextsymbolTimes-Roman]
  \definefontsynonym [TextsymbolSerifBold]        [TextsymbolTimes-Bold]
  \definefontsynonym [TextsymbolSerifItalic]      [TextsymbolTimes-Italic]
  \definefontsynonym [TextsymbolSerifSlanted]     [TextsymbolTimes-Italic]
  \definefontsynonym [TextsymbolSerifBoldItalic]  [TextsymbolTimes-BoldItalic]
  \definefontsynonym [TextsymbolSerifBoldSlanted] [TextsymbolTimes-BoldItalic]
  \definefontsynonym [TextsymbolSerifCaps]        [TextsymbolTimes-Roman]
\stoptypescript

\starttypescript [serif] [Adobe Times] [ec]
  \definefontsynonym [Times-Roman]                [ptmr8t]  [encoding=ec]
  \definefontsynonym [Times-Bold]                 [ptmb8t]  [encoding=ec]
  \definefontsynonym [Times-Italic]               [ptmri8t] [encoding=ec]
  \definefontsynonym [Times-BoldItalic]           [ptmbi8t] [encoding=ec]
  \definefontsynonym [TextsymbolTimes-Roman]      [ptmr8c]
  \definefontsynonym [TextsymbolTimes-Bold]       [ptmb8c]
  \definefontsynonym [TextsymbolTimes-Italic]     [ptmri8c]
  \definefontsynonym [TextsymbolTimes-BoldItalic] [ptmbi8c]
\stoptypescript
% the encoding=?? is only needed for mapping input; since we access symbols
% directly (\char...) the encoding for 'Textsymbol' fonts should not be important


\starttypescript [serif] [Adobe Times] [8r]
  \definefontsynonym [Times-Roman]                [ptmr8r]  [encoding=8r]
  \definefontsynonym [Times-Bold]                 [ptmb8r]  [encoding=8r]
  \definefontsynonym [Times-Italic]               [ptmri8r] [encoding=8r]
  \definefontsynonym [Times-BoldItalic]           [ptmbi8r] [encoding=8r]
  \definefontsynonym [TextsymbolTimes-Roman]      [ptmr8r]  [encoding=8r]
  \definefontsynonym [TextsymbolTimes-Bold]       [ptmb8r]  [encoding=8r]
  \definefontsynonym [TextsymbolTimes-Italic]     [ptmri8r] [encoding=8r]
  \definefontsynonym [TextsymbolTimes-BoldItalic] [ptmbi8r] [encoding=8r]
\stoptypescript


Jens

  reply	other threads:[~2003-03-19 16:08 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       ` 8r vs. ec vs. texnansi Patrick Gundlach
2003-03-19  9:14         ` 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 [this message]
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=20030319170818.1b481f12.morawski@gmx.net \
    --to=morawski@gmx.net \
    --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).