MickRose Posted November 8, 2019 Share Posted November 8, 2019 I have a 120 x 120mm document in AfDesigner. When it's exported as a PDF the size is 120.3 x 120.3. The release version also has the same problem. Publisher doesn't seem to have this problem. Windows 10 Pro, I5 3.3G PC 16G RAM Link to comment Share on other sites More sharing options...
Fritz_H Posted November 10, 2019 Share Posted November 10, 2019 It seems to me, that those issues about wrong sizes of exported documents mainly affect files set up in the metric system. I wonder, if Serif perhaps developed the Applications based on imperial units (instead of properly using the metric system) which needs conversions causing rounding errors/roundoff errors. ? Fritz Link to comment Share on other sites More sharing options...
MikeW Posted November 10, 2019 Share Posted November 10, 2019 25 minutes ago, Fritz_H said: It seems to me, that those issues about wrong sizes of exported documents mainly affect files set up in the metric system. I wonder, if Serif perhaps developed the Applications based on imperial units (instead of properly using the metric system) which needs conversions causing rounding errors/roundoff errors. Internally a pdf uses PostScript points as it coordinate/measurement system, so both imperial & metric measurement systems have to be converted. Link to comment Share on other sites More sharing options...
MickRose Posted November 10, 2019 Author Share Posted November 10, 2019 A bit more detail here. Publisher does in fact seem to behave the same as Designer. What seems to matter is the resolution set in Document Setup. Keeping with a 120mm square document a resolution of 72dpi gives a 120.3 page size, 75-70 gves 120.2 page size and 80 (and presumably higher gives the correct value of 120mm. It looks like a faulty algorithm somewhere along the line. Using APub beta I tried a few other dpi values and this is what I got: dpi mm 5 122 10 122 20 120.6 30 120.2 40 120 50 120.4 60 120.7 Windows 10 Pro, I5 3.3G PC 16G RAM Link to comment Share on other sites More sharing options...
Staff Sean P Posted January 8, 2020 Staff Share Posted January 8, 2020 Hi MickRose, This is a known issue that is with development to be fixed! Link to comment Share on other sites More sharing options...
Recommended Posts