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

 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)

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

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

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

 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?

 on: February 28, 2017, 10:57:10 PM 
Started by 55 - Last post by 55

We are trialing XMetal Authoring 11.0 and trying to get the external entities to show an 'icons' in Tags on View.

When we insert the entity, the icon shows as it should, but if we switch from Tags on View to any other view (and then back to Tags on View), the icon disappears and the actual character shows up instead.

Is this a bug or intentional?

 on: February 27, 2017, 07:04:13 PM 
Started by nouspoetikos - Last post by Derek Read
Referencing files outside the folder of the map file is not something the DITA Open Toolkit has really supported. You may wish to follow this discussion:

However, you might try using the DITA OT parameter "generate.copy.outer" documented here:

That parameter can be set using Tools > Configure Output on the Advanced tab by adding the following into the "Other output parameters" section:

ANT_PARAM_generate.copy.outer  =  3

That should help in the case where your file is outside the folder structure of the map, but not in the case where it is on another computer.

If that parameter does not help then the version of the DITA OT being run may have some issues.
By default the version of the DITA OT that is run with XMetaL Author Enterprise 11 is DITA OT 2.4, however, version 2.2 is also installed. You can change the DITA OT version to 2.2 by swapping the underscores between these two settings:


As far as I know there are no parameters supported by the DITA OT itself that allow you to reference files on another computer and have that content be parsed as an input file to the DITA OT (map or topic).

However, if you are generating output to PDF or some other file format  that results in a single file (CHM maybe) then you might try the XMetaL Author Enterprise setting "cmd_fs_sandboxing  =  yes". This setting was created specifically to support the Japanese edition of XMetaL Author Enterprise but may help in other situations. Most Japanese authors name their files using Japanese characters (of course) but the DITA OT generally cannot handle non-alphanumeric file names. This setting creates a copy of all referenced files (this is the part that would help with your files on the server), renames them using alphanumeric characters (in order to get around the Japanese language issue), and adjusts all links to point to the new file names. You can set this in Tools > Configure Output on the Advanced tab inside the "Other output parameters" section:
cmd_fs_sandboxing  =  yes

If you are generating output to an HTML-based format then having files outside the map's directory structure might make sense, but for most people I don't think it does. References to files outside the map's directory structure are usually to existing files that are not expected to be copied or moved. Regardless, when you reference a file in a folder that is outside the map's folder structure but on the same drive then the DITA OT can create an additional folder for that file (see the setting ANT_PARAM_generate.copy.outer above). However, in cases where a file is located on a different drive or a different computer the behaviour is undefined. The cmd_fs_sandboxing parameter can help because it effectively flattens the entire folder structure, but that may not be wanted because it also renames files. That's necessary because of the folder flattening, and is probably a minor issue unless your readers use the file names to navigate.

The best solution, probably for all possible cases, is to store, edit and generate output from local files. In cases where you wish to share or store files centrally you can have them delivered locally by a CMS or some other system before asking the DITA OT to do anything with them to avoid limitations with the DITA OT.

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