next »

[ORGA-SOFT B.]

Hello,

we want to use the compativility output from the genero report writer.
So our code is as follows

    CALL fgl_report_selectDevice("SVG")
    CALL fgl_report_selectPreview(TRUE)

   CALL fgl_report_setPageMargins("1.5cm","0.5cm","1.0cm","0.0cm")
   CALL fgl_report_setAutoformatType("COMPATIBILITY") # COMPATIBILITY
   CALL fgl_report_configureCompatibilityOutput(132, "Courier", FALSE, NULL, NULL, NULL)
   CALL fgl_report_configurePageSize("a4width","a4length")

so the output looked good but we need a bigger font size then the report writer uses.

So is there a little trick to do this?

Best regards
Martin

[Alex G.]

Hi Martin,
The font size is chosen by the system to be as big a possible without exceeding the page in any direction.
If you would make it only one point size bigger than it would either be too wide or to high resulting in characters printed outside of the page.
You can validate that by printing a page that contains text on every line and a characters at the rightmost column (column 132 in your case).
Typically you will have a gap at the bottom of the page or on the right.
There are two reasons for this:
1) The aspect ratio of the paper changed. Your original report was previously printed (132 x 72) on  15" x 12" (381mm x 305mm) and now you want to print it on A4 portrait (210 mm × 297 mm)
2) The aspect ratio of the font changed. Your original font printed 8 lines per inch and 10 character per inch. The font "Courier" that you use has a totally different aspect ratio.

To minimize that gap you have the following options:
- Choose a different font. On some Linux distributions there is a font called "Courier 10 Pitch" that has the same proportions as the original line printer fonts. If you use that one, you are however still faced with the paper problem.
- Switch from Portrait to Landscape.
- Change the page length or width in the 4GL (I know, that is hard)

There is no perfect solution to this. It seems that small gaps are inevitable. Things like changing the line spacing, the character spacing or (event worse) scaling asymmetrically are aesthetically worse.
The 3.10 documentation has a topic specially dedicated to this. If you get in touch with our support then I can see that you are given a copy of that chapter. Are you participating in the EAP? If yes, then you will find it included in that version.

Regards,

Alex