Pages: « 1 2 3 4 5 6 7 8 9 10 »
 11 
 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.

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

yourschemafile.dtd
yourschemafile.ctm
yourschemafile.css

Or:
yourschemafile.xsd
yourschemafile.ctm
yourschemafile.css

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

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!

Fa

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

XMetaL Author Enterprise version 10.0.0.074

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?

Thanks.

 15 
 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.

 16 
 on: March 10, 2017, 05:29:41 PM 
Started by zzz - Last post by zzz
Another really simple question: every time I open XMetal, why are the topbar File menu and icon groups always on 4 different rows.  It's like the program can't remember the layout of the toolbars on the top section.  This is version 10.  Word 95 could do this.  What gives?

 17 
 on: March 10, 2017, 05:10:37 PM 
Started by zzz - Last post by zzz
I appreciate your reply!  If you happen to know the css filename that would be edited, that'd be nice so I could just do it myself rather than go through administrators.

 18 
 on: March 10, 2017, 12:40:31 PM 
Started by Verner - Last post by Derek Read
Your screenshot shows something external to the XMetaL Author Enterprise UI that would be provided by SDL. If you must use it to create DITA conrefs you will have to deal with whatever requirements or limitations that system has.

I'm not sure why you would be forced to use Plain Text view but presumably that means SDL is disabling or modifying the built-in functions provided for conrefs (and perhaps other things) on the Reuse menu or that their system has additional requirements or limitations from the standard DITA markup. I can think of no reason that you could not still use the Attribute Inspector however. You can modify @id and @conref values there as well. Perhaps it seems easier to use Plain Text view as you are happy editing XML markup directly.

I would urge you to check with SDL to see if their system has done this for a reason. If these limitations are put there on purpose then bypassing them by creating DITA conref markup via other means (Plain Text or whatever) may not be a good thing for the SDL system. It is also possible that their system can handle DITA conrefs but that if you use them then you cannot take advantage of some other feature that SDL provides that is incompatible.

It would also be good to check with them in case these are limitations so that they are aware of them and can addess them in a future release, or in case they have already addressed them in a version of their software that is compatible with the current release of XMetaL Author Enterprise (currently version 11 and soon to be 12).

 19 
 on: March 08, 2017, 04:26:15 AM 
Started by Verner - Last post by Verner
It turns out that I can only do this in plain text mode.

If I use "Insert Element with Content Reference" I can only insert the entire table.
See the attachment. SDL does not seem to support this for XMETAL.

 20 
 on: March 06, 2017, 07:14:39 PM 
Started by Verner - Last post by Derek Read
Is this in reference to DITA documents? If not, ignore the following (we will then also need more detail).

I'm not sure about the requirements that come from the SDL side, but XMetaL Author Enterprise 9.0.0.053 does allow you to do this. The resulting DITA is valid so if there is some additional requirement coming from the SDL side that would not allow this I'm not sure what that would be. I think SDL has their own non-DITA method of reuse, so that might be in conflict somehow. Hopefully they can give you more detail.

If the row you want to conref to (the target) has an @id set on it you can select "Insert Element with Content Reference" from the Reuse menu and you will see that id value listed. I am attaching a screenshot of what you should see as the end result.
In this case:
a) The first row in the table has an @id set on the row element.
b) The last row in the table has @conref set to point to that id value. This was inserted using "Insert Element with Content Reference" and selecting the @id for the row listed in that dialog. As with any other conref it is displayed with a grey background indicating that its content cannot be modified directly.

In this example both the conref target and source are in the same file. This is only to make a single screenshot possible for this forum post. As with any other DITA conref the target and source can be in different files.

If you update the content in the first row of this table then select "Refresh References" (F11) the last row will update to match. The "Show Local Content" and other options related to conref and reuse are all applicable as well.

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