Re: String shapes and encodings
Lennart Regebro via reportlab-users <[email protected]> Wed, 8 Jun 2022 04:31:05 +0200
| Newsgroups | gmane.comp.python.reportlab.user |
|---|---|
| Message-ID | <CAHT-kBeOg338Mwtp7t+eqB9uKZgd=RoqSbg-jRzg6FqFeuOeeQ@mail.gmail.com> |
--===============8167758277741124879== Content-Type: multipart/alternative; boundary="000000000000eeb6f405e0e67f3a" --000000000000eeb6f405e0e67f3a Content-Type: text/plain; charset="UTF-8" On Tue, Jun 7, 2022 at 10:40 AM Robin Becker <[email protected]> wrote: > I don't think I would like to apply this patch anytime soon. If others > have an opinion please speak up. > As I understand it, the encoding will simply be ignored if a unicode string is given, so keeping the possibility of passing in a bytestring and an encoding is not a problem, even though it's no longer necessary. --000000000000eeb6f405e0e67f3a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail= _attr">On Tue, Jun 7, 2022 at 10:40 AM Robin Becker <<a href=3D"mailto:r= [email protected]">[email protected]</a>> wrote:<br></div><blockquote= class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so= lid rgb(204,204,204);padding-left:1ex"> I don't think I would like to apply this patch anytime soon. If others = have an opinion please speak up.<br></blockquote><div><br></div><div>As I u= nderstand it, the encoding will simply be ignored if a unicode string is gi= ven, so keeping the possibility of passing in a bytestring and an encoding = is not a problem, even though it's no longer necessary. <br></div><br><= /div></div> --000000000000eeb6f405e0e67f3a-- --===============8167758277741124879== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline