Re: [PHP-DOC] cvs: phpdoc /xsl htmlhelp.xsl
Hello, I've tried to use your new XSL sheets, but they didn't work correctly... They have created the TOC and the index, but the html files weren't created. Am I missing something??? Nuno
[PHP-DOC] cvs: phpdoc /xsl htmlhelp.xsl
techtonik Tue Oct 19 11:11:10 2004 EDT Modified files: /phpdoc/xsl htmlhelp.xsl Log: oops, debug params http://cvs.php.net/diff.php/phpdoc/xsl/htmlhelp.xsl?r1=1.2r2=1.3ty=u Index: phpdoc/xsl/htmlhelp.xsl diff -u phpdoc/xsl/htmlhelp.xsl:1.2 phpdoc/xsl/htmlhelp.xsl:1.3 --- phpdoc/xsl/htmlhelp.xsl:1.2 Mon Oct 18 16:28:10 2004 +++ phpdoc/xsl/htmlhelp.xsl Tue Oct 19 11:11:09 2004 @@ -3,7 +3,7 @@ HTML Help specific stylesheet - $Id: htmlhelp.xsl,v 1.2 2004/10/18 20:28:10 techtonik Exp $ + $Id: htmlhelp.xsl,v 1.3 2004/10/19 15:11:09 techtonik Exp $ -- xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; @@ -34,7 +34,7 @@ book toc,title chapter toc,title part toc,title -preface toc +preface toc,title qandadiv toc qandaset toc reference toc,title @@ -271,7 +271,6 @@ /xsl:template -xsl:param name=htmlhelp.only select=1/ !-- xsl:param name=htmlhelp.only select=1/ htmlhelp.autolabel - chapter and section numbers in ToC - off
[PHP-DOC] xCHM status, usability and Preface formatting question
Hello, [EMAIL PROTECTED] I bet you've already noticed some commits to XSL templates. I've made an update resulting in latest XSL DocBook templates 1.66.1 and xCHM files compile successfully again. Main htmlhelp.xsl was started from scratch again to make it current with latest DocBook XSL sources and keep redundant customizations at minimum. Now it inherits htmlhelp/ DocBook templates instead of operating on it's separate copy of them in htmlhelp-db.xsl. Now I'm reviewing and integrating old markup rules into new template to make upcoming xCHM version look exactly as the previous xCHM 12. It will take some time to do this. Meanwhile some structural changes had happened in manual and I'd like to decide how to handle them. Specifically Preface chapter. In version 12 it was one page with a short abstract only. In version 13 and latest sources there are also credits with authors and editors. This division makes additional expandable book in TOC with all bookmarks leading to the same page. I do not know if it confuses users, but for me such division is useless and make manual look more like hardcopy books, where you do not need to look at these pages as long as you don't interested in that kind of information. But that's not true for xCHM version where this attention can decrease usability because frequently accessed information is located among similar graphical markup. I'm writing this with a great respect to all manual developers, editors, authors and contributors, because I think PHP manual is a major part of PHP success on windows platform. That's why I'm asking about what will be the best way to include information about people, who contributed to PHP docs in xCHM version. I have some proposals: 1. Leave as is Default way some may easily agree with because of simplicity in implementation (which should not be the goal, right?). That way we will have structure like Preface Authors and Contributors Authors and Editors User Note Maintainers as the third item of the manual TOC. Decreases usability by adding additional burden for users reading additional book title and perhaps contents to locate needed manual part. 2. Leave as a bookmark instead of book We will have only one Preface page with all contributors described with references from index, but without any from TOC. Probably the best way to check a point that authors should be listed somewhere in the manual. =) And not the best way to show appreciation. There will be not too much people who could find this info. 3. Move contributors part to the end of manual. There are three ways of doing this: 1. Make it Authors and Contributors Authors and Editors User Note Maintainers 2. Authors and Contributors (or just Credits) 3. Authors and Editors User Note Maintainers The prefferable way because people, who will need this info can easily find it. Information about authors will be in the root of ToC. It will not decrease usability and it seems logically correct to start and end the good work with credits. Like in cinema. =) What is your choice? t -- --[ http://wiki.phpdoc.info/DocLinks ]--
Re: [PHP-DOC] xCHM status, usability and Preface formatting question
Hi techtonik, I bet you've already noticed some commits to XSL templates. I've made an update resulting in latest XSL DocBook templates 1.66.1 and xCHM files compile successfully again. Main htmlhelp.xsl was started from scratch again to make it current with latest DocBook XSL sources and keep redundant customizations at minimum. Now it inherits htmlhelp/ DocBook templates instead of operating on it's separate copy of them in htmlhelp-db.xsl. Now I'm reviewing and integrating old markup rules into new template to make upcoming xCHM version look exactly as the previous xCHM 12. It will take some time to do this. Good. Your contributions are valuable :) In version 12 it was one page with a short abstract only. In version 13 and latest sources there are also credits with authors and editors. This division makes additional expandable book in TOC with all bookmarks leading to the same page. I do not know if it confuses users, but for me such division is useless and make manual look more like hardcopy books, where you do not need to look at these pages as long as you don't interested in that kind of information. But that's not true for xCHM version where this attention can decrease usability because frequently accessed information is located among similar graphical markup. I'm writing this with a great respect to all manual developers, editors, authors and contributors, because I think PHP manual is a major part of PHP success on windows platform. That's why I'm asking about what will be the best way to include information about people, who contributed to PHP docs in xCHM version. I have some proposals: 1. Leave as is Default way some may easily agree with because of simplicity in implementation (which should not be the goal, right?). That way we will have structure like Preface Authors and Contributors Authors and Editors User Note Maintainers as the third item of the manual TOC. Decreases usability by adding additional burden for users reading additional book title and perhaps contents to locate needed manual part. I had a hard time to undestand the point. These TOC items are expandable from the Preface hierarchy, and by default they are not expanded. Or am I mistaken? Goba
Re[2]: [PHP-DOC] cvs: phpdoc /xsl htmlhelp.xsl
||*()*|| Hi, Nuno. NL I've tried to use your new XSL sheets, but they didn't work correctly... NL They have created the TOC and the index, but the html files weren't created. NL Am I missing something??? No. It is my fault. While debugging HTML HELP project files I've forgot to move out parameter xsl:param name=htmlhelp.only select=1/ which caused only ToC, index and HHP files to be generated. Commited fix to CVS. t --
Re[2]: [PHP-DOC] xCHM status, usability and Preface formatting question
||*()*|| Hi, Gabor. In version 12 it was one page with a short abstract only. In version 13 and latest sources there are also credits with authors and editors. This division makes additional expandable book in TOC with all bookmarks leading to the same page. I do not know if it confuses users, but for me such division is useless and make manual look more like hardcopy books, where you do not need to look at these pages as long as you don't interested in that kind of information. But that's not true for xCHM version where this attention can decrease usability because frequently accessed information is located among similar graphical markup. I'm writing this with a great respect to all manual developers, editors, authors and contributors, because I think PHP manual is a major part of PHP success on windows platform. That's why I'm asking about what will be the best way to include information about people, who contributed to PHP docs in xCHM version. I have some proposals: 1. Leave as is Default way some may easily agree with because of simplicity in implementation (which should not be the goal, right?). That way we will have structure like Preface Authors and Contributors Authors and Editors User Note Maintainers as the third item of the manual TOC. Decreases usability by adding additional burden for users reading additional book title and perhaps contents to locate needed manual part. GH I had a hard time to undestand the point. These TOC items are expandable GH from the Preface hierarchy, and by default they are not expanded. Or am GH I mistaken? You are right. They are not expanded by default, but displayed as a book, so one still need to read the title to see what it is only Preface. To get to function reference you will need to review 7 upper books titles. After that one can become interested what can be in preface so authors made it expandable. One clicks the book and sees another book. Inside second book there are two bookmarks, but this is still the same Preface page. So many excess operations just because of curiosity which at the same time don't reveal any new interesting information makes one feel uncomfortable, slightly disappointed. Maybe one was looking for PHP Tutorial, which is actually in Getting Started or Install Instructions and thought it can be in Preface part. t --
Re: [PHP-DOC] xCHM status, usability and Preface formatting question
In version 12 it was one page with a short abstract only. In version 13 and latest sources there are also credits with authors and editors. This division makes additional expandable book in TOC with all bookmarks leading to the same page. I do not know if it confuses users, but for me such division is useless and make manual look more like hardcopy books, where you do not need to look at these pages as long as you don't interested in that kind of information. But that's not true for xCHM version where this attention can decrease usability because frequently accessed information is located among similar graphical markup. I'm writing this with a great respect to all manual developers, editors, authors and contributors, because I think PHP manual is a major part of PHP success on windows platform. That's why I'm asking about what will be the best way to include information about people, who contributed to PHP docs in xCHM version. I have some proposals: 1. Leave as is Default way some may easily agree with because of simplicity in implementation (which should not be the goal, right?). That way we will have structure like Preface Authors and Contributors Authors and Editors User Note Maintainers as the third item of the manual TOC. Decreases usability by adding additional burden for users reading additional book title and perhaps contents to locate needed manual part. GH I had a hard time to undestand the point. These TOC items are expandable GH from the Preface hierarchy, and by default they are not expanded. Or am GH I mistaken? You are right. They are not expanded by default, but displayed as a book, so one still need to read the title to see what it is only Preface. To get to function reference you will need to review 7 upper books titles. After that one can become interested what can be in preface so authors made it expandable. One clicks the book and sees another book. Inside second book there are two bookmarks, but this is still the same Preface page. So many excess operations just because of curiosity which at the same time don't reveal any new interesting information makes one feel uncomfortable, slightly disappointed. Maybe one was looking for PHP Tutorial, which is actually in Getting Started or Install Instructions and thought it can be in Preface part. Since traditional textbooks use a similar formatting, I don't have a problem with this solution. Those who would like to conquer the preface will finally found our names :) This is not bad :)) Goba
[PHP-DOC] #30486 [NEW]: First call of imagecolorallocate in french
From: jsgoupil at lookstrike dot com Operating system: PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: First call of imagecolorallocate in french Description: You say in english that the first call of imagecolorallocate color the background, but there is no note that talk about that in french http://ca.php.net/manual/fr/function.imagecolorallocate.php I think it should be added because its really important -- Edit bug report at http://bugs.php.net/?id=30486edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=30486r=trysnapshot4 Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=30486r=trysnapshot50 Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=30486r=trysnapshot51 Fixed in CVS:http://bugs.php.net/fix.php?id=30486r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=30486r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=30486r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=30486r=needscript Try newer version: http://bugs.php.net/fix.php?id=30486r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=30486r=support Expected behavior: http://bugs.php.net/fix.php?id=30486r=notwrong Not enough info: http://bugs.php.net/fix.php?id=30486r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=30486r=submittedtwice register_globals:http://bugs.php.net/fix.php?id=30486r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=30486r=php3 Daylight Savings:http://bugs.php.net/fix.php?id=30486r=dst IIS Stability: http://bugs.php.net/fix.php?id=30486r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=30486r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=30486r=float MySQL Configuration Error: http://bugs.php.net/fix.php?id=30486r=mysqlcfg
[PHP-DOC] #30486 [Opn-Asn]: First call of imagecolorallocate in french
ID: 30486 Updated by: [EMAIL PROTECTED] Reported By: jsgoupil at lookstrike dot com -Status: Open +Status: Assigned Bug Type:Documentation problem PHP Version: Irrelevant -Assigned To: +Assigned To: didou Previous Comments: [2004-10-19 20:41:30] jsgoupil at lookstrike dot com Description: You say in english that the first call of imagecolorallocate color the background, but there is no note that talk about that in french http://ca.php.net/manual/fr/function.imagecolorallocate.php I think it should be added because its really important -- Edit this bug report at http://bugs.php.net/?id=30486edit=1
[PHP-DOC] #30486 [Asn-Csd]: First call of imagecolorallocate in french
ID: 30486 Updated by: [EMAIL PROTECTED] Reported By: jsgoupil at lookstrike dot com -Status: Assigned +Status: Closed Bug Type:Documentation problem PHP Version: Irrelevant Assigned To: didou New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: [2004-10-19 20:41:30] jsgoupil at lookstrike dot com Description: You say in english that the first call of imagecolorallocate color the background, but there is no note that talk about that in french http://ca.php.net/manual/fr/function.imagecolorallocate.php I think it should be added because its really important -- Edit this bug report at http://bugs.php.net/?id=30486edit=1
