[scribus-dev] Change to UTF-32

[William Bader]

> To: scribus-dev at lists.scribus.net
> From: ale.comp_06 at xox.ch
> Date: Tue, 31 May 2016 15:43:30 +0200
> Subject: Re: [scribus-dev] Change to UTF-32
> 
> hey
> 
> On 31/05/16 15:30, Gregory Pittman wrote:
> > On 05/31/2016 07:13 AM, Khaled Hosny wrote:
> >
> >> Any way, people are free to reject the parts of the patches they don’t
> >> like. I don’t have this weird notion that some characters or scripts are
> >> first class citizen and others we can think about them later. UTF-16 is
> >> the worst of encodings (as I explained in the IRC discussion), it
> >> encourages developers to write bad code, and the sorry state of non-BMP
> >> in Scribus is a great testimony about this.
> >>
> >
> > I do think we should do our users the favor of making sure that the
> > included scripts are all still working before we release some change
> > like the character encoding. Everything should be fixable, but it makes
> > a bad impression to break things and then wait for people to complain.
> 
> the problem are not the included scripts. we can fix them before 
> including them.
> 
> the problem are all the other scripts that are in the wild.
> 
> but i'm not that worried. if we document how the included scripts had to 
> be changed, at the time the new version will be stable, they have clear 
> recipes for fixing their scripts.
> 
> 
> ciao
> a.l.e


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. https://docs.python.org/3/c-api/unicode.html  External formats like SLA files could remain UTF-8. What kinds of scripts would be broken?
William
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20160531/9b1fc11b/attachment.html>