| Re: [AD] Windows unicode filename support |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Windows unicode filename support
- From: Milan Mimica <milan.mimica@xxxxxxxxxx>
- Date: Tue, 09 May 2006 10:43:29 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=aDNIpV8LSzJksDZQby4nrQpJv/8NxDRJXLvulTUlmrjp6zJTGgMwJzcrU0U/7ni8FiwucFvfiY2j6GvEPq/FJHpJSPYatWz8ZIIvB0U7MDwh3bSy2f6YZgQ7BlvOKqX/eZyPS51/TIg6429J5KeLLmVRxFSxzlOK+sUMzObAESU=
Chris wrote:
My last patch seems to be the best one so far. This will allow some of the
various file routines (file_length, find_first, etc) to work with unicode in
WinNT and up. However, as Milan Mimica pointed out, Windows won't be able to
open these files with open(), and needs to use wopen instead (which could be
wrapped up in _al_open as the Mac port apparently uses). I haven't gone
through the code yet to figure out what to do here, though.
Actually, I think we need a system vtable entry here. I'm not sure if
adding it would break ABI compatibility.
--
Milan Mimica
http://sparklet.sf.net