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

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

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

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

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

 76 
 on: March 06, 2017, 09:03:26 AM 
Started by Verner - Last post by Verner
Hi
We are using XMETAL 9.0.0.053 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?

 77 
 on: March 03, 2017, 10:18:20 PM 
Started by zzz - Last post by zzz
A lot of the text in Normal View is too small to easily read.  Is there any way to zoom in?  The XMetal options let you change the Plain Text View font size, but why not Normal View?  (I'm using XMetal 10)

 78 
 on: March 02, 2017, 08:37:29 PM 
Started by 55 - Last post by 55
Hi,

We are moving from XMetal 2.1 to Xmetal Authoring 11 (I know, a huge leap) and the Xmetal.ini file is only 15 lines long.

I can't find much information on where all the settings have gone (that were in the Xmetal21.ini file). The only other .ini file is in the \user\appdata folder - are the settings hidden elsewhere?
I'm not looking for a specific setting - we are just wondering where the bulk of the old 2.1 ini file has gone.

Thank you again :)

 79 
 on: March 02, 2017, 08:33:57 PM 
Started by 55 - Last post by 55
Actually, we have resolved it by disabling the character map - now the icons stay put :)

 80 
 on: March 01, 2017, 06:57:58 PM 
Started by 55 - Last post by Derek Read
This is intentional if your entity is a numeric character entity reference.

In addition, when you save the document, if the character entity reference has a defined value in the encoding used for the document (by default this is UTF-8 for XML documents) then the character will be saved, not the entity reference. This conversion is automatically applied.

What is your ultimate goal?

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