Working on a custom printer driver ...
I am having trouble getting some applications (like Microsoft Word, others) to recognize custom paper size.
The vendor paper sizes are shown, but in custom applications the "customsize" option doesn't show up at all
In Word, I see the Custom Page Size - but attempting to print, there are a series of warnings about the page margins:
......
And when printing, the custom size documents are sent to one of the defined sizes.
The gpd (assume 100 dpi):
*Feature: PaperSize
{
*rcNameID: =PAPER_SIZE_DISPLAY
*DefaultOption: Size_2x4
*Option: Size_2x4
{
*Name: "2 x 4"
*PageDimensions: PAIR(200, 400)
*PrintableArea: PAIR(200, 400)
*PrintableOrigin: PAIR(0, 0)
}
*Option: Size_4x4
{
*Name: "4 x 4"
*PageDimensions: PAIR(400, 400)
*PrintableArea: PAIR(400, 400)
*PrintableOrigin: PAIR(0, 0)
}
*Option: Size_4x6
{
*Name: "4 x 6"
*PageDimensions: PAIR(400, 600)
*PrintableArea: PAIR(400, 600)
*PrintableOrigin: PAIR(0, 0)
}
*Option: CUSTOMSIZE
{
*rcNameID: =USER_DEFINED_SIZE_DISPLAY
*MinSize: PAIR(40, 40)
*MaxSize: PAIR(1200, 3000)
*MaxPrintableWidth: 3000
*MinLeftMargin: 0
*TopMargin: 0
*BottomMargin: 0
*CenterPrintable?: TRUE
*CursorOrigin: PAIR(0, 0)
}
}
The only one item that is missing is the *Command
- In Microsoft examples :
*Command: CmdSelect
{
*Order: DOC_SETUP.13
*Cmd: "<1B>&l101a8c1e63F<1B>*p0x0Y<1B>*c0t12456x8184Y"
}
Unfortunately the custom printer I make this for has a different printer language that doesn't include page setup commands. So - since I have no command to give, it would make sense not to include a command. I have experimented with changing cursor position for portrait vs landscape, but it does not give good results.
Am I correct in my assumption that, if the gpd is correct, the application will send custom size info without the "Custom" option being available and selectable by the user ? I just can't see anything else I can do to fix the gpd...
I assumed that since these are standard sections, UI plugin does not need to create them specifically... If that assumption is wrong, what would be needed in a OEM UI plugin to make this section show ?