From 04edfe9fade7e77342f5e4fe694ee071554a119c Mon Sep 17 00:00:00 2001
From: Jay Berkenbilt <ejb@ql.org>
Date: Sat, 23 Jan 2021 17:58:23 -0500
Subject: QPDFObjectHandle::newUnicodeString to uses UTF-16 only when needed

Use the first of ASCII, PDFDocEncoding, or UTF-16 that is capable of
encoding the string.
---
 manual/qpdf-manual.xml | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

(limited to 'manual/qpdf-manual.xml')

diff --git a/manual/qpdf-manual.xml b/manual/qpdf-manual.xml
index a969ce32..e2b5a83e 100644
--- a/manual/qpdf-manual.xml
+++ b/manual/qpdf-manual.xml
@@ -4821,6 +4821,26 @@ print "\n";
    <varlistentry>
     <term>10.2.0: Month dd, YYYY</term>
     <listitem>
+     <itemizedlist>
+      <listitem>
+       <para>
+        Behavior Changes
+       </para>
+       <itemizedlist>
+        <listitem>
+         <para>
+          <function>QPDFObjectHandle::newUnicodeString</function> now
+          uses whichever of ASCII, PDFDocEncoding, of UTF-16 is
+          sufficient to encode all the characters in the string. This
+          reduces needless encoding in UTF-16 of strings that can be
+          encoded in ASCII. This change may cause qpdf to generate
+          different output than before when form field values are set
+          using <classname>QPDFFormFieldObjectHelper</classname>.
+         </para>
+        </listitem>
+       </itemizedlist>
+      </listitem>
+     </itemizedlist>
      <itemizedlist>
       <listitem>
        <para>
-- 
cgit v1.2.3-54-g00ecf