Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: DOORS 8.1 - Rich Text Corruption
Topic Summary: “ becomes “
Created On: 27-Sep-2006 19:20
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 27-Sep-2006 19:20
User is offline View Users Profile Print this message


Shawn Stepper

Posts: 96
Joined: 6-Aug-2004

Has anyone run into this issue with rich text processing? When looping through rich text elements in a rich text paragraph (as in for rt in rp do ... string = rt.text), pulling out the text property causes data corruption.

For example:

This describes the "what" from the customer point of view.

becomes:

This describes the “what” from the customer point of view.

The rich text of the original string is:

This describes the \ldblquote what\rdblquote from the customer point of view.

Which becomes:

This describes the "what" from the customer point of view.

The \ldblquote is being interpreted and convereted to " by calling rt.text.

The problem is then when setting the attribute value using "richText()":
"what"
becomes:
“what”

which in rich text looks like:
\uc1\u8220 ?what\u8221 ?

I've also run into this problem with accented characters and copyright symbols. It's clearly a unicode issue, but has anyone found a work-around?

Thanks!

Shawn

-------------------------
Shawn Stepper
shawn.e.stepper@wellsfargo.com
Report this to a Moderator Report this to a Moderator
 27-Sep-2006 21:04
User is offline View Users Profile Print this message


Marlin Wegner

Posts: 20
Joined: 2-Jun-2006

I am not using ver 8.1, but have noticed similar issues when I exported to WORD (etc.) documents,  the font map that was used by Doors was using wacky fonts that did not map well to "standard" fonts.  As well the color maps were not standard and my colors were thrown off.    My eventual output looked a lot like what you are describing.   I modified the font and color maps and it corrected the output. 

Report this to a Moderator Report this to a Moderator
 28-Sep-2006 10:07
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

Shawn, I just tried this on DOORS 8.1 and I cannot reproduce the error.
I am able to extract the text using rt.text and assign it to an attribute without problem.
Doesn't seem to matter whether I assign using o.attr = rt.text or o.attr = richText(rt.text).

Could this be something to do with your locale?

-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 18-Dec-2006 23:12
User is offline View Users Profile Print this message


Chris Jones

Posts: 177
Joined: 1-Jul-2005

quote:

Originally posted by: Marlin Wegner
I modified the font and color maps and it corrected the output.


We've also seen these sorts of problems. How did you modify the maps? Was it in DOORS, or Word?

Chris
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 2 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 2 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.