We are using DOORS 188.8.131.52 with RPE 1.1.2, however the symbols pasted into DOORS are still not exporting as symbols. The symbols are still exporting as squares. The fix was supposedly included in DOORS 184.108.40.206 and later with RPE 1.1.2 (RFE here: http://www-01.ibm.com/support/docview.wss?uid=swg1PM26621). Are we missing something?
Dragos.Cojocari 270001QUCG1654 Posts
Re: Symbols not printing in RPE 1.1.2 and DOORS 220.127.116.11013-10-18T13:30:22ZThis is the accepted answer. This is the accepted answer.
if I remember correctly with RPE 1.1.2 you had to use the nonUnicoeFonts property to specify the font to be used for symbols ( see http://pic.dhe.ibm.com/infocenter/rpehelp/v1r2/index.jsp?re=1&topic=/com.ibm.rational.pe.reference.doc/topics/r_flags_generic.html&scope=null) With 18.104.22.168 and newer that is no longer necessary (http://rpeactual.com/2012/05/02/rpe-1-1-2-2-details/).
But 1.1.2 ad eve 22.214.171.124 are old RPE versions. Why are you still using them? The current GA, 126.96.36.199. is a solid version of RPE and output is significantly improved compared to 1.1.2.
DragosUpdated on 2013-10-18T13:30:39Z at 2013-10-18T13:30:39Z by Dragos.Cojocari
alisyn.bechtel 270005VB3P16 Posts
Re: Symbols not printing in RPE 1.1.2 and DOORS 188.8.131.52013-10-18T15:44:30ZThis is the accepted answer. This is the accepted answer.
- Dragos.Cojocari 270001QUCG
Thanks, Dragos. Clarification: I tried the configuring the non Unicode Fonts property, which did not fix the issue. I also tried other settings based on other RPE information I read, including trying to configure the "non Unicode fonts" setting in Runtime > Metadata. At this point, my experience that we need to manually fix these characters after the document is published (see link below). If that is not correct, let me know.
- For Microsoft Word output, if you used a non-Unicode font, change the font in the output document after document generation.
We have been slowly adopting RPE, but recently it suddenly hit a fast track. We are working on getting upgraded to RPE 1.2. I will likely use this issue as a catalyst for that upgrade.
AlisynUpdated on 2013-10-31T13:25:43Z at 2013-10-31T13:25:43Z by alisyn.bechtel