fenix
/
cpdf-source
mirror of https://github.com/johnwhitington/cpdf-source.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove misleading description of JSON string format

This commit is contained in:
John Whitington 2022-01-23 12:20:41 +00:00
parent bdb855df06
commit 900f9c8acd
3 changed files with 5 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
cpdfjson.ml
View File

@ -23,12 +23,7 @@ Objects 1..n: The PDF's objects.
o Names are written as {"N": "/Pages"} o Names are written as {"N": "/Pages"}
o Indirect references are integers o Indirect references are integers
o Streams are {"S": [dict, data]} o Streams are {"S": [dict, data]}
o Strings are converted from UTF16BE/PDFDocEncoding to UTF8 before being o Strings are converted into JSON strings in a way which is fully reversible.
encoded in JSON. When they are read back the process is JSON encoded --> UTF8
--> UTF16BE/PDFDocEncoding. This process is fully reversible: it is to allow
easier editing of strings. This does not happen to strings within text
operators in parsed content streams, nor to /ID values in the
trailerdictionary, since neither is UTF16BE/PdfDocEncoding to begin with.
There are two subformats: parsing content streams or not. Hello World in CPDF There are two subformats: parsing content streams or not. Hello World in CPDF
JSON without parsing content streams: JSON without parsing content streams:

BIN
cpdfmanual.pdf
View File

Binary file not shown.

12
cpdfmanual.tex
View File

@ -2414,13 +2414,13 @@ annotations on the selected pages to standard output. Each annotation is precede
More information can be obtained by listing annotations in JSON format: More information can be obtained by listing annotations in JSON format:
\begin{framed} \begin{framed}
\small\verb!cpdf -list-annotations in.pdf > annots.txt! \small\verb!cpdf -list-annotations-json in.pdf > annots.json!
\vspace{2.5mm} \vspace{2.5mm}
\noindent Print annotations from \texttt{in.pdf}, redirecting output to \texttt{annots.txt}. \noindent Print annotations from \texttt{in.pdf} in JSON format, redirecting output to \texttt{annots.json}.
\end{framed} \end{framed}
This produces an array of (page number, CPDFJSON) pairs giving the PDF structure of each annotation. Destination pages for page links will have page numbers in place of internal PDF page links, and certain indirect objects are made direct but the content is otherwise unaltered. Here is an example entry for an annotation on page 10: This produces an array of (page number, annotation) pairs giving the PDF structure of each annotation. Destination pages for page links will have page numbers in place of internal PDF page links, and certain indirect objects are made direct but the content is otherwise unaltered. Here is an example entry for an annotation on page 10:
{\small\begin{verbatim} {\small\begin{verbatim}
[ [
@ -3171,11 +3171,7 @@ number, and flags used when writing (which may be required when reading):
\item Names are written as \texttt{\{"N":\ "/Pages"\}} \item Names are written as \texttt{\{"N":\ "/Pages"\}}
\item Indirect references are integers \item Indirect references are integers
\item Streams are \texttt{\{"S":\ [dict, data]\}} \item Streams are \texttt{\{"S":\ [dict, data]\}}
\item Strings are converted from UTF16BE/PDFDocEncoding to UTF8 before being \item Strings are converted to JSON string format in a way which, when reversed, results in the original string.
encoded in JSON. This process is fully reversible: it is to allow
easier editing of strings. This does not happen to strings within text
operators in parsed content streams, nor to /ID values in the
trailer dictionary, since neither is UTF16BE/PDFDocEncoding to begin with.
\end{itemize} \end{itemize}
\noindent Here is an example of the output for a small PDF: \noindent Here is an example of the output for a small PDF: