Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/evotecit/pswritepdf
PowerShell Module to create, edit, split, merge PDF files on Windows / Linux and MacOS
https://github.com/evotecit/pswritepdf
create edit hacktoberfest merge pdf powershell split
Last synced: 4 days ago
JSON representation
PowerShell Module to create, edit, split, merge PDF files on Windows / Linux and MacOS
- Host: GitHub
- URL: https://github.com/evotecit/pswritepdf
- Owner: EvotecIT
- License: agpl-3.0
- Created: 2019-11-02T09:47:30.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2024-06-29T15:35:52.000Z (5 months ago)
- Last Synced: 2024-10-29T21:06:12.602Z (14 days ago)
- Topics: create, edit, hacktoberfest, merge, pdf, powershell, split
- Language: PowerShell
- Homepage:
- Size: 34.1 MB
- Stars: 190
- Watchers: 9
- Forks: 20
- Open Issues: 19
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.MD
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# PSWritePDF
**PSWritePDF is** by no means a finished product. Like with most of my modules, I build some concept that matches view on how I would like it to look, and in the next months, I will probably update its functionality to match my expectations. Since PSWritePDF is based on **iText 7** it should be possible with some work to get all that functionality into **PowerShell**. That means that this module has excellent possibilities when it comes to potential use cases.
For now, I've divided the module functionality into two categories:
- ☑ Standalone functions such as Split-PDF, Merge-PDF or Convert-PDFtoText
- ☑ Bundled functions working like PSWriteHTML where they are not supposed to be used separately mainly to create PDF files (for now)
To find out more read following blog posts:
- ☑ [Merging, splitting and creating PDF files with PowerShell](https://evotec.xyz/merging-splitting-and-creating-pdf-files-with-powershell/)
## 3rd Party Notices
This PowerShell Module uses [iText 7 Community for .NET](https://github.com/itext/itext7-dotnet) therefore the license needs to be kept the same as iText (or at least I think so). If it isn't so I would be more than happy to release my **PowerShell** code as **MIT license**. I don't intend to modify **iText7** codebase, just using it's **API**. As I'm not an expert on licensing I'm attaching some of articles I found that may make this license terms clearer.
Recommended read:
- [How do I make sure my software complies with AGPL: How can I use iText for free?](https://itextpdf.com/en/blog/technical-notes/how-do-i-make-sure-my-software-complies-agpl-how-can-i-use-itext-free)
- [Can I bundle iText with my non-commercial software?](https://itextpdf.com/en/resources/books/best-itext-questions-stack-overflow/can-i-bundle-itext-my-non-commercial-software)
- [AGPLv3 source redistribution: when does it apply to my code for a server-side Java app using an AGPL-licensed library?](https://opensource.stackexchange.com/questions/5003/agplv3-source-redistribution-when-does-it-apply-to-my-code-for-a-server-side-ja)
Other software used:
- Bouncy Castle [MIT license](https://www.bouncycastle.org/licence.html)
- Common License [Apache License 2.0](https://github.com/net-commons/common-logging/blob/master/license.txt)
All that additional software is required to work with iText and so it's part of this package.
## Installing / Updating
```powershell
Install-Module PSWritePDF -Force
```