Thank you. Exactly what I needed. Looking at the DDS reference, I was lost with the term "font identifier".

With that, I am going to quit wasting time with ill-fitting overlays. Only thing I needed on the front was the company letterhead. Boxes with labels are easy enough to setup. Tedious, but way easier than dealing with multiple versions of the same scanned form. The back side is another matter. It is 99 percent canned text with three fields. Way easier than the front.

Maybe I can get this thing done, finally.

John McKee
-----Original message-----
From: "Jim Franz" franz400@xxxxxxxxxxxx
Date: Thu, 07 Apr 2011 17:54:38 -0500
To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx
Subject: Re: Forms printing

to get real small printing, try this keyword (on single field or at format
level)

FONT(2304 (*POINTSIZE 8))
the "8" can be lot's of other numbers (9, 10,11,12,14,16,18, etc)
I think 2304 is Times Roman??
2305 is same typeface but bold
It's typographic (each char not same width)

jim franz

----- Original Message -----
From: "jmmckee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, April 07, 2011 6:24 PM
Subject: Re: Forms printing


Thanks. I did figure out the TXTRTE. But, due to weird box sizes, I had
to change the CPI to 12 - which makes the single rotated field smaller
than is optimal. I was thinking that was a keyword I could use to change
the CPI for the sigle rotated field. Maybe there is. Finally had a
chance to look - CPI. That might work. Easier than messing with fonts,
from what I see of the keywords.

Thanks for the clarification on back side printing. Depending on
application, back overlay would not be used. I was hoping that all I had
to do was add a record format for the back and print it. I have a LOT
more fields to position before I get there. This form was reviewed by
some group years ago. Not very closely, from what I can tell. One date
is printed as CCYY/MM/DD another is printed as six digits, and a third is
printed as MM/DD/YY. Other weirdness exists. Just real tiresome dealing
with it.

John McKee

-----Original message-----
From: "Jim Franz" franz400@xxxxxxxxxxxx
Date: Thu, 07 Apr 2011 16:27:42 -0500
To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx
Subject: Re: Forms printing

to rotate - keyword is TXTRTT(90)

duplex - It is two pages so two writes, and if back of form is sometimes
blank - you have to still write 2nd page with at least a space ...

Form forms overlay it's had to get a form to line up with cpi.
I do a dummy page (with overlay) with field every 0.10 down and across so
I
can quickly line up "position".

Jim

----- Original Message -----
From: "jmmckee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, April 07, 2011 4:58 PM
Subject: Forms printing


Two direct questions:

1) I compile the printer file with 12 CPI instead of the default 10.
Most things fit nicely. One field is rotated 90 degrees. It is a bit
tiny. What keyword would I use on that field to make it print larger?

2) For a duplex form, are two writes used to get the back to print?


Now, a seemingly off-the-wall question: Forms are printed now by a
Lexmark printer, if it has a special forms chip installed. Is there
any
way to maybe get that file out of the printer without it printing and
then
rescanning it? I have been given multiple scanned versions of this
stupid
form. All >slightly< different. Bad enough that I have to use the
POSITION keyword on every field, in CM units, without having to keep
repositioning previous data. I have over a hundred fields to position.
have only managed to get maybe 20 so far. Every scan does something to
the height and width. Thus, my curiousity as to whether the Lexmark
>might< store the merged file somewheer internally until printed. FTP
right now shows only a single directory, and no read access - just
write.
Maybe the merged file gets dropped there. Or not. I just don't know a
command to change the access to the directory to make it readable, if
such
exists.

Anyway, apologies for bringing up this topic again.

John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].