ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: iso latin 2
Date: Thu, 10 Feb 2005 00:52:21 +0100	[thread overview]
Message-ID: <420AA235.7060200@seznam.cz> (raw)
In-Reply-To: <420A8CDF.1000406@wxs.nl>

Hans Hagen wrote:
> 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 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;

Problem is that il2 and ISO-8859-2 differs in next chars presented in il2:
dec   ISO          CS
184   cedilla      \`a
254   tcedilla     dblleftquote
255   dot above    dblrightquote

...

After some quotes (e.g. Adams'

 > "The Polish prefer it more upright. The Czechs prefer it more flat."

) I feel stronger and stronger that csr should coexist with lm for 
future. Perhaps like a option (not present in minimal distr?), but with 
full functionality if extra loaded.

So I would like il2 will be preserved as it is and new coding according 
to lm (ISO-8859-2 ?) would be introduce (enco-l2 ?).

Vit

  reply	other threads:[~2005-02-09 23:52 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   ` iso latin 2 Hans Hagen
2005-02-09 23:52     ` Vit Zyka [this message]
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=420AA235.7060200@seznam.cz \
    --to=vit.zyka@seznam.cz \
    --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).