![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Removing all Rich Text, same size fonts in Object Text Topic Summary: Rich Text font size Created On: 18-Nov-2004 15:04 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Be aware that DOORS V7.1, and likely earlier versions, now translates hidden text markup \v (On) and \v0 (off). * I found this out when investigating the more obvious font problem - in our case a mixture of Roman and Helvetica typefaces. I noticed that text that appeared in V5.2 documents was now missing. You can set up a layout DXL column to view the markup: string a a = richText obj."Object Heading" if(a!="") {display a} a = richText obj."Object Text" if(a!="") {display a} Then filter on the column using the regular expression \\v[^a-z]. This will reveal any objects with hidden text markup. We have reported this to Telelogic but so far had no solution. They did give us some DXL to eliminate the font problem so I hope they can build on that to solve this version of the problem. (* I originally wrote "If you save an object with hidden text it deletes the hidden text." but this no longer happens. This is not the only thing that changes its behaviour. I found once that making a copy of a module cured the font markup problem - but now it doesn't - however in that case I have the files that prove it once worked!) | |
![]() |
|
A number of modules that exist have been populated over time by various means: importing portions from various Word documents, manual inputs and probably other means. This has resulted in the text being all different sizes. Does anyone have any DXL scripts that would strip any and all Rich Text from a module to make the text the same font/size? I don't care about any other rich text that may have been deliberately added to the text.
TIA Frank |
|
![]() |
|
![]() |
|
Before you try it - be aware that this will delete all OLE Objects / diagrams etc that you may have in the Formal Module....
|
|
![]() |
|
![]() |
|
Frank,
I have such a script (Normalize Rich Text Markup) in the downloads area of my web site. It meets the followign requirements: (1) Eliminates all non-standard Font Markup for Object Heading and Object Text (2) Preserves Rich Text Markup ( bold, italic, strikethru, underline, superscript, subscript) (3) Preserves Symbol Font (4) Does not modify Object Text with embedded OLE, bullet, or indent markup (new features in DOORS 6) ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Be aware that DOORS V7.1, and likely earlier versions, now translates hidden text markup \v (On) and \v0 (off). * I found this out when investigating the more obvious font problem - in our case a mixture of Roman and Helvetica typefaces. I noticed that text that appeared in V5.2 documents was now missing.
You can set up a layout DXL column to view the markup: string a a = richText obj."Object Heading" if(a!="") {display a} a = richText obj."Object Text" if(a!="") {display a} Then filter on the column using the regular expression \\v[^a-z]. This will reveal any objects with hidden text markup. We have reported this to Telelogic but so far had no solution. They did give us some DXL to eliminate the font problem so I hope they can build on that to solve this version of the problem. (* I originally wrote "If you save an object with hidden text it deletes the hidden text." but this no longer happens. This is not the only thing that changes its behaviour. I found once that making a copy of a module cured the font markup problem - but now it doesn't - however in that case I have the files that prove it once worked!) Edited: 7-Dec-2004 at 10:12 by Peter Seager |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.