Hi Yegor,
I am the one who did the html_page logic in the Apache CMS in OOo and I brought
it over.
While it works for some I noticed similar problems recently. It is in
odf/site/trunk/lib/view.pm
sub html_page {
my %args = @_;
my %styleargs = @_;
my $file = "content$args{path}";
my $template = $args{template};
$args{breadcrumbs} = breadcrumbs($args{path});
read_text_file $file, \%args;
my $page_path = $file;
$page_path =~ s/\.[^.]+$/.page/;
if (-d $page_path) {
for my $f (grep -f, glob "$page_path/*.mdtext") {
$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {};
read_text_file $f, $args{$1};
}
}
$args{header} = `sed -n '/<head>/,/<\\/head>/p' ${file} | sed -e
'1s/.*<head>//' -e 's/<\\/head>.*//'`;
$args{content} = `sed -n '/<body>/,/<\\/body>/p' ${file} | sed -e
'1s/.*<body>//' -e "s/<\\/body>.*//"`;
return Template($template)->render(\%args), html => \%args;
}
This procedure needs to be adjusted.
In the html I see: <BODY BGCOLOR="white" onload="windowTitle();">
If the html clause in path.pm is removed then these pages will not be framed.
A suggestion for better head and body extraction patterns would be great.
Regards,
Dave
On Sep 7, 2011, at 4:58 AM, Yegor Kozlov wrote:
>>>
>>> How do you push javadoc ? I see that the files are in place, but they
>>> are all broken. All .html files have length of 2915 bytes and show
>>> some default content as you can see at
>>> http://incubator.apache.org/odftoolkit/simple/document/javadoc/index.html.
>>>
>>
>> I see the JavaDoc checked in to SVN in paths like this:
>>
>> odf/site/trunk/content/odftoolkit/simple/document/javadoc/
>>
>> The files that were checked in look fine.
>>
>> Is there some interaction with the Apache CMS? Is it smart enough to
>> ignore HTML files in that directory, or is it trying to process them
>> as Markdown?
>>
>
> I asked this question on @infra. Hope they will help.
>
> Yegor
