![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Problem exporting from DOORS 7.1 using WEXP 11.4 Topic Summary: Curly brackets are exported as bookmarks Created On: 23-Oct-2007 16:52 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: My workaround for this problem is to make two versions of WEXP available to users: version 11.4 in it's own menu for all users on all modules but one and version 10.6a buried in the User menu for use only by the author of the module that contains the curly brackets. The older version suffers from two problems:
| |
![]() |
|
Others seem to want bookmarks and the like in exported documents, but I want to get rid of them!
The following two problems occur when exporting from a module in DOORS 7.1 to MS Word using WEXP 11.4:
Both problems go away if I revert to WEXP 10.6a or if I filter out the objects containing the curly brackets from the view used by WEXP. However, neither of these options give me what I otherwise want. Telogic have stopped supporting WEXP (although Professional Services will still work on it for $) and are pushing DocExpress instead, which costs $$$ and seems like overkill, since WEXP has met our needs for several years. Any help with this problem would be appreciated. Many thanks, Ken. NAV CANADA Edited: 26-Oct-2007 at 15:41 by Ken McNair |
|
![]() |
|
![]() |
|
Hi Ken,
this is a bit surprising. AFAIK, bookmarks are created in WEXP using square brackets; curly brackets are used for the creation of field codes, therefore I don't see how an erroneous bookmark can be created with curly brackets. What's more, with a simple {text} I can't reproduce the described error, it just exports properly (well, at least on DOORS 7.0 / WEXP 11.4). Could you provide the actual "Object Text" of an object which creates the error message / bookmark? Regards, Peter |
|
![]() |
|
![]() |
|
IF I EXPORT THE FOLLOWING THREE OBJECTS:
ENTER AIRCRAFT IDENT - OPTIONAL ENTRIES SHOWN BY {} ENTER {STRIP TYPE} AIRCRAFT IDENT(S) - MAXIMUM OF 6 ENTER {TIME} - CURRRENT TIME THE FOLLOWING IS THE OUTPUT: ENTER AIRCRAFT IDENT - OPTIONAL ENTRIES SHOWN BY {} ENTER Error! Bookmark not defined. AIRCRAFT IDENT(S) - MAXIMUM OF 6 ENTER 11:31 AM - CURRRENT TIME Note that: The curly brackets in the first object are exported OK Word inserts the current time in the third object instead of the literal text "{time}". If I Toggle Field Codes, this changes to changes to "{ time *\MERGEFORMAT }" It looks like WEXP is interpreting curly brackets as square brackets. The module isn't corrupted, because I get the same results if I create a new object in a new module. Thanks, Ken. Edited: 26-Oct-2007 at 17:16 by Ken McNair |
|
![]() |
|
![]() |
|
O.K., the bookmark lead me into the wrong direction. What actually happens is that WEXP inserts Word field codes into the document. The WEXP documentation is pretty short on this topic, but Word fields are inserted using curly brackets. {time} is therefore exported into the appropriate Word field as should be expected from the documentation. The bookmark field code is somewhat strange. From the Word file you can clearly see that it is a Word field, so the WEXP part follows the documentation. Why Word interprets it as a bookmark reference I don't know.
So, unfortunately, the observed behaviour does follow the documentation, which means that I'd guess it is impossible to make WEXP export text within curly brackets. A workaround would be to type something like "... curlyOpen time curlyClose ..." in the module and use a Word macro in order to replace the "curly..." stuff with the appropriate brackets. Cheers, Peter |
|
![]() |
|
![]() |
|
Peter,
Thanks for the partial explanation. However, I can see this resulting in unresolved bookmarks, but why the "Internal error in WideCharToMultiByte -87"? The workaround you suggest won't fly for us, because we do most of our work in DOORS, so the curly brackets have to be visible in DOORS, not just in the exported Word doc. IMHO WEXP 11.4 should have an advanced option to turn this feature off, so that it would be backwards compatible with older versions. We don't have this problem with WEXP 10.6a, although we do have other problems like is many times slower (an hour to export some modules...) Regards, Ken. Edited: 29-Oct-2007 at 20:02 by Ken McNair |
|
![]() |
|
![]() |
|
My workaround for this problem is to make two versions of WEXP available to users: version 11.4 in it's own menu for all users on all modules but one and version 10.6a buried in the User menu for use only by the author of the module that contains the curly brackets. The older version suffers from two problems:
|
|
![]() |
|
![]() |
|
I finally worked around this problem by editing the WEXP 11.4 DXL script to always return false when searching for curly brackets. If anyone else has this problem, I'll show them the offending line of code. If I had the time I'd add some code to make this an advanced option that could be selected/unseleted by the user.
Thanks for the help Peter! Ken. Edited: 2-Jan-2008 at 15:27 by Ken McNair |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.