Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: September 20, 2017, 01:16:26 AM 
Started by Fa - Last post by Fa

I am having a very hard time figuring out how to deal with fonts. From my previous experience on XMetaL 6 with DITA-OT 1.3, it was quite straightforward: you would set the font in e.g. commons-attr.xsl to logical font (e.g. Serif), then you would tell in font-mappings what that logical font corresponds to (according to the language, if not specified it reverts to default), e.g. default is "DefaultFont", Simplified Chinese is "CNFont", etc. and then in XEP you would give the font data.

E.g. if I wanted DefaultFont to be Arial, then

      <font-family name="Arial">
          <font-data ttf="BAUHS93.TTF"/>
        <font style="oblique">
          <font-data ttf="ariali.ttf"/>
        <font weight="bold">
          <font-data ttf="arialbd.ttf"/>
        <font weight="bold" style="oblique">
          <font-data ttf="arialbi.ttf"/>

And then when the text was translated into Chinese, and I wanted CNFont to be e.g. SimSun, I'd have

      <font-family name="CNFont" embed="true">
        <font><font-data ttc="Simsun.ttc"/></font>

But I find that much has changed between 1.3 and 2.4, and there has probably has been much development in RenderX as well.

So I guess my first question is: does it still work like this (it doesn't seem so), and if it doesn't, what has changed?

And before I go any further, I also want to make sure that my plugin uses RenderX. I was under the impression that that was the default renderer that XMetaL uses, but I am not sure. Is it? If it is not, where do I set the renderer to be RenderX? (Or alternatively, how do I solve my problem using FOP?)

I have tried modifying the font data in the xep.xml file, but it doesn't seem to have any effect on my plugin output, not even on the English. However, changing the base-font in, e.g. common-attrs lets me choose the font I want for the pdf content, and the same goes for toc-attrs to select fonts for the TOC, etc.

Any hint is welcome!

Thank you!

 on: September 19, 2017, 04:26:21 PM 
Started by scott44 - Last post by Derek Read
I think the issue is that your customization is set up for the old way of doing things, which uses CSS only (and possibly complicated by the fact that the main element is named Table, which is fine, but without any additional settings the software is probably guessing if this is supposed to be HTML, CALS, other, and then maybe partially working but ultimately failing to figure it out).

If you add the following to your CTM file things should behave properly, and the new table editing behaviours will be enabled for your custom table type, including the functions in the Tables menu (that apply) and the Table Properties dialog (with functions that aren't relevant being disabled).

    <CustomTable useFindInsertLocation="true">

The <Tables> section should be made a sibling of the <ElementPropertiesList>, <Templates>, <ChangeLists>,  <OCXReplacements>, and <Images> sections in the CTM file.

 on: September 19, 2017, 11:13:58 AM 
Started by scott44 - Last post by scott44
Thank you for the post, Derek.

While waiting to see if I can upload our XSD (it is "owned" by another group), I will add a bit of information to my previous post.

I noticed that a table is properly rendered in Normal and Tags-on views immediately after the table is inserted in the document. I can switch between the Normal and Tags-on views with no effect on the table. However, as soon as I switch to Plain Text view (or close and re-open the document), the table is no longer rendered.  I attached a picture with some excerpts to illustrate.

Many thanks.

 on: September 18, 2017, 01:56:27 PM 
Started by rhastah - Last post by Derek Read
Yes, we've considered making this a first class feature. However, the number of different requests we have received with specific requirements for such a feature has made it difficult to create something that we feel would work for everyone. Maybe one day.

However, you might consider adding this macro, or making modifications to it and adding your own modified version:,26.0.html

It was written specifically for the DITA authoring functionality, but should work for most other customizations depending on the functionality they have included in their own MCR files associated with the DTD or XSD. This could potentially also conflict with application-level customizations (application-level MCR files). If so, you would likely want to incorporate these few lines of script into those customizations and make them compatible.

 on: September 18, 2017, 12:36:38 PM 
Started by rhastah - Last post by rhastah
Thank you for your reply. I will try using the Plain Text view. I've also been encouraged to use Notepad++ or similar to strip the formatting and then paste again. That works too, but it's an extra step.

The situation is sometimes a writer receives source materials in PDF, Word, or some other format and just wants to paste the text into a paragraph, edit/rewrite it, and then re-format it in DITA. The formatting that the Word file or PDF includes is irrelevant, as the writer may want to completely rearrange or rewrite the original text to conform to DITA conventions.

Maybe this could go into feature requests... Just a simple button combination, if ctrl+v is already used, maybe ctrl+shift+v?

 on: September 14, 2017, 02:22:54 PM 
Started by Mythri - Last post by Derek Read
In order for these options to be enabled a "connector" has to be installed that supports "XMetaL Connector". XMetaL Connector is one of the customization layers built into the software and has an SDK (this is basically just documentation that describes the XMetaL Connector APIs and provides a very simple sample connector). We provide this to our partners to allow them to integrate code into XMetaL Author Enterprise that allows it to interact and communicate with a CMS (the code they build is the "connector"). See the list here:,608.0.html

There is no connector for SVN as far as I know (if someone has built one they have not shared it publicly). XMetaL Connector is really designed to be used with a CMS and exposes features common to most CMS systems, so features that you might use with a source control system like SVN would require additional to expose them in the XMetaL UI (SVN's merging functionality might be one example). Features that overlap with a CMS could of course be implemented if they make sense (check in, check out, file locking, etc).

Having said that, you might look at this:,1331.0.html

 on: September 14, 2017, 04:26:22 AM 
Started by Mythri - Last post by Mythri

When working on XMetal Author Enterprise 10.0, the options in the Repository tab are disabled. I would like to understand about this feature as I am looking at connecting XMetal to SVN so that I can checkin and checkout files directly from SVN.


 on: September 11, 2017, 12:59:25 PM 
Started by bjorn - Last post by Derek Read
You might also look at DeltaXML's solution. It integrates with XMetaL Author and various other XML editors, as well as tools that are not dedicated XML editors and also content management systems (I believe). At least two of JustSystems' partners have experience with both DeltaXML and the XMetaL line of products (Sollan and Ovidius).

 on: September 11, 2017, 02:54:00 AM 
Started by bjorn - Last post by bjorn

What are your recommendations regarding integrating compare tools for 2 or 3 XML documents within XMetaL.
An integrated merge functionality may also be of interest.

I have had a glance on Altova DiffDog GUI and that functionality looks about appropriate.


 on: September 08, 2017, 12:43:58 PM 
Started by scott44 - Last post by Derek Read
Yes, things have changed in order to better support arbitrary table models. Anything that is not CALS and not HTML (which are both supported natively and automatically) can now be both rendered and edited as a table. Previously such tables could only be rendered while none of the fancy table editing functions available for CALS and HTML were available.

Any group of nested elements at three levels (parent/child/grandchild = table/row/cell) could always be rendered as a table (using CSS) but the Table Properties dialog and the table editing functions in the Table menu and Table toolbar would do nothing. You can now identify such tables using a "Treat As Table" setting in the CTM file and that will enable this functionality.

Having said all of that, any existing table model that follows the CALS or HTML table specs should "just work" as it always has. We would need to see your DTD / XSD and a sample XML file to let you know why it isn't working in your case. The feature has likely not been tested by that many clients so I wouldn't be surprised if you've turned up an issue.

If your table model isn't CALS or HTML then we would also want to see a copy of the DTD / XSD and a sample XML file so we could let you know what needs to be set in the CSS & CTM to enable both the display and editing capabilities.

Please submit any files through XMetaL Support.

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