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: Restoring 5.2 Archives in 6.0SR1 - not 1:1?
Topic Summary:
Created On: 10-Jan-2003 21:56
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.
Answer This question was answered by Peter Seager, on Friday, March 11, 2005 5:05 PM

Answer:
Maybe the following experience can help here.

We were running DOORS 5.1 on terminal server and various local installations. We noticed a difference between the typeface on the two types of installation.

The problem was that both the Classic and Modern display options are setup to use New Century Schoolbook as the body text font but both displayed as Helvetica on the terminal server installations. Because Helvetica is sanserif whereas New Century Schoolbook has serifs, the problem is obvious once you know.

We found that the local installations had New Century Schoolbook included in the Word fonts but the terminal server installation, being more recent, did not. Installing the New Century Schoolbook font with Word on terminal server solved the problem.

Most people did not know they had a problem, (Helvetica is our preferred font) but I was afraid it would cause problems if it fixed itself eg during an upgrade.
 10-Jan-2003 21:56
User is offline View Users Profile Print this message


Michael Mahler

Posts: 8
Joined: 10-Jan-2003


Using DOORS 6.0SR1, when I restore a module archive that was generated with DOORS 5.2 I've noticed the following:

1) Trailing line feeds are removed from Object Text

2) Font changes (from 5.2's Arial to Times New Roman best I can tell)

3) Object sizes (embedded pictures) change

Anyone else notice this and possible have DXL to fix it? Sure seems like a bug in 6.0 Restore to me.
Report this to a Moderator Report this to a Moderator
 13-Jan-2003 04:21
User is offline View Users Profile Print this message


Michael Sutherland

Posts: 248
Joined: 13-Sep-2002

Michael,

I have noticed all three of the effects you mentioned. They are caused by the migration of data from DOORS 5 to DOORS 6, and not specific to the process of restoring an archive. Migrating an entire database will demonstrate the same effects.

Telelogic has made some major changes in DOORS 6 with regards to how Rich Text and OLE Object are stored and managed. They now use Microsoft "Rich Edit Controls."

1) Trailing line feeds are removed from Object Text

If there was a trailing line feed in the Object Text attribute, it will be removed as the result of a migration. If there were more than one trailing line feed, only one will be removed. I don't have a workaround for this issue.

2) Font changes (from 5.2's Arial to Times New Roman best I can tell)

A technique that has worked for myself and others with similar problems in DOORS 5 is to clear the Module level attribute "Font Table" (if it exists) using the undocumented command:

deleteFontTable( current Module )

If that doesn't fix it, I would try resetting the "Object Text" using the documented removeUnlistedRichText() function.

If that doesn't fix it, I would try resetting the "Object Text" using the undocumented richTextFragment() function. Refer to the following thread for details:

http://www.telelogic.com/support/doorsers/forums/messageview.cfm?catid=17&threadid=619

Please let us know (in this forum) if any of the above ideas solve your particular issue.

3) Object sizes (embedded pictures) change

In terms of the size they appear on the screen when using the DOORS 6 interface, they appear larger. In terms of database storage bytes, they actually get smaller, because DOORS 6 now compresses OLE objects for storage.

It is a known issue (DL2022076) that the byte size of an OLE object exported to MS Word may be significantly larger in a DOORS 6 export than the same OLE object exported from DOORS 5.



-------------------------
Michael Sutherland
michael@galactic-solutions.com
http://galactic-solutions.com
Report this to a Moderator Report this to a Moderator
 13-Jan-2003 12:18
User is offline View Users Profile Print this message


Michael Mahler

Posts: 8
Joined: 10-Jan-2003

Michael,

Thanks for your reply - good to know I'm not going insane!

I'll try your suggestions and get back to you here. Telelogic should at least not be stripping CR's (or ANYTHING for that matter) from Object Text when restoring. I've opened a case with them to see if they've looked into it at all since it severely changes the format of some docs where CR's are used to maintain spacing.

BTW: Did you notice the same results using their moduleMigrator DXL? I can give it a whirl but didn't want to re-invent the wheel.

Edited: 13-Jan-2003 at 12:22 by Michael Mahler
Report this to a Moderator Report this to a Moderator
 13-Jan-2003 12:50
User is offline View Users Profile Print this message


Michael Sutherland

Posts: 248
Joined: 13-Sep-2002

Michael,

I have never used the moduleMigrator.dxl to automate the "second stage" (see below), but as long as you have opened and saved your Modules in D6 after initial migration or restore, you have completed the same task. All of the effects we are discussing persist after the "second stage" is completed.

The moduleMigratorreadme.txt says:

"Migration of data from DOORS 5.x to DOORS 6.x is in two stages.
The first stage is a database structure migration, and this is
performed when the Administrator logs into DOORS 6.x and confirms,
when prompted, that the migration should proceed.

The second stage requires that modules be opened and saved in
DOORS 6.x. The data migration is not complete until this has been done.
The moduleMigrator.dxl utility allows this second stage of migration
to be automated."

So the moduleMigrator.dxl doesn't do anything other than open and save Modules in DOORS 6. It is a necessary step, because the Modules are not completely converted, and open very slowly until the first time they are saved (I assume due to the workload necessary to complete the conversion of data). Then the next time they are accessed they open in the same amount of time as they did before the DOORS 6 migration.

Note: the moduleMigrator.zip package can be found at Telelogic's web site in the "DXL utilities" area:

