ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Yanrui Li <liyanrui.m2@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: latest beta: trouble with font loading
Date: Sat, 21 Nov 2009 16:29:25 +0800	[thread overview]
Message-ID: <c3f901470911210029w426a18ck707add3b80bfda15@mail.gmail.com> (raw)
In-Reply-To: <c3f901470911201728q5e27a05cv1884968b6db25035@mail.gmail.com>

2009/11/21 Yanrui Li <liyanrui.m2@gmail.com>:
> 2009/11/21 Hans Hagen <pragma@wxs.nl>:
>> Yanrui Li wrote:
>>>
>>> 2009/11/20 Hans Hagen <pragma@wxs.nl>:
>>>>
>>>> Yanrui Li wrote:
>>>>>
>>>>> I did so and solved this problem. However I can not use Chinese OTF
>>>>> fonts such as 'AdobeSongStd-Light.otf', because luatex need very very
>>>>> large memory to load it in the stage of *enhancing* . This is a test
>>>>> file:
>>>>>
>>>>> \definefont[song][name:adobesongstd]
>>>>> \starttext
>>>>> \song 测试
>>>>> \stoptext
>>>>>
>>>>> The process of compiling stops here:
>>>>>
>>>>> !load otf       : loading:
>>>>> /usr/share/fonts/adobe/AdobeSongStd-Light.otf (hash:
>>>>> adobesongstd-light)
>>>>> !load otf       : file size: 16229772
>>>>> !load otf       : enhancing ...
>>>>
>>>> that's only the first time
>>>>
>>>
>>> But it looks like abnormal. It is still *enhancing* after spending
>>> 3.3GB memory and about 1 minute. Finally I got the message:
>>
>> fixed in beta, was some kind of loop
>>
>
> Sorry for my noice. The problem still exists in the latest beta
> (2009.11.21 00:06, linux x86) which was installed after I removed the
> previous one completely. The problem just arise in loading Chinese OTF
> fonts. It is normal for loading Chinese TTF font.
>

I find out that the problem is caused by the new
'resolvers.split_path' function in data-res.lua. It can be solved with
the old  'resolvers.split_path' function instead of the new one.

-- 
Best regards,

Li Yanrui
___________________________________________________________________________________
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:[~2009-11-21  8:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 10:45 Thomas A. Schmitz
2009-11-20 10:59 ` Taco Hoekwater
2009-11-20 11:00   ` Taco Hoekwater
2009-11-20 12:17 ` Wolfgang Schuster
2009-11-20 12:34   ` Yanrui Li
2009-11-20 12:51     ` Hans Hagen
2009-11-20 13:03       ` Yanrui Li
2009-11-20 17:49         ` Hans Hagen
2009-11-21  1:28           ` Yanrui Li
2009-11-21  8:29             ` Yanrui Li [this message]
2009-11-21 20:45             ` Bernhard Rosensteiner
2009-11-22  1:34               ` Yanrui Li
2009-11-22 11:12                 ` Bernhard Rosensteiner
2009-11-20 12:38   ` Thomas A. Schmitz
2009-11-20 12:50     ` Hans Hagen
2009-11-20 13:41       ` Thomas A. Schmitz
2009-11-20 12:38 ` 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=c3f901470911210029w426a18ck707add3b80bfda15@mail.gmail.com \
    --to=liyanrui.m2@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).