Re: Chaining plguins (was Re: What does "XHTML2 as an internal document format" mean?)
On Thursday 15 September 2005 13:23, Ross Gardler wrote: > There is plenty of discussion about this in the archives, you and I have > discussed it to death before - the situation is still the same and the > design is still the same, it is unaffected by the move to XHTML2, unless > docbook provides a set of stylesheets to XHTML2? Right :-) Now when would be a good time. Since I think any solution would depend on having XHTML2 as core, right? My guess is you need to get XHTML2 outa da way before anyone can do anything on the input. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za ~ Registered Linux User #375355 http://wenzani.blogspot.com/
Re: Chaining plguins (was Re: What does "XHTML2 as an internal document format" mean?)
On Thursday 15 September 2005 12:52, Ross Gardler wrote: > As things are today it is not possible to have dependencies between > plugins. However, Daniel (from Cocoon) showed me how we can use a > feature of Cocoon blocks (wiring.xml) to manage ingheritance between > plugins. > > In other words we can write a docbook plugin that extends the XHTML > plugin. It will use the docbook stylsheets to convert to XHTML and then > the XHTML plugin to convert to our internal format. I've not found a use > case strong enough for me to take the time to implement this yet, > however, if anyone wants to tackle it I'll be happy to pass on what > Daniel showed me. Use cases 1. http://learnlinux.tsf.org.za 2. http://icdl.tsf.org.za -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za ~ Registered Linux User #375355 http://wenzani.blogspot.com/
Re: What does "XHTML2 as an internal document format" mean?
On Thursday 15 September 2005 01:56, Ross Gardler wrote: > An Example Input Plugin > --- > > It is the job of our input plugins to provide the internal format. > Consder a OpenOffice input plugin, it converts the OOo XML format to our > internal format. What forrest:contracts does it provide? > > An OOo document consists of meta-data, content (made up of pages, > sections, paragraphs) and style information. So logical contracts would > be various meta-data contracts (authors, statistics, abstract, > keywords), content (all, page X etc.) and style (produces CSS). This way > a user can decide which parts of the original document are used. Most Excellent Ross, Just a question. How do you propose managing Docbook :-) Stupid ppl, like me, like to use the power of all the Docbook Stylesheets as they do 99% of everything we need for publishing. So, as you know, there is a set of XHTML XSLT for DocbookXML2XHTML. If Forrest could input the XHTML from Docbook it would be so nice. dbxml > X/HTML (single/chunked) > input > internal > output > formats -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za ~ Registered Linux User #375355 http://wenzani.blogspot.com/
Re: New Forrest Example Site
On Wednesday 24 August 2005 03:13, David Crossley wrote: > You have been out of touch for a while, so please be aware > that the Forrest dev community is currently working on > a new facility codenamed "views" which will probably > replace "skins". dude, turn your head for a minute on this project and everything changes :-) No really, cool. I assume there is some documentation to help me get up to speed with views, right? -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpjInX9QrIry.pgp Description: PGP signature
New Forrest Example Site
Hey Forrest team, I've been in the woods for some weeks. I return with news that the OpenICDL Project website is currently based Forrest [http://icdl.tsf.org.za]. Now I am up for developing a new skin for the OpenICDL project and would like to contribute it back to the Forrest community. Any help or ideas will be much appreciated. I can be reach at the address below or better still on the icdl-user mailing list. http://icdl.tsf.org.za/mail.html Enjoy, -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355
Re: using lenya / forrest for ubuntu documentation?
On Sunday 12 June 2005 15:56, Gregor J. Rothfuss wrote: > > Some friends in the CO.ZA community are setting a server to run > > gnome.org.za. This is new, but would be used to edit docbook xml > > documents from the GNOME Documentation project checked out from GNOME > > CVS. Let me know if you would like to do this or not. It is not Ubuntu > > related and we have total autonomy over what we will do, so politics > > aside I think we can move quickly and possible have it up and running in > > 7 -14 days. It could be a great live test case. I think we are happy to > > play crash test dummy. > > i don't think we'll have time to set up another test system (we are busy > enough with our own), but please join our discussion if you are interested. :-) We have the technical expertise to do it, but may need to work together with you to iron out problems etc. Will let you know more next week. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpN6REFo6BPd.pgp Description: PGP signature
Re: using lenya / forrest for ubuntu documentation?
On Sunday 12 June 2005 11:14, David Crossley wrote: > BTW, it is a way off, but ... > http://incubator.apache.org/projects/harmony.html Thanks David, That's worth keeping an eye on ;-) -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpzIegmrGNKR.pgp Description: PGP signature
Re: using lenya / forrest for ubuntu documentation?
On Saturday 11 June 2005 19:00, Gregor J. Rothfuss wrote: > i just came across > > http://www.ubuntulinux.org/wiki/DocumentationTeamMeetingSummary4 > > especially: > Hello Gregor, African Greetings. Good to see you venturing beyond the ASF :-) You may or may not know me from the Forrest Project. I have a number of sites running under Forrest. My own included, which has a custom skin (URL at end). > > i wanted to alert you guys to an ongoing development over at the ASF. we > are in the process of eating our own dogfood, and making steps toward a > documentation system that might fit your bill: > > http://wiki.apache.org/cocoon/Doco I am aware of this project. I follow forrest-dev and contribute where I can. The idea of Doco is good and was the base of a concept that I tried to explain to people at ubuntu. Unfortunately, for numerous reasons, I failed. The problem is we need Docbook but users can't/don't want to spend time trying to learn it and work with it. Then there is SVN, as easy as it is to use, most users have a fear of working with revision control systems. They are comfortable hacking work in wiki or as HTML or in OOo Writer, but not using a Structured XML Editor or source/text editor. At Ubuntu most of the people who want to contribute docs are not very technical people, but they have figured out how to do something and want to contribute back by writing a how-to, for example. The Ubuntu-doc team policy has been to make it possible for everyone and anyone to contribute if the wish. As you know, the problem with having multiple formats for storage of documents is that it become near impossible to manage and repurpose information over time. So just as Doco describes, we wanted to bring the ease of wiki editing together with the valid and well-formed nature of XML. In particular to be able to utilize the batch processing environment already provided by Docbook. Mainly because Docbook is utilized by all Ubuntu upstreams. In a test box that I installed for the purpose of developing a solution to this problem, Lenya did 90% of what we need, BUT: 1. I could not test it in a production environment like ubuntu.com 2. Docbook is a big DTD and Bitflux took long to load over my LAN. I would not like to try it over the Internet. This Lenya was fed docbook xml from the docteam svn. So it was essentially editing the xml src of a working copy. It was a bit hectic trying to get the checkout files displayed in lenya but finally with lots of coffee and a few early mornings I got through the docs and made it work. Well, what worked was the editing, I made the system as easy possible for the test purpose. Working on Localhost and some computers in my LAN I was able to do edits. Then I would ssh into the box and svn diff to see it was working. If I could do that then I was happy because it mean I could merge the diff to the repos if I wanted. In my senario I saw lenya as a great big harvester, many authors editing one working copy of svn that commit users could control and merge back to the repos. I did for see some workflow problems with this, but seeing doco I think you may have already nailed them. One problem I must warn of. It's a religious question, of Java, that you will need to overcome with the ubuntu community, especially people at canonical. Seems that Java is a 4-letter word in the ubuntu community because it is not free. It's silly, I know, but that is the reality. I don't think the ubuntu-doc team cares what technology is used so long as the solution works, so there is your support base, but higher up you may have resistance. Sometime, the people up top, bless their cotton socks, tend to forget that this is a community project. Sorry I speak it how I see it these days. I think that with Lenya Dev and Forrest Dev we can get a working robust solution. Should you fail in your attempts with Ubuntu, I have another opportunity. Some friends in the CO.ZA community are setting a server to run gnome.org.za. This is new, but would be used to edit docbook xml documents from the GNOME Documentation project checked out from GNOME CVS. Let me know if you would like to do this or not. It is not Ubuntu related and we have total autonomy over what we will do, so politics aside I think we can move quickly and possible have it up and running in 7 -14 days. It could be a great live test case. I think we are happy to play crash test dummy. Hope this helps, -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpELsRuZGDxO.pgp Description: PGP signature
Plugin simplified.docbook
Hi, On a separate instance of forrest I have updated to svn HEAD. In my project forrest.properties I have defined project.required.plugins=org.apache.forrest.plugin.input.simplified-docbook When I run forrest my site is rendered but content (docbook 4.2 xml is not). Yet it appears that the plugin is installed and configured. check-java-version: This is apache-forrest-0.7-dev Using Java 1.4 from /usr/lib/jvm/java-1.4.2-sun-1.4.2.06/jre init-plugins: Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Installing plugin: org.apache.forrest.plugin.input.simplified-docbook configure-input-plugin: Mounting input plugin: org.apache.forrest.plugin.input.simplified-docbook Processing /home/sean/projects/inwordsweb/trunk/build/tmp/input.xmap to /home/sean/projects/inwordsweb/trunk/build/tmp/input.xmap.new Loading stylesheet /home/sean/projects/forrest/main/var/pluginMountSnippet.xsl Moving 1 files to /home/sean/projects/inwordsweb/trunk/build/tmp Processing /home/sean/projects/inwordsweb/trunk/build/tmp/resources.xmap to /home/sean/projects/inwordsweb/trunk/build/tmp/resources.xmap.new Loading stylesheet /home/sean/projects/forrest/main/var/pluginMountSnippet.xsl Moving 1 files to /home/sean/projects/inwordsweb/trunk/build/tmp Switching back to my previous instance of Forrest, the site renders with all content. Any pointers. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpnF7Vrg5YsS.pgp Description: PGP signature
I18n Property
Hi, I would like to translate my web site to a number of languages and have the possability for uses to select their language of preference using a drop-list. In forrest.properties I see #I18n Property only works for the "forrest run" target. #project.i18n=true Seems this will only work within a webapp environment. Anyone have sugestions on how I can implement this? -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgptdMBdbpqo2.pgp Description: PGP signature
Re: New Web Site based on Forrest
On Monday 09 May 2005 13:32, Ross Gardler wrote: > Sean Wheller wrote: > > Just a note to let you know that I have published my web site using > > Apache Forrest. I still have some minor issues to resolve, but the > > content is driven entirely from Docbook XML. > > > > http://www.inwords.co.za > > added, thanks Great. > > > Feedback thoughts, ideas, typos, etc. All welcomed. > > I was thinking of contacting people like yourself, who have customised > their skins, and requesting that you make the skin available for others > via the skin download mechanism. It would be an easy way to contribute > back to the community. > > All you need to do is package the skin using forrest and make it > available somewhere on the web and let us know what to add to the > skins.xml file (see http://forrest.apache.org/0.6/docs/skin-package.html ) > > Of course, there is no obligation to do this. If the skin is an > important part of your corporate branding we will understand perfectly. > > Problem is, the skin download mechanism has been around for a long time > but has not really been tested out in the real world. Perhaps you could > help us out by being the first to provide a skin to download? Yes, I am aware of this problem. However, like you say branding is an issue. I will see if I can squeeze some time to develop a more generic skin type, based on the one you see on my web site, and publish that. I may also have the opportunity to produce a new skin for another project I am working on. Keep in touch. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpbWulqy5TKz.pgp Description: PGP signature
New Web Site based on Forrest
Hello, Just a note to let you know that I have published my web site using Apache Forrest. I still have some minor issues to resolve, but the content is driven entirely from Docbook XML. http://www.inwords.co.za Feedback thoughts, ideas, typos, etc. All welcomed. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpVlb9xBDbwT.pgp Description: PGP signature
Re: docbook error
On Monday 18 April 2005 08:03, Joao Araujo wrote: > I have a large document site with mixed docbook and regular > forrest documentation. > After I upgraded my site from 0.6 to 0.7, the docbook info does > not appear anymore on the site. > I hit the link a menu only page shows up. Joao, Your sdocbook plugin is not found. Check forrest.properties. Make sure project.required.plugins=simplified-docbook This should rebuild the site. This should result in the installation of the docbook-plugin used to transform docbook documents. If it does not you will have to manually add it to the system. While we are on the subject. I once submitted a patch that enabled docbook 4.3. Anyone gonna used it? -- Sean Wheller Technical Author [EMAIL PROTECTED] http://www.inwords.co.za Registered Linux User #375355 pgpZCIIxbRBTC.pgp Description: PGP signature
Re: plugin install
On Tuesday 29 March 2005 17:08, Ross Gardler wrote: > Sean Wheller wrote: > > Do the plugins install yet as described at > > http://forrest.apache.org/docs/dev/plugins/usingPlugins.html > > Yes, they always have, but if you are behind a firewall you need to do > some configuration. What configuration is required? -- Sean Wheller Technical Author [EMAIL PROTECTED] http://www.inwords.co.za Registered Linux User #375355
plugin install
Do the plugins install yet as described at http://forrest.apache.org/docs/dev/plugins/usingPlugins.html Thanks, -- Sean Wheller Technical Author [EMAIL PROTECTED] http://www.inwords.co.za Registered Linux User #375355
New Forrest Site
Hello, Nobody has heard from me in awhile. I have been busy, busy on all sorts of projects. One of the new ones is http://computerdictionary.tsf.org.za So if anyone wants to add it to the list of sample sites. Please do. There are some forrest issue I need to resolve on this site, so I expect that I will be asking how to do this on the list very soon. Hope some of the solutions can come back to the project :-) Enjoy, -- Sean Wheller Technical Author [EMAIL PROTECTED] http://www.inwords.co.za Registered Linux User #375355 pgpHJWWS8pDuQ.pgp Description: PGP signature
[ANN] oXygen XML Editor 5.1
Hi devs, For those of you looking for a great and cost-effective XML Editor I am glad to announce a new version of XML Editor. The main additions in version 5.1 are folding, code templates, better Relax NG support, Schematron validation and the possibility to use MSXML and XSLTProc as XSLT transformers. is a Java app and runs on all platforms. If you decide to download or buy, please support my free contribution efforts to , aimed at improving the product documentation, You can do this by clicking this link. http://www.shareit.com/product.html?cart=1&productid=178941&affiliateid=72752 XML Editor has ready to use DocBook support including: * the DocBook 4.3 and 4.2 DTDs * the 1.67.2 XSL stylesheets * document templates (new book, article with or without XInclude support) * default transformation scenarios to convert DocBook documents to HTML and PDF * already setup XML Catalog * DocBook XInclude support * on the fly (as you edit) documentation for DocBook elements (based on DTD comments) * XSLT Debugger capable of handling the DocBook stylesheets * spell checking support * DocBook samples The full list of new features with descriptions and a few video demonstrations can be found at: http://www.oxygenxml.com/index.html#new-version Best Regards, -- Sean Wheller Technical Author [EMAIL PROTECTED] http://www.inwords.co.za Registered Linux User #375355 pgppXYI13At54.pgp Description: PGP signature
