Paulo Soares wrote: > Reinventing the wheel is something that we do everyday, either because > of licence issues or because the available wheels don't fit too well > to our requirements. The problem is that iText is not a Java only library > and for the moment the only thing that is not supported in C# is Graphics2D. > Basing everything in the Java layout capabilities closes the door to other > implementations. Before worrying about the layout itself maybe we should > worry about encapsulating it in a sort of plug-in or well defined classes > that could be replaced according to the language capabilities, layoutGlyphs() > in Java and Uniscribe in C#, for example.
That's a good idea. I'll think about it. I have my dayjob tomorrow, but I'll see what I can do the day after. -- This answer is provided by 1T3XT BVBA http://www.1t3xt.com/ - http://www.1t3xt.info ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.1t3xt.com/docs/book.php
