Hi, ok, I'm starting to understand what you want to do, but I still don't see what effect setting the new charset variable has, if it is never used anywhere.
You set the charset variable to the charset you want. Where and how does that
influence further processing? I am not aware of a situation where adding a
variable that is never read has an influence on the output.
Greetings,
Mark
On Tuesday 26 September 2006 16:05, Lidong Liu wrote:
> The added code does not deal with Asian encodings directory. But with these
> change we can support Asian encoded font by specifying the encoding
> directly while using the itext api, otherwise we just can't set the charset
> except the several western charsets decided by iText code automatically. In
> the mean while, iText has a bug when creating a new RtfFont from RtfFont,
> which does not copy the charset. This could make the specified RtfFont
> useless.
>
> Here is a RtfFont creation example:
> RtfFont font11 = new RtfFont(
> new String("宋体".getBytes("gb18030"), "iso-8859-1"),
> 11, RtfFont.NORMAL, Color.BLACK, 134);
>
> which creates a RtfFont of Chinese font SimSun, setting the charset to 134.
--
If you learn one useless thing every day, in a single year you'll learn
365 useless things.
My GPG public key is available at:
http://www.edu.uni-klu.ac.at/~mhall/data/security/MarkHall.asc
pgpw9SSwOyPzN.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions
