ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: font encodings (was: palatino fonts)
Date: Sat, 21 Jan 2006 16:16:44 +0100	[thread overview]
Message-ID: <9597EF30-4B6B-4B71-A95F-E1E394164F75@fiee.net> (raw)
In-Reply-To: <9D50E95F-5E45-48CC-961D-72379816D38A@fiee.net>

>> With curiosity, does your typescripts for Gentium support T5  
>> encoding ? :)
>> We use Gentium ok for Vietnamese utf-8 here (Openoffice,  
>> Abiword,....)
>> and it will be nice if you could provide vietnamese support ... :)
>
> My type scripts always use \defaultencoding - that's not always the  
> best,
> but mostly... (One could use a list of appropriate encodings instead.)
>
> I don't yet provide support files for t5 encoding, only ex,  
> texnansi and qx.
> But it would be no problem to make them for Gentium (and other  
> fonts that
> contain the glyphs).
>
> But I must think about a better structure of my fonts list before...
> (http://www.fiee.net/texnique/?menu=0-1-4)

Ok, Gentium is now online including t5 encoding. (That's not yet  
mentioned on the page.)

Now, Gentium also contains Greek glyphs, and some other fonts contain  
Cyrillic.
Which encoding should I provide for these scripts? (Only one for  
each, if possible!)

Is there any way how I could automatically detect, how much of some  
encoding a font covers?
E.g. check a font (TTF, OTF, AFM?) against texnansi, ec, qx, t5,  
t2a... and make the files for it if most of the slots could be filled.

Something completely different: I'm looking for an idea how I could  
automatically create a small font preview (one line) as a bitmap.

Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)

  reply	other threads:[~2006-01-21 15:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  9:23 palatino fonts Hans Hagen
2006-01-20  9:47 ` Henning Hraban Ramm
2006-01-20 10:09   ` Hans Hagen
2006-01-20 15:37     ` Steve Peter
2006-01-20 13:53   ` Thomas A. Schmitz
2006-01-20 14:02     ` Wolfgang Zillig
2006-01-20 14:16       ` Ville Voipio
2006-01-20 14:39       ` Johan Sandblom
2006-01-20 14:46       ` Thomas A. Schmitz
2006-01-20 15:39       ` Mojca Miklavec
2006-01-20 19:06         ` Henning Hraban Ramm
2006-01-20 20:29           ` VnPenguin
2006-01-21 14:43             ` Henning Hraban Ramm
2006-01-21 15:16               ` Henning Hraban Ramm [this message]
2006-01-21 16:11                 ` font encodings (was: palatino fonts) VnPenguin
2006-01-20 19:09     ` palatino fonts Henning Hraban Ramm

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=9597EF30-4B6B-4B71-A95F-E1E394164F75@fiee.net \
    --to=hraban@fiee.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).