I think it's better if PhysFS handled Unicode (UTF-8, UTF-16 or -- the easiest to handle -- UTF-32), because wchar_t is _HIGHLY_ compiler, system and language-dependant.<br><br><div class="gmail_quote">On 20 June 2010 02:28, Kip Warner <span dir="ltr"><<a href="mailto:kip@thevertigo.com">kip@thevertigo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Sat, 2010-06-19 at 12:00 -0400, <a href="mailto:physfs-request@icculus.org">physfs-request@icculus.org</a> wrote:<br>
<br>
> In the past I've written a basic filemanager class in C++ that<br>
> simply drops<br>
> in the file IO calls for PhysFS calls. Anything that needed<br>
> disc access had<br>
> to go through the File Manager. I didn't do anything fancy<br>
> like wrap C++<br>
> streams or anything. PhysFS worked perfectly for this task.<br>
<br>
</div>Interesting. I'd be interested in taking a look at your implementation,<br>
if you don't mind. That would be helpful.<br>
<div class="im"><br>
><br>
> > (2) Can PhysFS handle wchar_t characters? My engine relies<br>
> heavily on<br>
> > them to maintain flexible internationalization.<br>
> ><br>
> ><br>
> No idea on this one, I've been slow to embrace wide chars :)<br>
<br>
</div>Fair enough. It probably wouldn't be difficult to implement, but<br>
something to think about.<br>
<div><div></div><div class="h5"><br>
--<br>
Kip Warner -- Software Engineer<br>
OpenPGP encrypted/signed mail preferred<br>
<a href="http://www.thevertigo.com" target="_blank">http://www.thevertigo.com</a><br>
</div></div><br>_______________________________________________<br>
physfs mailing list<br>
<a href="mailto:physfs@icculus.org">physfs@icculus.org</a><br>
<a href="http://icculus.org/mailman/listinfo/physfs" target="_blank">http://icculus.org/mailman/listinfo/physfs</a><br>
<br></blockquote></div><br>