Menu
▾
▴
phpwebsite-developers
|
From: Don S. <do...@se...> - 2004-03-11 23:05:55
|
Is there a HOWTO or any nice procedure to migrate from using phatfile to documents? Meaning migrate existing phatfile documents to the documents module. Don. --=20 "Actually, this may sound a little West Texan to you, but I like it when I'm talking about myself, and when he's talking about myself, all of us are talking about me." George W. Bush May 31, 2000 Spoken to Chris Matthews on MSNBC's Hardball. |
|
From: Steven L. <st...@tu...> - 2004-03-12 15:01:29
|
On Thu, 2004-03-11 at 17:54, Don Seiler wrote: > Is there a HOWTO or any nice procedure to migrate from using phatfile to > documents? Meaning migrate existing phatfile documents to the documents > module. Darren has written us a nice conversion script. I have not had a chance to test it, but here it is. http://res1.stddev.appstate.edu/horde/chora/co.php/documents/convert/convert.php?login=2&r=1.1&Horde=761dd257b3401477f813bc83ebceb32e&Horde=761dd257b3401477f813bc83ebceb32e -- Steven Levin Computer Systems Admin I Electronic Student Services Appalachian State University Phone: 828.262.6740 http://phpwebsite.appstate.edu |
|
From: Don S. <do...@se...> - 2004-03-12 15:32:36
|
On Fri, Mar 12, 2004 at 09:47:33AM -0500, Steven Levin wrote: > Darren has written us a nice conversion script. I have not had a chance > to test it, but here it is. > http://res1.stddev.appstate.edu/horde/chora/co.php/documents/convert/conv= ert.php?login=3D2&r=3D1.1&Horde=3D761dd257b3401477f813bc83ebceb32e&Horde=3D= 761dd257b3401477f813bc83ebceb32e The instructions say to go to http://mysite.com/mod/documents/convert/convert.php, but what do I do for branch sites, since they don't have the mod dir structure? Looking at the script it seems geared towards only single-site operations. Perhaps I'll tweak it a little later if there isn't a fix. Thanks, Don. --=20 "The most important job is not to be governor, or first lady in my case." George W. Bush January 30, 2000 =46rom speech in Pella, Iowa and quoted in the San Antonio Express-News. |
|
From: Greg M. <drk...@co...> - 2004-03-13 15:15:04
|
Is there a document that explains how the xml build is setup? I was fooling around with the manual .xml files and could not get them to build the same way that they are in phpwebsiteroot/manual directory. Thanks, Greg |
|
From: Mike N. <mh...@us...> - 2004-03-13 17:58:39
|
On Sat, 2004-03-13 at 07:14, Greg Morgan wrote: > Is there a document that explains how the xml build is setup? I was > fooling around with the manual .xml files and could not get them to > build the same way that they are in phpwebsiteroot/manual directory. Greg, Building the DocBook manual should be fairly straight forward, provided your environment is setup properly. You'll need the proper entities also. Let me know if you need help. manual.xml http://res1.stddev.appstate.edu/horde/chora/cvs.php/phpwebsite/manual -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
|
From: Greg M. <drk...@co...> - 2004-03-15 00:54:20
|
Mike Noyes wrote: > On Sat, 2004-03-13 at 07:14, Greg Morgan wrote: > >>Is there a document that explains how the xml build is setup? I was >>fooling around with the manual .xml files and could not get them to >>build the same way that they are in phpwebsiteroot/manual directory. > > > Greg, > Building the DocBook manual should be fairly straight forward, provided > your environment is setup properly. You'll need the proper entities > also. Let me know if you need help. > > manual.xml > http://res1.stddev.appstate.edu/horde/chora/cvs.php/phpwebsite/manual > Good. It looks like no one has worked on these files for eight months. Here's what I have done so far http://kissalice.sourceforge.net/phpmanual/output/set1.html. It has all my rough ideas in rough rough form. I cleaned up the CVS section today. I have added an "Installation, Upgrade, and Maintenance" and fleshed out the "Developer's Guide". Essentially, I have cobble many of my phpWS forum responses together. I've started to manipulate them into a manual. I think Ray O. on the LEAF list said that's one way to help. Watch what is happening in the mailing lists/forums and try and solve those problems. LOL, I've created a few of my own with docbook. In the http://kissalice.sourceforge.net/phpmanual/ directory are two files. 00readme.txt explains what I had to do to get this working on Redhat's fedora core 1. That file says, " jw -f docbook -b html -o output manual.xml docbook2html manual.xml While working on this book, I had to change all instances of "http://docbook.org/xml/4.2/docbookx.dtd" to "/usr/share/sgml/docbook/sgml-dtd-4.2-1.0-22.1/docbook.dtd" on Fedora Core 1." The jw with -o to output placed all the html files in the output directory. makemanual.sh is the jw command in a shell script. I don't understand why the official manuals look like this ... bk01ch01.html bk01ch06s06.html bk02ch04s04.html bk02ch08s06.html bk01ch01s02.html bk01ch06s07.html bk02ch04s05.html bk02ch08s07.html bk01ch01s03.html bk01ch06s08.html bk02ch04s06.html bk02ch08s08.html ... when mine look like this ... book1977.html c2150.html x1048.html x2015.html x2154.html x252.html book1.html c2152.html x1051.html x2016.html x2155.html x312.html book2006.html c2155.html x107.html x2019.html x2156.html x35.html ... I believe the main problem I have is on this example page, http://kissalice.sourceforge.net/phpmanual/output/x2223.html. See all the '>'s. Those are supposed to be graphics. I receive this error when executing jade i.e. jw, "jade:/home/edrive/phpwebsite/phpwebsite932/manual/xml/core/developer/themedevel.xml:151:42:E: character data is not allowed here". Google did not point me to anything outstanding. Moreover, I copied this stanza from the user guide, <screenshot> <graphic fileref="images/winxp.png"/> </screenshot> These three lines are lines 150-152 in the above error message. I don't have a clue. Right now I am happy to massage the text into something meaningful. The module you and I talked about on IRC and email is at the beginning of the developer tutorial. Can I quote our session as an example of how the item class is discovered? Oh! I tried searching for the xml editor you and Lynn talked about on the LEAF developer's list. However, I was fruitless. Do you have have the URL for that editor? After reading this article, http://www106.pair.com/rhp/hacking.html, I thought I should post what I've done with the documentation. One the one hand, I wanted to be able to "show the code" while on the other hand I wanted to make sure that I start coordinating with others. If this is acceptable work, then I would like to merge it with the official documentation. I'd rather work in the community than go off and be the lone cowboy and have yet another place for the users to look for information. Any solutions and feedback would be appreciated. Regards, Greg Morgan |
|
From: Mike N. <mh...@us...> - 2004-03-15 21:46:15
|
On Sun, 2004-03-14 at 16:54, Greg Morgan wrote: > Here's what I have done so far > http://kissalice.sourceforge.net/phpmanual/output/set1.html. It has all > my rough ideas in rough rough form. I cleaned up the CVS section today. > I have added an "Installation, Upgrade, and Maintenance" and fleshed > out the "Developer's Guide". Essentially, I have cobble many of my > phpWS forum responses together. I've started to manipulate them into a > manual. I think Ray O. on the LEAF list said that's one way to help. > Watch what is happening in the mailing lists/forums and try and solve > those problems. LOL, I've created a few of my own with docbook. Greg, Nice work. :-) > In the http://kissalice.sourceforge.net/phpmanual/ directory are two > files. 00readme.txt explains what I had to do to get this working on > Redhat's fedora core 1. That file says, " > jw -f docbook -b html -o output manual.xml > > docbook2html manual.xml That is a jade wrapper script. It's not recommended for DocBook XML. You should be using xsltproc or saxon with the DocBook XSL Stylesheets. > While working on this book, I had to change all instances of > "http://docbook.org/xml/4.2/docbookx.dtd" to > "/usr/share/sgml/docbook/sgml-dtd-4.2-1.0-22.1/docbook.dtd" > on Fedora Core 1." Your catalog files in /etc/xml aren't setup properly. See: Catalog support http://xmlsoft.org/catalog.html > The jw with -o to output placed all the html files in the output > directory. makemanual.sh is the jw command in a shell script. > > I don't understand why the official manuals look like this <snip> This is a result of the xslt engine (jade) you used. Auto-generated chapter numbers are different for the DSSSL stylesheets. > Any solutions and feedback would be appreciated. Take a look at these resources: DocBookXSL: The Complete Guide http://www.sagehill.net/docbookxsl/ DocBookXSLStylesheet Documentation http://docbook.sourceforge.net/release/xsl/current/doc/ DocBook Wiki http://www.docbook.org/wiki/moin.cgi/ Docbook Frequently Asked Questions http://www.dpawson.co.uk/ Also, take a look at the XXE DocBook editor. XMLmind XML Editor http://www.xmlmind.com/xmleditor/ -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs |
|
From: Greg M. <drk...@co...> - 2004-03-17 03:26:23
|
Mike Noyes wrote: >>While working on this book, I had to change all instances of >>"http://docbook.org/xml/4.2/docbookx.dtd" to >>"/usr/share/sgml/docbook/sgml-dtd-4.2-1.0-22.1/docbook.dtd" >>on Fedora Core 1." > > > Your catalog files in /etc/xml aren't setup properly. See: > > Catalog support > http://xmlsoft.org/catalog.html <snip> > Take a look at these resources: > > DocBookXSL: The Complete Guide > http://www.sagehill.net/docbookxsl/ > > DocBookXSLStylesheet Documentation > http://docbook.sourceforge.net/release/xsl/current/doc/ > > DocBook Wiki > http://www.docbook.org/wiki/moin.cgi/ > > Docbook Frequently Asked Questions > http://www.dpawson.co.uk/ > > Also, take a look at the XXE DocBook editor. > > XMLmind XML Editor > http://www.xmlmind.com/xmleditor/ > Mike, Thanks for the response. I see I have a catalog in /etc/xml/catalog. I am still digesting the information from the sagehill site. I am still trying to understand the both the public identifier and system identifier mapped on my computer. xsltproc is doing a much better job. Greg |
|
From: Greg M. <drk...@co...> - 2004-03-24 07:04:47
|
I just finished additional updates to the CVS section of the manual. A sample is located here http://kissalice.sourceforge.net/phpmanual/output/c2120.html. I reworked it after seeing a post in the forums. Yeah I still stink at docbook. ;-) I am wondering about the opening line again. The original manual.xml file has this reference <!DOCTYPE set PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://docbook.org/xml/4.2/docbookx.dtd". While looking around it looks like all of the docbook.org references are being migrated to either docbook.sourceforge.net or www.oasis-open.org. Where should the '<!DOCTYPE set PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"' line be directed in the future? Greg |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X