Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: March 15, 2017, 07:30:24 PM 
Started by Fa - Last post by Derek Read
One more point of clarification, you say "They need this to be included in the htm files that are generated when building their software".

It sounds like this element ends up in the final output, meaning that it does not necessarily need to be in the DITA content itself. I suspect what might have occurred with the older version of the DITA Open Toolkit is that it did not recognize the element as being DITA, and it had some form of bug that caused it to pass this element through to the HTML output unmodified. Either newer versions of the DITA OT have corrected this bug or they are simply validating the document properly (stopping all output).

If that is the case then replacing it with a valid DITA element and then altering the DITA Open Toolkit (its XSLT) so that it inserts <Help_anchor> into the HTML output when it sees that element (and possibly element + specific attribute value) is probably what you would want to do.

I'm not even clear on that point though, because <Help_anchor> doesn't exist as part of any HTML spec that I'm aware of, so adding it to an HTML file would make that HTML invalid as well. Perhaps the HTML is custom as well? And it is being displayed with some custom browser or other software (so not really HTML, but perhaps based on HTML)?

 on: March 15, 2017, 07:24:24 PM 
Started by Derek Read - Last post by Derek Read
This topic has been moved to DITA and XMetaL Discussion.

 on: March 15, 2017, 12:30:53 PM 
Started by ChrisTMH - Last post by Derek Read
I think you should submit everything you have done to XMetaL Support with a good description of where everything needs to be installed. They they can try to set up a similar system to understand what your issue is, what you are trying to solve, and how that might be done. Most of this sounds like something that can be supported. Include a sample XML document that is representative of something that causes issues.

No guarantees, but it is possible that some kind of solution could be created.

The "custom toolbar" has me a bit concerned though as extending the DITA authoring functionality in this way is not something that is supported, but I guess we will know once they see everything.

Perhaps throwing a faster computer at this issue might be the easiest solution for people that need to work with files that have very large tables?

 on: March 15, 2017, 12:12:08 PM 
Started by Fa - Last post by Derek Read
Do you know what the purpose of the element is?
Do the people that are adding it know what it is for?
Are they aware that they are adding an element to the document that is making the document invalid?

By far the simplest solution would be to replace this element with an equivalent valid DITA element.

If you cannot modify the XML so it is valid you could create a specialized DITA DTD. DITA defines something called "specialization". This allows you to create a DTD that defines a select number of elements from the standard DITA DTDs as well as define new elements based on existing DITA elements (effectively performing the same "function" but having a different name). You would need to have someone familiar with creating a specialized DITA DTD do this. Once that is done the process for configuring XMetaL Author Enterprise to recognize that DTD as a DITA DTD is quite simple: you just fill in a couple of fields in a dialog and restart the software. Note that in this case you would still need to modify the XML files to change their PUBLIC id so that they no longer reference the standard DITA DTDs (because they are not standard DITA they are specialized). You would modify the XML's DOCTYPE declaration to use the PUBLIC id for the specialized DITA DTD. For all the information we document about DITA specializations see the Help topic: Working with DITA > DITA Specializations.

Of course any DTD used with XMetaL Author can simply be modified directly to allow any element, but that is a bad idea when working with a standards-based DTD like DITA as you are then creating files that are not compatible with the standard. It is only something you would do if you are in complete control of the DTD (in other words, you created or "own" the DTD, and you can roll out that change to everyone and all tools that need it).

 on: March 15, 2017, 03:01:20 AM 
Started by ChrisTMH - Last post by ChrisTMH
1. Yes
2. Yes that is the main issue
3. We have some topicrefs that are in excess of 600kb, the one I am currently working with has a table that is 500kb in size on it's own. Editing in itself is not slow, however loading the file takes a good fair few minutes. We use DITA.
4. Yes, this is a specialised DITA DTD. Using this function to create a different files containing the chosen elements means that the ditacomponent.dtd is referenced, and as our custom elements are not part of this DTD, they are not recognised. The document is thus always invalid and our custom toolbar is not used - changing the DTD to our specialisation solves this, however we want to save our authoring staff from having to do all of this manually.

 on: March 14, 2017, 06:10:07 PM 
Started by ChrisTMH - Last post by Derek Read
You mention the ditacomponent.dtd so I assume you are authoring DITA content?

Your files are large enough that editing is slow, and you wish to avoid that? That's the main issue?
Files need to be very large (generally) to make editing slow enough to be painful in XMetaL Author Enterprise.
That is even less likely to happen with DITA (since each topic is typically quite small).

You also say you have a custom DTD and customization. Is this a specialized DITA DTD?
If it is a specialized DITA DTD then the Reusable Component feature should work without modification (for authoring and with the DITA Open Toolkit). However, XMetaL Author Enterprise does need to be configured properly to set this up.

For non-DITA documents the Reuse menu and functionality isn't available as it is designed to be used with DITA. So if that is the case I'm not sure how to help.

Or perhaps you want to use files created using ditacomponent.dtd with some other system? In this case (assuming it is a validating XML parser) you should be able to provide it with the ditacomponent.dtd as well.

Or perhaps I'm completely misunderstanding this. I think I need more information or some clarification to help.

 on: March 14, 2017, 05:43:36 PM 
Started by zzz - Last post by Derek Read
At minimum your customization will have these files:



 on: March 14, 2017, 04:02:24 AM 
Started by Fa - Last post by Fa

I usually create all the documentation using XMetaL (using XMetaL 11.0), but for one particular project, my colleagues have created the DITA files (they do not use XMetaL) and they have included an element that XMetaL does not recognize. They need this to be included in the htm files that are generated when building their software, so removing it is not an option.

The element added is <Help_anchor> and has an "anchor" attribute (e.g. <help_anchor anchor="general"></help_anchor>)

I have a few years ago (using XMetaL 6) successfully generated the pdf. Back then, I think the only thing I did was to add an attribute for condition (output="htm", so that would be <help_anchor anchor="general" output="htm"></help_anchor>). XMetaL still would not show the tags on view, but at least it was able to just ignore it when building the pdf. However, this does not seem to work now, even with my old XMetaL. So I must have done something back then that worked, I just don't remember what it was.

Is there any way to just add that element so that it would be recognized by XMetaL? Or is there any other workaround?

Thank you in advance!


 on: March 13, 2017, 02:37:21 AM 
Started by ChrisTMH - Last post by ChrisTMH

XMetaL Author Enterprise version

In order to split some files down into smaller files, to make load time faster, we would like to use the reusable component functionality. The only issue we have is that this creates an XML file that uses the ditacomponent DTD, which means we cannot open the split file and edit it with our custom DTD.

By copying the part of a file we want to split into a new file which we create manually, using our customisation, it is then possible to import this as a reusable component. However, what we want is a user interface similar to the existing "Create Reusable Component", with the only difference being that our DTD is used.

Is it possible to customise this form, or are there any standard functions that we could use in a new form to achieve a similar effect? Or would we have to build this from the ground up?


 on: March 10, 2017, 07:59:08 PM 
Started by zzz - Last post by Derek Read
Something is wrong here. That's not normal behaviour. Not sure what would cause that. These settings are stored in the Windows registry, so if something is blocking those from being written, being read, or altering them (probably deleting them) that would be my best guess.

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