Bugs item #294, was opened at 2005-02-15 21:06
You can respond by visiting:
http://sarovar.org/tracker/?func=detail&atid=493&aid=294&group_id=106
Category: Fonts
Group: v1.21a
Status: Open
Resolution: None
Priority: 5
Submitted By: Hartmut Henkel (hhenkel)
Assigned to: The Thanh Han (hanthethanh)
Summary: pdfmovechars/encoding problem
Initial Comment:
This has been reported by Jörg Heinrich at 1 Feb. 2005
on the pdftex list (Subject: [pdftex] pdfetex). The
following derived example leads to a segfault:
% this works:
%\pdfmovechars=1
% this gives segfault:
\pdfmovechars=2
% this works:
%\pdfmapline{phvr8r Helvetica <8r.enc Comment By: Hartmut Henkel (hhenkel)
Date: 2005-04-02 00:53 Message:
Logged In: YES
user_id=929
This patch (patch-294b.tgz) removes the functionality of the
\pdfmovechars primitive. What remains for now is a warning,
once per run, if \pdfmovechars is set to a value unequal 0:
! pdfTeX warning: Primitive \pdfmovechars is obsolete.
Regards, Hartmut
----------------------------------------------------------------------
Comment By: Hartmut Henkel (hhenkel)
Date: 2005-03-31 23:57
Message:
Logged In: YES
user_id=929
In function t1_read_enc() the function t1_prefix() was
called while t1_line_array was not allocated yet, causing
the segfault. Making a do...while loop from the while loop
does allocation via t1_getline() in time, see the patch.
Maybe that's enough for now to close the bug.
It seems that the function t1_read_enc() is anyway called
only via get_enc() when pdfmovechars > 0, so both functions
serve only this special case, and are normally not in use.
I have done not any check whether \pdfmovechars general
functionality is ok, and one might as well thow out this
primitive, and the unneeded functions. Let's add a note
"deprecated" in the manual...
Regards, Hartmut
----------------------------------------------------------------------
You can respond by visiting:
http://sarovar.org/tracker/?func=detail&atid=493&aid=294&group_id=106