Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: May 03, 2017, 12:55:10 PM 
Started by Joddie - Last post by Derek Read
The most likely issue here is the difference in DPI declared in the images (in JPG I think this is called density, might be something else in other image formats if they support it) and what the DITA OT / deliverable used to generate output assumes which might be 72 or 96 or something else (this is then passed on to the PDF engine (RenderX XEP, Antenna House Formatter, or Apache FOP).

If this is working fine for your colleagues running version 11 then it sounds like the easiest thing to do is to upgrade (upgrades are free, check with the sales people). Makes sense for everyone to be running the same version anyway doesn't it? Also, keep in mind that version 8 supports Windows Vista, 7 and 8.0 (not 8.1 or 10) so if you want to upgrade your Windows version you should plan to upgradeanyway.

Why this would be working fine for some people and not others, or with some files and not others (I'm not sure which is the case here) is difficult to say without more information. There are too many possibilities here. If there are differences between the version 11 installs then it would be best to diff the files in the installations of the DITA OT on those computers to see what the differences are. If the difference is just between version 8 and 11 (for the same deliverable type) then that isn't too surprising as the DITA OT versions are different.

If you submit a case to XMetaL Support and provide the following they can look into it in detail:
- Full version number of your XMetaL Author Enterprise install.
- The name of the deliverable you are using to generate the PDF.
- A copy of any input files you are using to generate the output: a map, a topic and an image that reproduces the issue.

 on: May 03, 2017, 04:51:40 AM 
Started by Joddie - Last post by Joddie
Our team is struggling to try and get our pdf outputs to look ok using a combination of XMetal 8 (me) and Xmetal 11 (my colleagues).

All pdfs show outsize images that are spilling off the page. When I check our source control, I see that the writers on the project before had no problems generating pdfs that look ok. I am using the renderer recommended for the project and I cannot generate a good looking pdf, even in cases when I have made no changes to the source at all, but just rendered what was already there.

I googled the problem and I saw some discussion for XMetal 6 talking about making changes to xslt.. but i am uncertain what should be done... Furthermore I do not understand why the out of the box solution was working for other writers and not for us.

Thanks very much!

 on: May 02, 2017, 02:52:58 PM 
Started by C4 - Last post by Derek Read
So, what you really want to find and select is this?

“some text”

Which view do you need to do that in?

 on: May 01, 2017, 09:46:42 PM 
Started by C4 - Last post by C4
What we need to do is find and highlight text between left double quotes “ and right double quotes ” including the quotes. The quotes are marked up as entities.

eg "find and highlight this text" but not this text.


 on: May 01, 2017, 06:43:41 PM 
Started by C4 - Last post by Derek Read
Can you provide a bit more context?
Why specifically two entities? Is there something you need to do with two vs one?

When you say text does that mean the entity reference (something like &entityname; is what you want) or the content defined for that entity?

When you have that (or create a selection of some kind) what do you want to do with that?
What's the end goal?

 on: April 27, 2017, 02:06:49 PM 
Started by billburns - Last post by billburns
That's what I was hoping you'd say.


Bill Burns
Content Architect | Healthwise |
208.331.6917 (office)  |  208.345.1897 (fax)

 on: April 27, 2017, 12:54:23 PM 
Started by billburns - Last post by Derek Read
Just remove their entries from the ct_config.xml file.

 on: April 27, 2017, 12:27:56 PM 
Started by billburns - Last post by billburns
Looks like hit preview on the last try.

Can I suppress the standard profiling attributes? I don't think we're using conditions at all.


Bill Burns
Content Architect | Healthwise |
208.331.6917 (office)  |  208.345.1897 (fax)

 on: April 27, 2017, 12:04:23 PM 
Started by billburns - Last post by Derek Read
Though not designed for this, you could try to piggyback on the standard conditional text feature and configure the dialog so it lets you set your values for this other attribute.

Assuming your attribute is named "foo" you could just add something like this to the ct_config.xml file (and remove or change anything else that you don't want):

 <attribute name="foo" title="foo nice name">
    <value name="myvalue1" title="value (nice name) 1" />
    <value name="myvalue2" title="value (nice name) two" />
    <value name="myvalue3" title="value (nice name) 3" />

 on: April 27, 2017, 08:38:49 AM 
Started by billburns - Last post by billburns
Thanks, Derek. It's actually an @base specialization. If only it were props! I am sort of skirting the rules by changing CDATA to NMTOKEN. We have to control the values in some fashion. If this approach doesn't work, we'd like to build some kind of customization to control them without the constraint in our shells. So in either case, we'll still need a control for multiple value selections.

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