OIPI errors with RTF text (OpenInsight 32-bit Specific)
At 17 NOV 2003 12:26:06PM Kevin Bolitho wrote:
Is there a specification/reference for the RTF standard used by OIPI? It is obviously not compatible with MS Word's RTF files but MOST of what WordPad generates seems fine. Although a more limited subset, this seems to be an adequate editor for end-users to create RTF files for use with OIPI.
But I am getting errors from OIPI when the WordPad file contains a bitmap. SOME bitmaps are OK, but others generate an error from Set_Printer. After setting ENABLERTF to 1, I get one of two errors when printing Rich Text (that contains a bitmap) loaded from a file into a variable - either
1) -180 when using TEXTRTF, or
2) -158 using TEXTBOX.
I am using OIPI version 4.10.0048 with OI version 4.1.2
At 17 NOV 2003 12:26PM Tony Splaver wrote:
Hi Kevin,
Here is MS's reference for RTF: http://msdn.microsoft.com/library/en-us/dnrtfspec/html/rtfspec.asp. This reference is not fully supported by OIPI (VSPRINTER.OCX).
You do not need to set ENABLERTF to 1 if you are using TEXTRTF. I would also not use TEXTBOX with ENABLERTF set to 1. So, try setting ENABLERTF to 0, and only using TEXTRTF. I doubt that it would cause this problem, but it is worth a shot.
The -180 and -158 are internal runtime errors that are probably caused by something in the raw RTF that the OIPI (VSPRINTER.OCX) does not like. Revelation can give you a debug build of the OIPI32.EXE which will give you the exact error that is occurring, but I bet it is "invalid image" or something like that.
Tony
At 17 NOV 2003 12:26PM Kevin Bolitho wrote:
Hi Tony
Thanks for your response. I guess what I was after was something more specific to what IS "fully supported" by OIPI (VSPRINTER.OCX). Why should one small bitmap be OK and another not? Is there an RTF editor that end-users could use that would generate files that would be acceptable as input to OIPI? As I mentioned, I've found the output from WordPad to be a much better "match" for OIPI than, say MS Word, but bitmaps (eg company logos) may or may not work for them. Is there a "reliable" editor? Should we be using something like your RTF editor component as a built-in editor (is this 100% compatible with OIPI?) rather than relying on a 3rd-party tool (albeit free with Windows).
I had been using TEXTBOX (as well TEXTRTF) for the rtf data because this allowed you to restrict where the rtf output is presented (eg merge labels) - both seem to work/fail equally well. Whereas TEXTRTF is great for free-form multi-page output.
Is there a comprehensive list of the error codes generated by OIPI? (beyond -20)