Hi,
I have been playing with this functionality and have a requirement to have Arbortext write the DTD defined default attribute values. Executing the command after opening the application works as expected but is there any way to set this as a default value and not have to re-execute the command every time the application opens?
Thanks!
Hi Steve--
Yes, you can do this by adding a small script file to your custom directory. (If you are not using a custom directory of your own, you can use the one in the Arbortext installation directory.)
Create a file called init.acl, with the following command:
set writeunspecifiedattrs=all;
Then put it in the init folder in your custom directory. This will run the command every time you start up Arbortext.
--Clay
Hi Marko--
The first thing I would try is copy and paste. I don't know if it will handle your graphics, but it will try to do something reasonable with the main content and with tables. You might not get exactly what you hope for, but you should get something that you can clean up without too much effort. A lot depends on how well the source Word documents are formatted--do they use consistent paragraph and character styles, are they free from "format fudging" such as using empty paragraphs to insert white space, does the content structure make sense, etc.
If that doesn't work well enough, I've also had luck using LibreOffice to open a Word document, and save it as Docbook XML. From that point you should be able to convert to your target doctype.
Arbortext does offer a very powerful Import feature, but you have to pay an extra license fee for it, and it is probably overkill for your use case unless you have a large number of similarly-formatted Word documents to convert. It also takes a bit of training to get the hang of developing templates to map input styles into output markup.
--Clay
To say briefly - these software products are designed for a slightly different purpose:
Or you mean - better for connecting with Windchill PDM?
P.S. But apparently the functionality of both programs eventually merged into one new software.
The Arbortext for Aerospace and Defense (S1000D/S2000M) Solution, version 4.4 M120 is now available on the PTC software download site for download (https://support.ptc.com/).
Congratulations to all who worked on this release within PTC, and I hope that our customers find the new solution valuable. A full set of release notes is available on PTC.com that describes the content of this release. http://support.ptc.com/WCMS/files/170071/en/ad_release_notes.pdf
Thank you,
Ian Boulton
Sr Director, SLM Solution Mgt
I created a "doctypes" folder in "my Arbortext" folder on my hard drive, outside of the PTC (Arbortext Editor) folder. I downloaded my DTD from the AMECOM website and inserted the DTD in the doctypes folder (the other files you see in "my Arbortext" folder were also downloaded from the same site as the DTD).
I open (File->New) a new document in Arbortext Editor and the New Document window appears. I select the browse button and navigate to my doctypes folder, select the DTD I need to use (as indicated-You will navigate to where your DTDs are stored) and then my new document using the selected DTD opens and I can start working. Hope this helps.
Mike
To get the opportunity browse again to a dtd, then you need to delete the cache directory, which is where Arbortext Editor stores the location of the browsed dtd. See Help > Session > Session (tab) and scroll down to "Cache directory".
Close Arbortext Editor. Use Windows Explorer to locate the Arbortext Editor's cache directory. Delete the doctypes directory in that cache directory.
Another method for placing your document types, stylesheets and related doctype documents is to place them in the ArbortextInstallPath\custom\doctypes directory. Arbortext Editor automatically checks this area for dtds. For further details see the Arbortext Editor Help Center for information about the custom directory.
Hi:
Our writers are using Arbortext 6.1 M060. Is there some setting or customization available to turn off linktext elements when using Preview Link Text for link lists? Selecting Insert Preview Link Text in DITA preferences works fine for xrefs, but not for links in linklists.
The following link structure in link lists is a bug as inserting <? type statements in <linktext> will logically render an empty link in DITA processors like DITA OT, which will then have nothing to link, generating empty Related Topics sections (I have confirmed this):
<link format="dita" href="SomeFile.dita" scope="local" type="concept"><linktext><?Pub _previewtext text="Some Title or Text"?></linktext></link>
This is basically saying "insert emptiness" for the link text as the DITA processor will ignore <? type statements by design.
The form should be without linktext:
<link format="dita" href="c_Customizing_ribbons_and_Quick_Access_toolbars_aw1163702.dita" scope="local" type="concept"><?Pub _previewtext text="Some Title or Text"?></link>
This will allow Arbortext to display preview text to the writer while letting the processor pull the title for the actual link in HTML during build time. The completeness check in Arbortext runs fine using this format.
Obviously turning off preview link text will force the DITA processor to grab the title text for the link at build time, but then our writers will lose the extremely valuable feature of seeing their links previewed in Arbortext while authoring.
Writers should not have to fix this format by hand every time they build a link list, which is actually quite a tricky maneuver in Arbortext. I can set up a pre-build script to strip the linktext in linklists when using text previews, but I would rather not. Linktext should not appear in the first place when using link previews in link lists as linktext with--in effect--empty text makes no sense to processors.
Troy Klukewich
Documentation Manager
Oracle Corporation
thank you very much.
I think they are both easy to connect Windchill PDM.
This certainly doesn't sound like desired behaviour. You may need to end up filing a PTC Support ticket for this to get to the bottom of this (in case there is a good reason <linktext> is required).
I don't have any suggestions besides your idea of a fixup script. This could execute on document load in Editor, on completeness check in Editor, on document save in Editor, or at check-in to your CMS (via Arbortext burst hooks or CMS-side hooks).
I second Tim's suggestion to setup a "custom" doctypes folder and use catalog files to associate PUBLIC IDs with actual DTD file locations.
I keep the original files in the PTC folder and do not "infect" the original PTC folder with changes. This is how I have operated at my last two companies. My prior company has an Arbortext Administrator who strictly enforced this setup (leaving PTC folder isolated and using a "My Arbortext" folder for things that change/need updating). I assumed the Arbortext Administrator knew better than me so I continue using this procedure at my current company and suggest others that do not know the intricacies of Arbortext Editor to do the same and leave the complexities of PTC to the experts.
Good policy - you don't want to mess with the PTC folder as it can cause big problems when updating. The "My Arbortext" folder can be setup very simply by configuring the APTCUSTOM environment variable to point to the folder location. You can then copy over the "custom" folder contents from the original PTC folder. This will act as a template for the folder structure of your "My Arbortext" folder. If you ever move to a new machine, just copy over the "My Arbortext" folder and setup the APTCUSTOM again on the new machine.
Cosmin,
Be very careful when you configure your APTCUSTOM environment (Tools->Preferences->click on File Locations). Do not delete any of the original paths, only add your new path to the File Locations.
If you delete any of the original/existing paths, Arbortext Editor will stop functioning and you will have to either reinstall Arbortext Editor or .have someone from PTC reconfigure your Arbortext Editor. I speak from experience!!!
Mike
If I am understanding your question properly, you can set your default DTD in the File Locations link (Tools->Preferences->File Locations). Do NOT delete or modify any of the pre-existing paths. Just add the path to where your entities and DITA References are located on your hard drive or internet location.
I created a "My Arbortext" folder on my hard drive outside of the PTC folder where my DTDs, FOSIs, and ditarefs exist.
We have recently changed from DTD to a schema. Since doing so we have lost our entities/symbols from the drop-down list. From what I have read on this forum site, it appears that PTC has not made an atempt to resolve this issue. I am wondering if anyone has come up with a solution. I would appreciate if anyone could provide a few suggestions. Thanks
Hi Kathleen--
You can work around this using some ACL code. In your editinit.acl file, add the following:
require _findentdlg;
set entitylist="...";
_findentdlg::_updateEntityList(current_window(),current_doc());
Replace the "..." with a space delimited list of entity references. With a schema, you won't have named character entities, so you'll have to use numeric entities, for example if you want to include the copyright and trademark symbols, it would look like this:
set entitylist="© ™"
For some reason, just setting the entitylist option string won't update the droplist automatically, that's why you have to use the _findentdlg::_updateEntityList() function to do that.
--Clay
Hi,
I resolved my problem long time ago. Late, but I would like to share my solution.
My solution is almost similar to Andrew's comment.
It is as follow :
1. Prepare a font to support more than circle number 15
- I used 'Quivira' font.
2. Edit stylesheet
1) Add 'XPath Condition' for <li> tag
2) Add 'Generated text' for the 'XPath Condition'
- Because 'count method' starts with 0, 'Generated text' is a 1 bigger than count.
- However, this way has a constraint that must know the max number.
BR
Kim, Joon O
Does anyone know if there is a quick way of changing curves back to thick and thin if they have been converted to single thickness?
You can get thick and thin back using F12 but it converts arcs back to ellipses so you have to cut them out again.
I created pseudo elements in my document with ACL:
<?Pub _source_data><?Pub _rqrd_item
attr1="source2" attr2="Required Source Data Item"><?Pub /_rqrd_item><?Pub
_src_item attr1="source1" attr2="value1"><?Pub /_src_item><?Pub _src_item
attr1="source3" attr2="value3"><?Pub /_src_item><?Pub /_source_data>
I am trying to use the FOSI to format these elements:
<e-i-c gi="_source_data">
<charlist charsubsetref="standalone">
<usetext source="\SOURCE DATA:\" placemnt="after">
<subchars charsubsetref="gentext"></subchars>
</usetext>
</charlist>
</e-i-c>
I can't seem to get it to work. Am I missing something. I am using PTC 5.3.
