Re: XHTML
On Mon, 2010-10-25 at 10:06 +, greg wrote: Hello, how can I have an output in XHTML 1.1 with Forrest 0.8 ? Depends on skin or dispatcher. salu2 Thank you. -- Thorsten Scherler thorsten.at.apache.org codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/
[JOBS] Looking for a css and xhtml designer
Hi, I am getting involved in a tiny project and I would like to use forrest for it. As you may guess I am not a good designer so I need someone good in CSS and xhtml to create a site with better look than the standard Forrest look So if you are interested, please forward some urls of your work and I will show to my customers if they like it. we will work together :-) cheers, cheche
Re: Forrest internal format==XHTML in 0.8?
Ferdinand Soethe wrote: Christian Roth wrote: ... I'm asking because I'd like to only jump in when this transition has been made, so that any input and output/skinning plugins I'll need to probably write (we have several proprietary source DTDs and very specific output requirements) would not have to be changed from the ground up in a few weeks. Afaik we will continue to support documentvxx so your work would probably not be wasted. We will be making every effort to maintain backward compatability with 0.7. This should be provided transparently, so there should be no work on the part of the site admin. All the devs use Forrest in production environments, we have the same desires to not duplicate work as our users ;-) Ross
Forrest internal format==XHTML in 0.8?
Hello, I have been away from Forrest 0.6 since at that time, it did not meet my needs/expectations. I now get back to it, and I haven't found this questions answered in my quick glimpse over the docs: Is Forrest still using documentvXX as its internal format, or have you already been making the switch to XHTML(2) in 0.8? As far as I can remember, this was discussed some while ago and scheduled for 0.8 - is this still the current roadmap? I'm asking because I'd like to only jump in when this transition has been made, so that any input and output/skinning plugins I'll need to probably write (we have several proprietary source DTDs and very specific output requirements) would not have to be changed from the ground up in a few weeks. Thanks, Christian.
Re: Forrest internal format==XHTML in 0.8?
Christian Roth wrote: Is Forrest still using documentvXX as its internal format yes or have you already been making the switch to XHTML(2) in 0.8? We are right now preparing the switch. Might make sense to subcribe to the dev list to follow the discussion on it. I'm asking because I'd like to only jump in when this transition has been made, so that any input and output/skinning plugins I'll need to probably write (we have several proprietary source DTDs and very specific output requirements) would not have to be changed from the ground up in a few weeks. Afaik we will continue to support documentvxx so your work would probably not be wasted. Also: we already support xhtml as part of the html-processing. Check out the e,bedded html-sample (bad naming) in the seed site to see that. -- Ferdinand Soethe
Re: Forrest internal format==XHTML in 0.8?
Ferdinand Soethe wrote: or have you already been making the switch to XHTML(2) in 0.8? We are right now preparing the switch. Might make sense to subcribe to the dev list to follow the discussion on it. Ok, I have only been subscribed to the user list so far. Also: we already support xhtml as part of the html-processing. Check out the e,bedded html-sample (bad naming) in the seed site to see that. I'll have a look at this, thanks! Regards, Christian.
Re: How to use XHTML as input format
Ross Gardler wrote: What is required if I want to use XHTML as an input format. Just placing it in xdocs will not work, strangely enough if I do that with It should: http://forrest.apache.org/docs_0_70/upgrading_07.html#raw The way I read this is that I need not make any changes to a freshly seeded Forrest in order to have HTML/XHTML-files places in xdocs process as skinned documents, right! What is the name of your file, it should have the .html extension The extension is .html and it is in xdocs. As mentioned before it does get processed up to the http://localhost:/body-xhtml-test.html step of the pipeline, after that the page content simply vanished. -- Ferdinand Soethe
Re: How to use XHTML as input format
David Crossley wrote: Actually, this discussion would be useful as an FAQ, to explain the power of this source type match method. Thanks for explaining. Will try and find the bug in HTML-processing first though. -- Ferdinand Soethe
Re: How to use XHTML as input format
Try renaming the .xhtml files to .ihtml and then place them in the src/docs folder. cheers, Deepak. Ferdinand Soethe [EMAIL PROTECTED] wrote: Ross Gardler wrote: What is required if I want to use XHTML as an input format. Just placing it in xdocs will not work, strangely enough if I do that with It should: http://forrest.apache.org/docs_0_70/upgrading_07.html#rawThe way I read this is that I need not make any changes to a freshlyseeded Forrest in order to have HTML/XHTML-files places in xdocsprocess as skinned documents, right! What is the name of your file, it should have the .html extensionThe extension is .html and it is in xdocs. As mentioned before it doesget processed up to the http://localhost:/body-xhtml-test.htmlstep of the pipeline, after that the page content simply vanished.--Ferdinand Soethe Start your day with Yahoo! - make it your home page
Re: How to use XHTML as input format
Angeshwar Deepak wrote: Try renaming the .xhtml files to .ihtml and then place them in the src/docs folder. No *.ihtml is deprecated, the default behavior for HTML files is now to embed them. Ross
Re: How to use XHTML as input format
Ferdinand Soethe wrote: What is required if I want to use XHTML as an input format. Just placing it in xdocs will not work, strangely enough if I do that with ?xml version=1.0 encoding=UTF-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html xmlns=http://www.w3.org/1999/xhtml; head titleTestdocument XHTML/title /head body h1Testchapter/h1 pThis is a test to see what attributes are passed through when processing xhtml./p table border=1 width=30% tr tdZell 1-1/td tdZell 1-2/td tdZell 1-3/td /tr tr tdZell 2-1/td tdZell 2-2/td tdZell 2-3/td /tr /table /body /html I get a Forrest page with empty content area while calling the pipeline body-... will produce a clean looking document. Do I need to add a new mapping to the source pipeline, what else would I need to do. Yes, i think that all you need to do is add a new entry to the sitemap for that source type. Either to your project sitemap or to main/webapp/forrest.xmap in the core. SourceTypeAction (content aware pipelines) http://forrest.apache.org/docs/cap.html You ask what else. Well you need to construct pipelines to get your content to match our internal format. Perhaps re-use the html2xdoc transformer that is used for handling the html sources. Yes, the quicker we can go to xhtml2 as our internal format the better. Then the sitemap would only need to do map:read. Actually, this discussion would be useful as an FAQ, to explain the power of this source type match method. -David
How to use XHTML as input format
What is required if I want to use XHTML as an input format. Just placing it in xdocs will not work, strangely enough if I do that with ?xml version=1.0 encoding=UTF-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html xmlns=http://www.w3.org/1999/xhtml; head titleTestdocument XHTML/title /head body h1Testchapter/h1 pThis is a test to see what attributes are passed through when processing xhtml./p table border=1 width=30% tr tdZell 1-1/td tdZell 1-2/td tdZell 1-3/td /tr tr tdZell 2-1/td tdZell 2-2/td tdZell 2-3/td /tr /table /body /html I get a Forrest page with empty content area while calling the pipeline body-... will produce a clean looking document. Do I need to add a new mapping to the source pipeline, what else would I need to do. Thanks -- Ferdinand Soethe
Re: How to use XHTML as input format
Ferdinand Soethe wrote: What is required if I want to use XHTML as an input format. Just placing it in xdocs will not work, strangely enough if I do that with It should: http://forrest.apache.org/docs_0_70/upgrading_07.html#raw What is the name of your file, it should have the .html extension Ross
Introduction of XHTML?
I have two questions re the switch from Forrest document-v20-Format to xhtml: - What is a realistic expectation for this to happen in terms of time and version? (No guarantees expected of course!) - Will Forrest still support document-vxx after the switch? And if so, will document-vxx-support become a plugin? Thanks Ferdinand Soethe
Re: Introduction of XHTML?
Ferdinand Soethe wrote: I have two questions re the switch from Forrest document-v20-Format to xhtml: - What is a realistic expectation for this to happen in terms of time and version? (No guarantees expected of course!) It is part of the switch to the new skinning system that Thorsten has recently prototyped. Both he and I need this for our work so soon. Of course soon is a relative term. All I can say is that it *will* be in the next release. - Will Forrest still support document-vxx after the switch? Yes. And if so, will document-vxx-support become a plugin? Probably. Although it is likely that that plugin would be included in the default distribution for a while since there are a large number of sites using that format document. Ross
Re: Introduction of XHTML?
Thanks. Now I can safely train people to use document-v20 and wait for xhtml to come along and turn into a stable implementation. Ferdinand Soethe
Re: Introduction of XHTML?
Ferdinand Soethe wrote: Thanks. Now I can safely train people to use document-v20 and wait for xhtml to come along and turn into a stable implementation. It is a policy of the Forrest team to try not to break backward compatibility. Occasionally this is not possible. But usually it is. In other words, you can safely train folk up to use Forrest today, safe in the knowledge that we will at worst provide a migration path in the future. In this case you could consider using the XHTML subset we have defined now. We already support it as an input format, it's just that we don't use it internally yet. This will save you having to retrain folk in the future. Ross
