Hi,
So you are referring to the
othermeta DITA element:
http://docs.oasis-open.org/dita/v1.2/os ... #othermeta
Basically you have a couple of elegant ways and a hack (the hack being easier to implement).
1) Oxygen looks in the associated DTDs for such possible attribute values so if you would create a DITA specialization which would allow for the
@content attribute a set of certain values, then Oxygen would propose them in the Attributes view.
2) You could use our Java Author SDK:
http://www.oxygenxml.com/oxygen_sdk.htm ... horing_SDK
and implement a
ro.sync.contentcompletion.xml.SchemaManagerFilter interface which would allow you to provide extra values for the
@attribute
3) You could create code templates in the Oxygen Preferences->
Editor / Templates / Code Templates page for each
<othermeta> element which you usually insert. Such code templates would then be available in the content completion window both in the Text and Author pages.
4) The hack would be to go to the Oxygen Preferences->
Editor / Edit modes / Author / Profiling/Conditional Text and in the list of profiling attributes add a new entry matching
DITA*, specifying
content as the attribute name and a set of allowed values.
The list was not intended for this but the content completion in the Attributes View would propose these values when editing the specific attribute.
Regards,
Radu