- From: Chris Lilley <chris@w3.org>
- Date: Mon, 23 Jun 2008 14:43:05 +0200
- To: Anthony Grasso <anthony.grasso@cisra.canon.com.au>
- Cc: W3C SVG Public Working Group <public-svg-wg@w3.org>
On Monday, June 23, 2008, 9:59:11 AM, Anthony wrote: AG> Hi Team, AG> I went through all of the tests in the test suite and fixed up template AG> issues and minor issues that Erik and others have pointed out to me. AG> All of the issues regarding SVGFreeSans font for the $Revision text [1] AG> have been fixed. If I get some free time I'll start fixing the errors in AG> the reference images [2]. AG> I also fixed a problem with intro-compat-201-t.svg - the test claimed to AG> be testing that UTF-16 is supported. However, the file was UTF-8 encoded. Really? I loaded it into a text editor that does both UTF-8 and UTF-16, edited the encoding declaration, then saved it out as UTF16. Is this the file in svg or svggen, that was UTF16? Its possible that the conversion script forces everything to be UTF-8 ... AG> Anthony AG> [1] AG> http://www.w3.org/Graphics/SVG/WG/wiki/View_the_list_of_known_issues#Doesn.27t_use_the_SVGFreeSans_font_for_the_.24Revision_text AG> [2] AG> http://www.w3.org/Graphics/SVG/WG/wiki/View_the_list_of_known_issues#Errors_in_the_reference_image -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Monday, 23 June 2008 12:43:42 UTC