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

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

Thanks,


Bill Burns
Content Architect | Healthwise
bburns@healthwise.org | www.healthwise.org
208.331.6917 (office)  |  208.345.1897 (fax)

 53 
 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" />
  </attribute>

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

 55 
 on: April 26, 2017, 06:18:57 PM 
Started by C4 - Last post by C4
Hi,

Is it possible to write a macro that can select text within two entities?

I am using XMetaL Author Essential 11.

Thanks

 56 
 on: April 26, 2017, 06:06:15 PM 
Started by C4 - Last post by tonys
Maybe because you didn't call rng.Select()?

For efficiency, you should do everything with the Range object, then call the Select() method at the end.

 57 
 on: April 26, 2017, 06:02:51 PM 
Started by billburns - Last post by Derek Read
Screenshots of XMetaL Author Enterprise 9 and 12 showing their respective "Apply / Remove Conditions" dialogs for setting DITA conditional text attributes (default sample attribute values are listed).

 58 
 on: April 26, 2017, 05:55:44 PM 
Started by C4 - Last post by C4
Thanks

I tried both of those and it took me to the beginning of the element.

I've changed my code to this and it seems to work.

var rng=ActiveDocument.Range;
rng.MoveToElement("P",true);
rng.Select();
Selection.SelectAfterNode(Selection.ContainerNode);

 59 
 on: April 26, 2017, 05:32:07 PM 
Started by billburns - Last post by Derek Read
Is this attribute meant to be used like the DITA conditional text attributes @audience, @platform, @product, or @otherprops?

In other words, is the attribute you have specialized based on @props?

If so, you can configure the conditional text feature so that your attribute will work alongside the standard DITA conditional text attributes (listed above). See Help > Creating and modifying conditions (or search for "modifying conditions" or "ct_config.xml").

This enables a "..." button in the Attribute Inspector for conditional text attributes that opens a dialog that lets you select the values you have defined (in the ct_config.xml file). You can also access the same dialog via the Reuse menu by selecting "Apply / Remove Conditions" or by right clicking on any element and selecting "Apply / Remove Conditions". The Reuse menu contains another dialog that lets you configure how elements with specific attributes and values set appear using the "Style Conditional Text" option.

Or perhaps this is not a specialized DITA DTD? It sounds like you might be modifying the DTDs according to the XML specification (if you are creating attributes using NMTOKEN) and not DITA's more specific specialization rules. I guess we'd need to see it to be sure.

 60 
 on: April 26, 2017, 04:42:25 PM 
Started by billburns - Last post by billburns
Sorry, using Author Enterprise version 9.

Bill Burns
Content Architect | Healthwise
bburns@healthwise.org | www.healthwise.org
208.331.6917 (office)  |  208.345.1897 (fax)

Healthwise helps people make better health decisions.

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