![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: "diff" in DOORS 7.1 Topic Summary: The "diff" param compares richText markup! Created On: 9-Feb-2006 20:45 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I'm using the "diff" param with DOORS 7.1.
When I pass in plain text, the marked up text looks as expected with additional text underlined and deleted text in strike-through. When either the source or target buffers contain any richText markup (bold, italic, underline, etc), the richText markings are included in the result, and that just looks ugly. Run this example to see what I mean. Has anyone done any work to maintain the richText in the source and target buffers yet still use "diff" to show the changes? Thanks, Dennis |
|
![]() |
|
![]() |
|
You may remove rtf markers with a for loop before comparison.
Does anyone know any dxl native perm to perform this action in one move? (some kinf of "string removeListedAndUnlistedRichText(string)") ------------------------- E. Piallat CeBeNetwork |
|
![]() |
|
![]() |
|
This is a good suggestion, however I would like to maintain all of the RTF markings from the original versions through to the "diff" version. This would essentially keep all bold, italic, underline, symbol font, bulleted text, indentation, color, etc.
-Dennis |
|
![]() |
|
![]() |
|
I've got a "fStripRT" function that loops through all the "RichTextParagraphs" of the rich text, retrieves the "rtp.text", and separate each additional chunk with an EOL.
Good luck. How do you intend to show the differences when the user simply adds or removes bolding? You cannot "strike out" bolding. Rich Text markup, as far as I can tell, has two forms [1] Markup is in braces: {\b BoldedText}, [2] start and stopped: \b Bolded Text \b0 . I'd be tempted to explore this possibility as follows: Convert all the Rich Text indicators to some holding pattern, then do the diff(), then convert back the holding patters to their corresponding RT markup. I'm involved in something like that as we speak, writing a front end for "diff()" that allows the output to be placed in an attribute, or be exported to MS-Word. Its a nightmare just dealing with RAW text; i doubt I could ever get it to work with Rich Text. Problems I'm having is [1] Often an EOL is struck out and then underscored. MS-Word displays, of course, two EOLs and the output looks funny. [2] RT Markup must be followed by a white space, e.g. "\b ". An EOL qualifies as white space: "\b<eol>". But when I convert the EOLs it looks like: "\b**EOL**" and now the "\b" isn't followed by white space and is treated like regular text. No, I don't understand what I just said either. I've got a call into Telelogic asking for the delimitors used be "diff" to distinquish its "words", hoping they use one that's not a printable ascii character. - Louie |
|
![]() |
|
![]() |
|
I ran into this situation the other day while writing a baseline comparison/module comparison tool specific to our project. I believe I've come up with a rich text diff function that seems to be working for my baseline comparison tool. I still haven't figured out how to handle objects that contain an OLE object, so the OLE doesn't get put into the output buffer/string. If you use the function richTextWithOle () and the object contains an OLE the returned buffer/string ends up being jibberish after the OLE and it doesn't correctly insert the OLE. Still working on this. Attached is the function I use.
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com Edited: 6-Dec-2006 at 13:19 by Scott Boisvert |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
"diff" in DOORS 7.1
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.