Pages: « 1 2 3 4 5 6 7 8 9 10 »
 71 
 on: June 28, 2017, 07:58:57 AM 
Started by PhilB - Last post by PhilB
I'm new to XMetaL and DITA so please forgive me if I'm not providing enough information or asking a question properly. 

I have a few topics in XMetaL that have large tables in them.  I then have separate topics for each of the rows in the large tables.  Is it possible to reuse a single row from the large table and different topic without just copying the row into the other topic?

 72 
 on: June 28, 2017, 02:59:49 AM 
Started by MarcB - Last post by MarcB
Reverting to
DITA_OT_DIR  =  %XMETAL_SHARED_ALL%\DITA_OT2.0
did the trick.
DITA_OT2.2 returned the same error.

Of 3860 <entry> elements in the document, 3856 had @colname, which is inserted by XMetaL automatically when you edit tables. XMetaL does not insert @colnum on cells.
I think the problem starts when you merge cells (which I did using the XMetaL 12 GUI). Then @colname disappears, @namest and @nameend take over, and the error occurs.
I have 4 cells that do that, thus making up the number.
This phenomenon is also reported in https://github.com/dita-ot/dita-ot/issues/2212

For the moment, I will direct the team to use DITA_OT2.0 in the Other Output Parameters, but the feeling of unease prevails.....

Thanks, Derek.

Marc Beckers
Software AG

 73 
 on: June 26, 2017, 01:29:45 PM 
Started by MarcB - Last post by Derek Read
This sounds a bit like the issues described here:
https://github.com/dita-ot/dita-ot/issues/2212
https://github.com/dita-ot/dita-ot/issues/1715

I'm not sure what the best resolution will be. If you have a table that has an <entry> without @colnum set then I would say adding it might be the easiest solution. Assuming that is the trigger that is the cause for your problem and that it is the same issue. I'm not sure because I can't reproduce the issue.

Or you might try getting XMetaL Author Enterprise 12 to run an older version of the DITA Open Toolkit. But in the tracker above they seem to say that issue affects versions older than 2.2.2, so 2.4 should be OK. If you want to try an older You can do that by changing a parameter in the Other Output Parameters section on the Advanced tab in Tools > Configure Output.

By default XMetaL Author Enterprise 12 is configured to run DITA OT version 2.4 but installs 2.4, 2.2 and 2.0.

To change the version use this parameter:

DITA_OT_DIR  =  %XMETAL_SHARED_ALL%\DITA_OT2.4

Or

DITA_OT_DIR  =  %XMETAL_SHARED_ALL%\DITA_OT2.2

Or

DITA_OT_DIR  =  %XMETAL_SHARED_ALL%\DITA_OT2.0

 74 
 on: June 26, 2017, 04:28:04 AM 
Started by Fa - Last post by Fa
Thank you, Derek.

It worked like a charm!

Best regards,
Fa

 75 
 on: June 26, 2017, 02:12:11 AM 
Started by MarcB - Last post by MarcB
I am on Windows 7 Professional SP 1 and have just upgraded an XMetaL 10.0 installation to version 12. I am testing the installation before asking my team to do the upgrade (40 seats).
The only customization I made in the Advanced Output Configuration was adding the line: "DSDK_PARAM_ditaext = dita" like we had in XMetaL 10.0.

When I attempt to Generate Output for DITA Map or DITA Topic, I get an error. This was working in XMetaL 10.0 fine. This is what I see in the extended log:

Input file: C:\Users\mbe\Documents\fbl_stuff\documentation\SVN_VA\svn\sag\doc\sources\en\general\trunk\x_global_reuse\re-product_names.dita
Output file: C:\Users\mbe\Documents\fbl_stuff\documentation\SVN_VA\svn\sag\doc\sources\en\general\trunk\x_global_reuse\multiple_html_out\re-product_names_new.html
  DITA-OT Path: C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.4
  Transtype: xhtml
Transformation: Multiple HTML files
Parameters:
   DSDK_PARAM_indexshow = no
   DSDK_PARAM_artlbl = no
   DSDK_PARAM_draft = no
   cmd_default_config_topic = DITA15_1B9FF196523E459683C958FA9E31EEEE;C:\PROGRA~2\XMETAL~2.0\Author\DITA\XACs\shared\RENDIT~1\print_dita20.xml;0C41D0FDB1A24CE9B3FA702F1A85C0C5;C:\Users\mbe\AppData\Roaming\SoftQuad\XMetaL\12.0\print_local.xml; ;C:\Users\mbe\Documents\fbl_stuff\documentation\SVN_VA\svn\sag\doc\sources\en\general\trunk\x_global_reuse\multiple_html_out\re-product_names_new.html;C:\Users\mbe\Documents\fbl_stuff\documentation\SVN_VA\svn\sag\doc\sources\en\general\trunk\x_global_reuse\re-product_names.dita;
   DITA_OT_DIR = %XMETAL_SHARED_ALL%\DITA_OT2.4
   __DITA_OT_DIR = %XMETAL_SHARED_ALL%\DITA_OT2.2
   ANT_PARAM_args.xmfo.java_maxmemory = 1024m
   ANT_OPTS = "-Xmx1024m"
   run_plugin_integrator = no
   cmd_always_open_log = no
   cmd_fs_sandboxing = no
   cmd_cms_sandboxing = yes
   cmd_dita_ot_per_user_version = disable
   _rem_cmd_synchro_mode = 2
   DSDK_PARAM_ditaext = dita
   cmd_open_with = system_default
   DSDK_PARAM_OUTEXT = html
