On 30/08/2013 12:30, i...@samea.de wrote: > I do not sell or buy any licences > because my costumer do that.
Some integrators work like you do: they ask their customer to buy the license. However: they inform iText Software formally about the relationship with their customer, and often they get registered on the closed ticketing system (depending on the nature of the agreement). Some integrators even act as resellers, because it's a way for them to make some extra money: if they sell enough licenses, they can get a reduction/commission on the license price. We also forward assignments to them once in a while. The friction and frustration you witnessed today is due to the fact that you've never taken advantage of these options. Please look at the problem from my side: (1) The time aspect: Helping people for free is something we like doing, but we don't always have the time. Regardless of any rule, it's never fair for a subscriber of the FREE mailing-list to add pressure by posting the same question more than once, or by airing his frustration publicly. (2) The business aspect: I hope you also understand that integrators who do generate business get a higher priority than the ones that don't. The opposite would be unfair. (3) The reputation aspect: When somebody says "iText doesn't work", the problem often isn't caused by iText. For instance: you say that you followed the Kubrick example. If that is the case, you may have used the GoToE functionality. This functionality works in the Kubrick example because GoToE refers to PDF documents. It doesn't work for other types of documents, because of what is written in ISO-32000-1 section 12.6.4.4 "Embedded Go-To Actions": <quote>An embedded go-to action (PDF 1.6) is similar to a remote go-to action but allows jumping to or from a PDF file that is embedded in another PDF file.</quote> This tells you that jumping to or from an embedded PDF file is supported, not that jumping to docx or other formats is possible. So if you tell your customer that GoToE doesn't work for docx formats, it would be unfair to blame iText. It doesn't work in general. It's based on wrong interpretation of the spec. When somebody uses PdfCopy in a situation that calls for PdfStamper, one shouldn't blame iText, etc... At iText Software, we are PDF experts. We don't specialize in custom development (integration assignments, tailor-made projects,...), because we don't want to compete with you guys: freelancers, consultants, integrators,... On the contrary: we want to help your business! We want you to make as much money doing iText projects as possible. We don't expect freelancers, consultants, integrators,... to be experts with respect to PDF and/or iText, but we do want them to use iText correctly. If they don't know how to use iText correctly, they can expect our help... on condition that they work with us! If they don't (want to) work with us (for instance: I browsed your web site, and you don't mention iText anywhere), they get mails like the one that was sent today ;-) You wrote: "I was running out of time to proof that iText will be the right tool." That's a pity: you've spent 4 or 5 days looking for an answer that would have taken much less friction if you had contacted sales and specified that you had a pre-sales question. Sometimes we charge a small fee for an answer (if we need to write a PoC), but often that expense can be deducted from the license price once a license is purchased. Such an approach would probably have saved you and especially your customer time as well as money. I know that you'll no longer recommend iText, that's your decision and I respect it. I only wanted to share my personal point of view. ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. 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
