ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: ConTeXt ML <ntg-context@ntg.nl>
Cc: "Élie Roux" <elie.roux@telecom-bretagne.eu>
Subject: fontloader: “can't convert <float> into tounicode”
Date: Fri, 3 May 2013 21:04:07 +0200	[thread overview]
Message-ID: <20130503190407.GA19255@phlegethon> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 785 bytes --]

Hi,

loading this font:

    https://collab.itc.virginia.edu/access/content/group/26a34146-33a6-48ce-001e-f16ce7908a6a/Tibetan%20fonts/Tibetan%20Unicode%20Fonts/TibetanMachineUnicodeFont.zip

causes the fontloader to emit a dozen or so messages of the kind

    fonts           > loading > can't convert 7.27550912993e+22 into tounicode
    fonts           > loading > can't convert 3.1248073774797e+32 into tounicode
    fonts           > loading > can't convert 4.731809353839e+27 into tounicode
    ...

example code:

    \starttext
      foo
      {\definedfont[file:TibMachUni-1.901b.ttf*tibetan at 33pt]༡༢་༣༤་༥༦་༧༨}
      bar
    \stoptext

is this harmless? The typeset result appears to be satisfying.

Best regards,
Philipp



[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2013-05-03 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 19:04 Philipp Gesang [this message]
2013-05-04 12:01 ` Hans Hagen

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=20130503190407.GA19255@phlegethon \
    --to=philipp.gesang@alumni.uni-heidelberg.de \
    --cc=elie.roux@telecom-bretagne.eu \
    --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).