http://www.telelogic.com/support/doorsers/dxl/index.cfm

-------------------------
Michael Sutherland
michael@galactic-solutions.com
http://galactic-solutions.com
Report this to a Moderator Report this to a Moderator
 13-Jan-2003 13:00
User is offline View Users Profile Print this message


Michael Mahler

Posts: 8
Joined: 10-Jan-2003

Thanks once again, I somewhat suspected you'd say that. I wasn't sure if by "opened and closed" they meant "archived and restored".

Telelogic should consider the change of any Object Text during a restore as a bug, even if it's intended as a trimming of somesort of CR's. Perhaps I can write a script to run on the 5.2 modules that flags trailling CR's with some unique character (or combo) and then run another script in 6.0SR1 that will convert them back to CR's.


Edited: 13-Jan-2003 at 13:17 by Michael Mahler
Report this to a Moderator Report this to a Moderator
 13-Jan-2003 15:14
User is offline View Users Profile Print this message


Michael Mahler

Posts: 8
Joined: 10-Jan-2003


Ok, I was able to fix the fonts by using Tools->Options. But for the 6.0 chewing on last CR/LF... hmmm... I'm wondering if it's simplest to just write DXL to slap an extra CR/LF into each ObjectText attribute as a sacrifice to 6.0 restore?

Curious about thoughts on this.

Report this to a Moderator Report this to a Moderator
 13-Jan-2003 15:27
User is offline View Users Profile Print this message


Michael Sutherland

Posts: 248
Joined: 13-Sep-2002

Michael,

Tools->Options->?????? (what function did you use?)

Also, adding a line feed back to EVERY "Object Text" will likely give you line feeds where you had none, because the last one is stripped only if there was one there in the first place. Be careful of updating "Object Text" for Objects that originally had no value for the attribute (Heading Objects, etc.)

-------------------------
Michael Sutherland
michael@galactic-solutions.com
http://galactic-solutions.com
Report this to a Moderator Report this to a Moderator
 13-Jan-2003 15:53
User is offline View Users Profile Print this message


Michael Mahler

Posts: 8
Joined: 10-Jan-2003


Tools->Options-Display and "Fonts" tab on the right hand pane. Seems to make it DISPLAY properly, but interestingly enough, if you bring up the attribute properties and look at the ObjectText it sill shows up as New centruy schoolbook. Apparently, it was New century schoolbook in 5.2 as default, BUT, was showing up as Helvetica (maybe new century wasn't installed somehow in 5.2 properly). So I changed it to Helvetic in 6.0. Looks good on the GUI, but like I said, if you look at the properties, or even print it out - there are some places where it still comes out in New Century Schoolbook.

RE: CR's, my assumption was that if I just slam a CR on the end of every ObjectText that has text in it (good point), that it will eat at least that one. SO even if the attribute was:

Upgrading is fun.

and I change it to:

Upgrading is fun.<CR>

Won't 6.0's restore just return it to:

Upgrading is fun.

?
Report this to a Moderator Report this to a Moderator
 13-Jan-2003 16:21
User is offline View Users Profile Print this message


Michael Mahler

Posts: 8
Joined: 10-Jan-2003


Another anomally I just noticed: 6.0 INSERTS a CR before OLE objects in a table!
Report this to a Moderator Report this to a Moderator
 14-Jan-2003 19:05
User is offline View Users Profile Print this message


Michael Mahler

Posts: 8
Joined: 10-Jan-2003


It's interesting to note that when using Word Import you do not get the extra carriage return prepended. So this appears to be an issue with "restore".

Report this to a Moderator Report this to a Moderator
 4-Feb-2003 20:01
User is offline View Users Profile Print this message


Michael Sutherland

Posts: 248
Joined: 13-Sep-2002

2) Font changes (from 5.2's Arial to Times New Roman best I can tell)

After a recent DOORS 6 migration, some of my users have seen this font problem in some DOORS objects, which can be traced to "Times New Roman" markup being embedded in the Rich Text markup for those objects. The techniques I originally recommended do not quite eliminate this.

My understanding is this font markup was captured from text imported from MS Word documents in DOORS 5. DOORS 5 did not display the font indicated by the markup, but DOORS 6 does.

I have some ideas, and will be testing them out, but if anyone has already developed a reliable technique to strip the font information while preserving the other rich text and symbol font, please let us know.

-------------------------
Michael Sutherland
michael@galactic-solutions.com
http://galactic-solutions.com
Report this to a Moderator Report this to a Moderator
 17-Mar-2003 14:43
User is offline View Users Profile Print this message


Peter Seager

Posts: 32
Joined: 10-Feb-2003

Answer Answer
Maybe the following experience can help here.

We were running DOORS 5.1 on terminal server and various local installations. We noticed a difference between the typeface on the two types of installation.

The problem was that both the Classic and Modern display options are setup to use New Century Schoolbook as the body text font but both displayed as Helvetica on the terminal server installations. Because Helvetica is sanserif whereas New Century Schoolbook has serifs, the problem is obvious once you know.

We found that the local installations had New Century Schoolbook included in the Word fonts but the terminal server installation, being more recent, did not. Installing the New Century Schoolbook font with Word on terminal server solved the problem.

Most people did not know they had a problem, (Helvetica is our preferred font) but I was afraid it would cause problems if it fixed itself eg during an upgrade.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 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 1 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.