|
The ideal for publishers is often vector graphics, and MetaEdit+ supports that by https://metacase.com/support/55/manuals/meplus/Mp.html#Mp-5_1.html" rel="nofollow - printing to PDF. The details vary somewhat by platform (see e.g. https://metacase.com/download/metaedit/morelinux55sr1.html#print" rel="nofollow - Linux readme ) and what printer drivers are on offer, and the results will vary similarly. We tell each 'printer' the same things to draw, but they choose how to draw it.
In my experience, publishers are looking for a decent level of quality in bitmaps in terms of the dpi resolution of the image itself, rather than the actual dpi of the image in its published form. It's better not to scale it yourself first, as that will reduce the quality when they scale it again.
In some cases, the correct dpi is what is on the screen, e.g. if you also want to show the window around the diagram. That of course is easy, a simple screen shot.
In other cases, what is wanted is a bitmap at a higher resolution. One way is then to zoom in, and (unless you have a very large screen) probably make the image as a composite of several screenshots. (Note that at least on Windows, font scaling isn't always accurate, so you will probably need to resize some elements slightly if you have particular requirements for how text wraps etc.) When we wrote the http://dsmbook.com" rel="nofollow - DSM book we had to make a lot of screenshots, so we made a patch to MetaEdit+ to scale up PNG output by a factor of 4; here's an updated version for any MetaEdit+ 5.5: https://www.metacase.com/forums/uploads/3/png55_400.mep" rel="nofollow - png55_400.mep
Below is an example of the output from both PDF and scaled-up PNG with the above patch: click to open at full size. https://www.metacase.com/forums/uploads/3/WatchModelsPDFvs400.png" rel="nofollow">
|