Log path: C:\Users\mbe\AppData\Local\Temp\XMetaL\renditions\log\log.txt
 
  ↓    call ant dita2xhtml -d -Dargs.input="c:/users/mbe/documents/fbl_stuff/documentation/svn_va/svn/sag/doc/sources/en/general/trunk/x_global_reuse/re-product_names.dita" -Doutput.dir="C:\Users\mbe\Documents\fbl_stuff\documentation\SVN_VA\svn\sag\doc\sources\en\general\trunk\x_global_reuse\multiple_html_out" -Dtranstype=xhtml -Ddita.temp.dir=C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.4\temp -Ddita.dir=C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT2.4 -Dgenerate.copy.outer="3" -Dargs.xmfo.java_maxmemory=1024m -Dargs.logdir=C:\Users\mbe\AppData\Local\Temp\XMetaL\RENDIT~1\log -Dargs.indexshow=no -Dargs.artlbl=no -Dargs.draft=no -Dargs.filter=C:\Users\mbe\DOCUME~1\FBL_ST~1\DOCUME~1\SVN_VA\svn\sag\doc\sources\en\general\trunk\X_GLOB~1\MULTIP~1\re-product_names.ditaval -Ddita.ext=.dita
  ↓    BUILD FAILED
Errors summary (22):  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  Caused by: net.sf.saxon.trans.XPathException: An empty sequence is not allowed as the value of variable $colspec
  ↓  The system cannot find the file specified.


Any ideas?

Thanks,
Marc Beckers
Software AG

 76 
 on: June 23, 2017, 01:46:39 PM 
Started by kroan - Last post by Derek Read
I think your best hope for a resolution for this is through SDL's support team. They would need details describing how to reproduce the issue though.

They might know about it, they might already have a fix, or they might be able to help you configure your setup so it does not occur. SDL performs all testing of their bridge for XMetaL Author Enterprise. If the issue is reproducible then they should either be able to resolve it (in their code or through configuration) or they should be able to create a test case for the XMetaL development team to use to resolve it (if it turns out to be an issue with XMetaL Author Enterprise).

XMetaL Author Enterprise version 9 is three versions behind the current release though, so if the issue turns out to be an XMetaL problem, and not the SDL bridge, a fix would be unlikely for XMetaL Author Enterprise version 9. It would probably be addressed in a patch for version 12 (the current release) or the next version.

 77 
 on: June 23, 2017, 12:52:04 PM 
Started by kroan - Last post by kroan
Occasionally, XMetal becomes unresponsive and then crashes. Because it is occasional, I have not been able to pinpoint specific actions that cause it. The last time this happened, the system reported a Visual C++ Runtime Library error. 

Are there known conflicts with other C++ applications? Has anyone else seen this behavior? Is there a file where logging details are captured where I might be able to see more information?

To my knowledge, I am the only person in my organization that is experiencing these crashes.

I am running
  • XMetaL version 9.0.0.53
  • SDL LiveContect Architect 2014 author bridge
  • SDL publication Manager 11.1 (for LCA 2014)

 78 
 on: June 22, 2017, 05:23:22 PM 
Started by akheiljain - Last post by Derek Read
I'm not sure what the exact final goal is but perhaps one of these posts that include some example code will help?

http://forums.xmetal.com/index.php/topic,512
http://forums.xmetal.com/index.php/topic,514

 79 
 on: June 22, 2017, 05:18:03 PM 
Started by Fa - Last post by Derek Read
In the current release (12) you can modify the ct_config.xml file directly (as you have done) or you can use the new UI for that (Tools > Configure Conditional Text).

However, you also need to use Tools > Style Conditional Text. I think in previous releases that was not necessary but in version 12 it is. Once you do that (make at least one change) everything should work everywhere.

 80 
 on: June 22, 2017, 03:49:19 PM 
Started by akheiljain - Last post by tonys
This topic might also be relevant: http://forums.xmetal.com/index.php/topic,3706.0.html

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