> so just to make sure that we are on the same line, currently we will handle only <meta> and <base> tags, right? These should be deparsed into key/value pairs which will be then reconsructed by the templates.
meta: metaname => metavalue
It can't be exactly like that, because there is meta http-equiv too. I'll construct it like:
meta => [
{ name => '...',
content => '...',
},
{ 'http-equiv' => 'Content-type',
content => 'text/html',
} ]
But the idea is the same.
base: "href" => http:/...
yes.
so in the template we first convert the hardcoded headers into a datastructure:
[% default =
meta => {
author => "docs-dev (at) perl.apache.org",
description => "Manuals, Hints, Guidelines, Scenarios...",
...
},
%]
So that'd be:
[% default =
meta => [ { name => 'author', content => 'docs-...' }, { name => 'description', ....... etc. Same basic idea.
Anyway, we're along the same lines...I'll make it work soon :)
-- Per Einar Ellefsen [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
