From: Lutz Haseloff <Lutz.Haseloff@lbapdm.brandenburg.de>
Subject: Re: Update to Pdfetex 1.20a
Date: Wed, 13 Oct 2004 07:25:41 +0200 [thread overview]
Message-ID: <416CBC55.4050506@lbapdm.brandenburg.de> (raw)
In-Reply-To: <416AA607.9040500@wxs.nl>
Hans Hagen schrieb:
> Lutz Haseloff wrote:
>
>> Hi Hans, Hi all,
>>
>> \loadmapfile[gbk]
>> \usemodule[chinese]
>> \usemodule[chi-simplified]
>> \starttext
>> \section{test}
>> \stoptext
>>
>>
>> Is this a bug in pdfetex?
>
>
> welcome to the non downward compatible changes in tex and friends
>
> you may try: texmfstart textools --fixtexmftrees
no errors found
> to move your map and enc files to the new locations
>
> if things still fail ... then we have a problem in pdftex's font
> inclusion
>
I'm afraid so:
where pdfetex 1.20a breaks completely and texexec.pl reports:
-------------
systems : end file china at line 6
)<c:\tex\texmf-local/fonts/truetype/chinese/htsong.ttf
return code : 65280
run time : 3 seconds
total run time : 3 seconds
-------------
version 1.11 prepares nice chinese pdf and texexec.pl reports
-----
systems : end file china at line 6
){c:\tex\texmf-local/fonts/enc/chinese/GBK-bd.enc}<c:\tex\texmf-local/fonts/tr
uetype/chinese/htsong.ttf>{c:\tex\texmf-local/fonts/enc/chinese/GBK-d2.enc}<c:\
tex\texmf-local/fonts/truetype/chinese/htsong.ttf>{c:\tex\texmf-local/fonts/enc
/chinese/GBK-b5.enc}<c:\tex\texmf-local/fonts/truetype/chinese/htsong.ttf><c:\t
ex\texmf/fonts/type1/bluesky/cm/cmr12.pfb>
Output written on china.pdf (1 page, 11424 bytes).
Transcript written on china.log.
return code : 0
run time : 1 seconds
-----
> Hans
>
>
>
Greetings Lutz
prev parent reply other threads:[~2004-10-13 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 10:59 Lutz Haseloff
2004-10-11 15:25 ` Hans Hagen
2004-10-13 5:25 ` Lutz Haseloff [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=416CBC55.4050506@lbapdm.brandenburg.de \
--to=lutz.haseloff@lbapdm.brandenburg.de \
--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).