X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Message-ID: <556FCCDF.7080005@iki.fi> Date: Thu, 04 Jun 2015 06:58:23 +0300 From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: DJGPP v2.05: some thoughts References: <55673F0B DOT 1090103 AT iki DOT fi> <83twuwwshg DOT fsf AT gnu DOT org> <55675040 DOT 9030008 AT iki DOT fi> <556F6E49 DOT 8010006 AT gmx DOT de> In-Reply-To: <556F6E49.8010006@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com On 06/04/2015 12:14 AM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) wrote: > Am 28.05.2015 19:28, schrieb Andris Pavenis (andris DOT pavenis AT iki DOT fi): >> On 05/28/2015 07:56 PM, Eli Zaretskii (eliz AT gnu DOT org) wrote: >> >>>> One possible new feature that comes into mind : >>>> - changes for more full support of wide characters have been around for a long time. We must >>>> decide >>>> whether we want to get it in v2.05 or we should wait after release. >>> It's a large job, so unless there's code somewhere that is ready to be >>> committed, I'd advise against this. >>> >> It is perhaps mostly ready. I put ZIP archive (no changes from my side) at: >> >> http://ap1.pp.fi/djgpp/misc/ >> >> This is also mostly separate feature, so possible danger is rather low. Only some header files >> need to be merged. >> >> Andris >> > > > How is this supposed to work? > I would like to give it a try with the next ports. > I guess we must at first create a CVS branch for DJGPP 2.05. Wide character related changes could after that be committed to trunk. Andris