Re: [JIRA] Closed: (FOR-432) excel plugin does only work for own documentation
how can i do a patch if the directory structure changed? js [EMAIL PROTECTED] wrote: Message: The following issue has been closed. Resolver: Ross Gardler Date: Fri, 18 Feb 2005 6:44 AM Head has been pathed and the new version of the plugin has been deployed. Thanks. Please try and provide a patch in future, it is far easier to apply and so things will happen faster. - View the issue: http://issues.cocoondev.org//browse/FOR-432 Here is an overview of the issue: - Key: FOR-432 Summary: excel plugin does only work for own documentation Type: Bug Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: HEAD Versions: HEAD Assignee: Ross Gardler Reporter: Johannes Schaefer Created: Tue, 1 Feb 2005 11:56 AM Updated: Fri, 18 Feb 2005 6:44 AM Environment: r149399 from 2005-02-01 Description: In input.xmap the path to table2document.xsl is set relative to the project. This works for the excel-plugin documentation but not for other projects. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira -- User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99 Geschftsstelle: User Interface Design GmbH * Lehrer-Gtz-Weg 11 * D-81825 Mnchen www.uidesign.de Buch User Interface Tuning von Joachim Machate Michael Burmester www.user-interface-tuning.de Besuchen Sie uns auf der Hannover Messe 11.-15. April 2005 Halle 2, Stand C14 auf dem MMI Gemeinschaftsstand www.uidesign.de/hmi2005 Nchstes TAE-Seminar zu User Interface Design Ostfildern-Nellingen, 07.-08. April 2005 www.tae.de TAE-Veranstaltung Nr. 31189
Re: [RT] Directory structure and configuration
Ferdinand Soethe wrote: Hi Nicola, NKB Yes, I'm the initial author of that task :-) So is it agreed to implement the new structure like this: my-project/ conf/ forrest.properties skinconf.xml site.xml tabs.xml content/ status.xml ** all other content This would be a major improvement and simplification. And while we are at it, how about renaming 'conf' to 'configuration'. Doesn't seem to make a difference performance wise, does it. Well, it's shorter to type and akin to what Unix geeks are accustomed to. I'm ok for either. The same could be applied to skinfconf.xml = skinconfiguration.xml site = sitestructure.xml but I'm not sure that this is as easy to implement or up for discussion here. I understand, these names can change as well. So when can we expect this to be implemented? I'll look at the code and recast it as a proposal. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
[JIRA] Commented: (FOR-432) excel plugin does only work for own documentation
The following comment has been added to this issue: Author: Johannes Schaefer Created: Mon, 21 Feb 2005 5:19 AM Body: building a patch still doesn't work, see http://issues.cocoondev.org/browse/FOR-441 - View this comment: http://issues.cocoondev.org//browse/FOR-432?page=comments#action_12052 - View the issue: http://issues.cocoondev.org//browse/FOR-432 Here is an overview of the issue: - Key: FOR-432 Summary: excel plugin does only work for own documentation Type: Bug Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: HEAD Versions: HEAD Assignee: Ross Gardler Reporter: Johannes Schaefer Created: Tue, 1 Feb 2005 11:56 AM Updated: Mon, 21 Feb 2005 5:19 AM Environment: r149399 from 2005-02-01 Description: In input.xmap the path to table2document.xsl is set relative to the project. This works for the excel-plugin documentation but not for other projects. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-441) build patch doesn't work
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-441
Here is an overview of the issue:
-
Key: FOR-441
Summary: build patch doesn't work
Type: Bug
Status: Unassigned
Priority: Minor
Project: Forrest
Versions:
HEAD
Assignee:
Reporter: Johannes Schaefer
Created: Mon, 21 Feb 2005 5:18 AM
Updated: Mon, 21 Feb 2005 5:18 AM
Environment: Win XP, C:\j2sdk1.4.2_04, forrrest r. 154668
Description:
'build patch' doesn't work.
H:\forrest154656-0221svn status
? plugins\org.apache.forrest.plugin.excel\resources
! plugins\org.apache.forrest.plugin.excel\src\documentation\resources
H:\forrest154656-0221cd main
H:\forrest154656-0221\mainbuild patch
Using classpath:
;..\lib\endorsed\jakarta-bcel-20040329.jar;..\lib\endorsed\jakarta-regexp-1.3.jar;..\lib\endorsed\xala
n-2.6.1-dev-20041008T0304.jar;..\lib\endorsed\xercesImpl-2.6.2.jar;..\lib\endorsed\xml-apis.jar
Buildfile: build.xml
BUILD FAILED
H:\forrest154656-0221\main\build.xml:389: The following error occurred while
executing this line:
java.io.FileNotFoundException:
H:\forrest154656-0221\main\${forrest.home}\tools\targets\patch.xml (Das System
kann den a
ngegebenen Pfad nicht finden)
Total time: 0 seconds
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-442) build patch for plugins
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-442 Here is an overview of the issue: - Key: FOR-442 Summary: build patch for plugins Type: New Feature Status: Unassigned Priority: Minor Project: Forrest Versions: HEAD Assignee: Reporter: Johannes Schaefer Created: Mon, 21 Feb 2005 5:29 AM Updated: Mon, 21 Feb 2005 5:29 AM Description: It would be nice to have a 'build patch' for a plugin only, i.e. in the plugin's directory. Would ease plugin updates. See: http://marc.theaimsgroup.com/?l=forrest-devm=110735682109350w=2 This is related to FOR-340, FOR-441 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-443) manu disappeared
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-443 Here is an overview of the issue: - Key: FOR-443 Summary: manu disappeared Type: Bug Status: Unassigned Priority: Critical Project: Forrest Components: Core operations Versions: HEAD Assignee: Reporter: Johannes Schaefer Created: Mon, 21 Feb 2005 8:57 AM Updated: Mon, 21 Feb 2005 8:57 AM Environment: revisions 154655, 154656 Description: The navigation menu on the left side disappeared. From thread on user list (no link since Eyebrowse mail archive doesn't work): P 21. feb. 2005 kl. 12.45 skrev Johannes Schaefer: Hi! I did a completely new 'svn co' (revision is 154656) and it seems that the menu disappeared (even with a brandnew 'forrest seed'). SEE HTML snippet below. menu-index.html is empty (i.e. not even html/). The content is rendered correctly. I guess this is a bug?! I have the same problem (revision 154655): tabs and content is rendered correctly (although no tab highlighting), but no menu. Thus bug confirmed:-( Sjur - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-443) menu disappeared
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Mon, 21 Feb 2005 9:26 AM Changes: summary changed from manu disappeared to menu disappeared priority changed from Critical to Blocker - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-443?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-443 Here is an overview of the issue: - Key: FOR-443 Summary: menu disappeared Type: Bug Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Versions: HEAD Assignee: Reporter: Johannes Schaefer Created: Mon, 21 Feb 2005 8:57 AM Updated: Mon, 21 Feb 2005 9:26 AM Environment: revisions 154655, 154656 Description: The navigation menu on the left side disappeared. From thread on user list (no link since Eyebrowse mail archive doesn't work): P 21. feb. 2005 kl. 12.45 skrev Johannes Schaefer: Hi! I did a completely new 'svn co' (revision is 154656) and it seems that the menu disappeared (even with a brandnew 'forrest seed'). SEE HTML snippet below. menu-index.html is empty (i.e. not even html/). The content is rendered correctly. I guess this is a bug?! I have the same problem (revision 154655): tabs and content is rendered correctly (although no tab highlighting), but no menu. Thus bug confirmed:-( Sjur - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-443) menu disappeared
The following comment has been added to this issue: Author: Sjur N. Moshagen Created: Mon, 21 Feb 2005 9:39 AM Body: The thread is available at: http://mail-archives.eu.apache.org/mod_mbox/forrest-user/200502.mbox/[EMAIL PROTECTED] - View this comment: http://issues.cocoondev.org//browse/FOR-443?page=comments#action_12053 - View the issue: http://issues.cocoondev.org//browse/FOR-443 Here is an overview of the issue: - Key: FOR-443 Summary: menu disappeared Type: Bug Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Versions: HEAD Assignee: Reporter: Johannes Schaefer Created: Mon, 21 Feb 2005 8:57 AM Updated: Mon, 21 Feb 2005 9:39 AM Environment: revisions 154655, 154656 Description: The navigation menu on the left side disappeared. From thread on user list (no link since Eyebrowse mail archive doesn't work): P 21. feb. 2005 kl. 12.45 skrev Johannes Schaefer: Hi! I did a completely new 'svn co' (revision is 154656) and it seems that the menu disappeared (even with a brandnew 'forrest seed'). SEE HTML snippet below. menu-index.html is empty (i.e. not even html/). The content is rendered correctly. I guess this is a bug?! I have the same problem (revision 154655): tabs and content is rendered correctly (although no tab highlighting), but no menu. Thus bug confirmed:-( Sjur - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-443) menu disappeared
The following comment has been added to this issue: Author: Sjur N. Moshagen Created: Mon, 21 Feb 2005 9:44 AM Body: Unfortunately, Jira (or my browser) misinterpreted/misencoded the link when the comment was posted. so clicking it does not work. Selecting the whole text, copying and pasting it into the address bar works though. - View this comment: http://issues.cocoondev.org//browse/FOR-443?page=comments#action_12054 - View the issue: http://issues.cocoondev.org//browse/FOR-443 Here is an overview of the issue: - Key: FOR-443 Summary: menu disappeared Type: Bug Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Versions: HEAD Assignee: Reporter: Johannes Schaefer Created: Mon, 21 Feb 2005 8:57 AM Updated: Mon, 21 Feb 2005 9:44 AM Environment: revisions 154655, 154656 Description: The navigation menu on the left side disappeared. From thread on user list (no link since Eyebrowse mail archive doesn't work): P 21. feb. 2005 kl. 12.45 skrev Johannes Schaefer: Hi! I did a completely new 'svn co' (revision is 154656) and it seems that the menu disappeared (even with a brandnew 'forrest seed'). SEE HTML snippet below. menu-index.html is empty (i.e. not even html/). The content is rendered correctly. I guess this is a bug?! I have the same problem (revision 154655): tabs and content is rendered correctly (although no tab highlighting), but no menu. Thus bug confirmed:-( Sjur - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-435) Wiki input files (*.jspwiki) is not correctly read when in UTF-8
The following comment has been added to this issue: Author: Sjur N. Moshagen Created: Mon, 21 Feb 2005 9:47 AM Body: The whole discussion is found in this thread: http://mail-archives.eu.apache.org/mod_mbox/forrest-user/200502.mbox/[EMAIL PROTECTED] (if the link does not work, copy and paste the link text) - View this comment: http://issues.cocoondev.org//browse/FOR-435?page=comments#action_12055 - View the issue: http://issues.cocoondev.org//browse/FOR-435 Here is an overview of the issue: - Key: FOR-435 Summary: Wiki input files (*.jspwiki) is not correctly read when in UTF-8 Type: Bug Status: Unassigned Priority: Major Project: Forrest Components: Plugins (general issues) Versions: HEAD Assignee: Reporter: Sjur N. Moshagen Created: Thu, 17 Feb 2005 12:42 AM Updated: Mon, 21 Feb 2005 9:47 AM Environment: MacOS X, 10.3.8, Java 1.4.2 Description: According to the documentation at: http://chaperon.sourceforge.net/using-cocoon.html it should be possible to configure the Wiki plugin (or any plugin based on Chaperon) for different encodings of the input file, in my case UTF-8. But this does not work. I have: map:transformer name=lexer src=org.apache.cocoon.transformation.LexicalTransformer logger=sitemap.transformer.lexer map:parameter name=localizable value=true/ map:parameter name=encoding value=UTF-8/ /map:transformer in the input.xmap file in $FORREST_HOME/plugins/wiki, and I have run ant local-deploy, but to no avail: multibyte UTF-8 sequences come out as the Latin-1 counterpart of each byte in the sequence. A discussion about this bug can be found at: [mail archive not yet updated, will add link here later] - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Resolved: (FOR-443) menu disappeared
Message: The following issue has been resolved as FIXED. Resolver: Ross Gardler Date: Mon, 21 Feb 2005 10:33 AM SHould now be fixed, please test and close this issue if you can confirm it is fixed - View the issue: http://issues.cocoondev.org//browse/FOR-443 Here is an overview of the issue: - Key: FOR-443 Summary: menu disappeared Type: Bug Status: Resolved Priority: Blocker Resolution: FIXED Project: Forrest Components: Core operations Fix Fors: HEAD Versions: HEAD Assignee: Ross Gardler Reporter: Johannes Schaefer Created: Mon, 21 Feb 2005 8:57 AM Updated: Mon, 21 Feb 2005 10:33 AM Environment: revisions 154655, 154656 Description: The navigation menu on the left side disappeared. From thread on user list (no link since Eyebrowse mail archive doesn't work): P 21. feb. 2005 kl. 12.45 skrev Johannes Schaefer: Hi! I did a completely new 'svn co' (revision is 154656) and it seems that the menu disappeared (even with a brandnew 'forrest seed'). SEE HTML snippet below. menu-index.html is empty (i.e. not even html/). The content is rendered correctly. I guess this is a bug?! I have the same problem (revision 154655): tabs and content is rendered correctly (although no tab highlighting), but no menu. Thus bug confirmed:-( Sjur - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-427) Need licensing element in plugins.xml
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Mon, 21 Feb 2005 10:35 AM Comment: Reduced to Critical as this need not block the 0.7 release since we currently do not link to any plugins with incompatible licenses. Changes: priority changed from Blocker to Critical - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-427?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-427 Here is an overview of the issue: - Key: FOR-427 Summary: Need licensing element in plugins.xml Type: Improvement Status: Unassigned Priority: Critical Project: Forrest Components: Plugins (general issues) Versions: HEAD Assignee: Reporter: Ross Gardler Created: Sat, 22 Jan 2005 2:31 PM Updated: Mon, 21 Feb 2005 10:35 AM Description: Since plugins can be hosted on different sites they can be released under licenses other than the Apache one. We need an element in plugins.xml that records the type of license a plugin is released under. This element should be used by the plugin install process to verify that the user agrees to the terms of that license before download and installation is started. For example: license name=A.N.Other License url=http://www.domain.org/licenseText/ would result in the user being asked to read the license at the supplied URL and then typing yes to agree (no skips installation). license name=A.N.Other License This is the text of the license. /license would result in the license text being displayed and the user being asked to agree. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Reopened: (FOR-432) excel plugin does only work for own documentation
Message: The following issue has been reopened. Reopener: Ross Gardler Date: Mon, 21 Feb 2005 10:44 AM I clearly made some errors when applying your changes (this is easily done when there is no patch). I also forgot to add the resources folder I had created locally. I've added the resources folder now, but the samples pages are coming up blank. I'm afaid I don't have the time to fix this just yet so I've reopened the bug, I'm sure it is only a simple mistake though. - View the issue: http://issues.cocoondev.org//browse/FOR-432 Here is an overview of the issue: - Key: FOR-432 Summary: excel plugin does only work for own documentation Type: Bug Status: Reopened Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: HEAD Versions: HEAD Assignee: Ross Gardler Reporter: Johannes Schaefer Created: Tue, 1 Feb 2005 11:56 AM Updated: Mon, 21 Feb 2005 10:44 AM Environment: r149399 from 2005-02-01 Description: In input.xmap the path to table2document.xsl is set relative to the project. This works for the excel-plugin documentation but not for other projects. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-413) PDF: rendering fails when graphics too big - workaround inside
The following comment has been added to this issue:
Author: Johannes Schaefer
Created: Mon, 21 Feb 2005 10:46 AM
Body:
See also:
http://mail-archives.eu.apache.org/mod_mbox/forrest-user/200502.mbox/[EMAIL
PROTECTED]
-
View this comment:
http://issues.cocoondev.org//browse/FOR-413?page=comments#action_12059
-
View the issue:
http://issues.cocoondev.org//browse/FOR-413
Here is an overview of the issue:
-
Key: FOR-413
Summary: PDF: rendering fails when graphics too big - workaround inside
Type: Bug
Status: Unassigned
Priority: Major
Project: Forrest
Components:
Core operations
Versions:
0.6
Assignee:
Reporter: Olivier Jacques
Created: Fri, 10 Dec 2004 4:27 AM
Updated: Mon, 21 Feb 2005 10:46 AM
Description:
When forresting a document that has embedded images, the PDF rendering
sometimes stops with this error message:
BROKEN: org.apache.fop.apps.FOPException: No meaningful layout in block after
many attempts. Infinite loop is assumed. Processing halted.
I've found that this is caused by images that are too big to fit in the PDF
page (took me some times :) )
I temporary solved it by modifying the document2fo.xsl. When I specify the
width or height attribute to the img, then the value is taken and divided
by 2. WARNING: the value has to be an integer and a px (pixels) size.
We should find a way to reduce the size automatically.
$ diff -bruN document2fo.xsl~ document2fo.xsl
--- document2fo.xsl~2004-12-09 17:51:42.486185200 +0100
+++ document2fo.xsl 2004-12-09 22:03:32.465852800 +0100
@@ -755,10 +755,14 @@
/xsl:variable
fo:external-graphic src={$imgpath}
xsl:if test=@height
- xsl:attribute name=heightxsl:value-of
select=@height//xsl:attribute
+ xsl:variable name=reducedheight
+select=number(@height) /
+ xsl:attribute name=heightxsl:value-of
select=concat(number($reducedheight) div 2,'px')//xsl:attribute
/xsl:if
xsl:if test=@width
- xsl:attribute name=widthxsl:value-of
select=@width//xsl:attribute
+ xsl:variable name=reducedwidth
+select=number(@width) /
+ xsl:attribute name=widthxsl:value-of
select=concat(number($reducedwidth) div 2,'px')//xsl:attribute
/xsl:if
/fo:external-graphic
!-- alt text --
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-413) PDF: rendering fails when graphics too big - workaround inside
The following comment has been added to this issue:
Author: Johannes Schaefer
Created: Mon, 21 Feb 2005 10:57 AM
Body:
Image width seems not to be a problem, screenshots with 1024x768 are included
correctly although they're too high. It seems that FOP (?) scales them down
because of width. High but narrow images cause problems. Seems like FOP cannot
handle these ...
-
View this comment:
http://issues.cocoondev.org//browse/FOR-413?page=comments#action_12060
-
View the issue:
http://issues.cocoondev.org//browse/FOR-413
Here is an overview of the issue:
-
Key: FOR-413
Summary: PDF: rendering fails when graphics too big - workaround inside
Type: Bug
Status: Unassigned
Priority: Major
Project: Forrest
Components:
Core operations
Versions:
0.6
Assignee:
Reporter: Olivier Jacques
Created: Fri, 10 Dec 2004 4:27 AM
Updated: Mon, 21 Feb 2005 10:57 AM
Description:
When forresting a document that has embedded images, the PDF rendering
sometimes stops with this error message:
BROKEN: org.apache.fop.apps.FOPException: No meaningful layout in block after
many attempts. Infinite loop is assumed. Processing halted.
I've found that this is caused by images that are too big to fit in the PDF
page (took me some times :) )
I temporary solved it by modifying the document2fo.xsl. When I specify the
width or height attribute to the img, then the value is taken and divided
by 2. WARNING: the value has to be an integer and a px (pixels) size.
We should find a way to reduce the size automatically.
$ diff -bruN document2fo.xsl~ document2fo.xsl
--- document2fo.xsl~2004-12-09 17:51:42.486185200 +0100
+++ document2fo.xsl 2004-12-09 22:03:32.465852800 +0100
@@ -755,10 +755,14 @@
/xsl:variable
fo:external-graphic src={$imgpath}
xsl:if test=@height
- xsl:attribute name=heightxsl:value-of
select=@height//xsl:attribute
+ xsl:variable name=reducedheight
+select=number(@height) /
+ xsl:attribute name=heightxsl:value-of
select=concat(number($reducedheight) div 2,'px')//xsl:attribute
/xsl:if
xsl:if test=@width
- xsl:attribute name=widthxsl:value-of
select=@width//xsl:attribute
+ xsl:variable name=reducedwidth
+select=number(@width) /
+ xsl:attribute name=widthxsl:value-of
select=concat(number($reducedwidth) div 2,'px')//xsl:attribute
/xsl:if
/fo:external-graphic
!-- alt text --
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-443) menu disappeared
Message: The following issue has been closed. Resolver: Ferdinand Soethe Date: Mon, 21 Feb 2005 12:01 PM Menu is back in my test installation. Thanks! - View the issue: http://issues.cocoondev.org//browse/FOR-443 Here is an overview of the issue: - Key: FOR-443 Summary: menu disappeared Type: Bug Status: Closed Priority: Blocker Resolution: FIXED Project: Forrest Components: Core operations Fix Fors: HEAD Versions: HEAD Assignee: Ross Gardler Reporter: Johannes Schaefer Created: Mon, 21 Feb 2005 8:57 AM Updated: Mon, 21 Feb 2005 12:01 PM Environment: revisions 154655, 154656 Description: The navigation menu on the left side disappeared. From thread on user list (no link since Eyebrowse mail archive doesn't work): P 21. feb. 2005 kl. 12.45 skrev Johannes Schaefer: Hi! I did a completely new 'svn co' (revision is 154656) and it seems that the menu disappeared (even with a brandnew 'forrest seed'). SEE HTML snippet below. menu-index.html is empty (i.e. not even html/). The content is rendered correctly. I guess this is a bug?! I have the same problem (revision 154655): tabs and content is rendered correctly (although no tab highlighting), but no menu. Thus bug confirmed:-( Sjur - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
avoid rebuilding pages?
hey, the lenya site contains a changes.html created out of the SVN changelog [1] forrest takes over 5 minutes to create that page, which makes it a pita to wait for when running forrest site. from what i can tell, forrest spends a lot of time pondering the thousands of external links on that page (to SVN diffs) is it possible to instruct forrest to not rebuild that page? if not, maybe it should be developed. thanks, -gregor [1] http://lenya.apache.org/community/website-update.html#Generating+changes.html -- Gregor J. Rothfuss COO, Wyona Content Management Solutionshttp://wyona.com Apache Lenya http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED]
[JIRA] Commented: (FOR-356) multi-user capability (Was: Solaris problem)
The following comment has been added to this issue: Author: David Crossley Created: Mon, 21 Feb 2005 6:39 PM Body: Done the second part of Fabio's suggestion. Regarding the first part of the suggestion. That is not possible at the moment, because 'build clean' would remove it. Perhaps we should just have an FAQ about mult-user systems. - View this comment: http://issues.cocoondev.org//browse/FOR-356?page=comments#action_12063 - View the issue: http://issues.cocoondev.org//browse/FOR-356 Here is an overview of the issue: - Key: FOR-356 Summary: multi-user capability (Was: Solaris problem) Type: Bug Status: In Progress Priority: Major Project: Forrest Versions: 0.6 Assignee: Rick Tessner Reporter: Fabio Rinaldi Created: Mon, 8 Nov 2004 10:38 AM Updated: Mon, 21 Feb 2005 6:39 PM Description: Back in August I reported a problem about using Forrest in a multi-user environment. I have recently downloaded Forrest 0.6 and tried to install it on both a linux machine and a solaris system. I have found that there is still a problem that prevents generic users from using Forrest if installed as root. The problem is caused by an attempt to write in the forrest source code file area. I don't know which piece of code causes this error, but I have found that doing the following can solve it: chmod a+w $FORREST_HOME/context This solved the problem on the linux system, but not on the solaris system, because the filesystem where I have installed forrest is mounted read-only. In order to permanently solve the problem, it would be necessary to find the piece of code that requires write permissions to $FORREST_HOME/context (and change it, since there should be no reason to write there). - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: avoid rebuilding pages?
Gregor J. Rothfuss wrote: hey, the lenya site contains a changes.html created out of the SVN changelog [1] forrest takes over 5 minutes to create that page, which makes it a pita to wait for when running forrest site. from what i can tell, forrest spends a lot of time pondering the thousands of external links on that page (to SVN diffs) is it possible to instruct forrest to not rebuild that page? if not, maybe it should be developed. Try using the Cocoon cli.conf exclude pattern= ... http://forrest.apache.org/faq.html#ignoring_javadocs --David thanks, -gregor [1] http://lenya.apache.org/community/website-update.html#Generating+changes.html -- Gregor J. Rothfuss COO, Wyona Content Management Solutionshttp://wyona.com Apache Lenya http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED]
planning for 0.7 release
Ross Gardler wrote: David Crossley wrote: Dave Brondsema wrote: Because 0.6 docs are not split, things are pretty confusing. I speculate it might be worth it to get a 0.7 release out the door primarily so our online docs make sense. 0.7-dev has been pretty stable for a while and it has plugins working pretty good. release early, release often they say. We'd just bump all new features to the next version. Yes. I was going to propose the same thing. It would be okay to 0.8 0.9 0.10 0.11 until we are ready for the 1.0 release. We should prioritise the Jira Issues to aim for 0.7 ASAP. I'm fine with that, although I can't spend the time assisting right now (but should be able to in a couple of weeks). It takes quite a while to get ready for a release. It would be good to wait until Ross can help a bit because plugins is the major change for this release. I will also be busy for the next two weeks. Should we aim for a release date of Friday 2005-03-25? Remember that we need a week for release testing. --David
Re: planning for 0.7 release
David Crossley wrote: ... It takes quite a while to get ready for a release. It would be good to wait until Ross can help a bit because plugins is the major change for this release. I will also be busy for the next two weeks. Should we aim for a release date of Friday 2005-03-25? My birthday :-) Remember that we need a week for release testing. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: avoid rebuilding pages?
Gregor J. Rothfuss wrote: hey, the lenya site contains a changes.html created out of the SVN changelog [1] forrest takes over 5 minutes to create that page, which makes it a pita to wait for when running forrest site. Well, if you want to publish it, it has to be generated, no? ;-) For editing, use 'forrest run' and point to localhost:. from what i can tell, forrest spends a lot of time pondering the thousands of external links on that page (to SVN diffs) Are the svn diffs local? It should not go and look for public links, if it does it's wrong. Have you tried using a newer xalan and xerces version? Does the file take so long also doing a traqnsform ouside of Forrest? is it possible to instruct forrest to not rebuild that page? if not, maybe it should be developed. David already replied to this :-) thanks, -gregor [1] http://lenya.apache.org/community/website-update.html#Generating+changes.html -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
