OIPI and RTF not *seeming* to work (OpenInsight 32-bit Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== OIPI and RTF not *seeming* to work (OpenInsight 32-bit Specific) ====
=== At 12 AUG 2002 03:52:57PM dsig@teleport.com wrote: ===
 
{{tag>"OpenInsight 32-bit Specific"}}
 
<QUOTE>
I have a form which we are using OIPI. In preview the form looks great BUT when we use the rtf output the first x lines and the last x lines are all squished together.



The odd thing is that there is a center section which appears to be correct.



The form is a statement so the first bits (not printing well) are 15+ sections (name address yada yada).  Then there is 30-40 lines of detail with 4 sections accross.  This bit all prints well.  Then the last 10+ sections get all squished together ..



It is hard to explain what I am seeing. I would be happy to send of the rtf file.



The only thing that we do is use the textxy and in some parts change font. But there does not seem to be any *noticable* pattern here.



If I simply view or print to paper .. YEOW it looks good





dsig@teleport.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 503-639-4240
</QUOTE>
----

=== At 13 AUG 2002 11:10AM Tony Splaver wrote:  ===

<QUOTE>Hi David,



I would like to see this RTF file (tony@pacifier.com), and I will look at it before leaving to the conference in a few hours -- otherwise, please bring it to Vegas, and I will look at it there.



However, I bet the problem is caused by using the TEXTXY message. RTF (and HTML too) is basically a paragraph based document format, and positional information cannot be exported to this format. This is not a limitation of the OIPI, but of RTF in general. I think the only way to get a good export is to use the PDF format in the OIPI.



You should create a RTF doc in Word, and put a Textbox in the middle of the page, and then save the document as RTF. You will see that the RTF codes that Microsoft uses to put the text in the textbox is not the standard RTF:



\pard\plain 

\ql \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid9654528 This is a textbox in MS Word

\par }}}{\shprslt{\*\do\dobxcolumn\dobypara\dodhgt8193\dptxbx\dptxlrtb{\dptxbxtext\pard\plain \ql \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid9654528 This is a textbox 

in MS Word

\par





So... you can use the TEXTRTF message to embed this type of textbox in your RTF reports, but the OIPI will not be able to automatically translate the TEXTXY messages into the RTF codes necessary to display it correctly. So, you can create this type of report with TEXTRTF (instead of TEXTXY), but it might be easier to use a PDF export.



Tony

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=FC8B2988FCB9AE4185256C13006D380C|View this thread on the  forum...]]