Closed GoogleCodeExporter closed 9 years ago
yes if i don't mess up .net should use unicode by default (utf-16 i guess)
Original comment by pog...@gmail.com
on 19 Apr 2008 at 8:56
Original comment by rios.fer...@gmail.com
on 27 Apr 2008 at 6:14
MTPAxe r16 - changed all relevant variables and functions to their wide
character
equivalents. For files already on the player, reading international characters
in
file names and tags should work. Uploading new files with multibyte characters
won't
work due to stdin not (easily) supporting reading unicode. There are 3
solutions to this
1. continue to use standard input for transferring the filename/metadata from
WMTP
but encode the multibyte string (base64?) and decode it in MTPAxe.
2. Use VirtualAllocEx to allocate memory in MTPAxe from WMTP and have WMTP
write all
necessary data to this unmanaged block. Need to do more research to see if
this call
is allowed for non admin users.
3. set stdin to binary mode. This option isn't so good since it breaks scanf.
Option #2 seems the best for now.
Original comment by rios.fer...@gmail.com
on 29 Apr 2008 at 12:30
went with solution 2. it seems to work even under a limited user in Windows
Vista.
Original comment by rios.fer...@gmail.com
on 29 Jun 2008 at 10:10
Original issue reported on code.google.com by
rios.fer...@gmail.com
on 18 Apr 2008 at 9:42