ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: Adam Lindsay <atl@comp.lancs.ac.uk>
Subject: Re: Dense encoding, part II
Date: Fri, 10 Feb 2006 16:59:25 +0100	[thread overview]
Message-ID: <6faad9f00602100759w3e217c7avcaa50222ebcb6e2e@mail.gmail.com> (raw)
In-Reply-To: <43E640B7.7060007@comp.lancs.ac.uk>

On 2/5/06, Adam Lindsay wrote:
> Hans Hagen wrote:
> > Mojca Miklavec wrote:
> >
> >> Hello,
> >>
> >> The fact that all Polish fonts (lm, iwona, kurier, antt) now ship with
> >> el-* files makes me wonder: is there time to do the next step and
> >> finish the second encoding with symbols?
> >>
> >>
> > indeed
>
> Oop. Sorry, I hadn't been watching that.
> I've suggested texnansi as a starting point, at least within ConTeXt.
> What symbols do people want that *aren't* within texnansi?

1. Would Caron & similar uppercase accents make sense? I doubt that
many accents are needed in addition to what is already present in the
other encoding anyway, but something like that could be used if there
is no Ccaron present in the font for example:

\definecharacter Ccaron {\buildtextaccent\textCaron C}
instead of
\definecharacter Ccaron {\buildtextaccent\textcaron C}

In well-designed fonts (including all Polish fonts such as lm,
antykwa, iwona, ...) the lowercase and the uppercase variant of the
accent differ. (Try to write \Scaron\Ccaron in texnansi encoding for
example to see the difference).

Of course some care has to be taken, so that it will also work for
fonts without those additional accents for uppercase characters (using
\iffontchar perhaps?).

2. perhaps some currency symbols missing in texnansi
I would suggest to add Euro, but with some special care of course.
Perhaps some users still prefer to use the regular (geometrical)
symbol rather than the one taken from I-forgot-which-font (the default
behaviour when \texteuro is used).

Any other currency on this list worth supporting?
http://www.unicode.org/charts/PDF/U20A0.pdf
Perhaps dong, lira, Won ...

3. Perhaps a short glimpse into:
http://source.contextgarden.net/ts1-lm.enc
http://www.cstug.cz/aktivity/2005/lm-at11e.pdf
http://www.janusz.nowacki.strefa.pl/pliki/AntykwaTorunska-doc-en-2_03.pdf
if you notice anything worth supporting.

"married" might be useful for geneaology, I guess that the leaf is
there for the same purpose. No idea why anyone would want to use the
musical note (ugly in lm and probably hardly present in any other
font).

4. numero sign, ordfeminine, ordmasculine, copyleft ;), I don't know
if anybody needs fractions, permyriad, ... one/two/...superior
(present in some regimes) are pretty pointless in TeX where you can
use \high{} I guess. Perhaps there should be two different glyphs for
"tilde" and "asciitilde" (not sure about the last one.)

Mojca

  reply	other threads:[~2006-02-10 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 15:37 Mojca Miklavec
2006-01-23 15:55 ` Hans Hagen
2006-02-05 18:15   ` Adam Lindsay
2006-02-10 15:59     ` Mojca Miklavec [this message]
2006-02-10 16:35       ` Adam Lindsay
2006-02-10 18:01         ` Mojca Miklavec
2006-02-12 11:09           ` Taco Hoekwater

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=6faad9f00602100759w3e217c7avcaa50222ebcb6e2e@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=atl@comp.lancs.ac.uk \
    --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).