ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: iso latin 2
Date: Wed, 09 Feb 2005 23:21:19 +0100	[thread overview]
Message-ID: <420A8CDF.1000406@wxs.nl> (raw)
In-Reply-To: <420A81D5.702@seznam.cz>

Vit Zyka wrote:
> Hans Hagen wrote:
> 
>> I wonder,
>>
>> \definecharacter Aring         {\ilencodedrA}
>>
>> \definecharacter Lstroke       {\ilencodedL}
>> \definecharacter lstroke       {\ilencodedl}
>>
>> where do these come from? is that because csr does not provide those 
>> glyphs?
> 
> 
> il2 encoding is not ISO-8859-2 but encoding of CS fonts (csr...). It was 
> derived from ISOO-8859-2 but:
> - first 128 glyphs are the same as cmr...
> - upper part is added according to ISO-8859-2 
> (http://nl.ijs.si/gnusl/cee/charset.html) but only chars needed for 
> Czech/Slovak lang.
> 
> Neither Aring is present in CSfont, nor Lstroke, nor lstroke.
> 
>> (which makes il2 like aer (almoet ec) something almost il2 -)
> 
> 
> I have mentioned that when I was interested in CMAP.
> 
> ---
> 
> I entered these three chars definitions when I was preparing support for 
> Storm's fonts last weekend. It is a large collection (about 50 families) 
> of commercial fonts with large glyph set each (about 370). Since there 
> are prepared large collectin of tfm (t1 or il2 + one extended) from Petr 
> Olsak I decided to use them. I prepared enco-st2.tex (storm il2) and 
> enco-st3.tex (storm extended) for now (I intended also enco-st1 for t1). 
> The question is how to elegantly switch from standard (st2) tfm to 
> extended (st3) tfm when the glyph is not present in st2 - with 
> preserving \rm, \bf, \it, \bi.
> 
> Example: {\bf Bold text with special char \textplus} where \texplus is 
> bold variant from st3 encoded tfm. It is understandable?

I wonder, why don't you use the more recent qx encoding;

if il2 is only used for csr, then we can best extend il2 encoding since all the 
chars missing in csr are present in latin modern;

Hans

-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------

  parent reply	other threads:[~2005-02-09 22:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 17:29 Hans Hagen
2005-02-09 21:34 ` Vit Zyka
2005-02-09 22:18   ` Adam Lindsay
2005-02-09 23:33     ` Vit Zyka
2005-02-09 23:41       ` Adam Lindsay
2005-02-10  9:23         ` Hans Hagen
2005-02-11 10:56           ` Vit Zyka
2005-03-15 18:23       ` iso latin 2 ; storm fonts Vit Zyka
2005-03-15 18:29         ` Hans Hagen
2005-03-15 23:25         ` Hans Hagen
2005-03-16 23:52           ` Vit Zyka
2005-03-15 23:45         ` Adam Lindsay
2005-04-10 20:31           ` Vit Zyka
2005-04-11 11:16             ` Adam Lindsay
2005-02-09 22:21   ` Hans Hagen [this message]
2005-02-09 23:52     ` iso latin 2 Vit Zyka
2005-02-10  9:26       ` Hans Hagen
2005-02-11 10:17         ` Vit Zyka

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=420A8CDF.1000406@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).