I definitely want to start using Cognos. My first issue is trying to import my queries from Query builder into Cognos Business Report. It's not seeing my queries.
How do I contact the moderator to change the community?
Thanks for your assistance.
I definitely want to start using Cognos. My first issue is trying to import my queries from Query builder into Cognos Business Report. It's not seeing my queries.
How do I contact the moderator to change the community?
Thanks for your assistance.
Thanks Gareth, Suzanne, and Raymond for your input. It was very helpful, as was the PTC support team.
Here is what happened in my situation:
[Short version = Use the v6 set of files with v9 DTD to see what happens; proper solution would be to obtain or build a v9 stylesheet, which, in this case, would have probably only a few differences from v6.]
Long version:
When trying to use the new DTD, Arbortext Editor prompted me to compile the DTD.
This process returned an error:
[A20082] Cannot create or write to temporary file C:\Program Files (x86)\Arbortext\Editor\custom\doctypes\38784STD-BV9\_catpath. Unable to compile the DTD.
The error was resolved by running Arbortext Editor as an administrator.
Compiling the DTD generated these files:
38784STD-BV9.dec
38784STD-BV9.log
38784STD-BV9.pro
38784STD-BV9.ptd
dtgen.log
...within the custom\doctypes folder for v9. Also present were the v9 DTD and .fos that I had obtained from the AF.
I had been informed that the compiling process would generate a demo file but it didn’t appear to.
At the suggestion of PTC tech support, I copied demo.sgml from my older custom directory (v6) to the new one (v9). I changed v6 to v9 within the file’s text, using Notepad.
I also copied “catalog” from v6 to v9, and again changed v6 to v9 within the file, using Notepad.
Same for template.sgml though I am not sure that file was needed.
And for the stylesheet (.style), I copied v6 to v9, and changed 6 to 9 within both the filename and the text of the file.
The reason to copy these v6 files to v9 was because at that point I just wanted to be able to open an sgml file using the v9 DTD regardless of whether I had the other proper v9 custom config files in place.
When I opened this “v9” demo.sgml in AE it gave me only two context errors.
From this point I was able to successfully associate my v6-compliant sgml document with the v9 DTD instead, and I print-composed using the v6-renamed-as-v9 stylesheet, which, while not technically correct process-wise, produced a correct-looking PDF, and this whole process basically served as a teaching tool.
I then had further questions about some specific tags which I wasn’t able to control in the way that I thought I should be able to. (Though admittedly these were tags & elements that I hadn’t used before.)
The PTC support person looked at the custom config files mentioned above, and asked for the DCF as well. Again, I only had a v6 version, within which we simply changed the v6 to v9, per his suggestion, and copied to the v9 directory. He wasn’t able to resolve the inoperability of the tags in question. Regardless of that issue (or in part because of?) he stated that the solution going forward would be to obtain or build a v9 stylesheet for this MIL standard (as Gareth had explained above, I believe) though the v6 version could be used in the meantime.
Abortext IsoView does not appear to be qualified for touchscreen devices and there appears to be more development of functional improvements on the Creo View product range. Will IsoView be improved or can Creo View be considered a modern replacement for IsoView when viewing 2D technical illustrations on touch devices?
CreoView seems to support a wider range of Web broswers compared to IsoView, so it is not just the user experience aspect where this query is coming from.
Web Browser | IsoView | CreoView |
---|---|---|
Internet Explorer | ![]() | ![]() |
Firefox | ![]() | ![]() |
Chrome | ![]() | ![]() |
I'm currently working a problem with the pview plugin, I want to hide the 'File' menu, the toolbar contains 'Home', 'Markup', 'Sectioning', 'Animation' should be kept visible.
Can anyone give me some advice?
I have developed an Import Map Template (MS Word to XML) which does not pick up any lists within tables from the source document. All other lists are correctly recognized. To remedy this issue, I set the "include lists" option in "initial preprocessing options" to true. This resulted in lists within tables being correctly recognized by the Map Template Editor, however when using the Map Template to import the Word file into Arbortext Editor, all lists now restart after every list item.
For example, where you would normally have 10 listitems within an bulleted list, there are now 10 bulleted lists with one listitem each. This error occurs in all lists. I've included screengrabs of how it looks in the source file pane, and then the results in Arbortext Editor. So in summary: For the Map Template to pick up lists within tables, I enabled "include lists". However, now all lists refuse to have more than one listitem.
Any advice on how to how to fix this would be greatly appreciated!
Hello Dmitry,
thank you for your answer. We dont need autnumbering prefix/suffix. There are many   spaces inside the xml file. We would like to show a curl instead of the space in the Arbortext Editor.
I've been asked to create and configure a template for a new document and I don't know where to start. I'm navigating through the DOCTYPES directory for some guidance.
I tried to take some of the training online but my request must have been lost in the shuffle. Anyway, training or not, I need to do this and this file appears to be necessary for my new dtd but I don't know why.
Thanks.
Hi Joseph,
A DCF file is a Doctype Configuration File. It is a config file for an individual "doctype" within the doctypes folder in Arbortext custom folders. It specifiies things like tags for bolds, italic, and grapics. It specifies a table model. You can also configure what shows in the New Dialog in Editor for that doctype.
There are a host of options that can be configured in the dsf file and they are very useful. You can edit them directly in Arbortext Editor or in a text editor of your choice if you're careful. If you browse through the documenation on PTC support site, there is a Document Types Guide that defines the many options in a dcf pretty well.
Hope that helps!
I'm not sure what version of Arbortext you are working with, but here is a link to the latest DCF guide from PTC support.
http://support.ptc.com/WCMS/files/157541/en/doctype_guide.pdf
This is exactly the sort of guide that I've been looking for. Thank you!! I'm using Arbortext 5.3 but we also have 6 but have not implemented it yet. I'll go through your posted URL to see if there are other documents that will benefit me.
I can center text using the HTML and XHTML doctypes by editing the attributes but can't seem to do this in SGML or XML based docs like DocBook or any of our custom DTDs. It appears that it is disabled somehow but I don't know where to enable this?
I also tried to solve this by clicking on Format --> Touchup --> Custom Touchup --> Horizontal tab --> Justification = center
Does the solution involve the Styler? DTD? FOSI?
Please help, thanks!
You have to realise that Arbortext Editor is not like Microsoft Word. MS Word is about making the text look how you want. Editor is about making the content structured. The difference here is you should be picking an element/tag for your content that causes the display to be centred.
For example, if all Heading 1 should be centered then make sure to tag all Heading 1s with the appropriate tagging. You would then update the stylesheet (usually via Styler or FOSI edits) to set the centring you require. All Heading 1s will then be centred.
The sequence is a portrait figure followed by two foldouts... Then more levelledPara elements
The figure and foldout with two graphics are nested inside levelled paras
Thanks Gareth, I realize the differences in both applications so I'm trying to find a way to do this in the FOSI and I don't know if we own the full license that includes Styler (I'll find out later today). The free version of Styler doesn't really help me, or I'm not sure how to use it because I ultimately need to make edits to PDF files.
However, what is the FORMAT --> TOUCHUP menu for if everything depends on editing a .style or FOSI? How is that option used? Do you know?
Or is there something I'm still not getting?
The free version of Styler will let you edit stylesheets for screen display only, not the PDF output. If you need to modify the PDF output then you either need Styler or need to roll your sleeves up and learn FOSI or APP code
The Touchup options insert PIs (processing instructions) in the markup. These are not elements nor attributes, but they are interpreted during the publishing process and can modify the PDF output. They are intended for minor "one off" changes to font, colour, epmhasis, etc.
Hi Tag,
Were you able to work through this, or do you still need some assistance?
Hi Bruno,
Unfortunately, this is a limitation of modifying a table in this manner.
You'll need to find a way of wrapping the text manually via the styling code if it's too large for the cell, or resize the cell. Other limitations can be seen in the article detailing this process:
https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS38621
Hi Ajay,
This doesn't appear to be supported with OOTB behavior. It would likely take some APP source edits, which can get complicated. If you need further assistance, it may be best to open a case with TS for this.