OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita-comment] Public Comment


Hi Hedley,

The <ph> element provides what you're looking for, and is the ancestor of 
the elements you mention.

Michael Priestley
mpriestl@ca.ibm.com



comment-form@oasis-open.org 
03/21/2005 07:54 PM
Please respond to
hedley.finger


To
dita-comment@lists.oasis-open.org
cc

Subject
[dita-comment] Public Comment






Comment from: hedley.finger@myob.com

In the framemaker-dita forum and elsewhere I have expressed how important 
conditional content is to MYOB, and previously suggested some method of 
allowing unlimited additional condition attributes and values in the 
%select-attrs; attributes, instead of trying to cram all additional 
conditions into otherprops.
After scanning the DITA Language Reference v. 1.0, I cannot see any 
element that can be applied like <b> or <u> but has no formatting 
implications. I am thinking of something like the ubiquitous <span> 
element in HTML.
You need a vanilla, non-formatting inline element like this when you need 
to apply conditions to a an arbitrary text range within another element 
such as <p>.  Quite often conditions are applied to alternative forms of 
expression within a sentence, e.g. one condition refers to a singular 
situation while another refers to a plural situation, and noun, 
possessive, and verb forms need to agree.
In fact, a <span> element should be the ancestor of <b>, <u>, <tt>, etc. 
so it can be specialised to other inline text formatting if necessary in a 
custom DTD, e.g. <o> = overline.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]