![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Rich text export to Excel Topic Summary: Created On: 24-Mar-2004 08:18 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Using the DOORS 7 version of Galactic Solutions Enhanced Excel exporter, we noticed that richText is not handled very well. It exports rich text, but somehow the tags get displaced in the text, shifting forward a number of characters.
The tags exported can be seen in the code below. See the attached file for the output generated in Excel. My question: is this due to DOORS or our script, or is it something to be fixed in the Excel exporter? Nevertheless, we use the script often. Thanks Galactic for sharing it. Pieter ------------------------- Pieter de Waard www.nhindustries.com Edited: 24-Mar-2004 at 08:30 by Pieter DE WAARD |
|
![]() |
|
![]() |
|
Pieter,
Can you send me an archived Module with an Object that has text which demonstrates the problem when exported to Excel? One Object is all I need. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Pieter,
I have posted an updated v2.2.6 of the Enhanced Export to Excel which addresses two problems with exporting Rich Text. The first was a simple counting error where Rich Text markup was shifted because new line characters were not accounted for. This has been fixed. The second error was a bit tricker. It turns out that the DOORS 7.0 SP1 Rich Text commands do not return the correct value for Rich Text strings with embedded Symbol Font markup. The problem does not appear in earlier versions of DOORS, including DOORS 7.0. To work around this, I disabled Rich Text exporting for cells with Symbol Font markup, so that the symbols are preserved (in DOORS 7.0 SP1 only). I will report the situation to Telelogic so that they recognize the problem, and hopefully they will fix it in future versions. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Thanks Michael - I checked it out and it works fine.
Another question we have: I understand the need to export to Excel, but with it I see also a need for the opposite direction. Having the capability to read directly from Excel into DOORS without the need to pass via the TSV import spreadsheet route. 1. Is it possible/feasible/advisable to go this route? I.e. develop DXL that allows direct Excel importing? 2. If yes, can you give me some pointers on functions such as opening and reading an existing Excel file, finding a specific location from which to read, etc? Thanks again. - Pieter ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
Pieter,
I believe it is feasible. There is already code in the Enhanced Export to Excel that will open an existing Excel workbook and sheet, so you could start from there. The Enhanced Export to Excel also has examples of addressing specific cells in an Excel sheet. Good luck! ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Rich text export to Excel
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.