Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.227 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [API][WWW] Online API docs for AOO 3.4
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <4FB2A575.60801@googlemail.com>
Date: Tue, 15 May 2012 12:01:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E62E5EB-0AA9-47A4-84FA-B82DF3C4700F@comcast.net>
References: <20120515184012.GA3110@localhost> <4FB2A575.60801@googlemail.com>
To: ooo-dev@incubator.apache.org


On May 15, 2012, at 11:50 AM, Oliver-Rainer Wittmann wrote:

> Hi,
>=20
> Am 15.05.12 20:40, schrieb Ariel Constenla-Haile:
>> Hi there,
>>=20
>> now that AOO 3.4 is there, is there any chance to update the API docs =
at
>> =
http://www.openoffice.org/api/docs/common/ref/com/sun/star/module-ix.html
>> I could do it, if I knew the procedure: are these files in
>> ooo-site/trunk/content/api/docs/common/ref/ just a copy of the SDK
>> files?

They are a checked in copy. In order to exercise care, there was some =
hand editing, I would want to careful examine some diffs. Then I would =
tag the current tree, and replace with 3.4.


>>=20
>> On the other hand, there are two related issues:
>>=20
>> - the files on the web site, and the ones generated in AOO 3.4 SDK =
have
>>   the old copyright "Copyright =A9 1995, 2012, Oracle and/or its
>>   affiliates. All rights reserved. Oracle and Java are registered
>>   trademarks of Oracle and/or its affiliates. Other names may be
>>   trademarks of their respective owners."
>>=20
>> - on the website, the links on the navigator bar, for example
>>   http://www.openoffice.org/api/docs/common/ref/com/sun/star/ , =
generate
>>   directory listing, because there is no index.html, the SDK docs =
have
>>   a module-ix.html instead. I guess this could be solved with
>>   a .htaccess
>>=20
>>=20
>=20
> I assume that J=FCrgen knows more about it as he was deeply involved =
in the former api project - he was leading it.
> Thus, I propose to wait for J=FCrgen's input here.

It was discussed several months ago. I was thinking about this as well =
in the last couple of days.

J=FCrgen and I also discussed having the latest working SDK from trunk =
up in the project site.

Regards,
Dave


>=20
> Best regards, Oliver.