AW: Corrupt data

william humphrey bill at bluewatermaritime.com
Mon Apr 28 10:39:06 CDT 2014


The Valentina database we're using is presently UTF8 (doesn't display
diacritics correctly). I can't wait until LiveCode can understand
UTF16.

On Mon, Apr 28, 2014 at 6:27 AM, Tiemo Hollmann TB <toolbook at kestner.de> wrote:
> Hi Mark,
> thanks for your ideas. I will keep track of this, when switching to other
> versions.
> Perhaps Ruslan can confirm, that nothing has changed between V4 and V5 on
> Valentina side, so that we can concentrate on the LC side
> Tiemo
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Valentina [mailto:valentina-bounces at lists.macserve.net] Im Auftrag
> von
>> Mark Schonewille
>> Gesendet: Montag, 28. April 2014 11:11
>> An: Valentina Developers
>> Betreff: Re: AW: Corrupt data
>>
>> Hi Tiemo,
>>
>> Currently, I have no good explanation and I have no plans to investigate.
> What
>> I know is the following.
>>
>> The database is encoded as UTF16 and if no encoding is specified for the
>> connection, I would expect data to be transferred to LiveCode as UTF16.
>> However, UTF16 is an encoding that LiveCode 6.x can't display without
>> conversion. Therefore, I would think that the Valentina external takes
> care of
>> the conversion. AFAIK the external hasn't been changed for years.
>>
>> I do know that something has changed in LiveCode. Previously, LiveCode
>> wouldn't understand text encoded in UTF8 and UTF16 if that text were sent
> to
>> the engine by an external or the shell. Before 5.x we would get garbage
> and
>> since 5.x we get question marks. It is possible that something changed in
> the
>> way LiveCode reads data from externals.
>>
>> If the Valentina external returns UTF16, I couldn't explain why LiveCode
> would
>> be able to display that text without conversion. Perhaps the external
> returns
>> UTF8, which is quite similar to ASCII (equal up to ASCII 127 and slightly
>> different for ASCII 128 up to and including 255, but you won't notice the
>> differences if you're not using any diacritics).
>>
>> I haven't actually investigated this and I can't confirm any of the above.
> I'm
>> just saying it is possible.
>>
>> --
>> Best regards,
>>
>> Mark Schonewille
>>
>> Economy-x-Talk Consulting and Software Engineering
>> Homepage: http://economy-x-talk.com
>> Twitter: http://twitter.com/xtalkprogrammer
>> KvK: 50277553
>>
>> Installer Maker for LiveCode:
>> http://qery.us/468
>>
>> Buy my new book "Programming LiveCode for the Real Beginner"
>> http://qery.us/3fi
>>
>> LiveCode on Facebook:
>> https://www.facebook.com/groups/runrev/
>>
>> On 4/28/2014 09:19, Tiemo Hollmann TB wrote:
>> > Is there any explanation for that behavior?
>> > For years the encoding didn't worked without this encoding.
>> > Is it a change in LC 6.6 or a change in Valentina 5.5?
>> > Tiemo
>> >
>>
>>
>> _______________________________________________
>> Valentina mailing list
>> Valentina at lists.macserve.net
>> http://lists.macserve.net/mailman/listinfo/valentina
>
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina



-- 
http://www.bluewatermaritime.com


More information about the Valentina mailing list