On 28.02.2006 18:25:42 Andreas L Delmelle wrote:
> (Sorry, meant to reply on fop-users, so others have a chance to chime  
> in as well...)
> 
> Begin forwarded message:
> 
> > From: Andreas L Delmelle <[EMAIL PROTECTED]>
> > Date: February 28, 2006 18:17:26 GMT+01:00
> > To: [EMAIL PROTECTED]
> > Subject: Re: RTF and table/column widths
> >
> > On Feb 28, 2006, at 00:48, [EMAIL PROTECTED] wrote:
> >
> > > [Me: ]
> >>> On Feb 23, 2006, at 20:31, [EMAIL PROTECTED] wrote:
> >>>
> >>> <snip />
> >>>> (A less important fact is, that list bullets are not rendered
> >>>> properly, I had a question mark instead of a bullet. Somewhere I
> >>>> have the sample code for rendering fancy bullets to RTF...)
> >>>
> >>> Hmm... sounds like the much dreaded java.nio.charset.CharsetEncoder-
> >>> initial-value question-mark :-)
> >>> Is this really an RTF-specific issue AFAYCT? I hope...
> >> I dunno right now, but in PDF all the bullets are rendered  
> >> correctly, so there should be a possibility to render them both  
> >> from the same character, no matter what font or document format.  
> >> If it's totally impossible, a simple '-' should be used. Looks  
> >> better than '?'. I'll look through this, when I finished that  
> >> proportional width thing...
> >
> > I think I found what's causing the question-marks to appear in the  
> > RTF output...
> >
> > See org.apache.fop.render.rtf.RTFHandler, line 150. An  
> > OutputStreamWriter is instantiated, which uses the default platform  
> > encoding. Should be enough to force this Writer to use UTF-8, I think.

Nope, according to the RTF spec, the output should be in "US-ASCII"
(7-bit) for portability. UTF-8 is definitely not supported by RTF but I
think it's possible to use various 8-bit character sets and Unicode
escapes if the proper commands are generated. The Microsoft RTF spec
lists what is possible.


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to