Abdelrazak Younes <[EMAIL PROTECTED]> writes: > If you mean an unified interface for Paragraph then I'd agree. The > Range template I am talking about would be private to Paragraph. Then, > if we could have: > > CharAttributes Paragraph::getAttributes(pos_type) > > that will replace Paragraph::getFont(pos_type) and that will provide > all attributes in one go by looking up and gathering relevant Font, > Language and Change Tracking information.
This (getting attributes at _one_ point) is much less useful and does not gain anything. I was thinking about a nice way of accessing ranges from the paragraph api. JMarc
