{"id":60,"date":"2009-04-21T11:04:33","date_gmt":"2009-04-21T11:04:33","guid":{"rendered":""},"modified":"2009-04-21T11:04:33","modified_gmt":"2009-04-21T11:04:33","slug":"font-problems-with-the-pdf-generation-te","status":"publish","type":"post","link":"http:\/\/www.icetips.com\/blog_wp\/2009\/04\/21\/font-problems-with-the-pdf-generation-te\/","title":{"rendered":"Font problems with the PDF generation templates"},"content":{"rendered":"

Two months ago I implemented the Clarion PDF generation templates in a client project. I was pretty horrified by the results as characters were chopped and spaced very strangely. After posting about this on the Clarion newsgroups, Lee White suggested that this was because I was running Large Fonts on my system. <\/p>\n

Since I have had to deal with Large Font issues before simply because I use high resolution and need to be able to seeB) I decided to take a closer look at this and see what was going on. <\/p>\n

Sure enough the problem stems from code in the ABPRPDF.CLW file where the width of the characters is calculated. To fix this I made some changes to the files. <\/p>\n

This involves adding a single method to the PDFGeneratorClass class in ABPRPDF.INC and ABPRPDF.CLW:<\/p>\n

Add to class declaration in ABPRPDF.INC (I put it in at the top of the
\nmethod list, around line 195):<\/p>\n

\n
AdjustDPIValues   PROCEDURE(Long pValue),Long \r\n!! AB 2009-02-19  Adjusts DPI values\r\n<\/pre>\n<\/div>\n
In the classfile, ABPRPDF.clw, I added this:<\/p>\n
\n
PDFGeneratorClass.AdjustDPIValues   PROCEDURE(Long pValue)!!,Long \r\n!! AB 2009-02-19  Adjusts DPI values\r\nHDcScreen  UNSIGNED\r\nIDPI       Long\r\nR          Real\r\nL          Long\r\n Code\r\n R = 1\r\n HDcScreen = GetDC(0)\r\n If HDcScreen <> 0\r\n   IDPI = GetDeviceCaps(HDcScreen, 88)\r\n   L = ReleaseDC(0, HDcScreen)\r\n   R = IDPI\/96\r\n End\r\n Return (pValue \/ R)\r\n<\/pre>\n<\/div>\n
In PDFGeneratorClass.AddFontDescriptor method, you have code like this:<\/p>\n
\n
!SET the fonts Width\r\nLOOP LOC:I=SELF.FontsNames.FirstChar TO SELF.FontsNames.LastChar\r\n   LOC:CharToTest=CHR(LOC:I)\r\n   IF GetTextExtentPoint32(LOC:DC,LOC:CharToTest, 1,LOC:CharSize)<>0 THEN\r\n      IF LOC:Subclasing THEN\r\n         IF SELF.FontsNames.CharWidth[LOC:I] THEN\r\n            SELF.FontsNames.CharWidth[LOC:I] = LOC:CharSize.eW\r\n         END\r\n      ELSE\r\n         SELF.FontsNames.CharWidth[LOC:I] = LOC:CharSize.eW\r\n      END\r\n   END\r\nEND\r\n<\/pre>\n<\/div>\n
I changed both of the assignments to the CharWidth to:<\/p>\n
\n
SELF.FontsNames.CharWidth[LOC:I] = |\r\n           SELF.AdjustDPIValues(LOC:CharSize.eW)<\/pre>\n<\/div>\n
\nIn PDFGeneratorClass.GetTextWidth method, you have code like this:<\/p>\n
\n
 IF SelectObject(LOC:DC, LOC:HFont) THEN\r\n    RV = GetTextExtentPoint32(LOC:DC,pText, LEN(pText),LOC:CharSize)\r\n    LOC:OLDMAPMODE=SetMapMode(LOC:DC,LOC:OLDMAPMODE)\r\n    DeleteObject(LOC:HFont)\r\n    RETURN LOC:CharSize.eW + (LOC:CharSize.eW\/20)\r\n END\r\n<\/pre>\n<\/div>\n
I changed the RETURN to adjust the value:<\/p>\n
\n
RETURN SELF.AdjustDPIValues(LOC:CharSize.eW + (LOC:CharSize.eW\/20))\r\n<\/pre>\n<\/div>\n
\nThis takes care of the font sizing problem in any DPI combination that I
\nthrew at it:)<\/p>\n
Arnor Baldvinsson<\/p>\n<\/p>\n<\/p>\n<\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"
Two months ago I implemented the Clarion PDF generation templates in a client project. I was pretty horrified by the results as characters were chopped and spaced very strangely. After posting about this on the Clarion newsgroups, Lee White suggested that this was because I was running Large Fonts on my system. Since I have ...continue reading Font problems with the PDF generation templates<\/span><\/a><\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[5],"tags":[],"class_list":["post-60","post","type-post","status-publish","format-standard","hentry","category-technical"],"_links":{"self":[{"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/posts\/60","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/comments?post=60"}],"version-history":[{"count":0,"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/posts\/60\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/media?parent=60"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/categories?post=60"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.icetips.com\/blog_wp\/wp-json\/wp\/v2\/tags?post=60"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}