ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nikolai Weibull <context-list@pcppopper.org>
Subject: [FONTS] Japanese Unicode
Date: Thu, 2 Sep 2004 22:49:02 +0200	[thread overview]
Message-ID: <20040902204901.GA25326@puritan.pcp.ath.cx> (raw)

I'm trying to get some Japanese ideographs in my document, but haven't
succeeded yet.  Basically, what I've done is used Adam Lindsay's XSL-T
stuff for creating an .enc for my .ttf (mona.ttf) and then run texfont
to install the font in /usr/share/texmf/local/fonts.  Now, I can't get
the test .tex-file working because I get

Warning: pdfetex (file cork-lmr10): Font cork-lmr10 at 600 not found
{/usr/share/texmf/dvips/tetex/bbad153f.enc}</usr/share/texmf/fonts/type1/bluesk
y/cm/cmsy7.pfb>{/usr/share/texmf/dvips/tetex/aae443f0.enc}</usr/share/texmf/fon
ts/type1/bluesky/cm/cmmi10.pfb>{/usr/share/texmf/dvips/tetex/0ef0afca.enc}</usr
/share/texmf/fonts/type1/bluesky/cm/cmr5.pfb>{/usr/share/texmf/dvips/tetex/74af
c74c.enc}</usr/share/texmf/fonts/type1/bluesky/cm/cmti10.pfb></usr/share/texmf/
fonts/type1/public/marvosym/marvosym.pfb>{/usr/share/texmf/dvips/tetex/f7b6d320
.enc}</usr/share/texmf/fonts/type1/bluesky/cm/cmr8.pfb></usr/share/texmf/fonts/
type1/bluesky/cm/cmsy10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmr6.pfb>
Warning: pdfetex (file mona30xx-raw-mona): Font mona30xx-raw-mona at 600 not fo
und

from it.  Now, these are only warnings, so I tried showing it with
gpdf (xpdf), ggv, and acroread for linux.  Nothing worked correctly, and
only gpdf was able to show anything at all (albeit it wasn't right).  So
I figured I'd try it myself.  I wrote the following

type-mone30xx.tex:
\starttypescript[serif][mona30]
  \definefontsynonym[Mona30-Roman][mona30xx-mona][encoding=mona30xx]
\stoptypescript
\starttypescript[serif][mona30][name]
  \definefontsynonym[Serif][Mona30-Roman]
\stoptypescript
\starttypescript[Mona30]
  \definetypeface[Mona30][rm][serif][mona30][default]
\stoptypescript

and

test.tex:
\useregime[utf8]
\usetypescriptfile[type-mona30]
\usetypescript[Mona30]
\setupbodyfont[Mona30]
\starttext
オ
\stoptext

Guess what...the resulting PDF is completely empty.  Could someone
_please_ tell me what I'm missing?  I know I've been asking a lot of
questions lately and perhaps most could have been answered by me delving
deeper into the problem.  The issue for me right now, though, is that
I'm really stressed for time, as I need to get my masters' thesis done
soon, and a lot is working against me at the moment.  So, again, if you
can help out in any way, _please_ do.
	nikolai


--
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

             reply	other threads:[~2004-09-02 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 20:49 Nikolai Weibull [this message]
2004-09-03  7:39 ` Taco Hoekwater
2004-09-03 15:34   ` Nikolai Weibull
2004-09-03 15:44     ` Adam Lindsay
2004-09-03 18:37       ` Nikolai Weibull
2004-09-03 15:51     ` Hans Hagen
2004-09-03 18:22       ` Nikolai Weibull
2004-09-04 14:49         ` Hans Hagen Outside
2004-09-04 16:42           ` Nikolai Weibull

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=20040902204901.GA25326@puritan.pcp.ath.cx \
    --to=context-list@pcppopper.org \
    --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).