[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problem using llx/urx in PS_LinkDest
From: |
KHMan |
Subject: |
Problem using llx/urx in PS_LinkDest |
Date: |
Mon, 21 Apr 2008 15:10:06 +0800 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 |
Hi all,
I have a very old patch to target PDF link destinations properly
that I now plan to double-check and submit with the help of Barrie
Stott, but there are a few glitches due to the values of llx/urx
in PS_LinkDest (z49.c). Barrie Stott and I have been trying to
look into the issue.
Here is an example of an anomalous result:
%% calculating final coordinates
% CTM a,b [1.00 0.00]
% CTM c,d [0.00 1.00]
% CTM x,y [1417.00 1417.00]
%% in FULL_LENGTH units:
% llx=14754764 lly=10319
% urx=14754764 ury=10319
%% in PS user space points:
% llxd=737809.05 urxd=737809.05
% llyd=586.80 uryd=586.80
% finalx=737773.05 finaly=622.80
CTM is the transformation matrix needed to calculate the absolute
position for Postscript, and it's working fine, but llx and urx is
behaving badly for a handful of targets.
Tracing FixAndPrintObject() in z23.c, it looks like save_mark(x)
borked. But so far it appears to me that a LINK_DEST_NULL object
uses a valid osave_mark field. Changing oux from union into struct
makes the problem go away; I could get nice targets then. So at
the moment, we are trying to pinpoint the problem, and since it
appears to be a Lout glitch, I am notifying the list, perhaps
someone might have a good idea what went wrong.
--
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia
- Problem using llx/urx in PS_LinkDest,
KHMan <=