Bug 47752 - All Glyphs in the TTF files are not included
Summary: All Glyphs in the TTF files are not included
Status: NEW
Alias: None
Product: Batik - Now in Jira
Classification: Unclassified
Component: Utilities (show other bugs)
Version: 1.8
Hardware: PC Windows XP
: P2 enhancement
Target Milestone: ---
Assignee: Batik Developer's Mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-27 11:20 UTC by Damon Hopkins
Modified: 2009-10-22 06:52 UTC (History)
0 users



Attachments
A test font to reproduce said issue (46.44 KB, application/octet-stream)
2009-10-22 06:22 UTC, Xavier Tassin
Details
A test case to be used with Google Chrome (20.26 KB, application/zip)
2009-10-22 06:50 UTC, Xavier Tassin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Damon Hopkins 2009-08-27 11:20:05 UTC
In the windows system included font Arial.TTF some glyphs are not included in the SVG output. can you guys add a commandline option to include all glyphs?
Comment 1 Helder Magalhães 2009-08-28 05:44:56 UTC
(In reply to comment #0)
> In the windows system included font Arial.TTF some glyphs are not included in
> the SVG output. can you guys add a commandline option to include all glyphs?

Sorry, but I guess you'll need to be more specific [1]:

1. Instead of "All Glyphs in the TTF files are not included", do you mean that "not all glyphs in the TTF files are converted"?

2. I imagine you are using the SVG font converter [2], did you look at the available command-line switches ("l", "h", "ascii")?

3. Which glyphs were not included? Which command line did you use? What were you expecting? What would be "include all glyphs"? Etc.

4. Just stating "Arial.TTF" is probably not enough. Adding which particular font version (can be found in font preview dialog) might help.

5. Have you tried crawling through the mailing list? There are a few related posts [3] which might help.


I'd say that, without further information, this seems more a support request (which belongs best to the mailing list) than a bug report.


[1] http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
[2] http://xmlgraphics.apache.org/batik/tools/font-converter.html
[3] http://www.nabble.com/Help%3A-SVG-Font-Converter-cannot-extract-from-TTF-td24542788.html
Comment 2 Xavier Tassin 2009-10-22 06:22:50 UTC
Created attachment 24406 [details]
A test font to reproduce said issue
Comment 3 Xavier Tassin 2009-10-22 06:50:59 UTC
Created attachment 24407 [details]
A test case to be used with Google Chrome

Drop the test.html file in Google Chrome to see the missing glyph in action
Comment 4 Xavier Tassin 2009-10-22 06:52:34 UTC
Svg converted ttf fonts are often used for Google Chrome support of @font-face Css rule. HTML text using the svg font will display the <missing-glyph> (usually ugly little thing) when a Line-Feed character (U+000A) is met (in Windows).

I have fixed this manually, so far, by adding the following glyph entry to my svg font files:

<glyph unicode="&#x0a;" glyph-name="uni000A" horiz-adv-x="560" />

where the value of horiz-adv-x is equivalent to that of the "space" glyph. 

The font then behave as ttf does (in Firefox by example) by representing the LF character a simple space.

I am not sure, though, if this is acceptable both by SVG and Unicode standards.

This happened with every font I tested, with different range values and/or with setting the -autorange parameter.

Is it an idea to automatically (or by command) add the LF glyph to the font?