NAME

RTF::Control - Application of RTF::Parser for document conversion

VERSION

version 1.12

DESCRIPTION

Application of RTF::Parser for document conversion

OVERVIEW

RTF::Control is a sublass of RTF::Parser. RTF::Control can be seen as a helper module for people wanting to write their own document convertors - RTF::HTML::Convertor and RTF::TEXT::Convertor both subclass it.

I am the new maintainer of this module. My aim is to keep the interface identical to the old interface while cleaning up, documenting, and testing the internals. There are things in the interface I'm unhappy with, and things I like - however, I'm maintaining rather than developing the module, so, the interface is mostly frozen.

HOW IT ALL WORKS

For starters, go and look at the source of RTF::TEXT::Convertor

Except for RTF::Parser subs, the following is a list of variables exported by RTF::Control that you're expected to tinker with in your own subclass.

RTF::Parser subs

If you read the docs of RTF::Parser you'll see that you can redefine some subs there - RTF::Control has its own definitions for all of these, but you might want to over-ride "symbol()", "text()", and "char()". We'll look at what the defaults of each of these do, and what you need to do if you want to override any of them a little further down.

%symbol

This hash is actually merged into %do_on_control, with the value wrapped in a subroutine that effectively says "print shift". You can put any control words that should map directly to a certain output in here - "\tab", for example could be "$symbol{'tab'} = "\t"".

%info

This hash gets filled with document meta-data, as per the RTF specification.

%par_props

Not really sure, but paragraph properties

%do_on_event %do_on_control

%do_on_control tells us what to do when we meet a specific control word. The values are coderefs. %do_on_event also holds coderefs, but these are more abstract things to do, say when the stylesheet changes. %do_on_event thingies tend to be called by %do_on_control thingies, as far as I can tell.

$style $newstyle

Style is the current style, $newstyle is the one we're about to change to if we're about to change...

$event

Current event

$text

Pending text

new

Returns an RTF::Control object. RTF::Control is a subclass of RTF::Parser. Internally, we call RTF::Parser's new() method, and then we call an internal method called _configure(), which takes care of options we were passed.

ADD STUFF ON -output AND -confdir

application_dir

I'm leaving this method in because removing it will cause a backward-compatability nightmare. This method returns the ( wait for it ) path that the .pm file corresponding to the class that the object is contained, without a trailing semi-colon. Obviously this is nasty in several ways. If you've set "-confdir" in "new()" that will be returned instead. You should definitely take that route if you're on an OS on which Perl can't use / as a directory seperator.

charmap_reader

This nicely abstracts away using application_dir and so on. It's a method call. It'll take the name of the class, and an argument for the module/file it's looking for. This is likely to be 'ansi' or 'charmap'. This argument, for historical reasons (ho ho ho) will have any _'s removed in the check for a module name ... " $self-"charmap_reader('char_map') > will thus look for, for example, " RTF::TEXT::charmap " to load. It'll return the data in the file as an array of lines. This description sucks.

Stack manipulation

dump_stack

Serializes and prints the stack to STDERR

output

Holder routine for the current thing to do with output text we're given. It starts off as the same as $string_output_sub, which adds the string to the element at the "TOP" of the output stack. However, the idea, I believe, is to allow that to be changed at will, using "push_output".

POD ERRORS

Hey! The above document had some coding errors, which are explained below:

Around line 35:: Deleting unknown formatting code M<>