![]() |
Telelogic DOORS (steve huntington) | ![]() |
Topic Title: In Analysis view and when use WEXP export get incorrect font (wingdings) Topic Summary: Font Corruptions Created On: 6-Jun-2007 10:23 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am using DOORS 5.2 and have been having trouble with Wingding fonts appearing.
Using WEXP exported tables are coming out in Wingding font if I export from a certain module. If I pull in and export the same view from another module the text comes out ok. It just seems to have got worse, now after a Analysis wizard trace from another module back to the original module some of the object text is showing as Wingdings in the DOORS column itself. Anybody any idea what is happening and how to sort it. I have tried re-typing all the text in one of the affected objects but it has no effect - still appears in trace column as Wingdings. Thanks in advance |
|
![]() |
|
![]() |
|
DOORS is capable of storing more rich Text format with the Objects than it is actually capable of displaying in the GUI. It is possible that you copied and pasted text from e.g. a Word file into the table, thereby copying the Wingding font into DOORS. Altough properly displayed in the DOORS GUI, the (hidden) rtf features might still blow up your export. This is just an idea, however. You can check that with the following line of code in the DXL window:
print richTextFragment(richText((current Object)."Object Text")) If some strange font information is displayed, this might be the reason for your problems. Note that just re-typing the text in the GUI not necessarily solves the problem! I had a similar case once, and there a (current Object)."Object Text" = (current Object)."Object Text" "" actually did the trick. Note that this deletes OLE objects, if there are any, and any rtf features like bold and italic which might be there on purpose. It's worth a try Cheers, Peter |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.