Bugs fixed in PSAlter 1.6 (since 1.52)

Bug-id: 1.52/073/PolicyReport
Mode: any
Area: error in PostScript implementation

PSAlter does not call PolicyReport when Policies was consulted only for items in this list: OutputAttributes, MediaType, MediaColor, MediaWeight, and PageSize. It does for all other keys. Also, PolicyReport is fetched from the pagedevice dictionary, not from the Policies dictionary.

Bug-id: 1.52/074/binobj
Mode: any
Area: obscure error in PostScript implementation

When a binary object sequence is read, it appears to be in global VM, even if it is in local VM. In addition, if it is read by the "token" operator it is marked "executeonly" and cannot be read.

Bug-id: 1.52/075/filenameforall
Mode: any
Area: crashes on certain unusual files

The operator filenameforall will cause a crash if passed an empty procedure {}. Also the case where an empty target string is passed, but that would always be an error.

Bug-id: 1.52/076/packedarray
Mode: any
Area: crashes on certain unusual files

The sequence 0 packedarray would cause a crash.

Bug-id: 1.52/077/SubFileDecode
Mode: any
Area: unexpected error

The SubFileDecode filter did not work correctly, dropping approximately every 1000th character from its input.

Bug-id: 1.52/078/indexcolour
Mode: any
Area: unexpected error

In rare cases, but including Adobe InDesign's PostScript, the typecheck error may be issued. This occurred if real numbers were used instead of integers with the indexed colour space.

Bug-id: 1.52/079/xshow
Mode: any
Area: bad result

When using the xshow, yshow or xyshow operator the results may be incorrect, and spurious errors may occur, especially if garbage collection happened to coincide with the operation.

Bug-id: 1.52/080/CCITTFaxDecode
Mode: any
Area: occasional unexpected error

Encoded data for the CCITTFaxDecode filter was not always being read to end of data. This occurred when the number of columns was a multiple of 8, and the data contained the optional EOD mark following a complete data set.

Bug-id: PSAlter-2001-001
Mode: any
Area: occasional unexpected error

The currentpagedevice operator gave an invalidacesss error in global VM mode. This operator should have been returning an object in local VM, even when true setglobal is in effect

Bug-id: PSAlter-2001-002
Mode: any
Area: occasional unexpected error

Co-ordinate truncation is an option, in Limits Setup. This was not always effective, as in the example 40000 40000 scale 0 0 1 1 rectfill.

Bug-id: PSAlter-2001-004
Mode: any
Area: occasional unexpected error

If a binary sequence was for a string (starting with 142 etc.), then PSAlter did not correctly process the token.

			Home page \| Products \| Support \| Download \| Buy \| Contact You are here: Quite > Products > PSAlter > Bugs in 1.5

	PSAlter Introduction Viewing PostScript EPS Workbench Fonts Release notes Upgrade How to buy Manual (PDF)		Bugs fixed in PSAlter 1.6 (since 1.52) Bug-id: 1.52/073/PolicyReport Mode: any Area: error in PostScript implementation PSAlter does not call PolicyReport when Policies was consulted only for items in this list: OutputAttributes, MediaType, MediaColor, MediaWeight, and PageSize. It does for all other keys. Also, PolicyReport is fetched from the pagedevice dictionary, not from the Policies dictionary. Bug-id: 1.52/074/binobj Mode: any Area: obscure error in PostScript implementation When a binary object sequence is read, it appears to be in global VM, even if it is in local VM. In addition, if it is read by the "token" operator it is marked "executeonly" and cannot be read. Bug-id: 1.52/075/filenameforall Mode: any Area: crashes on certain unusual files The operator filenameforall will cause a crash if passed an empty procedure {}. Also the case where an empty target string is passed, but that would always be an error. Bug-id: 1.52/076/packedarray Mode: any Area: crashes on certain unusual files The sequence 0 packedarray would cause a crash. Bug-id: 1.52/077/SubFileDecode Mode: any Area: unexpected error The SubFileDecode filter did not work correctly, dropping approximately every 1000th character from its input. Bug-id: 1.52/078/indexcolour Mode: any Area: unexpected error In rare cases, but including Adobe InDesign's PostScript, the typecheck error may be issued. This occurred if real numbers were used instead of integers with the indexed colour space. Bug-id: 1.52/079/xshow Mode: any Area: bad result When using the xshow, yshow or xyshow operator the results may be incorrect, and spurious errors may occur, especially if garbage collection happened to coincide with the operation. Bug-id: 1.52/080/CCITTFaxDecode Mode: any Area: occasional unexpected error Encoded data for the CCITTFaxDecode filter was not always being read to end of data. This occurred when the number of columns was a multiple of 8, and the data contained the optional EOD mark following a complete data set. Bug-id: PSAlter-2001-001 Mode: any Area: occasional unexpected error The currentpagedevice operator gave an invalidacesss error in global VM mode. This operator should have been returning an object in local VM, even when true setglobal is in effect Bug-id: PSAlter-2001-002 Mode: any Area: occasional unexpected error Co-ordinate truncation is an option, in Limits Setup. This was not always effective, as in the example 40000 40000 scale 0 0 1 1 rectfill. Bug-id: PSAlter-2001-004 Mode: any Area: occasional unexpected error If a binary sequence was for a string (starting with 142 etc.), then PSAlter did not correctly process the token.