Dear Developers and All, when I create a PDF dictionary with a small number local mydict = lpdf.dictionary { TT = 0.000000000000000001 } lpdf.flushobject(mydict) I get in PDF << /TT 1e-18 >> that confuses the Adobe Reader (if dictionary is used). As far as I can investigate, lpdf.flushobject(mydict) calls pdf.immediateobj(tostring(mydict)) and tostring does the actual damage by introducing scientific notation. What is the correct way to deal with the problem? Converting the dictionary to string with my own code looks like a possible workaround, not a solution. Michail PS. Minimal example (it produces unused dictionary, so viewer does not complain) \nopdfcompression \starttext \startluacode local mydict = lpdf.dictionary { TT = 0.000000000000000001 } lpdf.flushobject(mydict) -- or, to the same result -- pdf.immediateobj(tostring(mydict)) logs.reporter("","")("mydict %s",tostring(mydict)) \stopluacode Test. \stoptext Context is current version: 2014.05.13 00:04
On 5/18/2014 1:25 PM, Michail Vidiassov wrote:
Dear Developers and All,
when I create a PDF dictionary with a small number
local mydict = lpdf.dictionary { TT = 0.000000000000000001 } lpdf.flushobject(mydict)
I get in PDF
<< /TT 1e-18 >>
that confuses the Adobe Reader (if dictionary is used).
As far as I can investigate, lpdf.flushobject(mydict) calls pdf.immediateobj(tostring(mydict)) and tostring does the actual damage by introducing scientific notation.
yes, tostring is not the most clever one on that
What is the correct way to deal with the problem?
I'll use a different serializer. In next beta Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (2)
-
Hans Hagen -
Michail Vidiassov