home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!lax.pe-nelson.com!lax!twbrown
- From: twbrown@PE-Nelson.COM (Tom W. Brown)
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: Re: Printing. How to make 11 pt come out...
- Message-ID: <732@lax.lax.pe-nelson.com>
- Date: 8 Jan 93 18:46:10 GMT
- References: <1993Jan8.144922.3697@cis.ohio-state.edu>
- Sender: news@lax.pe-nelson.com
- Organization: PE-Nelson
- Lines: 29
-
- In article <1993Jan8.144922.3697@cis.ohio-state.edu>, guzman@python.cis.ohio-state.edu (jonatan guzman) writes:
- |> ...looking like 11 pt regardless of the device onto which you are rendering the
- |> text?? I have a program that uses TT fonts for output (due to their scalabi-
- |> lity), but I am having to *manually* adjust the font size -when I CreateFont
- |> for the DC- depending on the output device (screen, printer).
- |>
- |> I am obviously missing something here. What??
-
- Try using the MM_TWIPS mapping mode for your output. This sets up the DC
- so that a logical unit is equal to a twentieth of a point. You then always
- use a font size of 220 (11 * 20) to get an 11 point font regardless of the
- device.
-
- The default mapping mode is MM_TEXT where a logical unit is the same as
- a device unit (pixel) and, as you've noticed, varies from device to device in
- terms of physical size.
-
- Since our application does more graphics then text output we pretty much
- stick with MM_ANISOTROPIC mapping and have our own conversion routines to
- convert printer points into logical units. This is probably much the same
- as you are doing with your manually adjusted font sizes. There's nothing
- wrong with doing it this way IMO.
-
-
- ----------------------------------------------------------------------------
- Tom Brown | "She turned me into a newt...
- PE Nelson Systems | ... I got better"
- twbrown@pe-nelson.com | Monty Python and the Holy Grail
- ----------------------------------------------------------------------------
-