ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: VnPenguin <vnpenguin@gmail.com>
Subject: Re: font encodings (glyph lossed with Gentium in T5)
Date: Sun, 22 Jan 2006 16:02:43 +0100	[thread overview]
Message-ID: <e5d3f2650601220702p133ee265qcd8671986a55c9c6@mail.gmail.com> (raw)
In-Reply-To: <1525176E-B661-490B-B8C6-DEC9A50E4E5B@uni-bonn.de>

[-- Attachment #1: Type: text/plain, Size: 757 bytes --]

On 1/22/06, Thomas A. Schmitz <thomas.schmitz@uni-bonn.de> wrote:
>
> OK, this may not be of much help, but I just converted GenR102.TTF to
> pfb via fontforge, and now the font correctly picks up the dcroat
> glyph. I mus admit I had similar situations in the past where simply
> regenerating the font would solve mysterious problems, so I shrugged
> my shoulders and did what a man must do. I think the new Gentium
> license allows for this conversion, and the LaTeX people will be
> distributing pfbs anyway, so why not convert to pfb (which is easier
> for TeX to use anyway?)
>

Hi Thomas,
You're completely right ! Just tried with PFB (converted by fontforge)
and it works :)

Thank you,

--
http://vnoss.org
Vietnamese Open Source Software Community

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-01-22 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 19:26 VnPenguin
2006-01-21 20:45 ` Henning Hraban Ramm
2006-01-21 21:48   ` Henning Hraban Ramm
2006-01-21 22:13   ` VnPenguin
2006-01-21 22:54     ` Henning Hraban Ramm
2006-01-22  7:03       ` VnPenguin
2006-01-22 12:36         ` Henning Hraban Ramm
2006-01-22 12:53           ` VnPenguin
2006-01-22 13:44           ` Thomas A. Schmitz
2006-01-22 15:02             ` VnPenguin [this message]
2006-01-30 17:11               ` VnPenguin

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=e5d3f2650601220702p133ee265qcd8671986a55c9c6@mail.gmail.com \
    --to=vnpenguin@gmail.com \
    --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).