CONTRIBUTING.md

@@ -0,0 +1,183 @@
+# Contributing to iText Community
+
+We'd love for you to contribute to our source code and to make **iText Community** even better than it is
+today! Here are the guidelines we'd like you to follow:
+
+ - [Question or Problem?](#question)
+ - [Issues and Bugs](#issue)
+ - [New Features](#feature)
+ - [Submission Guidelines](#submit)
+ - [Coding Rules](#rules)
+ - [Commit Message Guidelines](#commit)
+ - [Signing the iCLA](#cla)
+ - [Contributor Code of Conduct](#coc)
+
+
+## <a name="question">Got a Question or Problem?</a>
+
+If you have questions about how to use **iText Community**, please direct these to [Stack Overflow][stackoverflow].
+
+If you are a customer with a [support agreement][support], you also have direct access to our JIRA and our developers.
+
+
+## <a name="issue">Found an Issue?</a>
+If you find a bug in the source code or a mistake in the documentation, you can help us by
+submitting a [Pull Request][pull] with a fix.
+
+**Please see the [Submission Guidelines](#submit) below**.
+
+
+## <a name="feature">Want to implement a Feature?</a>
+If you would like to implement a new feature then consider what kind of change it is:
+
+* **Major Changes** that you wish to contribute to the project should be discussed first so that we can better
+coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully
+accepted into the project. Contact us at [community@itextpdf.com](mailto:community@itextpdf.com).
+* **Small Changes** can be crafted and submitted to the [GitHub Repository][github] as a [Pull Request][pull].
+
+
+## <a name="submit">Submission Guidelines</a>
+
+### Submitting a Question or an Issue
+Before you submit your question or issue, search [Stack Overflow][stackoverflow], maybe your question was already answered.
+
+If your issue appears to be a bug, and hasn't been reported, ask a question on [Stack Overflow][stackoverflow] to verify that is indeed a bug and not a mistake in your own code.
+Help us to maximize the effort we can spend fixing issues and adding new
+features, by not reporting duplicate issues. Providing the following information will increase the
+chances of your issue being dealt with quickly:
+
+* **[How to ask good questions][good-questions]**
+* **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
+* **Motivation for or Use Case** - explain why this is a bug for you
+* **iText Version(s)** - is it a regression?
+* **Operating System** - is this a problem on Windows or Linux, maybe on Mac?
+* **Reproduce the Error** - provide a [Short, Self Contained, Correct (Compilable), Example][sscce], also known as a [Minimal, Complete, and Verifiable example][mcve].
+* **Related Issues** - has a similar issue been reported before?
+* **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
+  causing the problem (line of code or commit)
+* **Tag the question** - add the tag `itext` to your question so we can find it.
+
+**If you get help, help others. Good karma rulez!**
+
+
+### Submitting a Pull Request
+Before you submit your pull request consider the following guidelines:
+
+* Search [GitHub][pull] for an open or closed Pull Request
+  that relates to your submission. You don't want to duplicate effort.
+* Verify that your proposed change hasn't already been addressed in the develop branch.
+* Don't send a separate pull request for every single file you change.  
+* Please sign the [iText Contributor License Agreement (iCLA)](#cla) before sending pull
+  requests. We cannot accept code without this agreement.
+* Fork the iText repository on GitHub.
+* Clone your iText fork to your local machine.
+* Make your changes, **including appropriate test cases**.
+* Follow our [Coding Rules](#rules).
+* Commit your changes using a descriptive commit message that follows our
+  [commit message conventions](#commit-message-format).
+* Now would be a good time to fix up your commits (if you want or need to) with `git rebase --interactive`.
+* Build your changes locally to ensure all the tests pass.
+* Push your changes to your GitHub account.
+* Create a pull request in GitHub.
+"Head fork" should be your repository, and the "base fork" should be the iText official repository.
+* If we suggest changes then:
+  * Make the required updates.
+  * Fix up your commits if needed, with an interactive rebase.
+  * Re-run the tests and make sure that they are still passing.
+  * Force push to your GitHub repository. This will update your Pull Request.
+
+That's it! Thank you for your contribution!
+
+#### After your pull request is merged
+
+After your pull request is merged, you can safely delete your fork and pull the changes
+from the main (upstream) repository.
+
+
+## <a name="rules">Coding Rules</a>
+To ensure consistency throughout the source code, keep these rules in mind as you are working:
+
+* We develop in Java first, and then port to .NET, so code submissions in Java are preferred.
+  Nevertheless this shouldn't stop you from making a good pull request to the .NET port.
+* All features or bug fixes **must be tested** by one or more unit tests.
+* All public API methods **must be documented** with JavaDoc. To see how we document our APIs, please check
+  out the existing [javadocs][javadocs].
+* We follow the rules contained in
+  [Oracle's Code Conventions for the Java Programming Language][java-style-guide], with these additions:
+    * Wrap all code at **100 characters**.
+
+
+## <a name="commit">Git Commit Guidelines</a>
+
+We have guidelines on how our git commit messages should be formatted. This leads to **more
+readable messages** that are easy to follow when looking through the **project history**. But also,
+we use the git commit messages to **generate the iText Community change log**.
+
+These guidelines were taken from Chris Beams' blog post [How to Write a Git Commit Message][git-commit].
+
+### Commit Message Format
+Each commit message consists of a **subject**, a **body** and a **footer**:
+
+```
+<subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+Any line of the commit message should not be longer 72 characters! This allows the message to be easier
+to read on GitHub as well as in various git tools.
+
+### Subject
+The subject contains succinct description of the change:
+
+* [Separate subject from body with a blank line][git-commit-separate]
+* [Limit the subject line to 50 characters][git-commit-limit-50]
+* [Capitalize the subject line][git-commit-capitalize]
+* [Do not end the subject line with a period][git-commit-end]
+* [Use the imperative mood in the subject line][git-commit-imperative]
+
+### Body
+* [Wrap the body at 72 characters][git-commit-wrap-72]
+* [Use the body to explain _what_ and _why_ vs. _how_][git-commit-why-not-how]
+
+### Footer
+The footer contains any information about **Breaking Changes** and is also the place to
+reference JIRA or GitHub issues that this commit **Closes**.
+
+
+## <a name="cla">Signing the iCLA</a>
+
+Please sign the [**iText Contributor License Agreement (iCLA)**][cla] before sending pull requests. For any code changes to be accepted, the iCLA must be signed. It's a quick process, we promise!
+
+We'll need you to [(digitally) sign and then email, fax or mail the form][cla].
+
+
+## <a name="coc">Contributor Code of Conduct</a>
+Please note that this project is released with a [Contributor Code of Conduct][coc]. By participating in this project you agree to abide by its terms.
+
+We use the [Stack Exchange][stackoverflow] network for free support and [GitHub][github] for code hosting. By using these services, you agree to abide by their terms:
+
+* StackExchange: [http://stackexchange.com/legal](http://stackexchange.com/legal)
+* Github: [https://help.github.com/articles/github-terms-of-service/](https://help.github.com/articles/github-terms-of-service/)
+
+[cla]: https://itextpdf.com/en/how-buy/legal/itext-contributor-license-agreement
+[coc]: CODE_OF_CONDUCT.md
+[github]: https://github.com/itext/i7j-pdfocr
+[java-style-guide]: https://www.oracle.com/technetwork/java/codeconvtoc-136057.html
+[javadocs]: https://itextpdf.com/api
+[pull]: https://github.com/itext/i7j-pdfocr/pulls
+[sscce]: http://sscce.org/
+[stackoverflow]: https://stackoverflow.com/questions/tagged/itext
+[good-questions]: https://stackoverflow.com/help/how-to-ask
+[mcve]: https://stackoverflow.com/help/mcve
+[support]: https://itextpdf.com/support
+[git-commit]: https://chris.beams.io/posts/git-commit/
+[git-commit-separate]: https://chris.beams.io/posts/git-commit/#separate
+[git-commit-limit-50]: https://chris.beams.io/posts/git-commit/#limit-50
+[git-commit-capitalize]: https://chris.beams.io/posts/git-commit/#capitalize
+[git-commit-end]: https://chris.beams.io/posts/git-commit/#end
+[git-commit-imperative]: https://chris.beams.io/posts/git-commit/#imperative
+[git-commit-wrap-72]: https://chris.beams.io/posts/git-commit/#wrap-72
+[git-commit-why-not-how]: https://chris.beams.io/posts/git-commit/#why-not-how

SECURITY.md

@@ -0,0 +1,40 @@
+# iText Security Policy
+
+## Reporting a Vulnerability
+
+We are committed to maintaining the security of our software. If you discover a security vulnerability, we encourage you to report it to us as soon as possible.
+
+To report a vulnerability, please visit our [Vulnerability Reporting Page](https://itextpdf.com/report-vulnerability), or email [vulnerability@apryse.com](vulnerability@apryse.com). If you do not receive a response in 2 business days, please follow up as we may not have received your message.
+
+We follow the procedure of Coordinated Vulnerability Disclosure (CVD) and, to protect the ecosystem, we request that those reporting do the same. Please visit the above page for more information, and follow the steps below to ensure that your report is handled promptly and appropriately:
+
+1. **Do not disclose the vulnerability publicly** until we have had a chance to address it.
+2. **Provide a detailed description** of the vulnerability, including steps to reproduce it, if possible.
+3. **Include any relevant information** such as the version of pdfOCR you are using, your operating system, and any other pertinent details.
+
+## Security Updates and Patches
+
+ When a vulnerability is reported, we will:
+
+1. **Investigate and verify** the vulnerability.
+2. **Develop and test** a fix for the vulnerability.
+3. **Release a patch** as soon as possible.
+
+
+## Known Vulnerabilities
+
+The iText Knowledge Base has a page for known [Common Vulnerabilities and Exposures](https://kb.itextpdf.com/itext/cves) (CVEs), please check it to ensure your vulnerability has not already been disclosed or addressed.
+
+## Supported product lines
+
+See [Compatibility Matrix](https://kb.itextpdf.com/itext/compatibility-matrix)
+
+## Security Best Practices
+
+To help ensure the security of your applications using pdfOCR, we recommend the following best practices:
+
+1. **Keep pdfOCR up to date** by regularly checking for and applying updates.
+2. **Review and follow** our security guidelines for secure usage.
+3. **Monitor your applications** for any unusual activity and investigate any anomalies promptly.
+
+Thank you for helping us keep iText secure!

pdfocr-api/pom.xml

@@ -5,13 +5,16 @@
   <parent>
     <groupId>com.itextpdf</groupId>
     <artifactId>pdfocr-root</artifactId>
-    <version>1.0.2</version>
+    <version>4.0.3-SNAPSHOT</version>
   </parent>
 
   <artifactId>pdfocr-api</artifactId>
 
   <name>pdfOCR API</name>
-  <description>pdfOCR is an iText 7 add-on for Java to recognize and extract text in scanned documents and images. It can also convert them into fully ISO-compliant PDF or PDF/A-3u files that are accessible, searchable, and suitable for archiving</description>
+  <description>pdfOCR is an iText add-on for Java to recognize and extract text in scanned documents and images. It can
+    also convert them into fully ISO-compliant PDF or PDF/A-3u files that are accessible, searchable, and suitable for
+    archiving
+  </description>
 
   <dependencies>
     <dependency>
@@ -47,4 +50,48 @@
       </resource>
     </resources>
   </build>
-</project>
+
+  <profiles>
+    <profile>
+      <id>with-sharpen</id>
+      <build>
+        <plugins>
+          <plugin>
+            <groupId>sharpen</groupId>
+            <artifactId>sharpen-maven-plugin</artifactId>
+            <version>1.0-SNAPSHOT</version>
+            <executions>
+              <execution>
+                <phase>install</phase>
+                <goals>
+                  <goal>sharpen</goal>
+                </goals>
+              </execution>
+            </executions>
+            <dependencies>
+              <dependency>
+                <groupId>sharpen</groupId>
+                <artifactId>standard-framework-mapping</artifactId>
+                <version>1.0-SNAPSHOT</version>
+              </dependency>
+            </dependencies>
+            <configuration>
+              <projectName>pdfocr</projectName>
+              <cSharpTargetFolder>./../../../sharp/pdfocr</cSharpTargetFolder>
+              <cSharpSourceCodeDestination>itext/itext.pdfocr.api</cSharpSourceCodeDestination>
+              <cSharpTestCodeDestination>itext.tests/itext.pdfocr.api.tests</cSharpTestCodeDestination>
+              <buildDotnet>${sharpen.builddotnet}</buildDotnet>
+              <showDiff>${sharpen.showdiff}</showDiff>
+              <sourceCodeFiles>
+                <file>**/src/main/java/**/*.java</file>
+              </sourceCodeFiles>
+              <testCodeFiles>
+                <file>**/src/test/java/**/*.java</file>
+              </testCodeFiles>
+            </configuration>
+          </plugin>
+        </plugins>
+      </build>
+    </profile>
+  </profiles>
+</project>

pdfocr-api/src/main/java/com/itextpdf/pdfocr/AbstractPdfOcrEventHelper.java

@@ -0,0 +1,55 @@
+/*
+    This file is part of the iText (R) project.
+    Copyright (c) 1998-2025 Apryse Group NV
+    Authors: Apryse Software.
+
+    This program is offered under a commercial and under the AGPL license.
+    For commercial licensing, contact us at https://itextpdf.com/sales.  For AGPL licensing, see below.
+
+    AGPL licensing:
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU Affero General Public License for more details.
+
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+ */
+package com.itextpdf.pdfocr;
+
+import com.itextpdf.commons.actions.AbstractITextEvent;
+import com.itextpdf.commons.actions.AbstractProductITextEvent;
+import com.itextpdf.commons.actions.confirmations.EventConfirmationType;
+import com.itextpdf.commons.actions.sequence.SequenceId;
+
+/**
+ * Helper class for working with events. This class is for internal usage.
+ */
+public abstract class AbstractPdfOcrEventHelper extends AbstractITextEvent {
+
+    /**
+     * Handles the event.
+     *
+     * @param event event
+     */
+    public abstract void onEvent(AbstractProductITextEvent event);
+
+    /**
+     * Returns the sequence id
+     *
+     * @return sequence id
+     */
+    public abstract SequenceId getSequenceId();
+
+    /**
+     * Returns the confirmation type of event.
+     *
+     * @return event confirmation type
+     */
+    public abstract EventConfirmationType getConfirmationType();
+}

pdfocr-api/src/main/java/com/itextpdf/pdfocr/IImageRotationHandler.java

@@ -1,7 +1,7 @@
 /*
     This file is part of the iText (R) project.
-    Copyright (c) 1998-2020 iText Group NV
-    Authors: iText Software.
+    Copyright (c) 1998-2025 Apryse Group NV
+    Authors: Apryse Software.
 
     This program is offered under a commercial and under the AGPL license.
     For commercial licensing, contact us at https://itextpdf.com/sales.  For AGPL licensing, see below.