From: "Bryant Eastham" <beastham@pewla.us.pewg.panasonic.com>
To: <ntg-context@ntg.nl>
Subject: Problem with TrueType MS Mincho, MKIV
Date: Fri, 23 Oct 2009 00:16:20 -0600 [thread overview]
Message-ID: <51CAD0CE1504444DBE77CBBE51A0135D6CE39D@slcmail.slc.mew.int> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1882 bytes --]
All-
On Windows XP, latest contextminimal:
\definefont[Japanese][msmincho]
\Japanese
\starttext
Hello
\stoptext
Yields:
(mincho.tex
ConTeXt ver: 2009.08.19 17:10 MKIV fmt: 2009.10.22 int:
english/English
[snip]
load otf | loading: c:/windows/fonts/msmincho.ttf
! Emergency stop.
\lowleveldefinefont ...dimexpr \textface \relax )}
\edef \somefontspec
{at \s...
\dododefinefont ...inefont {#2}\rawfontidentifier
\csname
\rawfontidentifier...
l.2 \Japanese
access violation
! ==> Fatal error occurred, no output PDF file produced!
Bug, or my lack of understanding?
-Bryant
Panasonic Electric Works Laboratory of America - SLC Lab
4525 So. Wasatch Blvd., Suite 100, 84124
Salt Lake City, UT 84124
T 801.993.7124
F 801.993.7260
beastham@pewla.us.pewg.pansonic.com
Bryant Eastham
Chief Architect
***CONFIDENTIALITY NOTICE***: This e-mail and any attachments may
contain information which is confidential, proprietary, trade secret,
privileged or otherwise protected by law. The information is the
property of Panasonic Electric Works Laboratory of America, Inc., and is
solely intended for the named addressee (or a person responsible or
delivering it to the addressee). If you are not the intended recipient
of this message, you are not authorized to read, print, retain copy or
disseminate this message or any part of it. If you have received this
e-mail in error, please notify the sender and the Office of General
Counsel at generalcounsel@us.pewg.panasonic.com
<mailto:generalcounsel@us.pewg.panasonic.com> immediately by return
e-mail and delete it from your computer.
[-- Attachment #1.1.2: Type: text/html, Size: 10030 bytes --]
[-- Attachment #1.2: image001.gif --]
[-- Type: image/gif, Size: 3779 bytes --]
[-- Attachment #1.3: image003.gif --]
[-- Type: image/gif, Size: 2360 bytes --]
[-- Attachment #1.4: image004.png --]
[-- Type: image/png, Size: 168 bytes --]
[-- Attachment #1.5: image005.png --]
[-- Type: image/png, Size: 168 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 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
___________________________________________________________________________________
next reply other threads:[~2009-10-23 6:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 6:16 Bryant Eastham [this message]
2009-10-23 6:57 ` Taco Hoekwater
2009-10-23 7:41 ` Bryant Eastham
2009-10-23 7:51 ` Taco Hoekwater
2009-10-23 11:50 ` Mojca Miklavec
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=51CAD0CE1504444DBE77CBBE51A0135D6CE39D@slcmail.slc.mew.int \
--to=beastham@pewla.us.pewg.panasonic.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).