RE: PHP website - OS Convention - ThoutReader
| From: | Mark D. Carey | Date: | Tue, 13 Jul 2004 21:51:15 +0000 |
| Subject: | RE: PHP website - OS Convention - ThoutReader | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-25315@lists.php.net to get a copy of this message | ||
Goba,
Of course we will ensure that all copyright issues are adhered to. We are
not planning on selling or profiting from the PHP documentation in any way.
Our ThoutTReader is free and the documentation is free.
Regarding the link you provided: I direct your attention to the following
statement:
"In case you are interested in redistribution or republishing of this
document in whole or in part, either modified or unmodified, and you have
questions, please contact the copyright holders at
doc-license@lists.php.net. Note that this address is mapped to a publicly
archived mailing list."
Does this mean we need permission to use a different format for the
documentation by e-mailing license@lists.php.net? Please advise.
Finally, it will take some time to format the content in 24 different
languages. Adding a separate row is probably the easiest way to do it - in
between View Online and Printer Friendly. Is there a way we can add the row
now with the top four or five languages and convert the others soon
afterward? I was thinking English, Spanish, German, French, and Russian??
Thanks for all your help. It's hard to improve PHP documentation because it
sets the standard in the OS community. We provide the ability for users to
browse, search, bookmark, and append not only their PHP documentation, but
also all of the supporting books and materials as well.
Mark
============================================
Mark D. Carey
President
OSoft, Inc.
2511 S. Hood Street
Tacoma, WA 98402
253-284-0475
mcarey@osoft.com
www.OSoft.com
"Mind Altering Software"
============================================
-----Original Message-----
From: Gabor Hojtsy [mailto:gabor@hojtsy.hu]
Sent: Tuesday, July 13, 2004 2:38 PM
To: mcarey@osoft.com
Cc: webmaster@php.net
Subject: Re: PHP website - OS Convention - ThoutReader
Hi Mark,
> We believe the PHP documentation is covered under your GPL but we just
> wanted to make sure it was ok to deliver it, unaltered, in the
ThoutTReader
> format.
No it is not under the GPL. Since you say you have processed the PHP
manual, you probably already processed the copyright part. See:
http://php.net/manual/en/copyright.php
> We have already converted PHP 4.0 into the ThoutTReader format and it is
> ready to load. We have written scripts that will convert PHP 5.0 into the
> ThoutTReader format in a matter of minutes once the documentation is
> released. The same holds true for any other documentation you wish to
> convert.
I expect you to refer to the PHP 4.0 and PHP 5.0 documentation
respectively above. First, currently we have 4.x versions, not only 4.0.
Second our current manual contains information for PHP 3.0.x, PHP 4.x.x,
and PHP 5.0.0 (currently the CVS version) as well. We do refer to
specific versions, including 5.0.0. We do not yet have a complete
documentation on new features in PHP 5, and we will probably not have
that when PHP 5.0.0 (the software) is released. The situation was
similar before. Some part of the documentation are way ahead of time,
documenting PHP 5 features for some time now, and some parts are not yet
up to date. There is no such thing as documentation date <-> PHP version
relationship.
> We need a point of contact to provide the PHP 4.0 documentation (.JAR
file)
> to with a short description of the ThoutTReader. Note: The ThoutTReader
> easily supports multiple languages.
Probably only systems@php.net people could help you get a file into the
documentation distribution space, I have no sufficient rights to help
you in this. It is sometimes not easy to get some quick action done
through systems@, since they are busy people. So if nothing else works,
we can put up a new format column and links to your site to download the
manual in different languages. Are you going to provide the manual in
non-English languages? If no, then a separate column might not be that
good an idea at all.
Goba