Hi, thats good news. The super/sub-script problem is/was the last point on my todo-list. (The 'regard-problem-from-svn-todo-list'. There is another 'fix-bugzilla-bugs-todo-list').
The other problems were some rendering-problems which i thought had to do with threading (from scripting). The images looked good on single processor, but looked 'incomplete' when rendered with dual core. It was broken from summer to december. Its ok now running with jdk1.3, 1.4, 1.5 on single or dual cpu. Not so bad... greetings ----- Original Message ----- From: "Cameron McCormack" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, January 10, 2007 4:20 AM Subject: Re: Super and Sub Scripts in 'flow' tests > Thomas DeWeese: > > I was tracking down why the 'super' and 'sub' script text in > > the flow text examples isn't super and sub scripted and I found it. > > > > The new SVGTextElement bridge checks if the elements are subclasses of > > the 'SVGOMTextPositioningElement' class, if they are then it adds the 'x', > > 'y', > > 'dx', 'dy', and 'rotate' attributes to the Attributed string. However in > > this case > > the flowSpan element really only supports dx,dy and perhaps rotate > > (absolute positioning is not a good idea). > > > > I can think of three solutions: > > 1) introduce a new interface or class that defines just the > > dx/dy/rotate, > > and have the span elements implement that. > > 2) Just make the span elements subclass SVGOMTextPositioningElement > > and not worry about the 'x' & 'y' support. > > 3) Chalk the whole thing up as a loss anyway since the WG has moved > > in another direction. > > > > Normally I'd be inclined towards 3, except this is a true regression > > (reasonable content that worked previously would stop working). > > My leaning is towards 2 since it's simple and the whole thing is a > > loss anyway ;) One is probably "the right thing" except the whole > > thing is a loss anyway and it's not clear we will want to keep the > > "albatross" once the WG points the correct direction. > > > > Any opinions from the peanut gallery? > > I’m willing to go for the easy route to fix it, number 2. We don’t want > to put any more work into the flowText than is necessary, until we know > how it’s going to have to change once SVG 1.2 Full is worked on again. > After making SVGOMFlowSpanElement extend SVGOMTextPositioningElement, > getX() and getY() could be overridden to return empty lists, just to > ensure that those attributes don’t affect anything. > > It’s a hack, yes, but I don’t think it matters. > > -- > Cameron McCormack, http://mcc.id.au/ > xmpp:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
