main logo
Subject: Re: RB programmers Unicode FAQ?
Author: erne
Posted: 2002/06/24 11:11:04
 
View Entire Thread
New Search


Hi Theo,

>> I'm quite confused about this but sure things will
>> come out clearer as time goes by
>> and knowledge will spread
>

thanx for often coming up in this thread
as I see you're one of those much needed knowledge spreaders :-)


>If you don't want to store encoding information, then make sure
>everything you write is UTF8. Then you can assume everything you
>have written and want to read, is UTF8. All you have to do next,
>is tell RB its UTF8.
>

well I was just figuring out some scenario
I mean if I store all my text as UTF8 then why I need the encoding info?
(I already got it or at least it could be one of the global kind)
but if I want to preserve original text encodings in the database
on a record basis then how I'll be able to search on that?

mmm...
I could have:
1) a field storing the encoded data
2) a field storing the encoding information
3) a field storing the data converted to a known encoding just for index
and search


>Its quite simple.
>

well not so quite but viable after all ;-)

>I don't know about vApp, but if vApp is written in RB, then I
>think with the latest versions of RB it should work fine, or
>with just some small modifications.
>

vApp is written in C and Valentina is a Database
supposed to be inquired from different environments
but maybe the above trick will do i.e.
If you know how to deal with encodings then use fields 1 + 2
otherwise lean on field 3

>To tell RB a string is UTF8, just use MyString =
>SetStringEncoding(MyString, kUTF8Enc) from my String Stuff
>plugin. Or use HackSetStringEncoding(MyString, kUTF8Enc) to set
>it globally without copying RAM (Although this is discouraged
>unless you know exactly what this function does).
>
>If you want to store encodings in the DB, go ahead. Use
>GetStringEncoding(MyString) as integer.
>
>Thats also from my String Stuff plugin.
>
>The plugin is available at www.elfdata.com/programmer/
>

I'm quite sure you've made a great work with it
and be sure I'll check it out!

>You won't need to store different encodings if you store in
>UTF8. UTF is a Universal encoding scheme. UTF8 can contain all
>the characters in use on this planet. So try to get used to UTF
>and Unicode in general, and avoid MacRoman and other encodings.
>

So you're arguing:
don't bother with encoding infos
just jump on the UTF8 train?



Cool Runnings,
Erne.



|er| musical box
|ne| a media store
 
©2002 erne
<-- Prior Message New Search Next Message -->