Skip to main content
M
mburge1-Visitor
1-Visitor
September 18, 2015
Question

XML to MS Word - Arbortext Import/Export Function

  • September 18, 2015
  • 4 replies
  • 4311 views

Hi,

I'm tasked with developing style sheets to convert XML to MS Word. This project will be performed in Arbortext E3 7.0 environment and will be required to use Import/Export function. Has anyone performed this type of task before and can provide some insights? Are there available literature/reading materials you can point me to on the web? Is there anything significant (good, bad, or indifferent) I should be aware of?

Thanks in advance for your help,

Morais

4 replies

S
smaclean1-Visitor
1-Visitor
September 22, 2015

Morais,

I am not the most experienced but I think the Arbortext Import mapping tool is used to go from Word to XML and it's a module of Arbortext Architect. If you are wanting a Word output for your XML that is just something you will write in your stylesheets using Arbortext Styler. It becomes one of your outputs at publish time.

Regards,

Stew Maclean

G
GarethOakes16-Pearl
16-Pearl
September 28, 2015

The "Export" part of Import/Export is what is used for XML->Word. You setup a stylesheet in Styler, and use the RTF features to make sure your output is styled appropriately. Develop/test on the desktop as an APTCUSTOM folder, then deploy that same folder to PE (E3) for production. I think there may be limits for complex content (e.g. tables, equations) so it depends on what you are trying to output as to how suitable that function will be.

BTW if you are using DITA content, you may find the DITA Open Toolkit MS Word output function worth looking at too.

T
thendricks12-Amethyst
12-Amethyst
October 2, 2015

Didn't PTC just announce the discontinuation of export/import support last week?

G
GarethOakes16-Pearl
16-Pearl
October 5, 2015

My understanding is that the problem with Arbortext Import/Export is that CambridgeDocs no longer license the xDoc technology which forms the underpinnings of the Import module. Therefore PTC are unable to continue shipping that component at this point, and are actively looking at replacement technologies. The Export component would be unaffected as it is PTC's own IP.

That's only my interpretation, PTC's official statement is here: https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS196045

M
mburge1-VisitorAuthor
1-Visitor
September 28, 2015

Hi,

Thanks for the feedback! It is well appreciated! Does anyone have some documentation I can use? Some kind of online help, tutorial, etc.

Regards,

Morais

R
rdiaz5-Regular Member
5-Regular Member
September 30, 2015

Hi Morais,

You may want to look over the documentation we have available in the Help Center, and go from there with any specific issues:

http://support.ptc.com/cs/help/arbortext_hc/ae61_hc/index.jspx?id=ID3855075948&action=show

T
TimPhelps12-Amethyst
12-Amethyst
October 12, 2015

Morais,

    Did you get a resolution to this issue?

If so, could you describe it for the community and/or indicate the correct answer that lead to your resolution?

M
mburge1-VisitorAuthor
1-Visitor
October 12, 2015

Hi Tim, et. al,

I am still investigating and trying to identify the best possible way to move forward with this implementation. Currently Iā€™m reviewing the information from the links provided by Rafael and Gareth.

I'd imagine this function was performed by others before. Do you have any documentation from PTC you can share? What is the correct process to use within Arbortext environment to accomplish XML to Word function if Import/Export feature is no longer available? Or is the Import feature is no longer supported due to the third party vendor discontinued developing/supporting this technology?

Regards,

Morais

R
rdiaz5-Regular Member
5-Regular Member
November 14, 2015

Hi Morais,

You're correct in your last statement.  The process still functions as best as it has, however it is no longer actively supported, so if you run into an issue that requires a bug fix, TS will be unable to provide one.  We can still help with non-bug issues and tips.

Hopefully the documentation has provided you with a jumping off point, and from there it may be best to just run a few trials to see what you can accomplish.

Let us know if there are any specific issues.

Terms & ConditionsCookie settingsAccessibility statement