*Did you read the documentation before firing away a question?* *Did you make a standalone example that reproduces the problem?* *Did you browse the archives to see if the problem was already solved?*
Hello all, this mailing list has been useful for many iText developers, but recently I'm seriously questioning if we shouldn't close the list down. Why? Because lately more and more programmers think they can ask just anything. Two examples: [1] "TTF file has no effect": In spite of the fact that several examples were provided PROVING that the allegation in the subject line was wrong, the OP kept on posting "it still doesn't work". It may very well be that "it didn't work" FOR THE OP, but that is NOT OUR BUSINESS. In that particular case, it worked for us, and we provided PROOF. The OP however didn't even bother to make a standalone example supporting his false allegation. If he had done that effort, he would have realized the problem wasn't an iText problem, and he wouldn't have produced unnecessary noise on the list. [2] "Merging multiple pdfs": This is explained in great detail in the book. Whoever wants to evaluate iText should browse the examples http://itextpdf.com/book/examples.php and the keywords http://itextpdf.com/themes/keywords.php That is a FREE way to find out if iText meets the requirements. Whoever starts to work with iText should invest $35 to $60 in the book. You'll save much more than $60 worth in time if you read the book. Before you ask: I'm not saying this to get rich. I get an average of about $3 for each copy. I can't hide that I'm very passionate about PDF and iText, and this works in different directions. My passion makes that I sacrifice time and energy whenever I see an interesting challenge (such as writing a book), but unfortunately, I also feel (almost physical!) pain whenever I see people posting code that is beyond repair BECAUSE THEY JUST DON'T TAKE THE TIME TO READ THE BOOK. That is passion. It's supposed to be a good thing, but apparently some people hate me for it. A genuine question, such as the question about the font in a text field, gets a useful answer about the different ways to deal with appearances (creating them with iText, or passing the responsibility to Adobe Reader). But then the OP almost causes me a heart attack when I see the code he has written (proving that he didn't read the book). It is not my intention to make people look ridiculous (IMHO people do that to themselves; that also goes for me), I'm just begging: think twice before you post a question to this list. Don't say "it doesn't work" without any proof. Don't post code that looks as if it was generated at random. Don't say things such as "I don't have the Action book, I looking for quick solution" posted in the thread "Merge external resources (images and fonts) inside PDF Document". Don't people like that feel any shame when they post such inconsiderate remarks??? Did you read the documentation before firing away a question? Did you make a standalone example that reproduces the problem? Did you browse the archives to see if the problem was already solved? Do you deserve respect if the answer to these questions is: "No, I didn't bother..." Please understand that I care for iText, and because I care, I can't accept "Me too lazy, me looking for quick solution." ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
