[Development] Deprecating QFile::encodeName/decodeName

Thiago Macieira thiago.macieira at intel.com
Thu Jun 7 10:20:58 CEST 2012


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.

I disagree.

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

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120607/eb532db9/attachment.sig>


More information about the Development mailing list