Add UTF-8 encoded string to TextStringObject

[j-t-1]

Explanation

The text string type shall be used for character strings that shall be encoded in PDFDocEncoding, the UTF-16BE Unicode character encoding scheme, or (PDF 2.0) the UTF-8 Unicode character encoding scheme.

PDF 2.0 specification.

TextStringObject does not have UTF-8, introduced in PDF 2.0.

Adding this will update the classTextStringObject to the PDF 2.0 standard. Currently the class ignores UTF-8, and may be categorizing it as PDFDocEncoding.

[stefan6419846]

Please use the issue template when reporting possible issues. Additionally, please provide some more information where this is causing issues - as is, it is unclear what should be done about your issue and thus it is rather likely that I will have to close it as "unplanned".

[j-t-1]

Please use the issue template when reporting possible issues. Additionally, please provide some more information where this is causing issues - as is, it is unclear what should be done about your issue and thus it is rather likely that I will have to close it as "unplanned".

Edited the original.

[stefan6419846]

I still do not see how to reproduce this. Where is this an actual issue? Please provide a complete verifiable example.

[j-t-1]

It makes pypdf more consistent with the standard. See Figure 7 — Relationship between string types. The issue is where is UTF-8 in TextStringObject.

[stefan6419846]

It still is not obvious for me how this would look like in reality, thus having a proper example where we are currently not handling it correctly versus the correct result would be desirable. Could you please provide an appropriate one?

[j-t-1]

It still is not obvious for me how this would look like in reality, thus having a proper example where we are currently not handling it correctly versus the correct result would be desirable. Could you please provide an appropriate one?

Yes, I will try and find one.

Conceptually do you understand it? There is also a possibility that I am not understanding our codebase. Or it could be simply that we have not updated this part to the PDF 2.0 standard.