Right, although we've already addressed this problem, but apparently it
didn't make it in to any 5.5.x release... I wouldn't hold my breath on it
either, so if you're really concerned about the extra byte then you could
convert it to UTF8 like you did before.
--
REAL World 2005 - The REALbasic User Conference
March 23-25, 2005, Austin, Texas
<http://www.realsoftware.com/realworld>
On 2/28/05 6:59 AM, "Björn Eiríksson" <bjorn at einhugur dot com> wrote:
> I imagine it is because most Windows File system calls require a NULL
> terminated string. Which is not the case on Mac for example.
>
> On 28.2.2005, at 11:46, Christian Schmitz wrote:
>
>> William Yu <william at realsoftware dot com> wrote:
>>
>>> One thing that should be pointed out is that when you build your
>>> string, you
>>> should also copy an extra null byte (this only applies to UTF16
>>> strings).
>>
>> Is there a logical reason for this?
>>
>> I copy an extra byte now and the problem is solved, except that
>> len(s)=lenb(s)*2+1 now which I'm not sure may make trouble.
>>
>> PS: Only on Windows, this is necessary, or?
>>
>> Mfg
>> Christian
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|