Re: BaseFont.DirectTextToByte

> -----Original Message-----
> From: Stew Meyers [mailto:smeyers@...]
> Sent: Thursday, June 25, 2009 6:46 PM
> To: 'Post all your questions about iTextSharp here'
> Subject: Re: [itextsharp-questions] BaseFont.DirectTextToByte
>
> Thanks for the link.
>
> I tried using the new version of DocumentFont, but got a
> bunch of compile
> errors that referred to abstract members not being
> implemented in the base
> class.  So then I downloaded the new version of BaseFont and
> am now getting
> compile errors in CJKFont, TrueTypeFont, Type1Font, &
> Type3Font.  Do you
> think I can download these files as well for use with v4.0.8.0?
>
> - Stew
>  
> -----Original Message-----
> From: Paulo Soares [mailto:psoares@...]
> Sent: Thursday, June 25, 2009 1:18 PM
> To: Post all your questions about iTextSharp here
> Subject: Re: [itextsharp-questions] BaseFont.DirectTextToByte
>
> You may get away with this:
> http://itextsharp.svn.sourceforge.net/viewvc/itextsharp/trunk/
> src/core/iText
> Sharp/text/pdf/DocumentFont.cs?revision=2&view=markup&sortby=d
> ate. Using
> BaseFont.DirectTextToByte is not recommended as it will fail with some
> encodings.
>
> Paulo
>
> > -----Original Message-----
> > From: Stew Meyers [mailto:smeyers@...]
> > Sent: Thursday, June 25, 2009 5:27 PM
> > To: 'Post all your questions about iTextSharp here'
> > Subject: Re: [itextsharp-questions] BaseFont.DirectTextToByte
> >
> > Unfortunately, I am stuck with sticking with v4.0.8.0 since
> > some deprecated
> > classes were unfortunately completely removed.  Is it
> > possible to either
> > describe the fix that was done so I can make the change in
> > v4.0.8.0; or if
> > you think it is Ok to always set BaseFont.DirectTextToByte to
> > true for all
> > text (including normal text, symbols, etc) then that would be
> > fine as well.
> >
> > Thanks much,
> >
> > - Stew
> >
> > -----Original Message-----
> > From: Paulo Soares [mailto:psoares@...]
> > Sent: Thursday, June 25, 2009 12:11 PM
> > To: Post all your questions about iTextSharp here
> > Subject: Re: [itextsharp-questions] BaseFont.DirectTextToByte
> >
> > That's a bug that's already fixed in the SVN.
> >
> > Paulo
> >
> > > -----Original Message-----
> > > From: Stew Meyers [mailto:smeyers@...]
> > > Sent: Thursday, June 25, 2009 2:47 PM
> > > To: itextsharp-questions@...
> > > Subject: [itextsharp-questions] BaseFont.DirectTextToByte
> > >
> > > Hello,
> > >
> > >  
> > >
> > > I was trying to determine how why certain symbols were not
> > > appearing on PDF forms created through iTextSharp, and came
> > > across BaseFont.DirectTextToByte.  After setting this
> > > property to true, the symbols now appear on the PDF form.  As
> > > an example, I want to use the 'Registered' symbol (decimal
> > > #174) in the Arial TTF.  Leaving BaseFont.DirectTextToByte at
> > > its default value (false) produces a blank, but setting the
> > > value to true produces the proper symbol.
> > >
> > >  
> > >
> > > I searched the archives and looked in iText in Action, but
> > > could not find any information about this property.  Is there
> > > any reason why it should not be set to true all the time?  So
> > > far in my tests, I have not had any problems with setting it
> > > to true for all text produced through iTextSharp.
> > >
> > >  
> > >
> > > Thank you