Next: Set up Active Contents handling Previous: Usual startup operations Contents: Contents |
Every converter supports a set of tags, but users can process the same sources by several converters which support different tags, so a source to be read by your converter may contain tags you did not think of. Fortunately this can be easily handled by implementing option -tagset
and the following statement.
# import tags PerlPoint::Tags::addTagSets(@{$options{tagset}}) if exists $options{tagset}; |
PerlPoint::Tags::addTagSets()
extends the converters tag definitions by loading foreign definition files. To make this intuitive, users have to pass target formats to -tagset
, e.g. HTML
.
If a document was initially written to be processed by pp2html and is now passed to your converter, a user can use "-tagset HTML". |
Tag definition packages are named PerlPoint::Tags::<target format>
, so this rule makes it easy to find the appropriate definitions, and PerlPoint::Tags::addTagSets()
can load them.
If "-tagset HTML" is specified, the definition module PerlPoint::Tags::HTML is loaded. |
Please note that because -tagset
is intended to reflect definitions made for a certain converter, there is no way to load only a subset of another converters tags descriptions.
Different to usual definition loading, no warning is displayed here if a loaded foreign tag is named like an own one, and the original converter definition will remain established to give the converter first priority.
Next: Set up Active Contents handling Previous: Usual startup operations Contents: Contents |