You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Clay Leeds (JIRA)" <ji...@apache.org> on 2006/04/26 00:33:02 UTC

[jira] Created: (FOR-872) Updated odt_to_xhtml.xsl to pass & <h1> elements.</h1><pre>Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. --------------------------------------------------------- Key: FOR-872 URL: http://issues.apache.org/jira/browse/FOR-872 Project: Forrest Type: Improvement Components: Plugins: Potential new Versions: 0.8-dev Reporter: Clay Leeds Priority: Minor Attachments: odt_plugin.diff Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Web Maestro Clay <th...@gmail.com>.</b><hr/><pre>On May 10, 2006, at 12:22 AM, Ross Gardler wrote: > Clay Leeds wrote: >> I am looking into this further. The PATH to the files in question >> are defined in OpenOffice.org as: >> file:///Users/clay/Sites/myproject/src/documentation/content/ >> xdocs/ images/picture_01.jpg >> However, the images are embedded in the document as well (under >> $filename.odt/Pictures/*.jpg). I might be able to reference the >> images in the document as '/images/picture_01.jpg' but then they >> will no longer show as an image in the OOo/OpenDocument file. > > I recall struggling with this in the OOo plugin. I suggest you look > at how images are handled in there. > > (I would like to echo Ferdinands concerns about re-inventing the > wheel with this new ODT plugin. We should have at least forked the > OOo plugin to do this - too late now, but Clay, you should be aware > many problems will already be solved in the OOo plugin). > > Ross Much of the code that is in odt was copied from OOo: - odt-to-forrest-xhtml.xsl (xsl:stylesheet elements match odt xpath) - locationmap.xml (changed pattern to point to the odt plugin files) - resources.xmap (changed pattern to say 'openDocumentEmbeddedImage/ zip...') <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"> <map:pipelines> <map:pipeline internal="true"> <map:match pattern="openDocumentEmbeddedImage/zip-**/file-**.*"> <map:read src="jar:file:///{lm:project.{1}!/{2}.{3}}" mime- type="image/{3}" /> </map:match> <map:match pattern="**/openDocumentEmbeddedImage/zip-**/file- **.*"> <map:read src="jar:file:///{lm:project.{1}/{2}!/{3}.{4}}" mime-type="image/{4}" /> </map:match> </map:pipeline> </map:pipelines> </map:sitemap> I'll keep plugging away. In any case I'll need to modify the system to copy the $filename to the images/ directory structure to ensure image integrity. Web Maestro Clay the.webmaestro@gmail.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Ross Gardler <rg...@apache.org>.</b><hr/><pre>Clay Leeds wrote: > On May 9, 2006, at 8:19 PM, Clay Leeds wrote: > >> On May 5, 2006, at 4:58 PM, David Crossley wrote: >> >>> There is recent discussion in the mail archives about >>> relative paths to images. It causes the problem that >>> you refer to. >>> >>> -David >> >> >> I think I found the thread[1]. But I don't think it helps much. >> >> The images I'm 'referencing' are embedded in the OpenOffice.org ODT >> files. I don't refer to them as 'images/blah.jpg'. I don't place >> them in 'xdocs/images/' or 'resources/images/' and then reference >> them using relative paths. I pasted the graphics into OpenOffice.org >> files. It is the Cocoon pipeline that is copying them to >> build/images/ instead of build/site/images/. Cocoon copies them from >> their embedded 'Pictures/' directory in the ODT 'zip' file to >> build/images/blah.jpg instead of build/site/images/blah.jpg. >> >> What I think I need to do, is modify the Cocoon pipeline to ensure >> images are copied from {$filename/Pictures/*.jpg} them to build/ >> site/images/*.jpg. >> >> Even better--since, as I mentioned in my post, there might be a >> problem of having the same image name signify different images, it >> would be best to have the pipeline copy the files (and reference >> them!) to: build/site/images/$filename/*.jpg >> >> [1] >> http://thread.gmane.org/gmane.text.xml.forrest.devel/20274/focus=20291 >> >> [2] >> http://article.gmane.org/gmane.text.xml.forrest.devel/20301 > > > I am looking into this further. The PATH to the files in question are > defined in OpenOffice.org as: > > file:///Users/clay/Sites/myproject/src/documentation/content/xdocs/ > images/picture_01.jpg > > However, the images are embedded in the document as well (under > $filename.odt/Pictures/*.jpg). I might be able to reference the images > in the document as '/images/picture_01.jpg' but then they will no > longer show as an image in the OOo/OpenDocument file. I recall struggling with this in the OOo plugin. I suggest you look at how images are handled in there. (I would like to echo Ferdinands concerns about re-inventing the wheel with this new ODT plugin. We should have at least forked the OOo plugin to do this - too late now, but Clay, you should be aware many problems will already be solved in the OOo plugin). Ross </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Clay Leeds <we...@mac.com>.</b><hr/><pre>On May 9, 2006, at 8:19 PM, Clay Leeds wrote: > On May 5, 2006, at 4:58 PM, David Crossley wrote: >> There is recent discussion in the mail archives about >> relative paths to images. It causes the problem that >> you refer to. >> >> -David > > I think I found the thread[1]. But I don't think it helps much. > > The images I'm 'referencing' are embedded in the OpenOffice.org ODT > files. I don't refer to them as 'images/blah.jpg'. I don't place > them in 'xdocs/images/' or 'resources/images/' and then reference > them using relative paths. I pasted the graphics into > OpenOffice.org files. It is the Cocoon pipeline that is copying > them to build/images/ instead of build/site/images/. Cocoon copies > them from their embedded 'Pictures/' directory in the ODT 'zip' > file to build/images/blah.jpg instead of build/site/images/blah.jpg. > > What I think I need to do, is modify the Cocoon pipeline to ensure > images are copied from {$filename/Pictures/*.jpg} them to build/ > site/images/*.jpg. > > Even better--since, as I mentioned in my post, there might be a > problem of having the same image name signify different images, it > would be best to have the pipeline copy the files (and reference > them!) to: build/site/images/$filename/*.jpg > > [1] > http://thread.gmane.org/gmane.text.xml.forrest.devel/20274/focus=20291 > > [2] > http://article.gmane.org/gmane.text.xml.forrest.devel/20301 I am looking into this further. The PATH to the files in question are defined in OpenOffice.org as: file:///Users/clay/Sites/myproject/src/documentation/content/xdocs/ images/picture_01.jpg However, the images are embedded in the document as well (under $filename.odt/Pictures/*.jpg). I might be able to reference the images in the document as '/images/picture_01.jpg' but then they will no longer show as an image in the OOo/OpenDocument file. Clay Leeds webmaestro@mac.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Clay Leeds <we...@mac.com>.</b><hr/><pre>On May 5, 2006, at 4:58 PM, David Crossley wrote: > Clay Leeds (JIRA) wrote: >> [ http://issues.apache.org/jira/browse/FOR-872? >> page=comments#action_12377939 ] >> >> Clay Leeds commented on FOR-872: >> -------------------------------- >> >> Uh oh... The images don't work as well as planned. The Forrest >> resources.xmap places them in '../images/' instead of 'images/'. >> Since the images were placed in 'build/images/' instead of 'build/ >> site/images/' I didn't notice the problem until I tested on a >> separate server. >> >> BTW, we also need to ensure embedded images are placed in >> subdirectories based on $filename (similar to how OOo plugin >> works) to ensure embedded images from different files have a >> unique path, to ensure integrity of the page (if two embedded >> images are assigned the same name, then the image from the last >> file transformed would replace earlier versions with the same name). > > There is recent discussion in the mail archives about > relative paths to images. It causes the problem that > you refer to. > > -David I think I found the thread[1]. But I don't think it helps much. The images I'm 'referencing' are embedded in the OpenOffice.org ODT files. I don't refer to them as 'images/blah.jpg'. I don't place them in 'xdocs/images/' or 'resources/images/' and then reference them using relative paths. I pasted the graphics into OpenOffice.org files. It is the Cocoon pipeline that is copying them to build/ images/ instead of build/site/images/. Cocoon copies them from their embedded 'Pictures/' directory in the ODT 'zip' file to build/images/ blah.jpg instead of build/site/images/blah.jpg. What I think I need to do, is modify the Cocoon pipeline to ensure images are copied from {$filename/Pictures/*.jpg} them to build/site/ images/*.jpg. Even better--since, as I mentioned in my post, there might be a problem of having the same image name signify different images, it would be best to have the pipeline copy the files (and reference them!) to: build/site/images/$filename/*.jpg [1] http://thread.gmane.org/gmane.text.xml.forrest.devel/20274/focus=20291 [2] http://article.gmane.org/gmane.text.xml.forrest.devel/20301 Clay Leeds webmaestro@mac.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by David Crossley <cr...@apache.org>.</b><hr/><pre>Clay Leeds (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12377939 ] > > Clay Leeds commented on FOR-872: > -------------------------------- > > Uh oh... The images don't work as well as planned. The Forrest resources.xmap places them in '../images/' instead of 'images/'. Since the images were placed in 'build/images/' instead of 'build/site/images/' I didn't notice the problem until I tested on a separate server. > > BTW, we also need to ensure embedded images are placed in subdirectories based on $filename (similar to how OOo plugin works) to ensure embedded images from different files have a unique path, to ensure integrity of the page (if two embedded images are assigned the same name, then the image from the last file transformed would replace earlier versions with the same name). There is recent discussion in the mail archives about relative paths to images. It causes the problem that you refer to. -David </pre><hr/> <h2>Re: when to create a new Jira Issue</h2> <b>Posted by Thorsten Scherler <th...@apache.org>.</b><hr/><pre>El sáb, 06-05-2006 a las 13:56 +0200, Thorsten Scherler escribió: > El sáb, 06-05-2006 a las 10:10 +1000, David Crossley escribió: > > Clay Leeds (JIRA) wrote: > > > [ http://issues.apache.org/jira/browse/FOR-872 ] > > > > > > Clay Leeds updated FOR-872: > > > --------------------------- > > > > > > Attachment: odt_clay_003.diff > > > > > > Enables Images added to odt file to display/pass-through to Forrest site. > > > > > > NOTE: I wasn't sure if I should create a new issue (as this is unrelated to adding <title> & <h1> elements...), but I figured a) this is as good a place as any; b) less 'issues' is better! If someone wants to rename this issue 'Create OpenDocument Input Plugin', that'd be fine by me. > > > > I don't agree. Specific issues for specific tasks is better. > > Especially good Summary lines helps Jira's boolean search facility. > > > > For example with your above patch is difficult to relate > > the attachment name to the comment. > > > > Also the patch queue will then better prompt us. > > > > BTW, it is a pity that your patches are not being > > applied. Thorsten, you have this Assigned to yourself. > > Do you want to relinquish that? > > I applied the patches (please see the svn mailing list)! > > Then the issue got new issues. > > You are right that we should not reuse issues. Further like you can see at http://issues.apache.org/jira/browse/FOR-872?page=history "Change by Thorsten Scherler [27/Apr/06 10:24 PM] Status In Progress [ 3 ] Resolved [ 5 ]" That means the issue is fixed and will not be pursued anymore, right? Further the *new* patches (from the 04.05) are currently under discussion in this list. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) </pre><hr/> <h2>Re: when to create a new Jira Issue</h2> <b>Posted by Thorsten Scherler <th...@apache.org>.</b><hr/><pre>El sáb, 06-05-2006 a las 10:10 +1000, David Crossley escribió: > Clay Leeds (JIRA) wrote: > > [ http://issues.apache.org/jira/browse/FOR-872 ] > > > > Clay Leeds updated FOR-872: > > --------------------------- > > > > Attachment: odt_clay_003.diff > > > > Enables Images added to odt file to display/pass-through to Forrest site. > > > > NOTE: I wasn't sure if I should create a new issue (as this is unrelated to adding <title> & <h1> elements...), but I figured a) this is as good a place as any; b) less 'issues' is better! If someone wants to rename this issue 'Create OpenDocument Input Plugin', that'd be fine by me. > > I don't agree. Specific issues for specific tasks is better. > Especially good Summary lines helps Jira's boolean search facility. > > For example with your above patch is difficult to relate > the attachment name to the comment. > > Also the patch queue will then better prompt us. > > BTW, it is a pity that your patches are not being > applied. Thorsten, you have this Assigned to yourself. > Do you want to relinquish that? I applied the patches (please see the svn mailing list)! Then the issue got new issues. You are right that we should not reuse issues. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) </pre><hr/> <h2>when to create a new Jira Issue</h2> <b>Posted by David Crossley <cr...@apache.org>.</b><hr/><pre>Clay Leeds (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-872 ] > > Clay Leeds updated FOR-872: > --------------------------- > > Attachment: odt_clay_003.diff > > Enables Images added to odt file to display/pass-through to Forrest site. > > NOTE: I wasn't sure if I should create a new issue (as this is unrelated to adding <title> & <h1> elements...), but I figured a) this is as good a place as any; b) less 'issues' is better! If someone wants to rename this issue 'Create OpenDocument Input Plugin', that'd be fine by me. I don't agree. Specific issues for specific tasks is better. Especially good Summary lines helps Jira's boolean search facility. For example with your above patch is difficult to relate the attachment name to the comment. Also the patch queue will then better prompt us. BTW, it is a pity that your patches are not being applied. Thorsten, you have this Assigned to yourself. Do you want to relinquish that? -David </pre><hr/> <h2>[jira] Updated: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Clay Leeds updated FOR-872: --------------------------- Attachment: odt_clay_003.diff Enables Images added to odt file to display/pass-through to Forrest site. NOTE: I wasn't sure if I should create a new issue (as this is unrelated to adding <title> & <h1> elements...), but I figured a) this is as good a place as any; b) less 'issues' is better! If someone wants to rename this issue 'Create OpenDocument Input Plugin', that'd be fine by me. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>Re: [jira] Réouvert: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Ross Gardler <rg...@apache.org>.</b><hr/><pre>Cyriaque Dupoirieux wrote: > I don't know how to rollback, > Can anyone help me ? http://marc.theaimsgroup.com/?l=forrest-dev&m=111515940003138&w=2 Should do the trick (we should start a developers FAQ with these kind of things in). Ross </pre><hr/> <h2>Re: [jira] Réouvert: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.</b><hr/><pre>I don't know how to rollback, Can anyone help me ? Cyriaque, le 26/04/2006 16:57 Clay Leeds a écrit : > I think this should just be rolled back. I will take more time to > learn the ins and outs of cocoon matching, so we can do it the right > way (by importing a forrest-specific stylesheet). > > Web Maestro Clay > > On Apr 26, 2006, at 1:27 AM, Cyriaque Dupoirieux (JIRA) wrote: >> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] >> >> Cyriaque Dupoirieux reopened FOR-872: >> ------------------------------------- >> >> Reopen to take into account the remarks of Thorsten. >> (At the moment I don't rollback the commit, We will supply another >> patch quickly, Clay ? Do you have time ?) > > Clay Leeds > webmaestro@mac.com > > My religion is simple. My religion is kindness. > -- HH Dalai Lama of Tibet > > > > </pre><hr/> <h2>Re: [jira] R?ouvert: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Web Maestro Clay <th...@gmail.com>.</b><hr/><pre>On Apr 26, 2006, at 6:46 PM, David Crossley wrote: > Clay Leeds wrote: >> I think this should just be rolled back. I will take more time to >> learn the ins and outs of cocoon matching, so we can do it the right >> way (by importing a forrest-specific stylesheet). > > More likely by an additional transformer. I think > Thorsten already showed how. > > -David I was able to add it via an xsl:include + changing linkmap.xml to point to the forrest-specific xsl file (which includes the common file). This solution (while not final) gets us to exactly the same spot we were with the modified odt_to_xhtml.xsl file. My next step will be to apply an additional transformer. Clay Leeds the.webmaestro@gmail.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] R?ouvert: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by David Crossley <cr...@apache.org>.</b><hr/><pre>Clay Leeds wrote: > I think this should just be rolled back. I will take more time to > learn the ins and outs of cocoon matching, so we can do it the right > way (by importing a forrest-specific stylesheet). More likely by an additional transformer. I think Thorsten already showed how. -David </pre><hr/> <h2>Re: [jira] Réouvert: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Clay Leeds <we...@mac.com>.</b><hr/><pre>I think this should just be rolled back. I will take more time to learn the ins and outs of cocoon matching, so we can do it the right way (by importing a forrest-specific stylesheet). Web Maestro Clay On Apr 26, 2006, at 1:27 AM, Cyriaque Dupoirieux (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-872?page=all ] > > Cyriaque Dupoirieux reopened FOR-872: > ------------------------------------- > > Reopen to take into account the remarks of Thorsten. > (At the moment I don't rollback the commit, We will supply another > patch quickly, Clay ? Do you have time ?) Clay Leeds webmaestro@mac.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] Réouvert: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Clay Leeds <we...@mac.com>.</b><hr/><pre>I think this should just be rolled back. I will take more time to learn the ins and outs of cocoon matching, so we can do it the right way (by importing a forrest-specific stylesheet. Web Maestro Clay On Apr 26, 2006, at 1:27 AM, Cyriaque Dupoirieux (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-872?page=all ] > > Cyriaque Dupoirieux reopened FOR-872: > ------------------------------------- > > Reopen to take into account the remarks of Thorsten. > (At the moment I don't rollback the commit, We will supply another > patch quickly, Clay ? Do you have time ?) Clay Leeds webmaestro@mac.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>[jira] Réouvert: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Cyriaque Dupoirieux (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Cyriaque Dupoirieux reopened FOR-872: ------------------------------------- Reopen to take into account the remarks of Thorsten. (At the moment I don't rollback the commit, We will supply another patch quickly, Clay ? Do you have time ?) > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Cyriaque Dupoirieux > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_plugin.diff > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Updated: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Clay Leeds updated FOR-872: --------------------------- Attachment: odt_clay_004.diff Updates resources/stylesheets/odt-to-forrest-xhtml.xsl to enable passing of images pasted into ODT files, as well as passing <strong> (bold) and <em> (italic) text. Unfortunately, as with the old SXW format, it appears OpenOffice.org is inconsistent in how it applies strong emphasis ('bold'). I suspect is similarly inconsistent with italic, but I haven't tested. In the following example, some bold items were styled 'on-the-fly' as "T1", according to this definition in the content.xml file: <style:style style:name="T1" style:family="text"> <style:text-properties fo:font-weight="bold" style:font-weight-asian="bold" style:font-weight-complex="bold" /> </style:style> The above is similar to how Dreamweaver creates a CSS stylesheet on-the-fly, embedded at the top of an HTML file. Here's one snippet of my ODT file: <text:p text:style-name="Standard"> <text:span text:style-name="T1"> ACME Systems </text:span> actively markets <text:span text:style-name="T1"> ACME </text:span> , a fully-integrated product movement and accounting system developed specifically for the industry. <text:span text:style-name="T1"> ACME </text:span> stands for <text:span text:style-name="Strong_20_Emphasis"> A </text:span> nother, <text:span text:style-name="Strong_20_Emphasis"> C </text:span> ool, <text:span text:style-name="Strong_20_Emphasis"> M </text:span> ediocre <text:span text:style-name="Strong_20_Emphasis"> E </text:span> ntity. The applications have been in operation since 1990 in the industry. </text:p> All items styled as "T1" or "Strong_20_Emphasis" are bold when displayed in OOo. Unfortunately, since ACME Systems is styled as T1, instead of Strong_20_Emphasis, it does not display as bold in my output. I would have to trap for T1, as well, which this attachment does not do. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_clay_004.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl, resources.xmap > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Updated: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Clay Leeds updated FOR-872: --------------------------- Attachment: odt_to_xhtml-forrest.xsl this belongs here: org.apache.forrest.plugin.input.odt/resources/stylesheets/odt_to_xhtml-forrest.xsl ... and expects to find the odt_to_xhtml.xsl file here: org.apache.forrest.plugin.input.odt/resources/stylesheets/common/odt_to_xhtml.xsl > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Assigned: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Thorsten Scherler reassigned FOR-872: ------------------------------------- Assign To: (was: Thorsten Scherler) I assigned myself for the patches till 27/Apr/06, where I reolved this issue. After this date the issue got still used besides the fact that the Status is "Resolved"! > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_clay_004.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl, resources.xmap > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Work started: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Work on FOR-872 started by Thorsten Scherler > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12378222 ] Clay Leeds commented on FOR-872: -------------------------------- Sorry about that. I should not have reused this issue. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_clay_004.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl, resources.xmap > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Fermé: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Cyriaque Dupoirieux (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Cyriaque Dupoirieux closed FOR-872: ----------------------------------- Fix Version: 0.8-dev Resolution: Fixed Assign To: Cyriaque Dupoirieux Patch applied, Thank to Clay Leeds. (BTW - The Idea to retrieve the Document Title is the best solution on my opinion.) > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Cyriaque Dupoirieux > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_plugin.diff > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Assignées: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Cyriaque Dupoirieux (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Cyriaque Dupoirieux reassigned FOR-872: --------------------------------------- Assign To: (was: Cyriaque Dupoirieux) > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_plugin.diff > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Ross Gardler <rg...@apache.org>.</b><hr/><pre>Web Maestro Clay wrote: > On May 5, 2006, at 8:36 AM, Ross Gardler wrote: > >> Cyriaque Dupoirieux wrote: >> >>> le 05/05/2006 17:13 Ross Gardler a écrit : >>> ... >>>> It doesn't require that much more work since it will (hopefully) >>>> only be a case of copying over the code from the OOo plugin. >>>> >>>> The fact that it creates invalid XDocs is not a huge problem as it >>>> only affects things on the internal side of Forrest and so >>>> validation checks are not an issue (in fact the internal format is >>>> not valid in many other ways too). We can return and address this at >>>> a later date. > > > David Crossley mentioned in another thread[1], that document-v11.dtd is > similar to document-v13.dtd, except: > ==== > >> Why "transform.docv10.docv11"? No problem: docv11 >> is essentially the same as docv13, some restrictions >> were relaxed and every element can have a @class attr. > > ==== It's not the presences of clas attributes that make it invalid. It is the fact that the class definitions are placed in the XDoc head. As I pointed out earlier we are now able to do this a different way, since locationmaps and plugin sitemaps allow us to intercept the request for skinconf.xml. In the dispatcher it will be slightly different (but easier). Are you using skins or dispatcher? Obviously you will ant a solution that suits your needs. >> In SXW, if I remember rifhtly, T1 was the predefined style called >> "Title 1" in the drop down styles list. > That is correct. This file did begin 'life' as an SXW file. I started > the site for a client by copying the files into using OOo and saving > them as SXW files. After getting bitten by the many bugs in OOo's SXW > styling system we opted to create an ODT plugin instead of updating OOo. > I'll have to go through each file and clear formatting, then reapply > bold and italic where necessary. Should be no need to do that with my approach. Simply allow whatever styiling you want to pass through. Remember with this appraoch it is irrevlevant what the style is called, we are using the actual definitions of styles not the names of styles. > [1] > http://article.gmane.org/gmane.text.xml.forrest.user/3540 > > p.s. Shouldn't this discussion be happening in JIRA? No we don't discuss in Jira, it's not a convenient mechanism for free flowing and threaded discussion. What we need to do now is place short a summary of the discussionin and a link to the archives in the relevant issue. Ross </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Web Maestro Clay <th...@gmail.com>.</b><hr/><pre>On May 5, 2006, at 8:36 AM, Ross Gardler wrote: > Cyriaque Dupoirieux wrote: >> le 05/05/2006 17:13 Ross Gardler a écrit : >>> Your approach makes two assumptions, both of which are, in my >>> opinion, flawed: >>> >>> 1) we know what T1 is used for by the user >>> 2) we can force a predefined style on T1 and the document will >>> still look right >>> >>> My approach allows us to pull the style information from the OOo >>> document and therefore respect the users wishes within the >>> confines of the web designers rules. Agreed. Let us proceed with your approach. >>> It doesn't require that much more work since it will (hopefully) >>> only be a case of copying over the code from the OOo plugin. >>> >>> The fact that it creates invalid XDocs is not a huge problem as >>> it only affects things on the internal side of Forrest and so >>> validation checks are not an issue (in fact the internal format >>> is not valid in many other ways too). We can return and address >>> this at a later date. David Crossley mentioned in another thread[1], that document-v11.dtd is similar to document-v13.dtd, except: ==== > Why "transform.docv10.docv11"? No problem: docv11 > is essentially the same as docv13, some restrictions > were relaxed and every element can have a @class attr. ==== >> Ross, I fully agree with you, but I have search in one of my odt >> files with bold characters (style="T1") and I can't find the style >> definition in the T1 style ? > > This highlights a third incorrect assumption about styles in ODT docs: > > - there is consistency in the style names used across different ODT > editing environemnts > >> It seems to be a predefined style ? > > I just loooked in an ODT file for the first time and was pleasently > suprised to find sensible style names and not codes like "T1" as > was used in SXW. Perhaps the document Web Maestro Clay is referring > to started life as an SXW? > > In SXW, if I remember rifhtly, T1 was the predefined style called > "Title 1" in the drop down styles list. > > Ross That is correct. This file did begin 'life' as an SXW file. I started the site for a client by copying the files into using OOo and saving them as SXW files. After getting bitten by the many bugs in OOo's SXW styling system we opted to create an ODT plugin instead of updating OOo. I'll have to go through each file and clear formatting, then reapply bold and italic where necessary. [1] http://article.gmane.org/gmane.text.xml.forrest.user/3540 p.s. Shouldn't this discussion be happening in JIRA? Web Maestro Clay the.webmaestro@gmail.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Ross Gardler <rg...@apache.org>.</b><hr/><pre>Cyriaque Dupoirieux wrote: > le 05/05/2006 17:13 Ross Gardler a écrit : > >> Web Maestro Clay wrote: >> >>> On May 5, 2006, at 3:01 AM, Ross Gardler wrote: >>> >> >> ... >> >>> In this case if the class="T1" attribute were allowed to pass >>> through, suppose I could just create a style for it in skinconf.xml. >>> Then, I don't think it would be invalid code (unless the DTD doesn't >>> allow that). We could 'pick and choose' styles that way... Any >>> styles which are not in skinconf.xml would be ignored. If we could >>> modify the pipeline to only allow styles from skinconf.xml it would >>> be all the better. >> >> >> Your approach makes two assumptions, both of which are, in my opinion, >> flawed: >> >> 1) we know what T1 is used for by the user >> 2) we can force a predefined style on T1 and the document will still >> look right >> >> My approach allows us to pull the style information from the OOo >> document and therefore respect the users wishes within the confines of >> the web designers rules. >> >> It doesn't require that much more work since it will (hopefully) only >> be a case of copying over the code from the OOo plugin. >> >> The fact that it creates invalid XDocs is not a huge problem as it >> only affects things on the internal side of Forrest and so validation >> checks are not an issue (in fact the internal format is not valid in >> many other ways too). We can return and address this at a later date. > > Ross, I fully agree with you, but I have search in one of my odt files > with bold characters (style="T1") and I can't find the style definition > in the T1 style ? This highlights a third incorrect assumption about styles in ODT docs: - there is consistency in the style names used across different ODT editing environemnts > It seems to be a predefined style ? I just loooked in an ODT file for the first time and was pleasently suprised to find sensible style names and not codes like "T1" as was used in SXW. Perhaps the document Web Maestro Clay is referring to started life as an SXW? In SXW, if I remember rifhtly, T1 was the predefined style called "Title 1" in the drop down styles list. Ross </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.</b><hr/><pre>le 05/05/2006 17:13 Ross Gardler a écrit : > Web Maestro Clay wrote: >> On May 5, 2006, at 3:01 AM, Ross Gardler wrote: >> > > ... > >> In this case if the class="T1" attribute were allowed to pass >> through, suppose I could just create a style for it in skinconf.xml. >> Then, I don't think it would be invalid code (unless the DTD doesn't >> allow that). We could 'pick and choose' styles that way... Any >> styles which are not in skinconf.xml would be ignored. If we could >> modify the pipeline to only allow styles from skinconf.xml it would >> be all the better. > > Your approach makes two assumptions, both of which are, in my opinion, > flawed: > > 1) we know what T1 is used for by the user > 2) we can force a predefined style on T1 and the document will still > look right > > My approach allows us to pull the style information from the OOo > document and therefore respect the users wishes within the confines of > the web designers rules. > > It doesn't require that much more work since it will (hopefully) only > be a case of copying over the code from the OOo plugin. > > The fact that it creates invalid XDocs is not a huge problem as it > only affects things on the internal side of Forrest and so validation > checks are not an issue (in fact the internal format is not valid in > many other ways too). We can return and address this at a later date. Ross, I fully agree with you, but I have search in one of my odt files with bold characters (style="T1") and I can't find the style definition in the T1 style ? It seems to be a predefined style ? Salutations, Cyriaque, > > Ross > > </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Ross Gardler <rg...@apache.org>.</b><hr/><pre>Web Maestro Clay wrote: > On May 5, 2006, at 3:01 AM, Ross Gardler wrote: > ... > In this case if the class="T1" attribute were allowed to pass through, > suppose I could just create a style for it in skinconf.xml. Then, I > don't think it would be invalid code (unless the DTD doesn't allow > that). > We could 'pick and choose' styles that way... Any styles which > are not in skinconf.xml would be ignored. If we could modify the > pipeline to only allow styles from skinconf.xml it would be all the > better. Your approach makes two assumptions, both of which are, in my opinion, flawed: 1) we know what T1 is used for by the user 2) we can force a predefined style on T1 and the document will still look right My approach allows us to pull the style information from the OOo document and therefore respect the users wishes within the confines of the web designers rules. It doesn't require that much more work since it will (hopefully) only be a case of copying over the code from the OOo plugin. The fact that it creates invalid XDocs is not a huge problem as it only affects things on the internal side of Forrest and so validation checks are not an issue (in fact the internal format is not valid in many other ways too). We can return and address this at a later date. Ross </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Web Maestro Clay <th...@gmail.com>.</b><hr/><pre>On May 5, 2006, at 3:01 AM, Ross Gardler wrote: > Clay Leeds (JIRA) wrote: >> [ http://issues.apache.org/jira/browse/FOR-872? >> page=comments#action_12377927 ] Clay Leeds commented on FOR-872: >> -------------------------------- >> BTW, you could add the following to resources/stylesheets/odt-to- >> forrest-xhtml.xsl to get T1 to be styled as STRONG/BOLD: >> <xsl:template match="text:p/text:span[@text:style-name='T1']"> >> <strong> >> <xsl:apply-templates/> >> </strong> >> </xsl:template> > > I've not looked at your full stylesheets yet, but have a comment on > the above. > > The problem with this kind of approach is that it assumes that "T1" > is always "strong". My experience with OOo tells me this is a bad > assumption (may have changed in OOo2. Yes I know. That's why I didn't commit the change and added it to a comment. But I'm glad you have a better idea... ;-) > It is better to dynamically generate the CSS from the styles > definitions in the ODT file. They are already in CSS format so it > is not a big job. I did this in the OOo plugin as an experiment > [1]. What it does is use the template below to generate the style > definitions in the head of the XDoc, but see [2] for some > discussion about this. > > <xsl:template name="style"> > <!-- HACK: This makes intermediate documents invalid per the > Forrest Document DTD. To find out why this is done this way > nonetheless, read the comments attached to issue FOR-433. --> > <style> > <xsl:apply-templates select="//office:styles/style:style"/> > <xsl:apply-templates select="//office:automatic-styles/ > style:style"/> > </style> > </xsl:template> > > Now, as you can see this not valid in the XDoc schema. It works, > but it is a hack (at least it did in my experiments, but that was a > long time ago, things may have changed to break it now). Instead of > embedding the content in the XDoc head we should have a separate > request that generates the extra-css for the skinnning stage. We > had a discussion about how to do this recently [3] > > My ultimate goal with these experiments (which stalled a long time > ago) was to allow a subset of the OOo style information to pass > through to the rendering of a Forrest content object. The idea was > to have this subset defined in a config file, thus individual users > would be able to say what style information from OOo was vald in > their final output. For example, they could choose to not allow > colour definition trough in order to ensure a consistent colour > scheme, but to allow underlines through. > > Ross In this case if the class="T1" attribute were allowed to pass through, suppose I could just create a style for it in skinconf.xml. Then, I don't think it would be invalid code (unless the DTD doesn't allow that). We could 'pick and choose' styles that way... Any styles which are not in skinconf.xml would be ignored. If we could modify the pipeline to only allow styles from skinconf.xml it would be all the better. > [1] http://svn.apache.org/viewcvs.cgi/forrest/trunk/plugins/ > org.apache.forrest.plugin.input.OpenOffice.org/resources/ > stylesheets/openoffice-common-to-forrest.xsl?rev=332656&view=markup > [2] http://issues.apache.org/jira/browse/FOR-433 > [3] http://marc.theaimsgroup.com/?l=forrest-dev&m=114605585503695&w=2 Web Maestro Clay the.webmaestro@gmail.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Ross Gardler <rg...@apache.org>.</b><hr/><pre>Clay Leeds (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12377927 ] > > Clay Leeds commented on FOR-872: > -------------------------------- > > BTW, you could add the following to resources/stylesheets/odt-to-forrest-xhtml.xsl to get T1 to be styled as STRONG/BOLD: > > <xsl:template match="text:p/text:span[@text:style-name='T1']"> > <strong> > <xsl:apply-templates/> > </strong> > </xsl:template> I've not looked at your full stylesheets yet, but have a comment on the above. The problem with this kind of approach is that it assumes that "T1" is always "strong". My experience with OOo tells me this is a bad assumption (may have changed in OOo2. It is better to dynamically generate the CSS from the styles definitions in the ODT file. They are already in CSS format so it is not a big job. I did this in the OOo plugin as an experiment [1]. What it does is use the template below to generate the style definitions in the head of the XDoc, but see [2] for some discussion about this. <xsl:template name="style"> <!-- HACK: This makes intermediate documents invalid per the Forrest Document DTD. To find out why this is done this way nonetheless, read the comments attached to issue FOR-433. --> <style> <xsl:apply-templates select="//office:styles/style:style"/> <xsl:apply-templates select="//office:automatic-styles/style:style"/> </style> </xsl:template> Now, as you can see this not valid in the XDoc schema. It works, but it is a hack (at least it did in my experiments, but that was a long time ago, things may have changed to break it now). Instead of embedding the content in the XDoc head we should have a separate request that generates the extra-css for the skinnning stage. We had a discussion about how to do this recently [3] My ultimate goal with these experiments (which stalled a long time ago) was to allow a subset of the OOo style information to pass through to the rendering of a Forrest content object. The idea was to have this subset defined in a config file, thus individual users would be able to say what style information from OOo was vald in their final output. For example, they could choose to not allow colour definition trough in order to ensure a consistent colour scheme, but to allow underlines through. Ross [1] http://svn.apache.org/viewcvs.cgi/forrest/trunk/plugins/org.apache.forrest.plugin.input.OpenOffice.org/resources/stylesheets/openoffice-common-to-forrest.xsl?rev=332656&view=markup [2] http://issues.apache.org/jira/browse/FOR-433 [3] http://marc.theaimsgroup.com/?l=forrest-dev&m=114605585503695&w=2 </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12377927 ] Clay Leeds commented on FOR-872: -------------------------------- BTW, you could add the following to resources/stylesheets/odt-to-forrest-xhtml.xsl to get T1 to be styled as STRONG/BOLD: <xsl:template match="text:p/text:span[@text:style-name='T1']"> <strong> <xsl:apply-templates/> </strong> </xsl:template> I've done that temporarily in my own template, but I don't think it makes sense to COMMIT this change, as I don't believe T1 will always just be BOLD/STRONG. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_clay_004.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl, resources.xmap > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12377911 ] Clay Leeds commented on FOR-872: -------------------------------- Ignore the 'diff' file 'odt_clay_003.diff' as 'odt_clay_004.diff' includes templates to match <strong> (bold) and <em> (italic) templates. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl, resources.xmap > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Assigned: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Thorsten Scherler reassigned FOR-872: ------------------------------------- Assign To: Thorsten Scherler > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12376579 ] Clay Leeds commented on FOR-872: -------------------------------- I notice that the OOo plugin places the 'common' file 'openoffice-common-to-forrest.xsl' at the same level as the openoffice-writer-to-forrest.xsl & openoffice-impress-to-forrest.xsl files. That would be fine. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Updated: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Clay Leeds updated FOR-872: --------------------------- Attachment: resources.xmap Enables OpenDocument images to be passed through, and included on the web page. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl, resources.xmap > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Thorsten Scherler <th...@apache.org>.</b><hr/><pre>To satisfy my curiosity, I just tested successfully as well with old fashion skins. Trying to say that both dispatcher and skins are working fine for me which is actually not a big surprise since the odt is an input plugin. That means the result of it, is a xdocs. Once it is a xdocs both dispatcher and skins should render it without problems. salu2 El vie, 28-04-2006 a las 21:02 +0200, Thorsten Scherler escribió: > El vie, 28-04-2006 a las 14:12 +0000, Clay Leeds (JIRA) escribió: > > [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12376943 ] > > > > Clay Leeds commented on FOR-872: > > -------------------------------- > > > > Does this work for you? What do I need to do, to be able to use this ODT plugin again? It worked before but now it's broken. > > It works for me just fine. > > Try to open > plugins/org.apache.forrest.plugin.input.OpenOffice.org/src/documentation/content/xdocs/samples/openoffice-writer-howto.sxw > with OOo2 and save it as odt to your xdocs dir > (openoffice-writer-howto.odt). > > IMPORTANT: Make sure you made an update of > https://svn.apache.org/repos/asf/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.odt!!! > > Deploy it local > cd $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.input.odt > $FORREST_HOME/tools/ant/bin/ant local-deploy > > cd $YOUR_PROJECT/ > forrest run > http://localhost:8888/openoffice-writer-howto.html > > P.S. I tried with the dispatcher. > > salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) </pre><hr/> <h2>Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Thorsten Scherler <th...@apache.org>.</b><hr/><pre>El vie, 28-04-2006 a las 14:12 +0000, Clay Leeds (JIRA) escribió: > [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12376943 ] > > Clay Leeds commented on FOR-872: > -------------------------------- > > Does this work for you? What do I need to do, to be able to use this ODT plugin again? It worked before but now it's broken. It works for me just fine. Try to open plugins/org.apache.forrest.plugin.input.OpenOffice.org/src/documentation/content/xdocs/samples/openoffice-writer-howto.sxw with OOo2 and save it as odt to your xdocs dir (openoffice-writer-howto.odt). IMPORTANT: Make sure you made an update of https://svn.apache.org/repos/asf/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.odt!!! Deploy it local cd $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.input.odt $FORREST_HOME/tools/ant/bin/ant local-deploy cd $YOUR_PROJECT/ forrest run http://localhost:8888/openoffice-writer-howto.html P.S. I tried with the dispatcher. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12376943 ] Clay Leeds commented on FOR-872: -------------------------------- Does this work for you? What do I need to do, to be able to use this ODT plugin again? It worked before but now it's broken. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12377939 ] Clay Leeds commented on FOR-872: -------------------------------- Uh oh... The images don't work as well as planned. The Forrest resources.xmap places them in '../images/' instead of 'images/'. Since the images were placed in 'build/images/' instead of 'build/site/images/' I didn't notice the problem until I tested on a separate server. BTW, we also need to ensure embedded images are placed in subdirectories based on $filename (similar to how OOo plugin works) to ensure embedded images from different files have a unique path, to ensure integrity of the page (if two embedded images are assigned the same name, then the image from the last file transformed would replace earlier versions with the same name). > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_clay_003.diff, odt_clay_004.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl, resources.xmap > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12377011 ] Clay Leeds commented on FOR-872: -------------------------------- It's working now. I had to use an older forrest distribution I had as a backup (to which I did an `SVN up`). I'm going to annihilate the other forrest dist and continue on with this other one. BTW, I had done all the regular stuff (`svn up`, `ant local-deploy`, etc.). Weird. > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Updated: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Clay Leeds (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Clay Leeds updated FOR-872: --------------------------- Attachment: odt_002.diff Here's the change to locationmap.xml I should've made. It was so easy! ;-) Sorry for the trouble! It requires the following: - an additional file (to be attached shortly): org.apache.forrest.plugin.input.odt/resources/stylesheets/odt_to_xhtml-forrest.xsl - odt_to_xhtml-forrest.xsl expects to find the odt_to_xhtml.xsl file here: org.apache.forrest.plugin.input.odt/resources/stylesheets/common/odt_to_xhtml.xsl Feel free to modify this however you see fit! If you want to move stuff around, or don't want it in a 'common/' folder, by all means change it! BTW, why is this empty: http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.odt/resources/stylesheets/ Are we doing magic where Lenya is hosting the info somehow and it's not duplicated? > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>Re: [jira] Resolved: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Web Maestro Clay <th...@gmail.com>.</b><hr/><pre>On Apr 27, 2006, at 3:24 PM, Thorsten Scherler (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-872?page=all ] > > Thorsten Scherler resolved FOR-872: > ----------------------------------- > > Resolution: Fixed Clay Leeds the.webmaestro@gmail.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>Re: [jira] Resolved: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by Web Maestro Clay <th...@gmail.com>.</b><hr/><pre>On Apr 27, 2006, at 3:24 PM, Thorsten Scherler (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-872?page=all ] > > Thorsten Scherler resolved FOR-872: > ----------------------------------- > > Resolution: Fixed I get errors now: <broken-links> <link message="The content of elements must consist of well-formed character data or markup." uri="products/invoicing.html"> <referrer uri="linkmap.html"/> </link> ... ...it appears that there is a serious issue which needs to be resolved. Any clues? Clay the.webmaestro@gmail.com My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet </pre><hr/> <h2>[jira] Resolved: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=all ] Thorsten Scherler resolved FOR-872: ----------------------------------- Resolution: Fixed > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Thorsten Scherler > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_002.diff, odt_plugin.diff, odt_to_xhtml-forrest.xsl > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> <h2>[jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.</h2> <b>Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.</b><hr/><pre> [ http://issues.apache.org/jira/browse/FOR-872?page=comments#action_12376414 ] Thorsten Scherler commented on FOR-872: --------------------------------------- IMO we should not patch the common/odt_to_xhtml.xsl. The patch can be applyed different: The idea is to have a forrest specific xsl which imports the common one and override some matches and adds new ones. Like shown in http://svn.apache.org/viewcvs?rev=394204&view=rev That mean we have to change the input.xmap from the odt plugin like: <map:resource name="file-resolver"> <map:select type="exists"> <map:when test="{lm:project.{uri}.odt}"> <map:generate src="zip://content.xml@{lm:project.{uri}.odt}" /> - <map:transform src="{lm:transform.odt.xhtml}" /> + <map:transform src="{lm:transform.odt.xhtml.forrest}" /> <map:transform src="{lm:transform.xml.xml-namespace-stripped}" /> <map:transform src="{lm:transform.html.document}" /> <map:serialize type="xml" /> </map:when> </map:select> </map:resource> where {lm:transform.odt.xhtml.forrest} looks kind of http://svn.apache.org/viewcvs.cgi/lenya/trunk/src/modules/opendocument/xslt/opendocument2xhtml.xsl?rev=394204&view=markup > Updated odt_to_xhtml.xsl to pass <title> & <h1> elements. > --------------------------------------------------------- > > Key: FOR-872 > URL: http://issues.apache.org/jira/browse/FOR-872 > Project: Forrest > Type: Improvement > Components: Plugins: Potential new > Versions: 0.8-dev > Reporter: Clay Leeds > Assignee: Cyriaque Dupoirieux > Priority: Minor > Fix For: 0.8-dev > Attachments: odt_plugin.diff > > Modified odt_to_xhtml.xsl to pass the first text heading (office:document-content/office:body/office:text/text:h[1]) as the Forrest output's HTML <title> & <h1> elements. > Eventually, this will be changed to grab the OpenDocument 'Title' attribute (/office:document-meta/office:meta/dc:title). -- 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 </pre><hr/> </body> </html>