Bug 34694 - ttf2svg and glyph-name attribute
Summary: ttf2svg and glyph-name attribute
Status: NEEDINFO
Alias: None
Product: Batik - Now in Jira
Classification: Unclassified
Component: Utilities (show other bugs)
Version: 1.6
Hardware: PC Windows XP
: P2 minor
Target Milestone: ---
Assignee: Batik Developer's Mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-01 11:54 UTC by Pierrick Brihaye
Modified: 2010-10-05 11:50 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pierrick Brihaye 2005-05-01 11:54:50 UTC 
Using ttf2svg from Batik 1.6 (sorry no entry for it in the combo).

I get a lot of glyph-name attributes with a "null" value.

From : http://www.w3.org/TR/SVG/fonts.html#GlyphElement

>A name for the glyph. It is recommended that glyph names be unique within a font.

and :

>glyph-name CDATA #IMPLIED

I think it's better to discard such unworthy glyph-name attributes.

p.b.
Comment 1 Cameron McCormack 2007-01-24 17:07:11 UTC 
Hi Pierrick.

Do you have a font which has these null glyph names that I could test with?

Thanks,

Cameron
Comment 2 Helder Magalhães 2010-10-05 11:50:34 UTC 
(In reply to comment #0)
> Using ttf2svg from Batik 1.6 (sorry no entry for it in the combo).

There is now! (Adjusted bug properties.) :-)


> I get a lot of glyph-name attributes with a "null" value.

As Cameron asked, it will be very hard to deal with this unless we can reproduce. Please consider either confirm this no longer occurs or attaching a problematic TTF file, along with some details (Java version, Operating System, Batik version, command line used).

Thanks! ;-)