<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br><br><div>> To: scribus-dev@lists.scribus.net<br>> From: jghali@libertysurf.fr<br>> Date: Tue, 31 May 2016 08:53:16 +0200<br>> Subject: Re: [scribus-dev] Change to UTF-32<br>> <br>> Le 31/05/2016 à 07:29, Khaled Hosny a écrit <br>> >> Jeans not convinced that we need to move to UTF32 at this stage in<br>> >> CTL, i.e. too early, not required. That we will see regressions in<br>> >> unknown places and find it hard to prove that the code is working<br>> >> properly for testing etc.<br>> > The fact that we already have a few reports at GitHub about supporting<br>> > characters outside BMP says otherwise.<br>> <br>> Supporting Emojis or historic scripts is certainly something nice, but supporting them is<br>> not in any way required at this point. So I maintain my position. UTF-32 has advantages<br>> but this is something which can wait after CTL code merge.<br><br></div><div><br></div><div>Even with UTF-32, there are still combining characters <a href="https://en.wikipedia.org/wiki/Combining_character" target="_blank" style="font-size: 12pt;">https://en.wikipedia.org/wiki/Combining_character</a> that require several code points per character. Doesn't that raise issues similar to characters outside BMP in UTF-16? Doing UTF-32 correctly might require touching all of the places that have BMP issues in UTF-16 because they will still need to deal with characters that require multiple integers, and Qt will be messier if you can't use QString.</div><div><br></div><div>William</div><div><br></div> </div></body>
</html>