Skip to main content
Legend
March 7, 2014
Question

font changes in <ph>

  • March 7, 2014
  • 2 replies
  • 366 views

I've prepared some DITA concepts outside FM. In these concepts, the name of the product is hauled in as a reference; the <ph> in the source files carefully reproduces the (naughty word ahead) formatting required by the product manager, namely <ph>productName <i>model</i></ph>.

How do I tweak my EDD so that <i> is seen as permissible content for <ph>? At the moment, my <ph> definition has got as far as

Element (Container): ph
   General rule:    <TEXT>
   Text format rules
      In all contexts.
         Text range.

Or is there some other mechanism I could be using?

Thanks in advance for hints and tips.

This topic has been closed for replies.

2 replies

ScottPrentice
Inspiring
March 7, 2014

Hi Niels...

Your best bet is to refer to the existing DITA EDDs that ship with Frame. These will provide the full model and you can copy just the bits you want.

Fundamentally, all you'd need to do is to make sure the <i> element definition is included in the EDD and change your <ph> general rule to ..

General rule: (<TEXT> | i )*

Cheers,

...scott

Legend
March 10, 2014

Hi Scott –

General rule: (<TEXT> | i )*

looks plausible :-} I'll give it a try as soon as my desk is clear.

I admire – who could fail to – the completeness and complexity of the DITA EDDs, but find them a Nasmyth steam hammer for my current documentation peanut: powerful, impressive, hard to drive <g> Still, while I'm not sure whether I'm ever going to switch to FM as my DITA authoring tool, the EDDs are a great place to learn from.

N

Smith_SK
Known Participant
March 7, 2014

Hello Niels.

<i> is part of the <ph> content model:

Element (Container): ph

     General rule: (<TEXT> | boolean | cite | keyword | apiname | option | parmname |

     cmdname | msgnum | varname | wintitle | ph | b | i | sup | sub | tt | u | codeph |

     synph | filepath | msgph | systemoutput | userinput | menucascade | uicontrol |

     q | term | abbreviated-form | tm | fm-xref | xref | state | data | data-about |

     foreign | unknown | image | draft-comment | fn | indextermref | indexterm |

     required-cleanup | text)*

You can go the the OASIS site and get the spec.

Hope that helps,

Stan