[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: KDE_3_2_BRANCH: kdelibs/kate/part
From:       David Faure <faure () kde ! org>
Date:       2004-06-28 14:58:09
Message-ID: 200406281658.10466.faure () kde ! org
[Download RAW message or body]

On Monday 28 June 2004 16:52, Nicolas Goutte wrote:
> > List:       kde-cvs
> > Subject:    KDE_3_2_BRANCH: kdelibs/kate/part
> > From:       David Faure <faure () kde ! org>
> > Date:       2004-06-28 14:17:36
> > Message-ID: <20040628141736.80D819976 () office ! kde ! org>
> > 
> > CVS commit by faure: 
> > 
> > Backport fix for #57623: kioslave:ftp uses binary mode to get files
> > CCMAIL: 57623-done@bugs.kde.org
> 
> Are you sure that you can do it?
> 
> What happens when loading UTF-16 and that you have the character 0x0d0a , 
> would it not be considered as CR/LF and transformed to LF, resulting in a bad 
> UTF-16 file? (And 0x0a0d if the UTF-16 is of the other endian or any similar 
> sequence of bytes made from 2 characters)

Who says this has anything to do with UTF-16?

I thought that report was only about using the FTP text ("ascii") mode instead of the \
binary mode for text files, I see no mention of UTF16 in the report.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).


[prev in list] [next in list] [prev in thread] [next in thread]