Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: February 23, 2017, 03:07:45 AM 
Started by nouspoetikos - Last post by Fa
I also have a very similar issue (in XMetaL 11 too).

I have created a small DITA map with a few topics that I keep always in the same location (a drive on our intranet, mapped on my computer). This DITA map (let's call it ComRef, for common references) will then be included in all my manuals (indented or embedded or however you want to call it in my manual DITA maps). The idea, since this is general information, is that if there is something to be updated, we correct it once here, and then any manual we generate subsequently will get the updated info.

Then I have created a template for my manuals. This template is a DITA map with several topics, and in it I have embedded the ConRef map (well, a link to it). The idea is that I can take that template and copy it anywhere on my local machine or network and it would work. This means I should be working with absolute paths, where by default XMetaL creates a relative path to the ConRef map (is there any way to change that?).

Unfortunately this ConRef map is not rendered in the pdf output. The only thing that works is if the embedded ConRef map is in the same folder or a subfolder of where my template map is, which defeats the purpose.

What I have tried unsuccessfully:

- Change the ConRef map path from relative to absolute.
- Change the reference to the map to topicref instead of mapref (XMetaL 6.0 created a topicref for embedded maps, so I gave it a shot)

I have tested this with my old XMetaL 6.0, and there there was no issue. The output pdf is created without problem and has the embedded ConRef map material in it.

I now finally seem to have solved it (partially). The trick was to work my way through the path of both maps and renaming everything so as not to have any space (in the folder names but also in the map names). At least this worked with a relative path, I still have to test with an absolute path. But this is very unpractical! I have thousands of folders, so I cannot obviously be expected to rename them all.

Anyway, hope this will help you and maybe put you on the right track to solve your own issue...


 on: February 21, 2017, 02:21:49 PM 
Started by rakesh - Last post by Derek Read
If the CMS you are using is listed in the following posting contact the CMS vendor as they provide the connector *,608.0.html

If you are using Documentum contact the XMetaL sales team and inquire about XMetaL Author Enterprise for Documentum Webtop.

If you are using Sharepoint contact the XMetaL sales team and inquire about XMetaL Author Enterprise - SP Edition.

If you want to build a connector to allow XMetaL Author Enterprise to interact with your own company's CMS (something not listed above) please contact the XMetaL sales team. An SDK is available to partners. Keep in mind that this is usually a significant undertaking that takes most partners between 3 to 6 man-months to code and test and can require ongoing development and testing if CMS functionality changes (the XMetaL connector APIs are generally guaranteed to remain stable).

* Connector is our term for the code added to XMetaL Author Enterprise that uses XMetaL's "connector SDK" to extend the relevant portions of XMetaL's UI so they can properly communicate with the CMS. Similar terms used for this are "bridge" and "integration".

 on: February 21, 2017, 02:10:28 AM 
Started by rakesh - Last post by rakesh

Please advice how to connect Xmetal with a CMS or Database. I want to connect Xmetal with CMS and open the xml document from there. I also want to make changes in xml document and able to save the updated xml document back to the CMS / database.


How do I create a Pane within xmetal that display the file name (fetched from CMA/Database) and when user click the file name the file will open in xmetal. After making changes I stored back the file to CMS/database


 on: February 21, 2017, 02:04:17 AM 
Started by rakesh - Last post by rakesh
Many thanks for your reply, Yes you are correct we have online dtd reference in our xml document. We have corrected the reference and now it is working fine.

 on: February 16, 2017, 06:49:32 AM 
Started by nouspoetikos - Last post by nouspoetikos

When a file contains a link or xref to a dita source file located on another machine, for example:
<xref href=file://lw5mlpdsy/WS/RELEASE_DOC/R420/BSFDOCEN/AadDoc/AadUserResources.doc/src/testfile.xml format="dita" scope="local"></xref>

The xref or link is not resolved in the published output.
Is there a specific syntax we can use to work around this problem or is this simply no longer supported by the toolkit?

This problem concerns XMetaL 11.
In the previous version of XMetaL we used (XMetaL 7) this problem did not exist.

Here's the error output we get in the log:

[topicpull] Transforming into C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.2\temp
[topicpull] Loading stylesheet C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.2\xsl\preprocess\topicpull.xsl
[topicpull] Processing C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.2\temp\testfile.xml
[topicpull] Recoverable error on line 597 of topicpullImpl.xsl:
[topicpull]   FODC0002:
[topicpull]   C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.2\temp\WS\RELEASE_DOC\R420\BSFDOCEN\AadDoc\AadUserResources.doc\src\testfile.xml (The system cannot find the path specified)
[topicpull] file:/E:/tmp/testfile.xml:11:31: [DOTX031E][ERROR]: The file file:/C:/PROGRA~3/SoftQuad/XMetaL/Shared/DITA_OT2.2/temp/WS/RELEASE_DOC/R420/BSFDOCEN/AadDoc/AadUserResources.doc/src/testfile.xml is not available to resolve link information.
[topicpull] Recoverable error on line 675 of topicpullImpl.xsl:
[topicpull]   FODC0002:
[topicpull]   C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.2\temp\WS\RELEASE_DOC\R420\BSFDOCEN\AadDoc\AadUserResources.doc\src\testfile.xml (The system cannot find the path specified)
[topicpull] Recoverable error on line 1102 of topicpullImpl.xsl:
[topicpull]   FODC0002:
[topicpull]   C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.2\temp\WS\RELEASE_DOC\R420\BSFDOCEN\AadDoc\AadUserResources.doc\src\testfile.xml (The system cannot find the path specified)
[topicpull] Recoverable error on line 1828 of topicpullImpl.xsl:
[topicpull]   FODC0002:
[topicpull]   C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.2\temp\WS\RELEASE_DOC\R420\BSFDOCEN\AadDoc\AadUserResources.doc\src\testfile.xml (The system cannot find the path specified)


 on: January 20, 2017, 10:34:59 AM 
Started by huntley - Last post by lxsibi
We had two issues with * Registration failed - *could not connect to* licensing server

1) This message appeared not during registration, but when opening an XML file from our content management system which we have been editing files in XMetaL for awhile.

