ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: S Barmeier <severinbarmeier@googlemail.com>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (Xe)ConTeXt and CJK support
Date: Tue, 14 Sep 2010 12:31:13 +0200	[thread overview]
Message-ID: <AANLkTikTPAXqw4pGY5=U8wdyQsmTXBWNtbMZQ+zii0ai@mail.gmail.com> (raw)
In-Reply-To: <6C0A6B50-11BC-4CCB-B795-F1CEA241678F@gmail.com>

Ok, this worked now. After reloading the fonts with mtxrun I was able
to find the fonts. Before I had always tried to "context --generate"
*after* "mtxrun --script font --reload" (as suggested on
http://wiki.contextgarden.net/Fonts_in_LuaTeX) but then ConTeXt can't
find the fonts anymore. Same with luatools, running "luatools
--generate" destroys the information from the font reload. (Why?) In
any case, I can work around this by always reloading the fonts after
generating context or luatools...

Again, many thanks.
Best,
Severin

On 9/14/10, Wolfgang Schuster <schuster.wolfgang@googlemail.com> wrote:
>
> Am 14.09.2010 um 11:10 schrieb S Barmeier:
>
>> Thank you for your quick reply. In the above example neither IPAMincho
>> nor Sazanami Mincho (Regular) are loaded correctly. I get several
>> lines of
>>
>> simplefonts   : font 'sazanamiminchoregular' not found
>>
>> interspersed with
>>
>> ! fonts   : font database matches configuration and file hashes
>>
>> The simplefonts message ignores spaces and caps... Any ideas?
>
> Simplefonts normalize the font name but this is not the problem,
> why you don’t get any output is because context can’t find the fonts.
>
> You can check if context finds the fonts with “mtxrun --script font --list
> --all --pattern=ipa*”
> and “mtxrun --script font --list --all --pattern=sazanami*”
>
> Maybe it helps when you put the fonts in the tex directory itself
> ($TEXFM/texmf-fonts/truetype/)
> and refresh the database with “luatools --generate” and ”mtxrun --script
> font --reload”.
>
> Wolfgang
>
>
___________________________________________________________________________________
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:[~2010-09-14 10:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09  8:21 S Barmeier
2010-09-10  7:47 ` Hans Hagen
2010-09-10 19:03 ` Mojca Miklavec
2010-09-10 19:10   ` Hans Hagen
2010-09-10 19:22     ` Mojca Miklavec
2010-09-12  7:10 ` Wolfgang Schuster
2010-09-14  0:28   ` S Barmeier
2010-09-14  5:54     ` Wolfgang Schuster
2010-09-14  9:10       ` S Barmeier
2010-09-14 10:09         ` Wolfgang Schuster
2010-09-14 10:31           ` S Barmeier [this message]

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='AANLkTikTPAXqw4pGY5=U8wdyQsmTXBWNtbMZQ+zii0ai@mail.gmail.com' \
    --to=severinbarmeier@googlemail.com \
    --cc=ntg-context@ntg.nl \
    --cc=schuster.wolfgang@googlemail.com \
    /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).