<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 31 May 2016, at 16:32, William Bader <<a href="mailto:williambader@hotmail.com" class="">williambader@hotmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Calibri; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""><br class=""><div class="">> To:<span class="Apple-converted-space"> </span><a href="mailto:scribus-dev@lists.scribus.net" class="">scribus-dev@lists.scribus.net</a><br class="">> From:<span class="Apple-converted-space"> </span><a href="mailto:ale.comp_06@xox.ch" class="">ale.comp_06@xox.ch</a><br class="">> Date: Tue, 31 May 2016 15:43:30 +0200<br class="">> Subject: Re: [scribus-dev] Change to UTF-32<br class="">><span class="Apple-converted-space"> </span><br class="">> hey<br class="">><span class="Apple-converted-space"> </span><br class="">> On 31/05/16 15:30, Gregory Pittman wrote:<br class="">> > On 05/31/2016 07:13 AM, Khaled Hosny wrote:<br class="">> ><br class="">> >> Any way, people are free to reject the parts of the patches they don’t<br class="">> >> like. I don’t have this weird notion that some characters or scripts are<br class="">> >> first class citizen and others we can think about them later. UTF-16 is<br class="">> >> the worst of encodings (as I explained in the IRC discussion), it<br class="">> >> encourages developers to write bad code, and the sorry state of non-BMP<br class="">> >> in Scribus is a great testimony about this.<br class="">> >><br class="">> ><br class="">> > I do think we should do our users the favor of making sure that the<br class="">> > included scripts are all still working before we release some change<br class="">> > like the character encoding. Everything should be fixable, but it makes<br class="">> > a bad impression to break things and then wait for people to complain.<br class="">><span class="Apple-converted-space"> </span><br class="">> the problem are not the included scripts. we can fix them before<span class="Apple-converted-space"> </span><br class="">> including them.<br class="">><span class="Apple-converted-space"> </span><br class="">> the problem are all the other scripts that are in the wild.<br class="">><span class="Apple-converted-space"> </span><br class="">> but i'm not that worried. if we document how the included scripts had to<span class="Apple-converted-space"> </span><br class="">> be changed, at the time the new version will be stable, they have clear<span class="Apple-converted-space"> </span><br class="">> recipes for fixing their scripts.<br class="">><span class="Apple-converted-space"> </span><br class="">><span class="Apple-converted-space"> </span><br class="">> ciao<br class="">> a.l.e<br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Shouldn't the internal representation in Scribus be separate from the encoding used by the interface between python and Scribus? Python provides codecs for common encodings. <a href="https://docs.python.org/3/c-api/unicode.html" target="_blank" style="font-size: 12pt;" class="">https://docs.python.org/3/c-api/unicode.html</a> External formats like SLA files could remain UTF-8. What kinds of scripts would be broken?</div><div class=""><br class=""></div><div class="">William</div><div class=""><br class=""></div></div><span style="font-family: Calibri; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_</span></div></blockquote><br class=""></div><div><br class=""></div><div>I agree, yes they should be.. </div><div><br class=""></div><div>Craig</div><br class=""></body></html>