[jira] Commented: (FOR-592) Pelt skin not HTML 4.01 compliant
[ http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317380 ] Gavin commented on FOR-592: --- Ok , Thanks Guys for the info, Now subscribed to the dev list. Looking through some archives I see it has been brought up before ( http://www.mail-archive.com/dev@forrest.apache.org/msg02334.html) though I dont see a solution proposed anywhere. I will get up to speed on i18n and look at some of the suggestions above. Thanks Gav... Pelt skin not HTML 4.01 compliant - Key: FOR-592 URL: http://issues.apache.org/jira/browse/FOR-592 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.7, 0.8-dev Reporter: Manuel Mall Fix For: 0.8-dev Just go to the Forrest home page and click the HTML 4.01 Compliance button. The page doesn't validate. Other sites, e.g. Apache FOP, created with the same skin have the same problem. One issue I could identify is that in the site2xhtml.xsl there are tags like: input type=submit value=Search name=Search i18n:attr=value/. The 'i18n:attr=value' bit creates a non HTML 4.01 compliant attribute. Other problems are related to Javascript not being escaped correctly, e.g. document.write(textLast Published:/text + document.lastModified); should be written as document.write(textLast Published:\/text + document.lastModified); I assume a requirement of being allowed to put the W3C HTML 4.01 Compliant logo on the site is that the pages correctly validate. Pages based on this skin don't validate but do carry the logo. Sounds like a problem to me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-604) The document-v* warning element does not get rendered properly
[
http://issues.apache.org/jira/browse/FOR-604?page=comments#action_12317898 ]
Gavin commented on FOR-604:
---
Ok, I have made the changes needed. You can view it in action, I have uploaded
a basic site and at http://apache.minitutorials.com/samples/sample.html you can
see the new CSS changes in action.
I am not all that familiar with svn, although it did state that basic.css could
not be diff'd (or something like that)
If somebody wants to explain how I can commit these changes, if I can not then
please paste the following into /pelt/css/basic.css as a replacement for the
code in my earlier message above.
.note, .warning, .fixme {
border: solid black 1px;
margin: 1em 3em;
}
.note .label {
background: #369;
color: white;
font-weight: bold;
padding: 5px 10px;
}
.note .content {
background: #F0F0FF;
color: black;
line-height: 120%;
font-size: 90%;
padding: 5px 10px;
}
.warning .label {
background: #C00;
color: white;
font-weight: bold;
padding: 5px 10px;
}
.warning .content {
background: #FFF0F0;
color: black;
line-height: 120%;
font-size: 90%;
padding: 5px 10px;
}
.fixme .label {
background: #C6C600;
font-weight: bold;
padding: 5px 10px;
}
.fixme .content {
padding: 5px 10px;
}
---
I guess to be consistent then leather-dev/css/basic.css will also need to
be changed the same way. I will load leather-dev and make the changes,
making sure that it does not break anything else and then post back here.
Is there anything else I need to do here, doc changes ?
Gav...
The document-v* warning element does not get rendered properly
--
Key: FOR-604
URL: http://issues.apache.org/jira/browse/FOR-604
Project: Forrest
Type: Bug
Versions: 0.8-dev
Reporter: David Crossley
Fix For: 0.8-dev
Attachments: 604-screenshot.png
The warning element is rendered differently to the note element. Perhaps
it only happens with the pelt skin - not yet verified. See screenshot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-605) CSS enhancements needed for MOTD area inside Table of Contents
[ http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12317899 ] Gavin commented on FOR-605: --- I removed the comment tags from the motd in /forrest/site-author/skinconf.xml but it has made no difference. Can you tell me how to enable motd so I can check it out. Looking at http://forrest.apache.org/pluginDocs/plugins_0_80/index.html where it displays correctly it is a width problem somewhere. Due to long URL description links on pages that have motd also, this would probably be unresolvable with motd in its current position, CSS or not. Moving motd above or below might be a better idea, but I'll have a play and let you see what I come up with. Gav... CSS enhancements needed for MOTD area inside Table of Contents -- Key: FOR-605 URL: http://issues.apache.org/jira/browse/FOR-605 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 605-screenshot.png The Message of the Day (MOTD) facility inserts a panel at the top right of the Table of Contents (ToC). However this panel interferes with the flow of text in the ToC, forcing items to be line-wrapped to a narrow width. The MOTD is not properly implemented with CSS, probably needs its own definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-604) The document-v* warning element does not get rendered properly
[ http://issues.apache.org/jira/browse/FOR-604?page=all ] Gavin updated FOR-604: -- Attachment: basic.css.diff The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png, basic.css.diff The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-604) The document-v* warning element does not get rendered properly
[ http://issues.apache.org/jira/browse/FOR-604?page=comments#action_12317907 ] Gavin commented on FOR-604: --- I have attatched basic.css.diff for inclusion. Thanks Gav... The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png, basic.css.diff The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-578) i18n working only for menus/tabs, not document
[ http://issues.apache.org/jira/browse/FOR-578?page=comments#action_12318698 ] Gavin commented on FOR-578: --- Just to confirm that using index.es.xml does work as expected. There may be confusion for some with this naming convension because when looking in the /translations/ folder for examples the naming convension is to use the underscore , such as :- tabs_es.xml menu_es.xml So trying to use index_es.xml would seem to be the natural course of action. I believe naming standards are being reviewed ? As Juan stated, using index.es.xml does work, have you now tried this sjuir ? Should this issue now be closed. Gav... i18n working only for menus/tabs, not document -- Key: FOR-578 URL: http://issues.apache.org/jira/browse/FOR-578 Project: Forrest Type: Bug Components: Core operations Versions: 0.7 Environment: MacOS X 10.4.2, Java 1.4.2 Reporter: Sjur N. Moshagen Assignee: Juan Jose Pablos Here's the steps I took: - Installed Forrest 0.7 - seeded a new project - turned on i18n in forrest.properties - added index_es.xml and index_en.xml (besides the existing index.xml) - started forrest (forrest run) - configured FireFox to have 'es' as first language - opened the newly seeded and i18n-ed site Result: menus and tabs are in 'es', but the index page served is coming from index.xml. Expected result: the page served should be the 'es' version, to adhere to the requested locale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-618) Create issues for items discussed at Apachecon
[ http://issues.apache.org/jira/browse/FOR-618?page=comments#action_12318699 ] Gavin commented on FOR-618: --- I am currently creating these issues, basically just a summary taken from the two posts mentioned. Maybe others could expand on them. Gav... Create issues for items discussed at Apachecon -- Key: FOR-618 URL: http://issues.apache.org/jira/browse/FOR-618 Project: Forrest Type: Task Components: Documentation and website Reporter: Ross Gardler Priority: Critical Fix For: 0.8-dev These two threads describe some of the major issues identified at ApacheCon. We should create an issue for each of the individual items to ensure we don't lose them and to help us in creating a strategy for implenetation: http://marc.theaimsgroup.com/?l=forrest-devm=112277664311322w=2 http://marc.theaimsgroup.com/?l=forrest-devm=112276762506270w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-621) Deciding which view to use
Deciding which view to use -- Key: FOR-621 URL: http://issues.apache.org/jira/browse/FOR-621 Project: Forrest Type: Improvement Components: Views Versions: 0.8-dev Reporter: Gavin Currently deciding which view to use is based on the location of the source file and/or the requested URL. It is suggested that selecting views based on the source documents doctype would be a more powerful approach. This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-624) Scope of views
[ http://issues.apache.org/jira/browse/FOR-624?page=comments#action_12318701 ] Gavin commented on FOR-624: --- For the most part, those that want pdf or text based alternatives, would do so for offline reading, maybe printing them out for later perusal. In these circumstances I agree with Diwaker, menus and tabs that link to other pages have no meaning. However, for the document to remain in context with other documents, a heirarchal position of where that document lies in relation to other related materials may be benefical. There may be some that prefer reading from pdfs, but would still like to be able to click on a link to related information, some of which would be in a menu or tab. Inline src's should remain as a quick route to related materials, this can be turned off for a print friendly format vias CSS. I dont think text based output would benefit from menus or tabs. We need to consider for disabed and/or visually impaired users that would benefit from a text based layout but still have the need for navigational elements. Gav... Scope of views -- Key: FOR-624 URL: http://issues.apache.org/jira/browse/FOR-624 Project: Forrest Type: Improvement Components: Views Versions: 0.8-dev Reporter: Gavin Diwaker has questioned whether views are applicable to other output formats such as text and pdf, observing that things like menus and tabs are not relevant in those formats. Ross added that many contracts are relevant, especially those that add content nuggets. Also relevent, the ability to alter the layout of a text rendering as an example is as important as altering the format of an HTML page. This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-622) Packaging of views and themes
Packaging of views and themes - Key: FOR-622 URL: http://issues.apache.org/jira/browse/FOR-622 Project: Forrest Type: Improvement Components: Views Versions: 0.8-dev Reporter: Gavin Priority: Minor It was generally felt (by those at Apachecon) that, once the design is stable, that views should go into core. Contracts to be made re-usable across multiple views by seperate packaging. Possible enabling view inheritence. Themes are (to be) independent of views and contracts. Utilise current extra-css in skinconf to extend CSS in packaged themes. This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-625) Scope of themes
Scope of themes --- Key: FOR-625 URL: http://issues.apache.org/jira/browse/FOR-625 Project: Forrest Type: Improvement Components: Views Versions: 0.8-dev Reporter: Gavin The current skinning system does not allow for skinning of formats other than pdf or html. Themes resolve this shortcoming. Diwaker wondered what a theme for a text document would look like. Ross suggested it could be things like line-wrapping,representation of each heading level, link representation and image handling. See link below for fuller explanation. This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-623) Configuration of views
Configuration of views -- Key: FOR-623 URL: http://issues.apache.org/jira/browse/FOR-623 Project: Forrest Type: Improvement Components: Views Versions: 0.8-dev Reporter: Gavin Possibly too many configuration files for views. Thorsten commented that there are problems with this in the current implementation. This needs exploring and devs with views experience to talk and contribute. Ideas already discussed at ApacheCon will be expanded on dev-list. This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-626) Reusing Cocoon Portal Engine
Reusing Cocoon Portal Engine Key: FOR-626 URL: http://issues.apache.org/jira/browse/FOR-626 Project: Forrest Type: Improvement Components: Views Versions: 0.8-dev Reporter: Gavin A couple of the Forrest devs attended a talk on the Cocoon Portal engine and came away feeling that we should explore leveraging *parts* of this engine in the views implementation. I can see there are a few strong cases for this, the most significant are: (NOTE: I (Ross) did not attend the presentation but I have said a few times that we should look at the Cocoon Portal, so I have some sypathies with this perspective): - The portal engine does what Views is intended to do. It adds more than views needs (such as authentication), but since it is modular we should be able to reuse what we need. - The technique for configuring the portal (or view) has been developed over a period of time and is in use on some excellent sites. In fact the config stuff is one of the major things that changed in the second release of the portal code. In other words, it is more mature. This was not discussed at the views workshop, and so the implications have not been fully explored. This will require some considerable thought. This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-627) Confiuration of Forrest
Confiuration of Forrest --- Key: FOR-627 URL: http://issues.apache.org/jira/browse/FOR-627 Project: Forrest Type: Improvement Components: Core operations Versions: 0.8-dev Reporter: Gavin Forrest's config files, as they stand have reached the end of their useful life. We are now limited in what we can do and views are making many of them redundant anyway. It is therefore proposed that we take this opportunity to simplify the config system. We had a design discussion about this and you can find Nicola's notes in SVN (see the hackathon directory in the etc directory of trunk). Together with the audio of our dicsussions (thanks David) Someone needs to summarise this discussion (Anil has stepped up to the plate on this one). NOTE: For any users thinking (oh no, the next forrest will be hard to upgrade because of fundamental changes in the way it is configured, don't worry. We will (most likely) provide tools to facilitate this upgrade, we will need them ourselves anyway). This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-628) I18n Management
I18n Management --- Key: FOR-628 URL: http://issues.apache.org/jira/browse/FOR-628 Project: Forrest Type: Improvement Components: Other Versions: 0.8-dev Reporter: Gavin There is a problem with the current I18N support for content. At present it is the responsability of the plugin designer to ensure their plugins are I18N compliant. At present none of them are and so only XDocs rendered in HTML will work in an I18N site. Cheche and I (Ross) looked at this. What we wanted to do was make it the responsabillity of core to manage the I18N stuff. We think we may have a solution using locationmaps, but it reqruies a little work on the Locationmap code. Basically, instead of using the I18N generator from Cocoon to resolve the source we would use the locationmap to resolve the correct source file. More on this including candidate code examples from the following link. This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-605) CSS enhancements needed for MOTD area inside Table of Contents
[ http://issues.apache.org/jira/browse/FOR-605?page=all ] Gavin updated FOR-605: -- Attachment: forrest_faq.png I am investigating this, and it seems there is doubled up use of margins and padding in adjacent areas of the stylesheet. For instance the width of a page within #content is #menu + #minitoc-area + #motd-area. All of these specify widths and margins and padding to differing degrees, and some overlap each other. I believe there is room here for much improvement. However, as this screenshot shows, it seems to be a lot better anyway than on Davids screenshot of the same page. We have to factor in resolution settings for different users and the fact you will always get word wrapping at 800x600 when the site is clearly more designed around 1024x762 users. The stylesheets I would say need a good re-vamp and cleanup, there is a mix of using px,em,% when I think probably we should be using % a lot more and px a lot less. CSS enhancements needed for MOTD area inside Table of Contents -- Key: FOR-605 URL: http://issues.apache.org/jira/browse/FOR-605 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 605-screenshot.png, forrest_faq.png The Message of the Day (MOTD) facility inserts a panel at the top right of the Table of Contents (ToC). However this panel interferes with the flow of text in the ToC, forcing items to be line-wrapped to a narrow width. The MOTD is not properly implemented with CSS, probably needs its own definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-650) MOTD Needs to have a working example.
[ http://issues.apache.org/jira/browse/FOR-650?page=all ] Gavin updated FOR-650: -- Attachment: faq.xml.diff This is the faq change to go with the MOTD changes in skinconf. Its just a pointer to where the MOTD is kept and its docs. This example could be enhanced with more code in the future. Let me know if there is a more suitable place for this and I can make the changes if required. MOTD Needs to have a working example. - Key: FOR-650 URL: http://issues.apache.org/jira/browse/FOR-650 Project: Forrest Type: Sub-task Components: Skins (general issues) Versions: 0.8-dev Environment: All Reporter: Gavin Priority: Minor Attachments: faq.xml.diff, skinconf.xml.diff MOTD area example code in skinconf.xml does not work 'out of the box' but requires subtle changes to get it to work. A very brief explanation and pointer should be in the samples/faq to show the way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-650) MOTD Needs to have a working example.
MOTD Needs to have a working example. - Key: FOR-650 URL: http://issues.apache.org/jira/browse/FOR-650 Project: Forrest Type: Sub-task Components: Skins (general issues) Versions: 0.8-dev Environment: All Reporter: Gavin Priority: Minor MOTD area example code in skinconf.xml does not work 'out of the box' but requires subtle changes to get it to work. A very brief explanation and pointer should be in the samples/faq to show the way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-650) MOTD Needs to have a working example.
[ http://issues.apache.org/jira/browse/FOR-650?page=all ] Gavin updated FOR-650: -- Attachment: skinconf.xml.diff Updates MOTD so there is a out of the box working example ready to go. The example also uses a new FAQ entry in faq.xml to help show the way. MOTD Needs to have a working example. - Key: FOR-650 URL: http://issues.apache.org/jira/browse/FOR-650 Project: Forrest Type: Sub-task Components: Skins (general issues) Versions: 0.8-dev Environment: All Reporter: Gavin Priority: Minor Attachments: skinconf.xml.diff MOTD area example code in skinconf.xml does not work 'out of the box' but requires subtle changes to get it to work. A very brief explanation and pointer should be in the samples/faq to show the way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-605) CSS enhancements needed for MOTD area inside Table of Contents
[ http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12320258 ] Gavin commented on FOR-605: --- I am now working on the CSS and will patch and go as I progress, this MOTD issue will get sorted as a side effect of the revamp. CSS enhancements needed for MOTD area inside Table of Contents -- Key: FOR-605 URL: http://issues.apache.org/jira/browse/FOR-605 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 605-screenshot.png, forrest_faq.png The Message of the Day (MOTD) facility inserts a panel at the top right of the Table of Contents (ToC). However this panel interferes with the flow of text in the ToC, forcing items to be line-wrapped to a narrow width. The MOTD is not properly implemented with CSS, probably needs its own definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-650) MOTD Needs to have a working example.
[ http://issues.apache.org/jira/browse/FOR-650?page=all ] Gavin updated FOR-650: -- Attachment: faq.xml.diff Sorry, last update invalidated the xml due to duplicate id name (motd), renamed second id to motd1. MOTD Needs to have a working example. - Key: FOR-650 URL: http://issues.apache.org/jira/browse/FOR-650 Project: Forrest Type: Sub-task Components: Skins (general issues) Versions: 0.8-dev Environment: All Reporter: Gavin Priority: Minor Fix For: 0.8-dev Attachments: faq.xml.diff, faq.xml.diff, skinconf.xml.diff MOTD area example code in skinconf.xml does not work 'out of the box' but requires subtle changes to get it to work. A very brief explanation and pointer should be in the samples/faq to show the way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-652) CSS Style Sheets need cleanup and optimization
CSS Style Sheets need cleanup and optimization -- Key: FOR-652 URL: http://issues.apache.org/jira/browse/FOR-652 Project: Forrest Type: Improvement Components: Skins (general issues) Versions: 0.8-dev Environment: All, Needs to make sure look and feel are the same in multiple browsers, e.g. IE6, Mozilla, Firefox, Camino, Konqeror. Reporter: Gavin The current CSS implementation needs a bit of a cleanup, some tweaking and optimization. It needs to be improved and some styles converted to % in order to cater for different browsers and user resolutions. A more fluid design needs to be the outcome. The overall style and look and feel of the current pelt skin is to largely remain the same where possible whilst implementing these improvements. The style sheets are to remain CSS1 valid and aim for CSS2 valid. When XHTML2 is implemented perhaps CSS3 can be achieved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-652) CSS Style Sheets need cleanup and optimization
[ http://issues.apache.org/jira/browse/FOR-652?page=all ] Gavin updated FOR-652: -- Attachment: screen.css.diff A start at making for a more fluid design. Some minor changes to improve fluidity. CSS Style Sheets need cleanup and optimization -- Key: FOR-652 URL: http://issues.apache.org/jira/browse/FOR-652 Project: Forrest Type: Improvement Components: Skins (general issues) Versions: 0.8-dev Environment: All, Needs to make sure look and feel are the same in multiple browsers, e.g. IE6, Mozilla, Firefox, Camino, Konqeror. Reporter: Gavin Attachments: screen.css.diff The current CSS implementation needs a bit of a cleanup, some tweaking and optimization. It needs to be improved and some styles converted to % in order to cater for different browsers and user resolutions. A more fluid design needs to be the outcome. The overall style and look and feel of the current pelt skin is to largely remain the same where possible whilst implementing these improvements. The style sheets are to remain CSS1 valid and aim for CSS2 valid. When XHTML2 is implemented perhaps CSS3 can be achieved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-605) CSS enhancements needed for MOTD area inside Table of Contents
[ http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12320349 ] Gavin commented on FOR-605: --- FOR 652 has been created for general CSS enhancements. The first enhancement of FOR 652 has been uploaded, if applied please see if the MOTD changes as part of it , are acceptable as a fix for this issue. CSS enhancements needed for MOTD area inside Table of Contents -- Key: FOR-605 URL: http://issues.apache.org/jira/browse/FOR-605 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 605-screenshot.png, forrest_faq.png The Message of the Day (MOTD) facility inserts a panel at the top right of the Table of Contents (ToC). However this panel interferes with the flow of text in the ToC, forcing items to be line-wrapped to a narrow width. The MOTD is not properly implemented with CSS, probably needs its own definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-655) Create sample document for XHTML2 subset
[ http://issues.apache.org/jira/browse/FOR-655?page=comments#action_12322690 ] Gavin commented on FOR-655: --- I have updated http://apache.minitutorials.com/xhtml2.html . I have also created an xml version at http://apache.minitutorials.com/xhtml2.xml . Both still need some finishing off. Create sample document for XHTML2 subset Key: FOR-655 URL: http://issues.apache.org/jira/browse/FOR-655 Project: Forrest Type: Sub-task Versions: 0.8-dev Reporter: Ross Gardler Fix For: 0.8-dev Define the set of XHTML2 modules that will be used and document those by example. See discussion in thread: Re: XHTML2 - let's do it! http://marc.theaimsgroup.com/?t=11248949717 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-655) Create sample document for XHTML2 subset
[ http://issues.apache.org/jira/browse/FOR-655?page=all ] Gavin updated FOR-655: -- Attachment: xhtml2_subset.xml.diff I have added all the rest of the sections mentioned in NKB's 'XHTML- lets do it!' mail. I have populated most of these new sections with content. There is still more content and more examples to come soon. I have added classes and id attributes, these need confirming or changing for the stylesheet. Create sample document for XHTML2 subset Key: FOR-655 URL: http://issues.apache.org/jira/browse/FOR-655 Project: Forrest Type: Sub-task Versions: 0.8-dev Reporter: Ross Gardler Fix For: 0.8-dev Attachments: xhtml2_subset.xml.diff Define the set of XHTML2 modules that will be used and document those by example. See discussion in thread: Re: XHTML2 - let's do it! http://marc.theaimsgroup.com/?t=11248949717 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-680) The jspwiki parser renders nested lists invalid
[ http://issues.apache.org/jira/browse/FOR-680?page=comments#action_12330806 ] Gavin commented on FOR-680: --- Hmm, that looks fine to me. You can not nest ul ol nl etc inside of li. li however must be inside of one of the above. second level nesting etc is the same, ul can go inside ul etc but not li I can not see anywhere in the dtds or forrest document-v11.* where this is any different. The jspwiki parser renders nested lists invalid --- Key: FOR-680 URL: http://issues.apache.org/jira/browse/FOR-680 Project: Forrest Type: Bug Components: Plugin: Wiki Versions: 0.7 Environment: MacOS X 10.4.2, Java 1.4.2 Reporter: Sjur N. Moshagen Lists within lists are parsed into an invalid structure. The following input: !!!Test title Test list: * li1 * li2 ** li2a ** li2b ** li2c * li3 comes out as the following xml: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN document-v11.dtd document header titletest/title /header body section titleTest title/title pTest list: /p ul lili1 /li lili2 /li ul lili2a /li lili2b /li lili2c /li /ul lili3 /li /ul /section /body /document Note that the inner ul is not within the preceding li as required by the dtd, but inserted between to lis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-694) Use locationmap in revisions.xmap
[ http://issues.apache.org/jira/browse/FOR-694?page=all ] Gavin updated FOR-694: -- Attachment: revisions.xmap.diff I have changed what I can see, please check. I note in this file a comment reads : Example URL: http://localhost:/community/howto/xmlform/howto-xmlform.xml I guess this is out of date now. Gav... Use locationmap in revisions.xmap - Key: FOR-694 URL: http://issues.apache.org/jira/browse/FOR-694 Project: Forrest Type: Sub-task Reporter: Ross Gardler Fix For: 0.8-dev Attachments: revisions.xmap.diff We need to modify all xmap files to use the locationmap. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-705) Target of LocationMap rewriteDemo causes build failure when target not available
Target of LocationMap rewriteDemo causes build failure when target not available Key: FOR-705 URL: http://issues.apache.org/jira/browse/FOR-705 Project: Forrest Type: Bug Components: Locationmap Versions: 0.8-dev Reporter: Gavin Build fails when given target URL of rewriteDemo is not available (site down, no longer exists, incorrect URL typing etc). For various reasons given in [1] and [2] this default feature should remain but alternative options should be made available. Possible solutions given in [3] [1] http://marc.theaimsgroup.com/?l=forrest-devm=112826350500282 [2] http://marc.theaimsgroup.com/?l=forrest-devm=11270994920771 [3] http://marc.theaimsgroup.com/?l=forrest-devm=112859428219336w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-680) The jspwiki parser renders nested lists invalid
[ http://issues.apache.org/jira/browse/FOR-680?page=comments#action_12331646 ] Gavin commented on FOR-680: --- Looking at the source of [1] shows that jspwiki does normally created nested bullets etc correctly, so I guess it is in the way we have implemented it. Just got to find out where this happens, if anyone has any clues please let me know, in the mean time grep is my friend. [1] - http://www.jspwiki.org/wiki/TextFormattingRules#section-TextFormattingRules-BulletedLists The jspwiki parser renders nested lists invalid --- Key: FOR-680 URL: http://issues.apache.org/jira/browse/FOR-680 Project: Forrest Type: Bug Components: Plugin: Wiki Versions: 0.7 Environment: MacOS X 10.4.2, Java 1.4.2 Reporter: Sjur N. Moshagen Lists within lists are parsed into an invalid structure. The following input: !!!Test title Test list: * li1 * li2 ** li2a ** li2b ** li2c * li3 comes out as the following xml: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN document-v11.dtd document header titletest/title /header body section titleTest title/title pTest list: /p ul lili1 /li lili2 /li ul lili2a /li lili2b /li lili2c /li /ul lili3 /li /ul /section /body /document Note that the inner ul is not within the preceding li as required by the dtd, but inserted between to lis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-680) The jspwiki parser renders nested lists invalid
[ http://issues.apache.org/jira/browse/FOR-680?page=comments#action_12331647 ] Gavin commented on FOR-680: --- Ok, I see the problem I think , In %forrest_home\plugins\org.apache.forrest.plugin.input.wiki\resources\chaperon\stylesheets\wiki2xdoc.xsl Bulleted Lists whether at Level 1, 2 or 3 are all put into ul/ul All Bulleted List items are put into lili whether at level 1,2 or 3. Example :- xsl:template match=st:bulletedlist1 mode=paragraph ul xsl:apply-templates select=st:bulletedlistitem1|st:bulletedlist2/ /ul /xsl:template xsl:template match=st:bulletedlistitem1 li xsl:apply-templates select=st:textsequence/st:textblock/*/ /li /xsl:template xsl:template match=st:bulletedlist2 ul xsl:apply-templates select=st:bulletedlistitem2|st:bulletedlist3/ /ul /xsl:template I will have a go at correcting this. The jspwiki parser renders nested lists invalid --- Key: FOR-680 URL: http://issues.apache.org/jira/browse/FOR-680 Project: Forrest Type: Bug Components: Plugin: Wiki Versions: 0.7 Environment: MacOS X 10.4.2, Java 1.4.2 Reporter: Sjur N. Moshagen Lists within lists are parsed into an invalid structure. The following input: !!!Test title Test list: * li1 * li2 ** li2a ** li2b ** li2c * li3 comes out as the following xml: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN document-v11.dtd document header titletest/title /header body section titleTest title/title pTest list: /p ul lili1 /li lili2 /li ul lili2a /li lili2b /li lili2c /li /ul lili3 /li /ul /section /body /document Note that the inner ul is not within the preceding li as required by the dtd, but inserted between to lis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-696) Use locationmap in tabs.xmap
[ http://issues.apache.org/jira/browse/FOR-696?page=all ] Gavin updated FOR-696: -- Attachment: tabs.xmap.diff Hopefully naming convension correct, I needed to update locationmap-transforms.xml to add as there didnt seem to be a match. Use locationmap in tabs.xmap Key: FOR-696 URL: http://issues.apache.org/jira/browse/FOR-696 Project: Forrest Type: Sub-task Reporter: Ross Gardler Attachments: tabs.xmap.diff -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-696) Use locationmap in tabs.xmap
[ http://issues.apache.org/jira/browse/FOR-696?page=all ] Gavin updated FOR-696: -- Attachment: locationmap-transforms.xml.diff Use locationmap in tabs.xmap Key: FOR-696 URL: http://issues.apache.org/jira/browse/FOR-696 Project: Forrest Type: Sub-task Reporter: Ross Gardler Attachments: locationmap-transforms.xml.diff, tabs.xmap.diff -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-696) Use locationmap in tabs.xmap
[ http://issues.apache.org/jira/browse/FOR-696?page=all ] Gavin updated FOR-696: -- Attachment: tabs.xmap.diff2 Missed a } from the first one, this fixes the first diff. Use locationmap in tabs.xmap Key: FOR-696 URL: http://issues.apache.org/jira/browse/FOR-696 Project: Forrest Type: Sub-task Reporter: Ross Gardler Attachments: locationmap-transforms.xml.diff, tabs.xmap.diff, tabs.xmap.diff2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-743) siteinfo-feedback contract returns multiple nested ahref declarations.
siteinfo-feedback contract returns multiple nested ahref declarations. Key: FOR-743 URL: http://issues.apache.org/jira/browse/FOR-743 Project: Forrest Type: Bug Components: Views Versions: 0.8-dev Reporter: Gavin This description taken from http://marc.theaimsgroup.com/?l=forrest-devm=113313199327182w=2 3. index.fv provided with /samples/ has this for the footer feedback contract :- forrest:contract name=siteinfo-feedback forrest:properties contract=siteinfo-feedback forrest:property name=siteinfo-feedback feedback to=[EMAIL PROTECTED] href=mailto:[EMAIL PROTECTED]#160; Send feedback about the website to: /feedback /forrest:property /forrest:properties /forrest:contract The code this produces is :- div id=siteinfo-feedback Send feedback about the website to: a id=feedbackto href=mailto:[EMAIL PROTECTED] samples/index.htmla href=mailto:[EMAIL PROTECTED]webmaster at foo.com/a/a/div which is incorrect nesting of the a element and also multiple declarations of the href and mailto when there is no need. Should this not read div id=siteinfo-feedback Send feedback about the website to: a id=feedbackto href=mailto:[EMAIL PROTECTED] samples/index.html/a/div Where is the extra.. a href=mailto:[EMAIL PROTECTED]webmaster at foo.com/a ..coming from ?? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-744) Inline CSS produces extra unwanted url references - Views V2 -
Inline CSS produces extra unwanted url references - Views V2 -
--
Key: FOR-744
URL: http://issues.apache.org/jira/browse/FOR-744
Project: Forrest
Type: Bug
Components: Views
Versions: 0.8-dev
Reporter: Gavin
Taken from http://marc.theaimsgroup.com/?l=forrest-devm=113313199327182w=2
5. In the inline CSS of the /samples/index.html page there is produced a
wierd and non-compliant use of code when ever the background-image url is
used.
For instance multiple times there are instances of :-
#header .round-top-left-small {
background-image:
url(../themes/images/roundcorner-t-l-5-bgFF-stroke00-fg00.png);a
href=../themes/images/roundcorner-t-l-5-bgFF-stroke00-fg00.png
/a;
background-repeat: no-repeat;
background-position: top left;
}
This occurs on every instance of when an image is referenced using the
background-image: url .
The extra :-
a
href=../themes/images/roundcorner-t-l-5-bgFF-stroke00-fg00.png
/a;
is neither required nor compliant.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (FOR-781) Coat Theme CSS Enhancements
Coat Theme CSS Enhancements --- Key: FOR-781 URL: http://issues.apache.org/jira/browse/FOR-781 Project: Forrest Type: Improvement Components: Skins (general issues) Versions: 0.8-dev Reporter: Gavin Priority: Minor Attachments: coat.css.diff Ross has begun work on a Coat Theme. Currently in forrest_home\whiteboard\plugins\org.apache.forrest.theme.Coat . This Issue is created to put CSS enhancements to. As well as curing the footer problem mentioned on list, this patch also alters the left navigation to make it look more like http://apache.org. More to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-790) Head part is included as many times a contract is used
[
http://issues.apache.org/jira/browse/FOR-790?page=comments#action_12362854 ]
Gavin commented on FOR-790:
---
This can be avoided by using onFocus inline for Form values instead of calling
the getBlank.js script.
A generic e.g to adapt :-
divlabel for=usernameUsername/label
input name=username type=text id=username value=Username
title=Enter your Username here onfocus=if(this.value == 'Username')
this.value = ' '; /
/div
Not sure how many forms we have, not many I know of, so simple to do.
If however, it is prefered to keep the getBlank.js script, then a check to see
if the getBlank.js has already been inlcuded should do the trick.
Let me know which way is preferred and I'll create a patch.
Gav...
Head part is included as many times a contract is used
--
Key: FOR-790
URL: http://issues.apache.org/jira/browse/FOR-790
Project: Forrest
Type: Improvement
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: Cyriaque Dupoirieux
Priority: Minor
Fix For: 0.8-dev
Example :
In the search contract - which is used twice in the pelt theme (as locations
examples), the getBlank.js file is, also, included twice.
forrest:content
forrest:part xpath=/html/head
script type=text/javascript language=javascript
src={$root}themes/getBlank.js#160;/script
/forrest:part
...
/forrest:content
gives :
script language=javascript src=../themes/getBlank.js
type=text/javascript /script
script language=javascript src=../themes/getBlank.js
type=text/javascript /script
in the head part.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365194 ] Gavin commented on FOR-803: --- Using Dispatcher rc1 I can see no performance lags when doing a forrest run,forrest site,forrest -f bot.xml . If anything, things are slightly quicker now. It is only a sample site though with few pages so the difference may be more noticable on a larger site. I have no previous records of a site-author build so someone else needs to check that. Gav... Profile new dispatcher plugins -- Key: FOR-803 URL: http://issues.apache.org/jira/browse/FOR-803 Project: Forrest Type: Sub-task Components: Dispatcher (aka views) Reporter: Thorsten Scherler http://marc.theaimsgroup.com/?t=11383024561 El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió: A while ago i noticed big performance problems. e.g. building site-author took four times as long. We need to do at least basic profiling. http://marc.theaimsgroup.com/?l=forrest-devm=113845026822103w=2 David was talking about v2 but this needs to be verified with the refactored version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-811) shine and polish the pelt theme so that it closely resembles the pelt skin
[ http://issues.apache.org/jira/browse/FOR-811?page=all ] Gavin updated FOR-811: -- Attachment: pelt.fv.diff pelt.screen.css.diff siteinfo-credits.ft.diff 3 Attatchments go a way towards addressing this issue. There are still some minor adjustments to make, however what has been done needs checking first. The CSS file pelt.basic.css has been done away with and any applicable CSS from it transferred into pelt.screen.css. Some changes were required also to pelt.fv and siteinfo-credits.fv. Please check Test, I have tested these files using a dispatcher enabled seed-sample site using forrest run. shine and polish the pelt theme so that it closely resembles the pelt skin -- Key: FOR-811 URL: http://issues.apache.org/jira/browse/FOR-811 Project: Forrest Type: Sub-task Components: Skins (general issues), Dispatcher (aka views) Reporter: David Crossley Attachments: pelt.fv.diff, pelt.screen.css.diff, siteinfo-credits.ft.diff So that they can just switch from pelt skin to pelt theme and not get any surprises, e.g. pelt skin' has no xml doc link. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-831) Dispatcher Build, Clean and Deploy Batch File for Windows
Dispatcher Build, Clean and Deploy Batch File for Windows - Key: FOR-831 URL: http://issues.apache.org/jira/browse/FOR-831 Project: Forrest Type: Improvement Components: Dispatcher (aka views) Versions: 0.8-dev Reporter: Gavin Priority: Trivial Attachments: builddispatcher.bat This simple batch file, mentioned I would do this at the recent Forrest Friday, basically just does all the building,cleaning and deploying of plugins neccessary for using the Dispatcher. A time saver, if nothing else. Put it in the %FORREST_HOME%/main/ directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-820) tools/forrestdoc needs general tidy up and some documentation to encourage its use
[ http://issues.apache.org/jira/browse/FOR-820?page=comments#action_12370503 ] Gavin commented on FOR-820: --- But we have to get it working yet, or did I miss that bit? Around Line 667 of Pass2.java is being pointed to as the culprit, but as ever with programming, the cause could be earlier on, I don't know enough about it to know. return ((String) o1).compareTo(o2); Looks ok, but other files skipped during compilation may be having an effect. Just a guess, if someone can look to get it working, then we can work on this issue of tidy up doc creation. tools/forrestdoc needs general tidy up and some documentation to encourage its use -- Key: FOR-820 URL: http://issues.apache.org/jira/browse/FOR-820 Project: Forrest Type: Bug Components: Documentation and website, Forrestdoc Versions: 0.8-dev Reporter: David Crossley Priority: Minor tools/forrestdoc needs general tidy up and some documentation to encourage its use. See collection of some links in http://marc.theaimsgroup.com/?l=forrest-devm=114082527806288 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-811) shine and polish the pelt theme so that it closely resembles the pelt skin
[ http://issues.apache.org/jira/browse/FOR-811?page=comments#action_12370517 ] Gavin commented on FOR-811: --- There is a width problem concerning the tables in IE6, they are too wide making the pages scrollable horizontally, it's fine in Firefox. There is a hack in the CSS already to cure this, but appears not to be working, I will investigate and then provide a patch. This issue should then be closed so as to not hold up FOR-816 as I think everything else looks ok. shine and polish the pelt theme so that it closely resembles the pelt skin -- Key: FOR-811 URL: http://issues.apache.org/jira/browse/FOR-811 Project: Forrest Type: Sub-task Components: Skins (general issues), Dispatcher (aka views) Reporter: David Crossley Attachments: pelt.fv.diff, pelt.screen.css.diff, siteinfo-credits.ft.diff So that they can just switch from pelt skin to pelt theme and not get any surprises, e.g. pelt skin' has no xml doc link. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-831) Dispatcher Build, Clean and Deploy Batch File for Windows
[ http://issues.apache.org/jira/browse/FOR-831?page=all ] Gavin updated FOR-831: -- Attachment: builddispatcher.bat Original file had 'build' , 'build clean' instructions in the wrong order. Now corrected. Dispatcher Build, Clean and Deploy Batch File for Windows - Key: FOR-831 URL: http://issues.apache.org/jira/browse/FOR-831 Project: Forrest Type: Improvement Components: Dispatcher (aka views) Versions: 0.8-dev Reporter: Gavin Priority: Trivial Attachments: builddispatcher.bat, builddispatcher.bat, builddispatcher.bat This simple batch file, mentioned I would do this at the recent Forrest Friday, basically just does all the building,cleaning and deploying of plugins neccessary for using the Dispatcher. A time saver, if nothing else. Put it in the %FORREST_HOME%/etc/ directory. (forrest-trunk/etc/) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-831) Dispatcher Build, Clean and Deploy Batch File for Windows
[ http://issues.apache.org/jira/browse/FOR-831?page=all ] Gavin updated FOR-831: -- Attachment: builddispatcher.bat Updated batch file, original had the order of 'build' , 'build clean' instead of the other way around. Dispatcher Build, Clean and Deploy Batch File for Windows - Key: FOR-831 URL: http://issues.apache.org/jira/browse/FOR-831 Project: Forrest Type: Improvement Components: Dispatcher (aka views) Versions: 0.8-dev Reporter: Gavin Priority: Trivial Attachments: builddispatcher.bat, builddispatcher.bat, builddispatcher.bat This simple batch file, mentioned I would do this at the recent Forrest Friday, basically just does all the building,cleaning and deploying of plugins neccessary for using the Dispatcher. A time saver, if nothing else. Put it in the %FORREST_HOME%/etc/ directory. (forrest-trunk/etc/) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-591) MaxMemory needs increasing
[ http://issues.apache.org/jira/browse/FOR-591?page=comments#action_12371889 ] Gavin commented on FOR-591: --- Another update note : I have just added a comment (to COCOON-1574) to see how they are getting on, if no near time frame for resolving it then maybe this will have to be put back to a 0.9 release. Ralph Goers has replied and said will look at it in the next few days (http://issues.apache.org/jira/browse/COCOON-1574#action_12371833) MaxMemory needs increasing -- Key: FOR-591 URL: http://issues.apache.org/jira/browse/FOR-591 Project: Forrest Type: Bug Components: Core operations Versions: 0.8-dev Reporter: Ross Gardler Priority: Blocker Fix For: 0.8-dev Since the docs restructurng for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site. Does this indicate a memory leak? Does someone have the tools to run some diagnostics? (NB maxmemory has been increased in forrest.properties, if we resolve this issue it should be reduced again) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-713) HTML-to-document.xsl no longer generates an XDoc
[ http://issues.apache.org/jira/browse/FOR-713?page=comments#action_12371890 ] Gavin commented on FOR-713: --- Was wondering if any conversions have been missed (remember the name changes of '2' to '-to-' - html2document becomes html-to-document, and now with lm: should this be html.document) , perhaps references to html2document still exist in the processing, they do certainly in the docs, I will patch the docs. HTML-to-document.xsl no longer generates an XDoc Key: FOR-713 URL: http://issues.apache.org/jira/browse/FOR-713 Project: Forrest Type: Bug Components: Core operations Reporter: Ross Gardler Priority: Blocker Fix For: 0.8-dev html-to-document.xsl no longer converts content to an XDoc. Instead it renders converts documents to XDoc, instead it allows H1, H2 etc. elements to pass through. The result is a page that seems to render correctly and in the single test case I have used it still renders correctly in PDF and Text format. However, this is a backward incompatible change that will break sites that use includes with XPath statements such as /[EMAIL PROTECTED]foo] (sections are no longer created) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-208) Selected 2nd level tabs not highlightet
[ http://issues.apache.org/jira/browse/FOR-208?page=comments#action_12371918 ] Gavin commented on FOR-208: --- Second level tabs look fine now on main forrest.apache.org site, fine in site-author, works fine in seed-sample (although color scheme not matching , the second level tabs do hightlight). Second level tabs also work fine in default Pelt Theme in Dispatcher. Can someone confirm this and then close the Issue if correct. Selected 2nd level tabs not highlightet --- Key: FOR-208 URL: http://issues.apache.org/jira/browse/FOR-208 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.6 Environment: MacOS X 10.3.4, Java 1.4.2 Reporter: Sjur N. Moshagen When there are two levels of tabs, the selected 2nd level tab does not get highlighted, nor are there any other visual or structural clues as to which of the selected tabs are active. This is checked with both the default skin, and with tigris-style. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-834) GenericMarkup strips comments
[
http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12372230 ]
Gavin commented on FOR-834:
---
Possibly related, comments in pelt.fv are causing whitespace in the resultant
output.
In this case though I think the comments are intended for dev use and are not
to be converted or included in the output as comments or otherwise. The
whitespace in place of the comments in the resultant markup are an annoyance
more than anything.
e.g. -
forrest:property name=branding-css-links-input
css url=common.css media=screen rel=alternate stylesheet
theme=common/
css url=leather-dev.css media=screen rel=alternate stylesheet
theme=common/
css url=pelt.screen.css media=screen theme=Pelt/
!-- You can request request specific css, but beware that you need
to use the *.dispatcher.css extension!!!--
!-- FIXME: that is not working ATM in forrest for subdir/bla needs
more testing --
!--css url=#{$getRequest}.dispatcher.css media=screen
theme=Pelt/--
css url=pelt.print.css media=print/
Converts to :-
link href=themes/common.css media=screen rel=alternate stylesheet
title=common type=text/css /
link href=themes/leather-dev.css media=screen rel=alternate
stylesheet title=common type=text/css /
link href=themes/pelt.screen.css media=screen rel=stylesheet
title=Pelt type=text/css /
link href=themes/pelt.print.css media=print rel=stylesheet
title=pelt.print.css type=text/css /
GenericMarkup strips comments
-
Key: FOR-834
URL: http://issues.apache.org/jira/browse/FOR-834
Project: Forrest
Type: Bug
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: paul bolger
Priority: Minor
Comments added to the markup in GenericMarkup are not passed to the output.
This has implications for using server side includes within a Forrest site.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-755) Glossary Input Plugin
[ http://issues.apache.org/jira/browse/FOR-755?page=comments#action_12372779 ] Gavin commented on FOR-755: --- I am working on getting this working, see http://marc.theaimsgroup.com/?t=11438913811r=1w=2 Once done terms for http://issues.apache.org/jira/browse/FOR-639?page= can go in the glossary.xml file. Glossary Input Plugin - Key: FOR-755 URL: http://issues.apache.org/jira/browse/FOR-755 Project: Forrest Type: New Feature Components: Plugins: Potential new Reporter: Ross Gardler Priority: Minor Attachments: glossary-v10(2).dtd, glossary-v10.mod, glossary.xmap, glossary.xml, glossary2document.xsl A glossary plugin that allows us to define terms across a whole site and easily link to them from anywhere would be very useful. I did something like this a long time back (Forrest 0.4) - before plugins were available. The issue has been raised again onlist so this issue is a dumping ground for the relevant files. Someone should bring these up to date and create an input plugin for them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-755) Glossary Input Plugin
[ http://issues.apache.org/jira/browse/FOR-755?page=all ] Gavin updated FOR-755: -- Attachment: org.apache.forrest.plugin.input.glossary.zip Zip file attached. Glossary Input Plugin - Key: FOR-755 URL: http://issues.apache.org/jira/browse/FOR-755 Project: Forrest Type: New Feature Components: Plugins: Potential new Reporter: Ross Gardler Priority: Minor Attachments: glossary-v10(2).dtd, glossary-v10.mod, glossary.xmap, glossary.xml, glossary2document.xsl, org.apache.forrest.plugin.input.glossary.rar, org.apache.forrest.plugin.input.glossary.zip A glossary plugin that allows us to define terms across a whole site and easily link to them from anywhere would be very useful. I did something like this a long time back (Forrest 0.4) - before plugins were available. The issue has been raised again onlist so this issue is a dumping ground for the relevant files. Someone should bring these up to date and create an input plugin for them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ] Gavin updated FOR-639: -- Attachment: glossary.xml.add Not sure you need an .add file, but I did to then create the .diff define terminology for the various aspects of Dispatcher Key: FOR-639 URL: http://issues.apache.org/jira/browse/FOR-639 Project: Forrest Type: Task Components: Dispatcher (aka views), Documentation and website Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev Attachments: glossary.xml.add See the email thread: http://marc.theaimsgroup.com/?t=11227664371 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ] Gavin updated FOR-639: -- Attachment: glossary.xml.diff site.xml.diff glossary-to-document.xsl.diff Glossary File added, not complete but a start. Site.xml changed to accomodate Glossary in 0.80 Versioned Docs section glossary-to-document.xsl changed to tidy up the td's to have a constant width throughout. define terminology for the various aspects of Dispatcher Key: FOR-639 URL: http://issues.apache.org/jira/browse/FOR-639 Project: Forrest Type: Task Components: Dispatcher (aka views), Documentation and website Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev Attachments: glossary-to-document.xsl.diff, glossary.xml.add, glossary.xml.diff, site.xml.diff See the email thread: http://marc.theaimsgroup.com/?t=11227664371 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-756) Citations Plugin
[ http://issues.apache.org/jira/browse/FOR-756?page=comments#action_12374186 ] Gavin commented on FOR-756: --- I have made a start and created the (input) plugin for this, now to configure it. Citations Plugin Key: FOR-756 URL: http://issues.apache.org/jira/browse/FOR-756 Project: Forrest Type: New Feature Components: Plugins: Potential new Reporter: Ross Gardler Priority: Minor Attachments: reference2document.xsl, references-v10.dtd, references-v10.mod, references.xmap, references.xml A plugin to provide a central location for citations across the whole content object would be useful. We could then use a special class of link to create to correct link to the citation page, and report an error if no such citation exists. I did someting like this a long time ago before plugins existed. This issue is a place to put the files I created. We should create a plugin from these files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-858) glossary items with see for other items creates broken links
[ http://issues.apache.org/jira/browse/FOR-858?page=comments#action_12374488 ] Gavin commented on FOR-858: --- The 'see' elements is broken as it relys on the Citations Plugin. This is being worked on currently. 'See' FOR-756 also. glossary items with see for other items creates broken links -- Key: FOR-858 URL: http://issues.apache.org/jira/browse/FOR-858 Project: Forrest Type: Bug Components: Plugin: input.glossary Versions: 0.8-dev Reporter: David Crossley The glossary-to-document.xsl handles the see elements to create links to other items. However this broken and so is commented-out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-595) Hard-coded project name in input.projectinfo plugin
[ http://issues.apache.org/jira/browse/FOR-595?page=comments#action_12374742 ] Gavin commented on FOR-595: --- Looking at the code it looks fixed to me. title xsl:choose xsl:when test=@title!='' xsl:value-of select=@title/ /xsl:when xsl:otherwise xsl:textRelease Notes for Apache Forrest /xsl:textxsl:value-of select=$versionNumber/ /xsl:otherwise /xsl:choose /title ... have you tried putting in your own Title ? If not it will default to Apache Forrest. Hard-coded project name in input.projectinfo plugin --- Key: FOR-595 URL: http://issues.apache.org/jira/browse/FOR-595 Project: Forrest Type: Bug Components: Plugin: input.projectInfo Versions: 0.7 Reporter: fuat ormaci Title of release notes page always reads Release Notes for Apache Forrest X.Y The string Apache Forrest should not be hard-coded in releaseNotes2document.xsl, real project name has to be picked instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-595) Hard-coded project name in input.projectinfo plugin
[ http://issues.apache.org/jira/browse/FOR-595?page=comments#action_12374922 ] Gavin commented on FOR-595: --- I have an idea that may cure this but not sure of the 'how'. What about we create a comment/comment element that when processed by genericMarkup.ft , gets converted into xsl:comment/xsl:comment. Then the final output will render correctly into !-- -- and will work for both comments and SSI commands.? So in the theme.fv file we could have :- forrest:contract name=genericMarkup forrest:property name=genericMarkup hr/ commentThis is a comment/comment /forrest:property /forrest:contract Then we transform this in genericMarkup.ft :- xsl:template match=/ forrest:content forrest:part xsl:copy-of select=$genericMarkup/*/ /forrest:part /forrest:content /xsl:template Now somewhere above we get it to check for comment and transform it into xsl:comment , this is the bit I'm stuck on. Then, hopefully the output file will contain !-- This is a comment -- For SSI the deal is the same, in the theme.fv file we say :- comment#include virtual=/file.inc /comment Which after processing will say:- !--#include virtual=/file.inc -- OR - Is there a way of putting xsl:comment directly into the theme.fv file - I tried it already as is and got :- The prefix xsl for element xsl:comment is not bound , hence the above idea. WDYT ? Hard-coded project name in input.projectinfo plugin --- Key: FOR-595 URL: http://issues.apache.org/jira/browse/FOR-595 Project: Forrest Type: Bug Components: Plugin: input.projectInfo Versions: 0.7 Reporter: fuat ormaci Title of release notes page always reads Release Notes for Apache Forrest X.Y The string Apache Forrest should not be hard-coded in releaseNotes2document.xsl, real project name has to be picked instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-834) GenericMarkup strips comments
[ http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12374923 ] Gavin commented on FOR-834: --- I have an idea that may cure this but not sure of the 'how'. What about we create a comment/comment element that when processed by genericMarkup.ft , gets converted into xsl:comment/xsl:comment. Then the final output will render correctly into !-- -- and will work for both comments and SSI commands.? So in the theme.fv file we could have :- forrest:contract name=genericMarkup forrest:property name=genericMarkup hr/ commentThis is a comment/comment /forrest:property /forrest:contract Then we transform this in genericMarkup.ft :- xsl:template match=/ forrest:content forrest:part xsl:copy-of select=$genericMarkup/*/ /forrest:part /forrest:content /xsl:template Now somewhere above we get it to check for comment and transform it into xsl:comment , this is the bit I'm stuck on. Then, hopefully the output file will contain !-- This is a comment -- For SSI the deal is the same, in the theme.fv file we say :- comment#include virtual=/file.inc /comment Which after processing will say:- !--#include virtual=/file.inc -- OR - Is there a way of putting xsl:comment directly into the theme.fv file - I tried it already as is and got :- The prefix xsl for element xsl:comment is not bound , hence the above idea. WDYT ? GenericMarkup strips comments - Key: FOR-834 URL: http://issues.apache.org/jira/browse/FOR-834 Project: Forrest Type: Bug Components: Dispatcher (aka views) Versions: 0.8-dev Reporter: paul bolger Priority: Minor Comments added to the markup in GenericMarkup are not passed to the output. This has implications for using server side includes within a Forrest site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-595) Hard-coded project name in input.projectinfo plugin
[ http://issues.apache.org/jira/browse/FOR-595?page=all ] Gavin updated FOR-595: -- Sorry, last comment was for FOR-834, can it be removed from this one? Hard-coded project name in input.projectinfo plugin --- Key: FOR-595 URL: http://issues.apache.org/jira/browse/FOR-595 Project: Forrest Type: Bug Components: Plugin: input.projectInfo Versions: 0.7 Reporter: fuat ormaci Title of release notes page always reads Release Notes for Apache Forrest X.Y The string Apache Forrest should not be hard-coded in releaseNotes2document.xsl, real project name has to be picked instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-492) Inconsistent Line Endings in generated sites
[ http://issues.apache.org/jira/browse/FOR-492?page=comments#action_12375069 ] Gavin commented on FOR-492: --- As far as I can see, all lines on Windows from a generated .html file all end with CRLF. Also I see no difference in the way comments are treated as previously mentioned. Example code from an index.html file. Oops, sorry cant paste code - the ^M gets converted to a CRLF !!, I'll attach a file instead. This Wikipedia explains the difference between the 3 main OS versions and their handling. I blame it on CP/M myself :) Inconsistent Line Endings in generated sites Key: FOR-492 URL: http://issues.apache.org/jira/browse/FOR-492 Project: Forrest Type: Bug Components: Core operations Versions: 0.7 Environment: Windows (with or without CYGWIN) Reporter: Ross Gardler Priority: Blocker Fix For: 0.8-dev Sites generated by Forrest have inconsistent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce run forrest site in any site and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-492) Inconsistent Line Endings in generated sites
[ http://issues.apache.org/jira/browse/FOR-492?page=all ] Gavin updated FOR-492: -- Attachment: index.html I wonder how those on other OS will be able to check this anyway, a screen shot may be needed ? Forgot to mention that link : http://en.wikipedia.org/wiki/Line_break Inconsistent Line Endings in generated sites Key: FOR-492 URL: http://issues.apache.org/jira/browse/FOR-492 Project: Forrest Type: Bug Components: Core operations Versions: 0.7 Environment: Windows (with or without CYGWIN) Reporter: Ross Gardler Priority: Blocker Fix For: 0.8-dev Attachments: index.html Sites generated by Forrest have inconsistent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce run forrest site in any site and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-834) GenericMarkup strips comments
[ http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12375100 ] Gavin commented on FOR-834: --- a working solution is provided at http://marc.theaimsgroup.com/?l=forrest-devm=114544554025191w=2 A patch will be available if approved. On another note, the comments being stripped from pelt.fv etc and replaced with whitespace is I believe totally unrelated. GenericMarkup strips comments - Key: FOR-834 URL: http://issues.apache.org/jira/browse/FOR-834 Project: Forrest Type: Bug Components: Dispatcher (aka views) Versions: 0.8-dev Reporter: paul bolger Priority: Minor Comments added to the markup in GenericMarkup are not passed to the output. This has implications for using server side includes within a Forrest site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-834) GenericMarkup strips comments
[ http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12375101 ] Gavin commented on FOR-834: --- a working solution is provided at http://marc.theaimsgroup.com/?l=forrest-devm=114544554025191w=2 A patch will be available if approved. On another note, the comments being stripped from pelt.fv etc and replaced with whitespace is I believe totally unrelated. GenericMarkup strips comments - Key: FOR-834 URL: http://issues.apache.org/jira/browse/FOR-834 Project: Forrest Type: Bug Components: Dispatcher (aka views) Versions: 0.8-dev Reporter: paul bolger Priority: Minor Comments added to the markup in GenericMarkup are not passed to the output. This has implications for using server side includes within a Forrest site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-756) Citations Plugin
[ http://issues.apache.org/jira/browse/FOR-756?page=all ] Gavin updated FOR-756: -- Attachment: org.apache.forrest.plugin.input.citations.zip Working version of Citations Plugin. Tested with 'Ant Test' and used a test site using 'forrest run' and 'forrest site' . All work fine. Citations Plugin Key: FOR-756 URL: http://issues.apache.org/jira/browse/FOR-756 Project: Forrest Type: New Feature Components: Plugins: Potential new Reporter: Ross Gardler Priority: Minor Attachments: org.apache.forrest.plugin.input.citations.zip, reference2document.xsl, references-v10.dtd, references-v10.mod, references.xmap, references.xml A plugin to provide a central location for citations across the whole content object would be useful. We could then use a special class of link to create to correct link to the citation page, and report an error if no such citation exists. I did someting like this a long time ago before plugins existed. This issue is a place to put the files I created. We should create a plugin from these files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-858) glossary items with see for other items creates broken links
[ http://issues.apache.org/jira/browse/FOR-858?page=comments#action_12375117 ] Gavin commented on FOR-858: --- Now that I have finished the Citations Plugin, I think there is a bit of misunderstanding on the use of the 'see' element and 'cite'. It looks to me like the 'see' element is in fact to be used in-document, that is provide a href link to an anchor in the same Glossary document. 'See' therefore refers to another Glossary Item. It is in fact 'cite' that is to reference the external citations.xml document. That said, the 'see' element is still broken, but we just need to make it reference an anchor rather than an external page as it tries to currently. glossary items with see for other items creates broken links -- Key: FOR-858 URL: http://issues.apache.org/jira/browse/FOR-858 Project: Forrest Type: Bug Components: Plugin: input.glossary Versions: 0.8-dev Reporter: David Crossley The glossary-to-document.xsl handles the see elements to create links to other items. However this broken and so is commented-out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ] Gavin updated FOR-639: -- Component: Plugin: input.glossary define terminology for the various aspects of Dispatcher Key: FOR-639 URL: http://issues.apache.org/jira/browse/FOR-639 Project: Forrest Type: Task Components: Dispatcher (aka views), Documentation and website, Plugin: input.glossary Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev Attachments: glossary-to-document.xsl.diff, glossary.xml.add, glossary.xml.diff, site.xml.diff See the email thread: http://marc.theaimsgroup.com/?t=11227664371 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ] Gavin updated FOR-639: -- Attachment: glossary-v10.mod.diff glossary-to-document.xsl.diff glossary-v10.mod - added definitions element. glossary-to-document.xsl - added definitions template , fixed see elemnt to reference #anchor. More to come. define terminology for the various aspects of Dispatcher Key: FOR-639 URL: http://issues.apache.org/jira/browse/FOR-639 Project: Forrest Type: Task Components: Dispatcher (aka views), Documentation and website, Plugin: input.glossary Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev Attachments: glossary-to-document.xsl.diff, glossary-to-document.xsl.diff, glossary-v10.mod.diff, glossary.xml.add, glossary.xml.diff, site.xml.diff See the email thread: http://marc.theaimsgroup.com/?t=11227664371 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-767) Forrestbot webapp reports succesful even when there are broken links
[
http://issues.apache.org/jira/browse/FOR-767?page=comments#action_12375847 ]
Gavin commented on FOR-767:
---
Looking at deploy.xml the build will fail if deploy is local :-
target name=deploy.local unless=build.failed description=FB: Deploy to a
local location
but will ignore a fail if deploy is ftp :-
target name=deploy.ftp unless= description=Forrestbot:Deploy via FTP
and should fail if via SVN
target name=deploy.svn unless=build.failed description=FB: Deploy by
committing to an SVN repository
...
exec executable=svn dir=${deploy.svn.svn-dir}
output=${deploy.svn.svn-filestoadd} failonerror=true
Looking in notify.xml a failed or success build will be notified either way via
email.
failonerror is set to false in notify.email target, so I guess the end result
will
show 'build succeeded' because a notify email has been sent, whether the intial
site build
was successful or not. (?)
Forrestbot webapp reports succesful even when there are broken links
Key: FOR-767
URL: http://issues.apache.org/jira/browse/FOR-767
Project: Forrest
Type: Bug
Components: Tool: Forrestbot
Versions: 0.8-dev
Reporter: Ross Gardler
Priority: Minor
Fix For: 0.8-dev
We should also report why it failed:
- plugin problem
- broken link (with a link to the broken links file)
- ??
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-562) Update Plugins howto
[ http://issues.apache.org/jira/browse/FOR-562?page=all ] Gavin updated FOR-562: -- Attachment: howto-buildPlugin.xml.diff Changes applied as per Issue instructions. Do we need to repeat the changes for the docs_0_80 version too ? Update Plugins howto Key: FOR-562 URL: http://issues.apache.org/jira/browse/FOR-562 Project: Forrest Type: Improvement Components: Documentation and website Versions: 0.7 Reporter: Ross Gardler Fix For: 0.8-dev Attachments: howto-buildPlugin.xml.diff The document at http://forrest.apache.org/docs_0_70/howto/howto-buildPlugin.html needs to be updated in the following ways: - remove warnings about instability - add details about creating plugins outside of FORREST_HOME (mkdir PROJECT_HOME/plugins, copy whiteboard/plugins/build.xml to PROJECT_HOME/plugins, edit forrest.plugins.dir property) - update section on seeding a plugin to reflect working outside of FORREST_HOME - remove the existing note about copying build.xml NB here should be no need to edit the forrest.plugins.dir, simply set it to '.' In addition the buil file template should really be provided from the plugins directory rather than the whiteboard dir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-851) upgrade Voice plugin to use current Dispatcher
[ http://issues.apache.org/jira/browse/FOR-851?page=all ] Gavin updated FOR-851: -- Attachment: voice-plugin.diff Well, I tried a different way of making the diff file, so all changes are in the one file rather than having a diff file for each file I changed/added/deleted. Let me know if this works and if so should be easier to apply. The diff attached upgraded the voice plugin to dispatcher. Checklist : Passes Ant Test, Passes Forrest Site, Passes Forrest Run and works fine in localhost. Plugin Tested in Opera and seems to work fine. upgrade Voice plugin to use current Dispatcher -- Key: FOR-851 URL: http://issues.apache.org/jira/browse/FOR-851 Project: Forrest Type: Bug Components: Dispatcher (aka views), Plugin: output.voice Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: voice-plugin.diff The voice plugin is still using the old experimental Structurer plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-537) Plugin documentation sitemap references
[
http://issues.apache.org/jira/browse/FOR-537?page=comments#action_12375880 ]
Gavin commented on FOR-537:
---
Ok, I see there are references to the 'three' plugin types further up the file,
but still remains references to sitemap.xmap also. I have corrected what I can
where I can that needed changing still, but there remains this section I am not
sure on how this works as it has changed recently, so if someone could re-word
this bit I'll add it to my patch of changes.
section
titleHow does Installation work?/title
pWhen Forrest installs a plugin it downloads a zip of the plugin code and
extracts it into the codeplugins/code directory of Forrest and an entry
is made
in codesrc/plugins/sitemap.xmap/code. For example, installing the
IMSManifest plugin described above will result in the following entry
being added to the plugin sitemap:/p
source![CDATA[
map:select type=exists
map:when test=sitemap.xmap
map:mount uri-prefix=
src=sitemap.xmap
check-reload=yes
pass-through=true/
/map:when
/map:select
]]/source
pInstalled plugins are managed by the
FORREST_INSTALL_DIR/plugins/sitemap.xmap file. This file is mounted
by the main Forrest sitemap with the following code:/p
source![CDATA[
map:pipeline internal-only=false
map:mount uri-prefix=
src={forrest:plugins}/sitemap.xmap
check-reload=yes
pass-through=true/
/map:pipeline
]]/source
noteThe plugin sitemap.xmap file is automatically managed by Forrest,
the
end user need never edit this file./note
/section
Plugin documentation sitemap references
---
Key: FOR-537
URL: http://issues.apache.org/jira/browse/FOR-537
Project: Forrest
Type: Bug
Components: Documentation and website
Versions: 0.7
Environment: n/a
Reporter: Tim Williams
Priority: Minor
Fix For: 0.8-dev
This one references:
FORREST_INSTALL_DIR/plugins/sitemap.xmap
and
src/plugins/sitemap.xmap
and
map:mount uri-prefix=
src={forrest:plugins}/sitemap.xmap:
http://forrest.apache.org/0.7/docs/plugins/pluginInfrastructure.html#How+does+Installation+work%3F
--tim
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-211) whole-site html and pdf: broken ext links
[ http://issues.apache.org/jira/browse/FOR-211?page=comments#action_12377807 ] Gavin commented on FOR-211: --- Ok, I wonder if I can take a look at this, where should I start looking at ? whole-site html and pdf: broken ext links - Key: FOR-211 URL: http://issues.apache.org/jira/browse/FOR-211 Project: Forrest Type: Bug Components: Core operations Versions: 0.6 Reporter: David Crossley Fix For: 0.8-dev In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-848) upgrade NoteTaking plugin to use current Dispatcher
[ http://issues.apache.org/jira/browse/FOR-848?page=comments#action_12378211 ] Gavin commented on FOR-848: --- I am working on this and am making some progress. The plugin has now been converted to use current Dispatcher. I still need to get a 'notes' example working however. upgrade NoteTaking plugin to use current Dispatcher --- Key: FOR-848 URL: http://issues.apache.org/jira/browse/FOR-848 Project: Forrest Type: Bug Components: Dispatcher (aka views), Plugin: internal.NoteTaking Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev The NoteTaking plugin is still using the old experimental Structurer plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-848) upgrade NoteTaking plugin to use current Dispatcher
[ http://issues.apache.org/jira/browse/FOR-848?page=all ] Gavin updated FOR-848: -- Attachment: notetaking_plugin.diff Attached diff file upgrades plugin to dispatcher. The actual 'notes' part of it does not work atm. See http://marc.theaimsgroup.com/?l=forrest-devm=114692015816349w=2 for why. upgrade NoteTaking plugin to use current Dispatcher --- Key: FOR-848 URL: http://issues.apache.org/jira/browse/FOR-848 Project: Forrest Type: Bug Components: Dispatcher (aka views), Plugin: internal.NoteTaking Versions: 0.8-dev Reporter: David Crossley Attachments: notetaking_plugin.diff The NoteTaking plugin is still using the old experimental Structurer plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-635) images not reproduced in PDFs, if sources are in xdocs/images directory
[ http://issues.apache.org/jira/browse/FOR-635?page=all ] Gavin updated FOR-635: -- Attachment: fo.diff added pathutils.xsl to fo directory, altered document-to-fo.xsl. images not reproduced in PDFs, if sources are in xdocs/images directory --- Key: FOR-635 URL: http://issues.apache.org/jira/browse/FOR-635 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7, 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: fo.diff We used to enable images to be placed in the xdocs/images directory. However, now they are intended to go in the resources/images directory instead. Both methods will work for html pages, but only the latter method for the PDF pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-889) Use by Ant of newer catalog entity resolver failing for Windows
[ http://issues.apache.org/jira/browse/FOR-889?page=all ] Gavin updated FOR-889: -- Attachment: beforeUpgrade.txt afterUpgrade.txt Build Passes before upgrade, fails after upgrade. Use by Ant of newer catalog entity resolver failing for Windows --- Key: FOR-889 URL: http://issues.apache.org/jira/browse/FOR-889 Project: Forrest Type: Bug Components: XML grammars validation Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: afterUpgrade.txt, beforeUpgrade.txt, n-cyg-resolver.log, o-cyg-resolver.log Some people on Windows report that the 'forrest validate-xdocs' task is failing when we upgrade the $FORREST_HOME/tools/ant/lib/xml-commons-resolver.jar See discussion in: [heads up] Ant upgraded, please test http://marc.theaimsgroup.com/?t=11480039011 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-635) images not reproduced in PDFs, if sources are in xdocs/images directory
[ http://issues.apache.org/jira/browse/FOR-635?page=comments#action_12413570 ] Gavin commented on FOR-635: --- Does somebody want to test this. images not reproduced in PDFs, if sources are in xdocs/images directory --- Key: FOR-635 URL: http://issues.apache.org/jira/browse/FOR-635 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7, 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: fo.diff We used to enable images to be placed in the xdocs/images directory. However, now they are intended to go in the resources/images directory instead. Both methods will work for html pages, but only the latter method for the PDF pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-891) css-validator reports CSS errors and many warnings for pelt skin
[ http://issues.apache.org/jira/browse/FOR-891?page=all ] Gavin updated FOR-891: -- Attachment: screen_2.css.diff This revised patch fixes the errors ONLY - this will ensure that it passes CSS compliance. The warnings remain however and will work through these as they need discussion. css-validator reports CSS errors and many warnings for pelt skin Key: FOR-891 URL: http://issues.apache.org/jira/browse/FOR-891 Project: Forrest Type: Bug Components: Skins (general issues), Documentation and website Versions: 0.8-dev Reporter: David Crossley Assignee: Gavin Priority: Blocker Fix For: 0.8-dev Attachments: screen.css.diff, screen_2.css.diff Our home page does not pass CSS validation with http://jigsaw.w3.org/css-validator/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-891) css-validator reports CSS errors and many warnings for pelt skin
[ http://issues.apache.org/jira/browse/FOR-891?page=comments#action_12415349 ] Gavin commented on FOR-891: --- No thanks, I'll send in a new patch shortly to hopefully close the Issue. css-validator reports CSS errors and many warnings for pelt skin Key: FOR-891 URL: http://issues.apache.org/jira/browse/FOR-891 Project: Forrest Type: Bug Components: Skins (general issues), Documentation and website Versions: 0.8-dev Reporter: David Crossley Assignee: Gavin Attachments: screen.css.diff, screen_2.css.diff Our home page does not pass CSS validation with http://jigsaw.w3.org/css-validator/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-876) locationmap demo in fresh-site is broken
[ http://issues.apache.org/jira/browse/FOR-876?page=comments#action_12415549 ] Gavin commented on FOR-876: --- I tried this and it works fine for me in a freshly seeded site. pa href=lm:rewriteDemo/indexThis link is rewritten to an offsite address/a not specified in the link, which has codehref=lm:rewriteDemo/index/code./p pa href=lm:remoteDemo/samples/index.xmlThis link goes to svn samples/index.xml/a/p locationmap demo in fresh-site is broken Key: FOR-876 URL: http://issues.apache.org/jira/browse/FOR-876 Project: Forrest Type: Bug Components: Core operations, Locationmap Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev See Re: locationmap demo is broken http://marc.theaimsgroup.com/?t=11468186513 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-897) Added dutch translations of menu, tabs and index.xml
[ http://issues.apache.org/jira/browse/FOR-897?page=comments#action_12416746 ] Gavin commented on FOR-897: --- Hi Nico, Had a quick look and the only error I can see at the moment is your file names index.nl.xml is incorrectly named. Try renaming it to index_nl.xml and your patch should work fine. When I can work out how to add your patch locally to me (my bad, not yours) I will test it. Gav... Added dutch translations of menu, tabs and index.xml Key: FOR-897 URL: http://issues.apache.org/jira/browse/FOR-897 Project: Forrest Type: Improvement Components: Internationalisation (i18n) Versions: 0.8-dev Reporter: Nico Veenkamp Priority: Trivial Attachments: dutch_translation.txt I have translated several files, in the fresh-site part of the trunk, that generate the menu, the tabs and the index.html file, into dutch. I was not able to test it though because when I created a new site (using forrest seed; forrest run) I was able to see the english, french and german versions. When I changed to ?locale=nl I received an Internal Server Error. So I probably missing something. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-897) Added dutch translations of menu, tabs and index.xml
[ http://issues.apache.org/jira/browse/FOR-897?page=comments#action_12416748 ] Gavin commented on FOR-897: --- Ignore that sorry, looking at wrong naming convensions. index.nl.xml is correct. Added dutch translations of menu, tabs and index.xml Key: FOR-897 URL: http://issues.apache.org/jira/browse/FOR-897 Project: Forrest Type: Improvement Components: Internationalisation (i18n) Versions: 0.8-dev Reporter: Nico Veenkamp Priority: Trivial Attachments: dutch_translation.txt I have translated several files, in the fresh-site part of the trunk, that generate the menu, the tabs and the index.html file, into dutch. I was not able to test it though because when I created a new site (using forrest seed; forrest run) I was able to see the english, french and german versions. When I changed to ?locale=nl I received an Internal Server Error. So I probably missing something. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-897) Added dutch translations of menu, tabs and index.xml
[ http://issues.apache.org/jira/browse/FOR-897?page=comments#action_12416759 ] Gavin commented on FOR-897: --- Back Again, Applied your patch locally to my system and to confirm, yes the space between '' and 'a' in your index.nl.xml file makes all the difference, once changed it worked fine. A committer just needs to remove the space from line 53 at a href=index.html?locale=nlNederlandse/a to read a href=index.html?locale=nlNederlandse/a Good patch, thanks. Added dutch translations of menu, tabs and index.xml Key: FOR-897 URL: http://issues.apache.org/jira/browse/FOR-897 Project: Forrest Type: Improvement Components: Internationalisation (i18n) Versions: 0.8-dev Reporter: Nico Veenkamp Priority: Trivial Attachments: dutch_translation.txt I have translated several files, in the fresh-site part of the trunk, that generate the menu, the tabs and the index.html file, into dutch. I was not able to test it though because when I created a new site (using forrest seed; forrest run) I was able to see the english, french and german versions. When I changed to ?locale=nl I received an Internal Server Error. So I probably missing something. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-822) Problem with i18n with the structurer
[ http://issues.apache.org/jira/browse/FOR-822?page=comments#action_12416881 ] Gavin commented on FOR-822: --- I tested this using checkout 414415 and on a Dispatcher and i18n enabled seed-sample site and these errors are now gone and it all seems to work fine (as far as this issue goes) Problem with i18n with the structurer - Key: FOR-822 URL: http://issues.apache.org/jira/browse/FOR-822 Project: Forrest Type: Bug Components: Dispatcher (aka views), Internationalisation (i18n) Versions: 0.8-dev Reporter: Cyriaque Dupoirieux Fix For: 0.8-dev If the project.i18n is set to true in the project forrest.properties, I have the following error message : X [0] linkmap.html BROKEN: dispatcherError: 500 - Internal server error The contract siteinfo-meta-navigation has thrown thrown an exception by resolving raw data from cocoon://linkmap.navigation.xml. dispatcherErrorStack: org.apache.excalibur.source.SourceException: Exception during processing of cocoon://linkmap.navigation.xml Total time: 0 minutes 10 seconds, Site size: 0 Site pages: 0 Java Result: 1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-785) plugins/*/skinconf.xml does not validate since using entity to ease management
[ http://issues.apache.org/jira/browse/FOR-785?page=comments#action_12417076 ] Gavin commented on FOR-785: --- Ok, So I altered the DTD and moved project-name and project-description to the end. This works fine and validates, have I missed something as to why we can not moved these to the end, or shall I send a patch in? (The produced site still looks the same) (Another Alternative would be use variables for these, haven't worked that out though) plugins/*/skinconf.xml does not validate since using entity to ease management -- Key: FOR-785 URL: http://issues.apache.org/jira/browse/FOR-785 Project: Forrest Type: Bug Components: Plugins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Recently i split the skinconf.xml for each plugin to refer to common stuff via an external entity. Works nicely. Okay, i admit it ... forgot to do 'build test' :-) and it doesn't validate. The DTD insists on having the elements in a specific order. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-209) First level selected tab is not highlighted when containing 2nd level tabs
[ http://issues.apache.org/jira/browse/FOR-209?page=comments#action_12417097 ] Gavin commented on FOR-209: --- If we are not fixing this for 0.7, this looked fixed to me in 0.8 - if everyone agrees this issue should be closed. Sjur or anykne, if any more visual clues are needed to indicate a tab has second level tabs, maybe a downward facing arrow could be added to the 'unversioned docs' first level tab ? First level selected tab is not highlighted when containing 2nd level tabs -- Key: FOR-209 URL: http://issues.apache.org/jira/browse/FOR-209 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.6, 0.7 Environment: MacOS 10.3.4, java 1.4.2 Reporter: Sjur N. Moshagen Fix For: 0.8-dev When there are two levels of tabs, the selected first level tab does not get highlighted, nor are there any other visual or structural clues as to which first-level tab is active, and which contains the displayed 2nd level tabs. This is checked with both the default skin, and with tigris-style. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-785) plugins/*/skinconf.xml does not validate since using entity to ease management
[ http://issues.apache.org/jira/browse/FOR-785?page=comments#action_12417244 ] Gavin commented on FOR-785: --- Yes, I changed the forrest-validate.skinconf to = true again before testing (also you can 'forrest validate-skinconf' on the CLI.) I will send a patch later and see what you think. plugins/*/skinconf.xml does not validate since using entity to ease management -- Key: FOR-785 URL: http://issues.apache.org/jira/browse/FOR-785 Project: Forrest Type: Bug Components: Plugins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Recently i split the skinconf.xml for each plugin to refer to common stuff via an external entity. Works nicely. Okay, i admit it ... forgot to do 'build test' :-) and it doesn't validate. The DTD insists on having the elements in a specific order. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-785) plugins/*/skinconf.xml does not validate since using entity to ease management
[ http://issues.apache.org/jira/browse/FOR-785?page=all ] Gavin updated FOR-785: -- Attachment: dtdchanges.diff dtdchanges.diff cures problems associated with plugins failing validation. I am working through the plugins and have almost finished the main plugins. The fact that validation for these plugins has been turned off means that a few errors have crept in to some of them. listLocations needed a file altering for it pass validation OpenOffice needed some alterations also. PhotoGallery and ProjectInfo both pass validation but fail the Ant Test due to some other errors, so I will leave them off of this round of patched and just submit the ones which pass - which is now all of them bar those two. I have yet to test the WhiteBoard Plugins so will leave them until later. Another patch will the passing plugin alterations I will post in the morning. plugins/*/skinconf.xml does not validate since using entity to ease management -- Key: FOR-785 URL: http://issues.apache.org/jira/browse/FOR-785 Project: Forrest Type: Bug Components: Plugins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: dtdchanges.diff Recently i split the skinconf.xml for each plugin to refer to common stuff via an external entity. Works nicely. Okay, i admit it ... forgot to do 'build test' :-) and it doesn't validate. The DTD insists on having the elements in a specific order. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-785) plugins/*/skinconf.xml does not validate since using entity to ease management
[ http://issues.apache.org/jira/browse/FOR-785?page=all ] Gavin updated FOR-785: -- Attachment: enableValidatePlugins.diff enableValidatePlugins turns all of the main plugins into 'forrest.validate.skinconf=true' except those that do not pass 'Ant Test' . Other minor work performed on a few files to get them to validate/pass ant test again. plugins/*/skinconf.xml does not validate since using entity to ease management -- Key: FOR-785 URL: http://issues.apache.org/jira/browse/FOR-785 Project: Forrest Type: Bug Components: Plugins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: dtdchanges.diff, enableValidatePlugins.diff Recently i split the skinconf.xml for each plugin to refer to common stuff via an external entity. Works nicely. Okay, i admit it ... forgot to do 'build test' :-) and it doesn't validate. The DTD insists on having the elements in a specific order. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-488) Remove Zip Java components from Forrest
[ http://issues.apache.org/jira/browse/FOR-488?page=comments#action_12417621 ] Gavin commented on FOR-488: --- Ok, so I guess this can be removed now then ? Remove Zip Java components from Forrest --- Key: FOR-488 URL: http://issues.apache.org/jira/browse/FOR-488 Project: Forrest Type: Improvement Components: Core operations Versions: 0.7 Reporter: Ross Gardler Priority: Trivial Fix For: 0.8-dev Here's a comment from org.apache.cocoon.components.source.impl.ZipSource in our SVN /** * ATTENTION: The ZIP protocol is also part of Cocoon 2.1.4 (scratchpad). When *Forrest uses this version or higher this file can be removed!!! (RP) * * @since 2.1.4 */ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-203) 2nd level tabs are not selected appropriately
[ http://issues.apache.org/jira/browse/FOR-203?page=comments#action_12418011 ] Gavin commented on FOR-203: --- I have tested this and it all seems to work fine. From what I understand of the original problem it could be a case of misunderstanding of the configuration. I added a new directory called 'bug-sample' as a subdir off of xdocs. I added in a test file (I used static.xml) in this directory. I added an entry to tabs.xml as a sub-tab of the samples tab. wich looks like :- tab id=samples-sample3 label=Sample3 dir=bug-sample indexfile=static.html/ forrest run and it shows in the second level tabs area as 'Sample 3' When clicked on goes correctly to /bug-sample/static.html. The OP stated This happens because the starts-with() path comparison fails for menu entries that do not reside the same directory as is specified in the dir attribute of the 2nd level tabs. Of course it wont, you should be specifying the directory that the menu entries reside in! This makes me think that maybe the 'dir' attribute did not point to the new directory. tested in 0.8-dev. Should this be closed ? 2nd level tabs are not selected appropriately - Key: FOR-203 URL: http://issues.apache.org/jira/browse/FOR-203 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.6 Reporter: Lorenz Froihofer Fix For: 0.8-dev Attachments: bug-demo.tgz The 2nd level tabs are not shown for menu entries that caused the issue FOR-111. This happens because the starts-with() path comparison fails for menu entries that do not reside the same directory as is specified in the dir attribute of the 2nd level tabs. See the attached bug-demo.tgz for an example. Select Samples/Apache document and notice that the 2nd level tabs are shown. Now select Samples/BUG DEMO and notice that the 2nd level tabs are not shown. This is because the document corresponding to Samples/Apache document resides in the directory /samples whereas the document corresponding to Samples/BUG DEMO resides in the directory /bug-sample. Kind regards, Lorenz Froihofer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-203) 2nd level tabs are not selected appropriately
[ http://issues.apache.org/jira/browse/FOR-203?page=comments#action_12418013 ] Gavin commented on FOR-203: --- Also, I do not think this is a duplicate of FOR-208 . 2nd level tabs are not selected appropriately - Key: FOR-203 URL: http://issues.apache.org/jira/browse/FOR-203 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.6 Reporter: Lorenz Froihofer Fix For: 0.8-dev Attachments: bug-demo.tgz The 2nd level tabs are not shown for menu entries that caused the issue FOR-111. This happens because the starts-with() path comparison fails for menu entries that do not reside the same directory as is specified in the dir attribute of the 2nd level tabs. See the attached bug-demo.tgz for an example. Select Samples/Apache document and notice that the 2nd level tabs are shown. Now select Samples/BUG DEMO and notice that the 2nd level tabs are not shown. This is because the document corresponding to Samples/Apache document resides in the directory /samples whereas the document corresponding to Samples/BUG DEMO resides in the directory /bug-sample. Kind regards, Lorenz Froihofer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-203) 2nd level tabs are not selected appropriately
[ http://issues.apache.org/jira/browse/FOR-203?page=comments#action_12418202 ] Gavin commented on FOR-203: --- I have tested the attachment now, and I still feel this is a user or documentation error - or can someone tell me if this feature is required. I mean, why have (using the above example) the bug-demo in a different directory ? If you want it to belong in the 'Samples' tab and on the Samples part of the site navigation, then it makes sense to have the file(s) in the /samples/* directory. Or, if it really has to be separate, have it as a subdir such as /samples/bug-demo/ (or create another tab for it) I dont think it is wrong that this does not work when trying to link a Samples menu item to a directory that is outside of the samples directory tree. Can someone else look and give thier opinion, so this can be resolved/closed. 2nd level tabs are not selected appropriately - Key: FOR-203 URL: http://issues.apache.org/jira/browse/FOR-203 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.6 Reporter: Lorenz Froihofer Fix For: 0.8-dev Attachments: bug-demo.tgz The 2nd level tabs are not shown for menu entries that caused the issue FOR-111. This happens because the starts-with() path comparison fails for menu entries that do not reside the same directory as is specified in the dir attribute of the 2nd level tabs. See the attached bug-demo.tgz for an example. Select Samples/Apache document and notice that the 2nd level tabs are shown. Now select Samples/BUG DEMO and notice that the 2nd level tabs are not shown. This is because the document corresponding to Samples/Apache document resides in the directory /samples whereas the document corresponding to Samples/BUG DEMO resides in the directory /bug-sample. Kind regards, Lorenz Froihofer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-907) Apachecon Images blurred due to resizing on the fly
Apachecon Images blurred due to resizing on the fly --- Key: FOR-907 URL: http://issues.apache.org/jira/browse/FOR-907 Project: Forrest Issue Type: Improvement Components: Documentation and website Affects Versions: 0.8-dev Reporter: Gavin The current ApacheCon US and ASIA images are blurred due to images being pulled from respective servers and squashed into 150x50. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-907) Apachecon Images blurred due to resizing on the fly
[ http://issues.apache.org/jira/browse/FOR-907?page=all ] Gavin updated FOR-907: -- Attachment: apache_con_asia_header.png ASF-us-2006-web_masthead.jpg apachecon.diff Attached are resized to 150x50 versions of images and the diff to suit. Still can not really make out smaller writing in higher resolutions but the images overall are sharper. Apachecon Images blurred due to resizing on the fly --- Key: FOR-907 URL: http://issues.apache.org/jira/browse/FOR-907 Project: Forrest Issue Type: Improvement Components: Documentation and website Affects Versions: 0.8-dev Reporter: Gavin Attachments: apache_con_asia_header.png, apachecon.diff, ASF-us-2006-web_masthead.jpg The current ApacheCon US and ASIA images are blurred due to images being pulled from respective servers and squashed into 150x50. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-285) Make the html export+rendering reasonably stable
[ http://issues.apache.org/jira/browse/FOR-285?page=comments#action_12421442 ] Gavin commented on FOR-285: --- Unless NKB can enlighten as to what this is and if it is still needed - I don't see it as Incubator does not use Forrest - this could be closed. Make the html export+rendering reasonably stable Key: FOR-285 URL: http://issues.apache.org/jira/browse/FOR-285 Project: Forrest Issue Type: Improvement Components: Core operations Affects Versions: 0.8-dev Reporter: Nicola Ken Barozzi We need to get this done for the Incubator. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-827) Weirdness in CSS after url
[ http://issues.apache.org/jira/browse/FOR-827?page=comments#action_12421443 ] Gavin commented on FOR-827: --- So, should this workaround be documented as the way to do it, then close the issue, or does someone think there may be a better solution somewhere else? Weirdness in CSS after url -- Key: FOR-827 URL: http://issues.apache.org/jira/browse/FOR-827 Project: Forrest Issue Type: Bug Components: Dispatcher (aka views) Affects Versions: 0.8-dev Reporter: paul bolger Priority: Minor Don't quite understand were this is coming from. It appears that Forrest is trying to improve on my stylesheets... If a stylesheet contains a a URL, when referencing a background image in this particular case, Forrest inserts an extra semicolon after the closing bracket containing the URL. This is get-roundable normally, skip the semicolon, but it prevent the use of the shorthand background property as the semicolon truncates the rule. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-731) empty linkmap.html document, side-effect of workaround to FOR-675
[ http://issues.apache.org/jira/browse/FOR-731?page=comments#action_12421444 ] Gavin commented on FOR-731: --- The linked issue of which this is a workaround, has been scheduled for fix version 0.9, so I guess this should follow suit. empty linkmap.html document, side-effect of workaround to FOR-675 - Key: FOR-731 URL: http://issues.apache.org/jira/browse/FOR-731 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev The main/webapp/resources/stylesheets/linkmap-to-document.xsl has a workaround for a side-effect to the of the workaround for issue FOR-675. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ] Gavin updated FOR-639: -- Attachment: dispatcher.diff Added dispatcher-glossary.xml to plugin, enabled glossary plugin. define terminology for the various aspects of Dispatcher Key: FOR-639 URL: http://issues.apache.org/jira/browse/FOR-639 Project: Forrest Issue Type: Task Components: Documentation and website, Dispatcher (aka views), Plugin: input.glossary Affects Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev Attachments: dispatcher.diff, glossary-to-document.xsl.diff, glossary-to-document.xsl.diff, glossary-v10.mod.diff, glossary.xml.add, glossary.xml.diff, site.xml.diff See the email thread: http://marc.theaimsgroup.com/?t=11227664371 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ] Gavin updated FOR-639: -- Attachment: glossary.xml.diff2 glossary.xml.diff2 removes dispatcher related terms, these are now in the dispatcher-glossary.xml which resides in the dispatcher plugin instead. define terminology for the various aspects of Dispatcher Key: FOR-639 URL: http://issues.apache.org/jira/browse/FOR-639 Project: Forrest Issue Type: Task Components: Documentation and website, Dispatcher (aka views), Plugin: input.glossary Affects Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev Attachments: dispatcher.diff, glossary-to-document.xsl.diff, glossary-to-document.xsl.diff, glossary-v10.mod.diff, glossary.xml.add, glossary.xml.diff, glossary.xml.diff2, site.xml.diff See the email thread: http://marc.theaimsgroup.com/?t=11227664371 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