We resolved it by re-installing XMetaL. Should this happen again, what would be a better solution than re-installing?

2) We have translators residing in Japan who are trying to register their XMetaL license. Could you provide instructions how to update the settings in IE?

Thank you.

 on: January 19, 2017, 10:57:27 AM 
Started by huntley - Last post by huntley
Hi Paul,

If you don't mind, I would like to take a look at your workaround for the Windows security update. I think you know my email address :-)

As far as I know, we aren't using a proxy server but I can check the user's settings to verify.

Several U.S-based users haven't had any issue with the licensing server so I suppose it could be locale-based.


 on: January 19, 2017, 10:02:22 AM 
Started by huntley - Last post by pmasal
XMetaL Support helped McAfee with this issue, which is fixed in XMetaL9+ (our situation is likely similar to yours - we plan to upgrade soon, but can't right now). We were seeing one or both of the following during XMetaL8 installs:

 * Registration failed - *request refused by* licensing server.
    This was an issue with recent Windows security updates preventing the install program from running one or more licensing web services.
    A temporary workaround allows the install program to circumvent those security updates (applies only to the install, then things can go back to normal).  I can send the procedure to you offline, if you like.

 * Registration failed - *could not connect to* licensing server.
    This was an issue with Windows proxy settings, which was fixed by updating those settings in IE Tools | Internet Options.
Hope this helps...
Paul Masalsky

 on: January 19, 2017, 09:23:11 AM 
Started by huntley - Last post by huntley
Version: XMetaL Author Enterprise

We have a user who is trying to register a new install of XMetaL but he is receiving an error when registering the license. When he tries to register his system, he receives an error that the license server cannot be reached.

I checked the license file and it looks valid, though the connection error makes me think it is getting to the point where it validates the license.

I have two questions:
- The license server is still running at I know XMetaL 8 is long in the tooth.

- Is there a way to verify that the license server is reachable from his location? He is overseas.


 on: January 06, 2017, 01:16:09 PM 
Started by jrob61 - Last post by jrob61
we are looking into the possibility that our .ctm file may be the culprit?

Pages: « 1 2 3 4 5 6 7 8 9 10 »
email us