[Development] Deprecating QFile::encodeName/decodeName

Oswald Buddenhagen oswald.buddenhagen at nokia.com
Thu Jun 7 11:52:34 CEST 2012


On Thu, Jun 07, 2012 at 10:20:58AM +0200, ext Thiago Macieira wrote:
> On quinta-feira, 7 de junho de 2012 10.06.31, Oswald Buddenhagen wrote:
> > it's not a no-op as soon as we actually implement some escaping
> > mechanism.
> > as joao pointed out, it is all about applying the decoding and escaping
> > at the right layer - which is exactly when using posix file i/o
> > functions, and nowhere else. as soon as you start doing it with cmdline
> > args and the environment you are in workaround land, and that only
> > increases the mess (because you don't know what encoding the other side
> > uses - the only reasonable assumption is that it wants locale encoding
> > (because that would be the right thing to do)).
> 
> So you're saying that we don't need to pass these file names with broken 
> encoding to other applications, nor do we need to accept them in the command-
> line.
> 
correct

> I disagree.
> 
you need to provide arguments which refute my "it only makes things
worse" stance.

> Maybe you'll want to revert this then: 
> https://codereview.qt-project.org/#change,22854
> 
indeed



More information about the Development mailing list