Hi, I tried to use the parameter pageSeparator on PDFTextStripper and noticed that it has no effect. I checked the sources and discovered that in all versions up to the current trunk, the setting is simply not used anywhere.
The only method using a set separator is writePageSeperator(), which also includes a typo worth fixing, but this method isn’t called anywhere. It should probably be called in processPages(). However, and this is why I didn’t go ahead and submit a patch myself, what does happen is that the pageEnd marker is written, which is initialized to the value of pageSeparator. So if both get used, this will probably end up in the same marker emitted twice on each page break. As a result, I’m unsure what to do about this and thought I’d leave it to the core team maintaining this, so I’m just reporting it here. Regards Maik
