« Return to Thread: BaseFont.DirectTextToByte
Re: BaseFont.DirectTextToByte
by Stew Meyers-2
::
Rate this Message:
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
>
>
>
>
Aviso Legal:
Esta mensagem i destinada exclusivamente ao destinatario. Pode conter
informagco confidencial ou legalmente protegida. A incorrecta transmissco
desta mensagem nco significa a perca de confidencialidade. Se esta mensagem
for recebida por engano, por favor envie-a de volta para o remetente e
apague-a do seu sistema de imediato. I proibido a qualquer pessoa que nco o
destinatario de usar, revelar ou distribuir qualquer parte desta mensagem.
Disclaimer:
This message is destined exclusively to the intended receiver. It may
contain confidential or legally protected information. The incorrect
transmission of this message does not mean the loss of its confidentiality.
If this message is received by mistake, please send it back to the sender
and delete it from your system immediately. It is forbidden to any person
who is not the intended receiver to use, distribute or copy any part of this
message.
------------------------------------------------------------------------------
_______________________________________________
itextsharp-questions mailing list
itextsharp-questions@...
https://lists.sourceforge.net/lists/listinfo/itextsharp-questions
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
>
>
>
>
Aviso Legal:
Esta mensagem i destinada exclusivamente ao destinatario. Pode conter
informagco confidencial ou legalmente protegida. A incorrecta transmissco
desta mensagem nco significa a perca de confidencialidade. Se esta mensagem
for recebida por engano, por favor envie-a de volta para o remetente e
apague-a do seu sistema de imediato. I proibido a qualquer pessoa que nco o
destinatario de usar, revelar ou distribuir qualquer parte desta mensagem.
Disclaimer:
This message is destined exclusively to the intended receiver. It may
contain confidential or legally protected information. The incorrect
transmission of this message does not mean the loss of its confidentiality.
If this message is received by mistake, please send it back to the sender
and delete it from your system immediately. It is forbidden to any person
who is not the intended receiver to use, distribute or copy any part of this
message.
------------------------------------------------------------------------------
_______________________________________________
itextsharp-questions mailing list
itextsharp-questions@...
https://lists.sourceforge.net/lists/listinfo/itextsharp-questions
« Return to Thread: BaseFont.DirectTextToByte
| Free embeddable forum powered by Nabble | Forum Help |
