Merge branch 'release/7.0.3'

Author: pavel-alay

BUILDING.md

@@ -0,0 +1 @@
+To build **iText 7 Community**, you need to build `itextsharp/itextcore/iTextCore.sln`.

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at http://itextpdf.com/contact. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,230 @@
+# Contributing to iText 7 Community
+
+We'd love for you to contribute to our source code and to make **iText 7 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 7 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 [[email protected]](mailto:[email protected]).
+* **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 `itext7` 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 for any change of more than 20 significant lines of code (we're not counting curly braces and other syntactical sugar).
+  We cannot accept code without this agreement.
+* Clone **iText 7 Community** to your local machine.
+
+     ```shell
+     git clone [email protected]:itext/itext7.git
+     cd itext7
+     git fetch origin
+     git checkout -b develop origin/develop
+     ```
+
+* Make your changes in a new git branch based off the develop branch:
+
+     ```shell
+     git checkout -b my-fix-branch develop
+     ```
+
+* Create your patch, **including appropriate test cases**.
+* Follow our [Coding Rules](#rules).
+* Run the full **iText 7 Community** test suite and ensure that all tests pass.
+* Commit your changes using a descriptive commit message that follows our
+  [commit message conventions](#commit-message-format).
+
+     ```shell
+     git commit -a
+     ```
+  Note: the optional commit `-a` command line option will automatically `add` and `rm` edited files.
+
+* 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 branch to your GitHub account:
+
+    ```shell
+    git remote add my-remote [email protected]:my-remote/itext7.git
+    git push my-remote my-fix-branch
+    ```
+
+* In GitHub, send a pull request to `itext7:develop`.
+* If we suggest changes then:
+  * Make the required updates.
+  * Re-run the **iText 7 Community** test suite to ensure tests are still passing.
+  * Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
+
+    ```shell
+    git fetch origin
+    git rebase develop -i
+    git push my-remote my-fix-branch -f
+    ```
+
+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 branch and pull the changes
+from the main (upstream) repository:
+
+* Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
+
+    ```shell
+    git push my-remote --delete my-fix-branch
+    ```
+
+* Check out the develop branch:
+
+    ```shell
+    git checkout develop -f
+    ```
+
+* Delete the local branch:
+
+    ```shell
+    git branch -D my-fix-branch
+    ```
+
+* Update your develop with the latest upstream version:
+
+    ```shell
+    git pull --ff upstream develop
+    ```
+
+
+## <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 Java code **must** be Java 7. Sorry, no lambda expressions or other Java 8 language features.
+* All features or bug fixes **must be tested** by one or more [unit tests][unit-testing].
+* 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 7 Community change log**.
+
+### 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 70 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:
+
+* use the imperative, present tense: "change" not "changed" nor "changes"
+* don't capitalize first letter
+* no dot (.) at the end
+* describe what the **change** does, not the actions the developer has done
+
+### Body
+Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
+The body should include the motivation for the change and contrast this with previous behavior.
+
+### Footer
+The footer should contain 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)** before sending pull requests. For any larger code
+changes (more than 20 lines of significant code) 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]: http://itextpdf.com/policy
+[coc]: CODE_OF_CONDUCT.md
+[github]: https://github.com/itext/itext7
+[java-style-guide]: http://www.oracle.com/technetwork/java/codeconvtoc-136057.html
+[javadocs]: http://itextpdf.com/api
+[pull]: https://github.com/itext/itext7/pulls
+[sscce]: http://sscce.org/
+[stackoverflow]: http://stackoverflow.com/questions/tagged/itext7
+[good-questions]: http://stackoverflow.com/help/how-to-ask
+[mcve]: http://stackoverflow.com/help/mcve
+[support]: http://itextpdf.com/support
+[unit-testing]: http://junit.org/

README.md

@@ -1 +1,59 @@
-This repository contains the .NET port of iText 7 Core.
+**[iText 7 Community][itext]** for .NET consists of several dlls.
+
+The **iText 7 Core/Community** release contains:
+
+- ```kernel.dll```: low-level functionality
+- ```io.dll```:  low-level functionality
+- ```layout.dll```: high-level functionality
+- ```forms.dll```: AcroForms
+- ```pdfa.dll```: PDF/A-specific functionality
+- ```pdftest.dll```: test helper classes
+- ```barcode.dll```: use this if you want to create bar codes
+- ```hyph.dll```: use this if you want text to be hyphenated
+- ```font-asian.dll```: use this is you need CJK functionality (Chinese / Japanese / Korean)
+- ```sign.dll```: use this if you need support for digital signatures
+
+The **iText 7 Community** source code is hosted on [Github][github], where you can also [download the latest releases][latest].
+
+*We strongly recommend that you use [NuGet][nuget] to add **iText 7 Community** to your project:*
+
+    Install-Package itext7
+
+You can also [build iText 7 Community from source][building].
+
+We also have a Java tool that can help you debug PDFs:
+
+- ```itext-rups-x.y.z.jar```
+
+RUPS is also hosted on [Github][github-rups].
+
+If you have an idea on how to improve **iText 7 Community** and you want to submit code,
+please read our [Contribution Guidelines][contributing].
+
+**iText 7** is dual licensed as [AGPL][agpl]/[Commercial software][sales].
+
+AGPL is a free / open source software license.
+
+This doesn't mean the software is [gratis][gratis]!
+
+Buying a license is mandatory as soon as you develop commercial activities
+distributing the iText software inside your product or deploying it on a network
+without disclosing the source code of your own applications under the AGPL license.
+These activities include:
+
+- offering paid services to customers as an ASP
+- serving PDFs on the fly in the cloud or in a web application
+- shipping iText with a closed source product
+
+Contact [sales] for more info.
+
+[agpl]: LICENSE.md
+[building]: BUILDING.md
+[contributing]: CONTRIBUTING.md
+[itext]: http://itextpdf.com/
+[github]: https://github.com/itext/itext7-dotnet
+[github-rups]: http://github.com/itext/rups
+[latest]: https://github.com/itext/itext7-dotnet/releases/latest
+[nuget]: https://www.nuget.org/packages/itext7
+[sales]: http://itextpdf.com/sales
+[gratis]: https://en.wikipedia.org/wiki/Gratis_versus_libre

itext.tests/itext.barcodes.tests/Properties/AssemblyInfo.cs

@@ -14,8 +14,9 @@
 
 [assembly: Guid("d015a3aa-613c-45d9-b908-7d47c4b613af")]
 
-[assembly: AssemblyVersion("7.0.2.0")]
-[assembly: AssemblyFileVersion("7.0.2.0")]
+[assembly: AssemblyVersion("7.0.3.0")]
+[assembly: AssemblyFileVersion("7.0.3.0")]
+[assembly: AssemblyInformationalVersion("7.0.3")]
 
 #if !NETSTANDARD1_6
 [assembly: NUnit.Framework.Timeout(300000)]

itext.tests/itext.barcodes.tests/itext/barcodes/Barcode128Test.cs

@@ -99,5 +99,11 @@ public virtual void Barcode02Test() {
             NUnit.Framework.Assert.IsNull(new CompareTool().CompareByContent(destinationFolder + filename, sourceFolder
                  + "cmp_" + filename, destinationFolder, "diff_"));
         }
+
+        [NUnit.Framework.Test]
+        public virtual void BarcodeRawValueGenerationTest01() {
+            NUnit.Framework.Assert.AreEqual(iText.IO.Util.JavaUtil.GetStringForBytes(new byte[] { 103, 17, 18, 19, 20, 
+                21, 17, 18, 19, 20, 21 }), Barcode128.GetRawText("1234512345", false, Barcode128.Barcode128CodeSet.A));
+        }
     }
 }