https://issues.apache.org/bugzilla/show_bug.cgi?id=50100

--- Comment #4 from Helder Magalhães <[email protected]> 2010-10-27 
01:13:01 EDT ---
(In reply to comment #3)
> It appears that the class SVGFontDescriptor is responsible for display the 
> text
> and modifying:
> 
> attrMap.put(SVG_FONT_SIZE_ATTRIBUTE, fontSize);
> 
> to
> 
> attrMap.put(SVG_FONT_SIZE_ATTRIBUTE, fontSize + "px");
> 
> resolves the issues, but in doing so also impacts the case when useCSS=false,
> though [...]

Could you generate a patch with this and attach to this bug? I'd say it's not a
good correction, but I may already help other users in the meantime... :-)


> [...] it should be noted that in testing with Opera, Safari and Firefox that
> all three browsers appear to accept the unit in the non-CSS "font-size"
> attribute, and display the font in the correct sizes.

As stated (in comment 2) this had to do with compliance. I haven't checked for
sure but yes, your description corresponds to what the specification says it
should happen (and also to what my testing experience with this sort of things
has showed me, but last time I checked was probably a few years ago).


> Would simply appending the unit in this location be appropriate as a fix, or
> should we be looking at another approach to fixing this issue?

I'd say no, this isn't a good fix: you even already recognize it breaks
"useCSS=false", which would be an important regression IMO.

Also, I guess you generally can do that assumption (user units=px) but my
feeling is that some corner cases (like percent sizes) may not be covered by
this...? To be further investigated.

As stated above, I'd consider this a workaround until a better fix/ideas can be
provided (Cameron? Thomas?).

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to