Doc #48707 [ReO->Csd]: File php_manual_notes.chm not available on site
| From: | rquadling@php.net | Date: | Mon, 06 Jun 2011 12:30:22 +0000 |
| Subject: | Doc #48707 [ReO->Csd]: File php_manual_notes.chm not available on site | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-6703@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=48707&edit=1
ID: 48707
Updated by: rquadling@php.net
Reported by: drgnllc at gmail dot com
Summary: File php_manual_notes.chm not available on site
-Status: Re-Opened
+Status: Closed
Type: Documentation Problem
Package: Documentation problem
PHP Version: Irrelevant
-Assigned To:
+Assigned To: rquadling
Block user comment: N
Private report: N
New Comment:
I think we've done everything here.
Previous Comments:
------------------------------------------------------------------------
[2011-06-06 14:28:32] rquadling@php.net
There were 2 significant features of the old style "Extended CHM" files.
1 - User notes
2 - User selectable CSS styling.
Both of these issues have now been resolved. To a degree.
For the User Notes, the PhD system now has a new format for PHP called
EnhancedCHM (yeah, sure, the name is pretty poor and is obviously confusable
with the extended chm ... so shoot me!).
As you can see on the CHM Downloads page (http://www.php.net/download-docs.php),
you can download a version of the CHM file with the user notes. These are
generated weekly.
For the User selectable CSS styling, then this has been implemented by the use
of the --css parameter when running PhD.
You can add multiple CSS files. If you add
--css reset.css --css theme.css --css doc.css
to the PhD build call, this will include the new CSS styling from the currently
in-progress new styling. As seen if you run http://www.php.net/?beta=1
I have found 1 issue with this
(http://www.php.net/manual/en/win32service.constants.servicetype.php is a good
an example as any).
The normal web page (as via the URL) and the HTML file generated by PhD for
including into the CHM both show the correct alternative line colouring. In the
CHM file, this isn't the case.
As far as I can tell, this is an MS issue and one that is unlikely to be fixed.
If you have your own CSS file, then you could use ...
--css C:\MyPHPManual\my.css
I've just added this support based upon this conversation
(http://svn.php.net/viewvc?view=revision&revision=311863).
So, you can now build your own CHM files and apply user defined CSS styling to
the EnhancedCHM format.
Now... if the CHM viewer supports @import(), I think it could be possible to
implement many different styling schemes from an unamended, pre-compiled CHM
file.
The downside is that the CSS file would have to be in the same location as the
CHM file at all times - unless you built your own CHM file, in which case, why
use @import? Build in the CSS you want using --css.
I don't think PHP will be providing any additional stylings.
------------------------------------------------------------------------
[2011-06-06 14:28:19] philip@php.net
There are now two versions of the CHM build available:
http://www.php.net/download-docs.php?sizes=1
The 'enhanced' version contains the user notes. The aforementioned old format no
longer exists, nor is it planned.
------------------------------------------------------------------------
[2011-06-06 13:21:48] t dot kmieliauskas at gmail dot com
so is the old format (skinnable) manual going to be maintained again?
------------------------------------------------------------------------
[2011-02-24 02:55:16] philip@php.net
This is being worked on.
------------------------------------------------------------------------
[2010-04-28 09:59:19] bjori@php.net
Because it is no longer available.
We have noone that has that has the know-how and time to implement this CHM
stuff.
The references to this package have been removed, it is highly unlikely that it
will ever exist again.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=48707
--
Edit this bug report at http://bugs.php.net/bug.php?id=48707&edit=1