sambox | PDFBox fork intended to be used as PDF processor | Document Editor library

by torakiki Java Version: v3.0.1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | sambox Summary

sambox is a Java library typically used in Editor, Document Editor applications. sambox has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

An [Apache PDFBox] fork intended to be used as PDF processor for [Sejda] and [PDFsam] related projects. What’s different from PDFBox?. SAMBox is a fork of a SNAPSHOT of PDFBox 2.0.0 and we try to keep it aligned with it. We performed massive changes on the original codebase and the same did the PDFBox guys since the time of the forking so merging back stuff from the PDFBox trunk is sometime challenging, we do our best. How do I load a document?. Some system properties are available to modify SAMBox default behaviour. Take a look at org.sejda.io.SeekableSources and org.sejda.sambox.SAMBox to find out which are currently available.

Support

Quality

Security

License

Reuse

Support

sambox has a low active ecosystem.

It has 45 star(s) with 16 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

There are 6 open issues and 147 have been closed. On average issues are closed in 0 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of sambox is v3.0.1

Quality

sambox has 0 bugs and 0 code smells.

Security

sambox has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sambox code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

sambox is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sambox releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

sambox saves you 77526 person hours of effort in developing the same functionality from scratch.

It has 89628 lines of code, 7244 functions and 797 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed sambox and discovered the below as its top functions. This is intended to give you an instant insight into sambox implemented functionality, and help decide if they suit your requirements.

Writes the page .
Extracts a seekable source from a tiff file .
Draw an ellipse .
Internal method to decrypt the enveloped data .
Insert a generated appearance stream .
Decodes predictor row .
Generate the normal appearance .
Creates cached color space if not already cached .
Reads a quoted string from the input stream .
Get the raster as a raster .

Get all kandi verified functions for this library.

sambox Key Features

No Key Features are available at this moment for sambox.

sambox Examples and Code Snippets

No Code Snippets are available at this moment for sambox.

Community Discussions

Trending Discussions on sambox

git is not having all branch files in ref dir AND not maintaining commit id in branch reference file. Why?

Strange behaviour of sejda-console in batch for loop

Split and merge pdf files using PDFBOX produces large file

QUESTION

git is not having all branch files in ref dir AND not maintaining commit id in branch reference file. Why?

Asked 2019-Sep-17 at 18:02

From, my understanding, GIT keeps track of branches using plain text files with name same as the branch name. These files are stored in .git\refs\remotes\origin for remote tracking of remote branches and for local branches these file are in .git\refs\heads

Below is the output from git branch:

...

ANSWER

Answered 2019-Sep-17 at 18:02

GIT keeps track of branches using plain text files with name same as the branch name.

Sometimes, yes. Sometimes no. You're not supposed to care. Why are you trying to inspect the .git/refs/heads/ files at all?¹

Git has a database,² somewhere, of name-to-hash-ID mappings. You can extract hash IDs from names using the git rev-parse program:³

Source https://stackoverflow.com/questions/57975690

QUESTION

Strange behaviour of sejda-console in batch for loop

Asked 2017-Nov-18 at 14:17

I try to write a wrapper script for songbook generation using lilypond, latex and sejda-console (for the pdf part). Everything works so far, but I have a problem with sejda that is giving me nuts. Here is the relevant part of my code:

...

ANSWER

Answered 2017-Nov-18 at 14:17

I'd suggest that sejda.bat is changing the current directory.

Try

Source https://stackoverflow.com/questions/47367010

QUESTION

Split and merge pdf files using PDFBOX produces large file

Asked 2017-Jul-12 at 04:27

I have this large print file in pdf that's contains 5544 pages and is about 36mb in size. The file is created by MS Word 2010 and contains only text and a logo on each letter/document.

I split it into 5544 files and merge back into 2770 letters, based on keywords. Each letter is approx. 140-145kb.

When I merge all the letters into a new pdf print file, still containing 5544 pages, the size of the file is grown to 396mb.

All text extracting, splitting and merging is performed with calls to Apache PDFBox command-line tools from PHP, but result is the same when run from a console.

Any idea how to reduce the file size of the letters and the final print file? It seems like PDFBox has just appended each letters in the final print file, instead creating a new pdf-document.

It's only in the testing phase that all the documents are merged into the final print file, some of the documents will be send by email.

I have also tried SAMBox (a fork of PDFBox) but with nearly the same result:

pdfinfo Original.pdf Title: Printfile Author: Claus Hjort Bube Creator: Microsoft® Word 2010 Producer: Microsoft® Word 2010 CreationDate: Fri May 19 12:16:34 2017 CEST ModDate: Fri May 19 12:16:34 2017 CEST Tagged: yes UserProperties: no Suspects: no Form: none JavaScript: no Pages: 5544 Encrypted: no Page size: 595.32 x 841.92 pts (A4) Page rot: 0 File size: 36092281 bytes Optimized: no PDF version: 1.5

pdfinfo PDFBox.pdf Title: Printfile Author: Claus Hjort Bube Creator: Microsoft® Word 2010 Producer: Microsoft® Word 2010 CreationDate: Fri May 19 12:16:34 2017 CEST ModDate: Fri May 19 12:16:34 2017 CEST Tagged: no UserProperties: no Suspects: no Form: none JavaScript: no Pages: 5544 Encrypted: no Page size: 595.32 x 841.92 pts (A4) Page rot: 0 File size: 396622354 bytes Optimized: no PDF version: 1.4

pdfinfo SAMBox.pdf Creator: Sejda Console 3.2.17 Producer: SAMBox 1.1.8 (www.sejda.org) ModDate: Tue Jul 11 23:34:33 2017 CEST Tagged: no UserProperties: no Suspects: no Form: none JavaScript: no Pages: 5544 Encrypted: no Page size: 595.32 x 841.92 pts (A4) Page rot: 0 File size: 378779436 bytes Optimized: no PDF version: 1.7

...

ANSWER

Answered 2017-Jul-12 at 04:27

That may sound sad but it is correct. When splitting, each file gets the resources (e.g. fonts and company logo graphic) it needs. When merged back, PDFBox does not know that these may be the same over the whole document, so these are now duplicated a lot.

The only solution I see for you would be to use the PDFBox java API to create the mailing files and the final print file in one step, i.e. without creating single files that are merged back.

Source https://stackoverflow.com/questions/45045571

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sambox

You can download it from GitHub, Maven.
You can use sambox like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the sambox component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: