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

 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?

 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.

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

 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.

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

 on: March 06, 2017, 06:24:45 PM 
Started by zzz - Last post by Derek Read
This is controlled by the CSS file associated with your DTD or XSD. Have the people that created your CSS file modify it so that it uses a larger font size for any elements you want to be larger. If all of the font sizes in the CSS are declared using relative font sizes then this change is easy to make as you just need to change the font size for an ancestor of those elements (usually the document's root element).

 on: March 06, 2017, 06:22:55 PM 
Started by 55 - Last post by Derek Read
The bulk of what was set in really old versions of the XMetaL INI files were default values and also included some documentation about the settings. At some point, probably around 3 or 4 it was decided that this was  encouraging end users to make changes and we had a number of admins (people setting up systems that included XMetaL) that were seeing people change things that would break the way things needed to be set up. So the file now contains (mostly and hopefully) only settings that override some default value and the documentation was moved into the Configuration Guide included with XMetaL Developer.

 on: March 06, 2017, 06:15:24 PM 
Started by 55 - Last post by Derek Read
I see. It sounds like I completely misunderstood your issue. Probably best to disregard my previous message (I still don't really know what the problem is or was). If you have resolved it then I guess that's good enough.

 on: March 06, 2017, 09:03:26 AM 
Started by Verner - Last post by Verner
We are using XMETAL and SDL Publication manager 11.1.1.
I would like to conref table rows. I can only conref a whole table. Our system manager tells me that this does not work with XMETAL.
is this correct? Will it work with a newer version of XMETAL?

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