Menu
▾
▴
xmlroff-list
|
From: Stefan S. <sse...@ar...> - 2004-09-16 18:00:34
|
Tony Graham wrote: >I downloaded the current DocBook Website files and then updated the >DOCTYPE declarations in all the XML files to match. Once I added the >Website catalog to the system catalogs, it just worked. Amazing. Great. >There's a few rough spots -- No Sourceforge logo at present (my fault) >and still no documentation or development content -- but finally its >up. yeah, I'm still looking into these issues. Unfortunately the docbook-website xsl stuff only supports rss 1.0 out of the box (sf.net feeds version 2.0), so I have to rewrite the templates. Second, the website dtd doesn't appear to support the injection of headlines from rss (nor other restrictions such as 'first item only'). I'v filed an RFE for it, but in the mean time: since you already ship the website dtd, shouldn't we add local modifications that allow new attributes for the 'rss' element such as 'from' and 'to' ? Otherwise modifications that I apply to embedd a 'news' headline into the frontpage won't validate any more (which might not be a problem, if you process the stuff only with 'xsltproc --novalid'). Regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-09-16 20:45:58
|
Stefan Seefeld <sse...@ar...> writes: Stefan, you posted from an address that is not subscribed to this list. > Tony Graham wrote: >>There's a few rough spots -- No Sourceforge logo at present (my fault) >>and still no documentation or development content -- but finally its >>up. The logo is back. I should look at how to get it on every page so we get more brownie points with SourceForge's broken project-ranking system. Please let me know whether or not you can create HTML without having to modify anything. > yeah, I'm still looking into these issues. Unfortunately the docbook-website > xsl stuff only supports rss 1.0 out of the box (sf.net feeds version 2.0), > so > I have to rewrite the templates. Second, the website dtd doesn't appear > to support the injection of headlines from rss (nor other restrictions such > as 'first item only'). > I'v filed an RFE for it, but in the mean time: since you already ship the > website dtd, shouldn't we add local modifications that allow new attributes > for the 'rss' element such as 'from' and 'to' ? I don't "ship the website DTD", but I expect that it's possible to make a local customization that refers to the standard website DTD. This is DocBook (and Norm's handiwork), after all. custom-website.xsl is now back in use, so you could put any XSL customizations in there. > Otherwise modifications that I apply to embedd a 'news' headline into the > frontpage won't validate any more (which might not be a problem, if you > process the stuff only with 'xsltproc --novalid'). It's worse than that: I've started using nXML mode in Emacs, which means I'll need a RNG version of the DTD customization if nXML is going to validate on the fly. Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2004-09-17 05:18:26
|
Tony Graham wrote: > The logo is back. I should look at how to get it on every page so we > get more brownie points with SourceForge's broken project-ranking system. > > Please let me know whether or not you can create HTML without having > to modify anything. you mean by modifying the stylesheets (xslt or css) ? I hope so ! I believe the sf.net logo should go on the bottom of the navigation bar (together with the 'docbook website' logo, similar to http://nwalsh.com/docbook/index.html), so it's just a matter of setting up the xslt templates correctly. >>Otherwise modifications that I apply to embedd a 'news' headline into the >>frontpage won't validate any more (which might not be a problem, if you >>process the stuff only with 'xsltproc --novalid'). > > > It's worse than that: I've started using nXML mode in Emacs, which > means I'll need a RNG version of the DTD customization if nXML is > going to validate on the fly. ok, so we need to adjust the rng and generate the dtd from it if we want to validate. Sounds like a good occasion to get familiar with relaxng :-) Regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-09-20 23:44:25
|
Stefan Seefeld <se...@sy...> writes: > you mean by modifying the stylesheets (xslt or css) ? I hope so ! > I believe the sf.net logo should go on the bottom of the navigation > bar (together with the 'docbook website' logo, similar to > http://nwalsh.com/docbook/index.html), so it's just a matter of > setting up the xslt templates correctly. The version currently in CVS adds some logos at the bottom of the navigation bar. It would look better if a 'rowspan="2"' deep inside the DocBook website stylesheets were 'rowspan="3"', but that was more than I wanted to customise at this time of night. I'll leave the RSS stuff up to you, Stefan. Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2004-10-04 02:15:31
Attachments:
patch
|
Tony Graham wrote: > The version currently in CVS adds some logos at the bottom of the > navigation bar. fine. Though the website doesn't appear to be updated from this new source. I was ready to investigate when I realized that a simple build fixed the site locally. Don't you regenerate the website automatically either per crontab or per checkin ? > It would look better if a 'rowspan="2"' deep inside the DocBook > website stylesheets were 'rowspan="3"', but that was more than I > wanted to customise at this time of night. > > I'll leave the RSS stuff up to you, Stefan. The attached patch replaces the current 'news.html' content by the rss news feed from sf.net. The styling still needs a lot of work, but as that can all be done via css customization, I'll keep that issue open for the moment. Please add some news (on the sf.net) so we can all see the rss feed working :-) I'd still like to see the website give a more accurate impression of the current status of the project. I'm not sure though how feasable that is without more manual work (from your part). Can't the unit tests be run automatically and some status page generated from that ? Just so that occasional visitors that want to watch the progress in terms of feature coverage could get a quick impression. Any suggestions ? Kind regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-10-05 15:42:45
|
Stefan Seefeld <se...@sy...> writes: > Tony Graham wrote: >> The version currently in CVS adds some logos at the bottom of the >> navigation bar. > > fine. Though the website doesn't appear to be updated from this new > source. I was ready to investigate when I realized that a simple build > fixed the site locally. Don't you regenerate the website automatically > either per crontab or per checkin ? SourceForge crontabs are currently disabled, and setting everything up to regenerate the html on checkin might be a bit much to do. The Makefile for the actual DocBook web pages has a better-developed use of ssh for getting pages onto the SourceForge site than the ways that I've played with so far. I didn't update the web site because I was intending to come back and do a better customization than at present. I don't like the fact that the current logos also add extra whitespace in the body of the page. >> It would look better if a 'rowspan="2"' deep inside the DocBook >> website stylesheets were 'rowspan="3"', but that was more than I >> wanted to customise at this time of night. >> I'll leave the RSS stuff up to you, Stefan. > > The attached patch replaces the current 'news.html' content by the > rss news feed from sf.net. The styling still needs a lot of work, Thank you. > but as that can all be done via css customization, I'll keep that > issue open for the moment. > Please add some news (on the sf.net) so we can all see the rss feed > working :-) I've added a new item (partly so you can see what I've been working on when I didn't reply yesterday), but when I generate news.html, all I get is an empty <div>. Any ideas? It shouldn't be a proxy problem, since I'm no longer getting the error message that I used to get before I had my proxy set up. > I'd still like to see the website give a more accurate impression of > the current status of the project. I'm not sure though how feasable that > is without more manual work (from your part). Can't the unit tests > be run automatically and some status page generated from that ? If I'd answered yesterday, I would have said that it would be comparatively easy to generate a version of the test results report that didn't link to the cgi scripts for updating the result summaries. Today, it seems to me that an occasional visitor would be more impressed if there was a graph showing number of tests and percentage of passed tests (increasing) over time. Now, that would be more work. > Just so that occasional visitors that want to watch the progress > in terms of feature coverage could get a quick impression. A good idea, certainly. Would the static test result summary page suffice for starters? Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2004-10-06 00:36:55
|
Tony Graham wrote: > I've added a new item (partly so you can see what I've been working on > when I didn't reply yesterday), but when I generate news.html, all I > get is an empty <div>. Any ideas? Sorry, no. Doing a build locally, I get the content wrapped in '<div class="rss">'. Is it the same <div> you see, just empty ? > It shouldn't be a proxy problem, since I'm no longer getting the error > message that I used to get before I had my proxy set up. may be a <xsl:message> put into the xslt file to 'debug' the process will reveal whether the rss feed could be accessed correctly. > If I'd answered yesterday, I would have said that it would be > comparatively easy to generate a version of the test results report > that didn't link to the cgi scripts for updating the result summaries. > > Today, it seems to me that an occasional visitor would be more > impressed if there was a graph showing number of tests and percentage > of passed tests (increasing) over time. Now, that would be more work. yeah, you'd have to keep a log of the tests. Well, if I'm interested in the evolution of the project, I'd track the 'news'. If I want to get an idea of the 'current status', I'd look at the feature coverage (i.e. both the static matrix you generate manually as well as a possible automatically generated test report). >>Just so that occasional visitors that want to watch the progress >>in terms of feature coverage could get a quick impression. > > > A good idea, certainly. Would the static test result summary page > suffice for starters? Sure. As long as it is not too much out of sync. One thing I hope we could improve over the current website is to make sure the information correctly reflects the current status, i.e. at least the state from the current release, may be even from current 'snapshots'. Having to update lots of different places is annoying for you, so I hope with some scripts we can automatize that. Running the tests should be something that can be done automatically, and so should be the generation of a little report (html, xml, rss, whatever). Regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-10-06 12:19:00
|
(Replying to part of Stefan's message) Stefan Seefeld <se...@sy...> writes: > Tony Graham wrote: >> I've added a new item (partly so you can see what I've been working on >> when I didn't reply yesterday), but when I generate news.html, all I >> get is an empty <div>. Any ideas? > > Sorry, no. Doing a build locally, I get the content wrapped in > '<div class="rss">'. Is it the same <div> you see, just empty ? That is what I see. I'm using the 2.5 version of the website stylesheets. Looking at the stylesheets and the SourceForge RSS, it appears that the stylesheets are expecting the RSS to use namespaced elements and the SourceForge RSS doesn't. SourceForge claims all sorts of wonderful compatibility and testing for correctness for its RSS feeds, so I don't know who's right and who's wrong about namespaces for RSS. The first step would be to copy the template for the <rss> element into the custom stylesheet and tweak the namespaces on the "select" and "match" attributes to make it work. Second step would be to submit a bug report or enhancement request to the DocBook project. Ideally the templates in the rss.xsl file in the website stylesheets would have "name" attributes so you can call the right template from your customisation even if you're working with not-quite-correct RSS. It might also require that the website templates be more relaxed about namespaces (e.g., use "*:title|title" instead of "rss:title") in their "select" attributes since the structure of the RSS is likely to be correct even when the namespace isn't. >> It shouldn't be a proxy problem, since I'm no longer getting the error >> message that I used to get before I had my proxy set up. > > may be a <xsl:message> put into the xslt file to 'debug' the process > will reveal whether the rss feed could be accessed correctly. You get text in the output HTML when you can't access the URL for the RSS. That's what I used to get before I correctly set my http_proxy environment variable. Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2004-10-07 00:42:23
|
Tony Graham wrote: > (Replying to part of Stefan's message) > > Stefan Seefeld <se...@sy...> writes: >>Sorry, no. Doing a build locally, I get the content wrapped in >>'<div class="rss">'. Is it the same <div> you see, just empty ? > > > That is what I see. > > I'm using the 2.5 version of the website stylesheets. huh ? The first statement inside the custom-website.xsl file reads <xsl:import href="http://docbook.sourceforge.net/release/website/2.4.1/xsl/tabular.xsl"/> Are you not using this file ? But anyways, even if I replace '2.4.1' there by '2.5.0' I get a 'correct' news listing. > Looking at the stylesheets and the SourceForge RSS, it appears that > the stylesheets are expecting the RSS to use namespaced elements and > the SourceForge RSS doesn't. yeah, you are talking about the 'rss.xsl' file that's shipped with the db-website xsl distribution, right ? That appears indeed to be written for rss 1.0, while sf.net provides rss 2.0 feeds. That's why I don't use the xsl templates from Norm, but my own, which don't use the rss namespace. I'm a bit lost now. Let me try on sf.net... > SourceForge claims all sorts of wonderful compatibility and testing > for correctness for its RSS feeds, so I don't know who's right and > who's wrong about namespaces for RSS. the docbook website xsl says it provides support for rss 1.0 (0.9x) feeds, while sf.net provides rss 2.0 feeds. They may both be correct. > The first step would be to copy the template for the <rss> element > into the custom stylesheet and tweak the namespaces on the "select" > and "match" attributes to make it work. I thought that was what I had been doing all the time :-) Is it possible that you forgot to apply the patch to the custom-website.xsl file ? > Second step would be to submit a bug report or enhancement request to > the DocBook project. Yeah, I did that some weeks ago. Regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-09-17 09:14:54
|
Stefan Seefeld <se...@sy...> writes: > Tony Graham wrote: >> The logo is back. I should look at how to get it on every page so we >> get more brownie points with SourceForge's broken project-ranking system. >> Please let me know whether or not you can create HTML without having >> to modify anything. > > you mean by modifying the stylesheets (xslt or css) ? I hope so ! > I believe the sf.net logo should go on the bottom of the navigation > bar (together with the 'docbook website' logo, similar to > http://nwalsh.com/docbook/index.html), so it's just a matter of > setting up the xslt templates correctly. My thoughts exactly, even down to the inclusion of the docbook website logo. It should just need an addition to custom-website.xsl. >>>Otherwise modifications that I apply to embedd a 'news' headline into the >>>frontpage won't validate any more (which might not be a problem, if you >>>process the stuff only with 'xsltproc --novalid'). >> It's worse than that: I've started using nXML mode in Emacs, which >> means I'll need a RNG version of the DTD customization if nXML is >> going to validate on the fly. > > ok, so we need to adjust the rng and generate the dtd from it if we > want to validate. Sounds like a good occasion to get familiar with > relaxng :-) Well-formed is good enough for starters. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-06 15:30:17
Attachments:
index.html
|
Stefan Seefeld <se...@sy...> writes: ... >>>Just so that occasional visitors that want to watch the progress >>>in terms of feature coverage could get a quick impression. >> A good idea, certainly. Would the static test result summary page >> suffice for starters? > > Sure. As long as it is not too much out of sync. One thing I hope we > could improve over the current website is to make sure the information > correctly reflects the current status, i.e. at least the state from > the current release, may be even from current 'snapshots'. Having to > update lots of different places is annoying for you, so I hope with > some scripts we can automatize that. > Running the tests should be something that can be done automatically, > and so should be the generation of a little report (html, xml, rss, whatever). I'm attaching a copy of the current summary page. The tests are run and the report is generated using a combination of shell scripts, Perl scripts, and XSLT stylesheets. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-07 01:53:02
|
Stefan Seefeld <se...@sy...> writes: > Tony Graham wrote: >> (Replying to part of Stefan's message) >> Stefan Seefeld <se...@sy...> writes: > >>>Sorry, no. Doing a build locally, I get the content wrapped in >>>'<div class="rss">'. Is it the same <div> you see, just empty ? >> That is what I see. >> I'm using the 2.5 version of the website stylesheets. > > huh ? The first statement inside the custom-website.xsl file reads > > <xsl:import href="http://docbook.sourceforge.net/release/website/2.4.1/xsl/tabular.xsl"/> That's what's in the catalog for the DocBook website files that I downloaded, so I used that. > Are you not using this file ? But anyways, even if I replace '2.4.1' there by '2.5.0' > I get a 'correct' news listing. And there's a reason for that: as you surmised, I had missed your custom-stylesheet.xsl patch. It works for me now. Thank you and sorry for the mix-up. ... >> The first step would be to copy the template for the <rss> element >> into the custom stylesheet and tweak the namespaces on the "select" >> and "match" attributes to make it work. > > I thought that was what I had been doing all the time :-) > Is it possible that you forgot to apply the patch to the custom-website.xsl file ? > >> Second step would be to submit a bug report or enhancement request to >> the DocBook project. > > Yeah, I did that some weeks ago. I'm glad that we think alike in this. I think I would have done better if my mailer hadn't inlined both of your patches one after the other. Sorry about that. The patch is applied and checked in, and the website has been updated. We now have multitudinous logos and, more importantly, RSS. Thank you for that. Regards, Tony. |
×
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