RagTime 6.0.2 Build 1613
Build Nummer 1613 aus KW 6
Release Notes - RagTime - Build 1613
Improvements
There is one visible change in this version: We allow to turn off RagTime's own PostScript generation mechanism for output on PostScript printers. If this is done, RagTime uses the mechanisms of the operating system software (GDI+ on Windows, Quartz on Mac OS X) for the print job.
The PostScript conversion will be left to the system software in that case.
This setting has any effect if and only if a PostScript printer is used.
The new setting is in a new "printing" panel in the dialogue "Extras - Settings" (i.e. "Paramètres", "Grundeinstellungen", "Programma-instellingen" in French, German, Dutch).
Existing settings for fine-tuning the printing process ("7-Bit ASCII PostScript") are likely to moved to that panel in some later build.
Which are the cases where the new option makes sense?
Again: This option is useless if your printer does not use PostScript. Else:
If some strange printing problems occur with RagTime but not with other software, try the new option.
(Mac OS:) If the printer setting "Collated copies" creates print jobs of unacceptable size, try this setting.
If printing of a document with opacity setting creates unacceptably large print jobs or even exceeds the memory capabilities of the printer, try this setting.
The purpose of this new setting needs some explanation:
Typically, applications for drawing and for page layout purposes create their own PostScript code for output on a PostScript device. This allows highest precision and most efficient use of the technology prevalent in the printing industry. Particularly in the past, system technologies like GDI and QuickDraw were light-years behind the PostScript technology.
The new system technologies GDI+ and Quartz narrowed that gap, in some cases they even left PostScript behind. Opacity settings for objects are the most obvious example. Direct PostScript output is still the way to go in prepress contexts like process colour separation. But for most purposes apart from prepress context, using the system technology is not inferior to direct PostScript output anymore.
Opacity settings between 0% and 100% require pretty difficult strategies for PostScript printing. The strategy RagTime uses will differ from the system strategy. Switching between RagTime PostScript and system PostScript should affect both quality and speed. Try which compromise is better for you.
PostScript printers use different implementations of that language and like any software, bugs may occur. While any vendor checks his device against the system software, the specific PostScript code of some application may run into printer problems, even if the PostScript code is perfectly OK. The most recent incident of that type was a printer that seemingly does not handle page orientation properly. When printing from RagTime, some pages were rotated - no problem for simple white sheets, but nasty for letters, where paper with company logo etc. is used.
Usually, direct PostScript generation from RagTime makes sense and is the default settings still. In cases where problems with the printer do occur, the system software way is likely to be a viable alternative.
As with every new user interface element, technical implementation precedes translations. Names of panel and controls will not appear in French and Dutch so far, English wording may sound strange. This is no bug, translations just needs to be done still.