DO NOT REPLY [Bug 48108] New: Special Characters are not rendering

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

           Summary: Special Characters are not rendering
           Product: Fop
           Version: all
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: critical
          Priority: P2
         Component: general
        AssignedTo: fop-dev@...
        ReportedBy: priyananth@...


if the source XML has "~" or "→" it renders as # in the output.

--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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

Jeremias Maerki <jeremias@...> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Jeremias Maerki <jeremias@...> 2009-11-02 23:45:46 UTC ---
Please see the following FAQ entry:
http://xmlgraphics.apache.org/fop/faq.html#pdf-characters

If the font you're using doesn't have the necessary glyphs, FOP can't make them
appear. You will need to select a font that has the glyphs you need. That '~'
is not available is a little peculiar. That glyph is available in almost all
latin fonts. However the arrow glyph is not. Maybe if you mentioned what fonts
you're trying to use, it would be easier to tell exactly what's going on.

Please follow up on fop-users@.... I'm fairly sure that this
is no bug.

--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[J.Pietschmann]

On 03.11.2009 08:45, bugzilla@... wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48108
[Snip]

Hi Devs,

I want to get an opinion: Should we start to emit error
messages if there is no glyph for a character in the current
font set? Of course, the user shouldn't be drowned in
essentially the same message over and over again, perhaps
by deferring the message to the end of processing and trying
to compressing multiple missing characters to ranges or
something like "mulitple characters from unicode block
NNN didn't have a glyph in font ..."

J.Pietschmann

[Christopher R. Maden]

J.Pietschmann wrote:
> I want to get an opinion: Should we start to emit error
> messages if there is no glyph for a character in the current
> font set? Of course, the user shouldn't be drowned in
> essentially the same message over and over again, perhaps
> by deferring the message to the end of processing and trying
> to compressing multiple missing characters to ranges or
> something like "mulitple characters from unicode block
> NNN didn't have a glyph in font ..."

+1, especially for the summary report format.

~Chris
--
Chris Maden, text nerd  <URL: http://crism.maden.org/ >
“The State is that great fiction by which everyone tries to live at
 the expense of everyone else.” — Frédéric Bastiat, “L’État”
GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319

[Jeremias Maerki-2]

We do warn about missing glyphs already in FOP Trunk but I'm sure this
can be improved. Here's some sample output:

[WARN ] Glyph "?" (0x223c, similar) not available in font "Helvetica".
[WARN ] Glyph "?" (0x2192, arrowright) not available in font "Helvetica".
[WARN ] Glyph "?" (0x3b1, alpha) not available in font "Helvetica".
[WARN ] Glyph "H" (0x48, H) not available in font "Symbol".
[WARN ] Glyph "e" (0x65, e) not available in font "Symbol".
[WARN ] Glyph "l" (0x6c, l) not available in font "Symbol".
[WARN ] Glyph "o" (0x6f, o) not available in font "Symbol".
[WARN ] Glyph "W" (0x57, W) not available in font "Symbol".
[WARN ] Glyph "r" (0x72, r) not available in font "Symbol".
[WARN ] Glyph "d" (0x64, d) not available in font "Symbol".
[WARN ] Glyph "~" (0x7e, asciitilde) not available in font "Symbol".
[WARN ] Glyph "?" (0x223c, similar) not available in font "ArialMT".

There's even a guard against to many such warnings per font. See
Typeface.java.

On 03.11.2009 21:53:17 J.Pietschmann wrote:

> On 03.11.2009 08:45, bugzilla@... wrote:
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=48108
> [Snip]
>
> Hi Devs,
>
> I want to get an opinion: Should we start to emit error
> messages if there is no glyph for a character in the current
> font set? Of course, the user shouldn't be drowned in
> essentially the same message over and over again, perhaps
> by deferring the message to the end of processing and trying
> to compressing multiple missing characters to ranges or
> something like "mulitple characters from unicode block
> NNN didn't have a glyph in font ..."
>
> J.Pietschmann

Jeremias Maerki