tags 492125 + upstream thanks I received a note from upstream indicating that the next release of pstoedit is scheduled to contain a workaround for this issue: > Good new and bad news. > The good one first. There is really a bug in pstoedit which is exposed in > this case. I have corrected this bug and there is no "crash" anymore in > pstoedit. However not the bad news. The crash happened during the try of > drawing certain text via the charpath operator. For some reasons this > throws an error in this example and the there was an error in pstoedit's > error handling case. Now the error is handled correctly in the sense that > it doesn't lead to a crash anymore, but still charpath throws this error. > This can have different reasons and this behaviour of charpath is also > specified in the PostScript LRM. So it is somehow normal. > At the end - even if pstoedit runs through the file now - the result is > not really useful and as expected. -- The road to hell is paved with telecom billing requirements.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
