On Fri, Jan 07, 2011 at 02:44:13PM +0100, Jeremias Maerki wrote:
> I think so. The use of "#" is mostly historical due to lack of Unicode
> support initially. At least I believe so. The first fonts were WinAnsi
> only. IMO, it makes sense to make that transition. However, for
> single-byte fonts, we might still need to use "#". Not sure.

Then it might be better to use '?', which many tools use for that
purpose.

Let us put that on our wish list. It is not part of the fix for this
bug report.

Simon

> On 07.01.2011 14:17:42 Simon Pepping wrote:
> > On Fri, Jan 07, 2011 at 07:31:07AM -0500, bugzi...@apache.org wrote:
> > > https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
> > > 
> > > --- Comment #4 from Andreas L. Delmelle <adelme...@apache.org> 2011-01-07 
> > > 07:31:03 EST ---
> > > 
> > > Very right indeed. 
> > > So, if no one objects, I will apply the patch as proposed. FOP will no 
> > > longer
> > > crash, but simply show a '#' for such unassigned codepoints in the output.
> > > Treating them as regular alphabetic characters seems to be safe enough 
> > > for the
> > > time being.
> > 
> > Would it not be better to use character FFFD, 'Replacement Character',
> > ?, for this?

Reply via email to