I am using iTextSharp to read pdf file. I am using pdfreader.GetPageContent() and PdfTextExtractor.GetTextFromPage() methods using simple text extraction strategy.
Both the methods not reading all the pdf's.
For one pdf if I use GetTextFromPage it's throwing Index was outside the bounds of the array exception(that page having bullet marks and special chars).
How to solve this problem ?
Recently a few bugs were fixed, so you have two options:
Wait for 5.1.4 to be released
Download and build the latest SVN yourself.
If you still have issues after building the latest SVN, either submit a bug report at sourceforge or subscribe to the mailing list and post there.
The recent bug fixes may or may not fix your specific problem. People keep complaining about the parsers, but many are unwilling to submit sample PDF(s) that reproduce the issue.
In other words, if the fixes don't solve your problem and you're unwilling to submit a bug report and sample PDF(s) you're out of luck.
Related
A day ago my prestashop website, in the comment box of the blog started to display the following message:
And entering the post that explains how to migrate the version of TinyMCE , I do not understand very well how to perform these steps in my prestashop.
How can I update this?a
if you are using a third-party module to make your blog it might be is including its own version of TinyMCE. You should try to dig in its code to understand that.
If this is not the case, the blog uses TinyMCE which is normally included in Prestashop core.
On said that, this second case is likely to be the one. Update the e-commerce unlikely will solve your problem. I honestly don't remember in which version they are with TinyMCE but doing an upgrade like that might break back-office editor forms so I don't think they are keen on that at the moment. They are doing a major rollover to Symfony, I am pretty sure this is their priority right now. As said in one comment, Prestashop's dev team has to solve the issue on their side.
I have iText version 5.0.4 installed and it has been working well. I was not aware at the rate new versions are being created.
Has anyone jumped from a similar version to a much later version and did you have any problems ?
I am experiencing a problem reading a few pdf's where pdfReader is failing when merging multiple pdf's into a single pdf and as I have not been able to identify the reason for the problem wanted to try upgrading as a test.
Thanks
You didn't specify which exception you're getting, but I can see three possible causes:
Closing streams, more specifically closing PdfReader, is now a responsibility of the developer, rather than a responsibility of iText. You may have to add or move reader.close() invocations.
We are less tolerant with respect to using broken PDFs (because using a broken PDF as input can lead to unexpected, incomplete results). We now throw an InvalidPdfException more often. (You can work around this by setting the debugmode to true).
There's a known problem (already fixed in the trunk) with 5.5.1 with respect to PdfCopy. If you use iText 5.5.0, this problem doesn't occur.
If one of your PDFs is encrypted, you'll need to make sure you also upgrade the BouncyCastle version. Mixing BouncyCastle versions leads to unpredictable errors. Check the POM file for each iText version to know which BouncyCastle is required.
If you're using PdfWriter to merge documents, you're doing it wrong.
Pick your answer depending on the exception you're getting.
In some cases I need to mark (several) lines of code in Eclipse. For example when reviewing, or when testing. Is there a feature or plug-in in Eclipse which can help me to that?
For now I'm just putting #REVIEWED or #TOBEREVIEWED on lines or around blocks. But that is a lot of work.
Any ideas?
EDIT: I'm aware of the Bookmark feature, but that seems to cover only 1 line.
EDIT2: I'm also aware of Task tags like TODO and FIXME, thanks E-Riz
You can use custom task tags in comments (the default is //TODO), which are automatically added to the Markers or Problems views in Eclipse. for example, you could create a custom task tag like //TO-REVIEW.
It's not exactly marking blocks of code, since it's essentially a marker for one line, but it is a convenient way to track and locate them. See the Eclipse Help page for more details.
Why not use some code review features of external server like GitHub?
I mean it could be nice to comment and discuss code blocks just within Eclipse,
but it is much overhead to develop and maintain comparing to web-based solution (that would be universal).
Then possibly such server has similar feature support as Eclipse plugin.
For example
if you use git, you can check GitHub and Eclipse EGit and Eclipse Mylyn tasks.
For perforce there is job concept (similar to issues).
So it leads to understanding that what you actually need is issue-tracker integrated into Eclipse that can conveniently point to code blocks. Again depends on your SCM.
You can us Eclipse plugin like Jupiter for code review. It will help to identify issues (if any) in code blocks with review comments without touching actual code.
The code review comments get stored in jupiter files in your respective project.
Developer can see those issues, fix and comment on them.
While doing some analysis on the usage details for the SquishIt framework, I came across a link as mentioned below:
https://danielsaidi.wordpress.com/tag/squishit/
which describes that SquishIt is having some problems with getting to work with JavaScript closures.
I am currently using the latest version :0.9.3.0 of SquishIt.Mvc. Can anyone help me to know whether this version has still the issues while working with JavaScript closures.
I am not aware of any issues at this time (was not aware of any in 2010 either however). It seems like any issues with closures are probably really issues with the minification library used, or files incorrectly terminated. At some point in the last couple years I think we did start adding semicolons between concatenated files if not present to deal with the latter. If you do find any I would love to hear about them.
There are certain Crystal Reports features that cannot be combined in the same report, for example SQL command objects and server side grouping. However, as far as I can find, the built-in help doesn't seem to clearly document these conflicts. For example, checking the help page for either of those features doesn't mention that it doesn't work with the other. I want to be able to find out about these conflicts when I decide to use a new feature, not later when I go to use some other feature and the option is greyed out. Is there any place that documents these conflicts?
I am specifically working with Crystal Reports XI. Bonus points if the list of conflicts documents what range of versions each feature is available and conflicting in.
I have now also checked the release notes (release.pdf on install CD), and it does not have any answers to this question.
I have not found these anywhere, my suggestion is to create a test/dummy report, make something painfully simple that runs what your trying together.
This is of course no guarantee that is will work once you get all your real data in there. But I've upvoted your question, cause I'd like to see those doc's myself.
For installation notes and details
regarding known issues with this
release, please refer to release.pdf
on the Crystal Reports CD.
How about the Known Issues list? Did you find anything there?