V4RB2 // storing encoding
Ruslan Zasukhin
sunshine at public.kherson.ua
Sat Oct 23 09:11:24 CDT 2004
On 10/23/04 1:35 AM, "erne" <ernestogiannotta at tiscalinet.it> wrote:
>>> sure, that is why I expect to deal with that data in my preferred
>>> encoding
>>> I really can appreciate that Vale will convert any string fed to her
>>> into preferred encoding, this is smart
>>> But I'd expect to get back my data in that encoding and not have to
>>> convert them from UTF8
>>
>> I see.
>>
>> Okay I see 2 steps for this
>>
>> 1) GetString( Locale as String )
>>
>
> maybe you mean GetString( Encoding as String ) ?
>
> btw why not use the Encoding RB object to tell Vale about this?
> e.g.
> GetString( Encoding as textEncoding )
> db.StorageEncoding as TextEncoding
> etc.
Because here must be names of encodings that ICU want to see
Actually this is ISO names:
GetString( "Latin-1" )
>> 2) add also
>>
>> db.IOEncoding
>>
>> So if you always want work in UTF16 then inform about this db object.
>>
>
> fair enough :!)
>
> still looking a bit redundant
Why ?
--
Best regards,
Ruslan Zasukhin [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com
To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------
More information about the Valentina-beta
mailing list