Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.2.1

Bug #13002 styles for span elements are rendered with incorrect style:family
Submitted: 2008-01-30 10:54 UTC
From: charonme Assigned: cweiske
Status: Closed Package: OpenDocument (version 0.1.2)
PHP Version: 5.2.1 OS: linux 2.6.20
Roadmaps: 0.2.0    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 49 - 7 = ?

 
 [2008-01-30 10:54 UTC] charonme (Charon Me)
Description: ------------ style:style elements (in content.xml) for text:span elements are rendered with incorrect attribute style:family="paragraph" instead of style:family="text" (the way OOo renders it). Test script: --------------- function applyStyle() in OpenDocument.php, line 522: $style->setAttributeNS(self::NS_STYLE, 'family', 'paragraph'); it works when replacing this line with something like: if (get_class($object)=='OpenDocument_Span') { $style->setAttributeNS(self::NS_STYLE, 'family', 'text'); } else { $style->setAttributeNS(self::NS_STYLE, 'family', 'paragraph'); } but it's possible that not all cases are handled or that this would have more severe side-effects in more complex situations Actual result: -------------- Styles set for span elements are not visible when opening the odt document in OOo or odf viewer.

Comments

 [2009-06-12 11:46 UTC] cweiske (Christian Weiske)
-Status: Open +Status: Verified
I can confirm this - had the same problem and found the same reason.
 [2009-06-22 00:07 UTC] cweiske (Christian Weiske)
-Status: Verified +Status: Closed -Assigned To: +Assigned To: cweiske
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.