On Aug 30, 2008, at 8:02 PM, David Bovill wrote:
Still having a few problems:
Using this function:
setprop view_Utf8 someUtf8
put the text_Field of me into textField
put uniencode(someUtf8, "UTF8") into someU16
set the unicodetext of textField to someU16
end view_Utf8
David,
I won
Still having a few problems:
Using this function:
setprop view_Utf8 someUtf8
put the text_Field of me into textField
put uniencode(someUtf8, "UTF8") into someU16
set the unicodetext of textField to someU16
end view_Utf8
and getting UTF8 from the XML file (an assumption), I get resul
Well inside Rev - I "think" that most users would like to use the htmlText.
From my point of view i would like to be able to do the following:
set the text of fld "Title" to the id3_Title of player 1
set the htmltext of fld "Title" to the id3_Title ["htmlText"] of player
1 -- (could have
Mark, this seems like a good idea. Would I be right in thinking that
to translate a string from UTF16 to UTF8 I would do this:
put unidecode(someUTF16String,"UTF8") into tUTF8String ?
Thanks,
Mark
On 4 Feb 2007, at 18:23, Mark Schonewille wrote:
Hi Mark,
May I suggest that you translate a
Hi Mark,
May I suggest that you translate all strings into and deliver all
strings as ut8? This would avoid any confusion on the user's side.
Best,
Mark
--
Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Get your store on-line within min
That's the point - I don't want the user to have to guess. The
library 'knows', because the encoding information is in the id3 tag
it's just read, what I'm wondering about is simplest wasy to let the
user of the library know.
So if the 'client' app asks the library for the title of a file,
I am not really sure - can you put it into a field and if it differs from
the original "text" value assume it is unicode, or maybe regEx looking for
some chars outside of the ascii range?
___
use-revolution mailing list
use-revolution@lists.runrev.com
Pl
David, thanks for the reply - it's actually both questions.
I like the style of interface using set/getprops, and will probably
do exactly what you suggest.
However, the unicode problem is that in an ID3 tag, text information
(that the library will extract from the tag) may be encoded as
u
I hope I got your question right - it is more abot an interface style to a
library than auto-detecting whether which format the data is in?
If so - arrays are a good bet, but in my opinion the most user friendly
approach is to create a "model" which deals with the functions and commands
for getti
Hi, all. I'm finally updating my id3 tag library (it will write as
well as read), and I want to handle unicode issues correctly.
My question is : when using any library that is going to give you
back some text as the result of a function, how is it best to
indicate whether it is unicode or
Hello,
I was wondering if once the unicodetext of a fields content has been
set if that field will then Keep that characteristic always. Or do I
then always have to use the "set the unicodetext of" when I am putting
text into fields? Is this the same for variables as well?
set the unicodetext o
I have a field that displays names of some of the users files.
I want to be certain that *any* file name (including those with
non-english spelling)
will be displayed properly.
What sort of scripting is needed for the field?
If I use: set the useUnicode of fld "files" to true
will that do
12 matches
Mail list logo
