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 minutes with Salery Web Store software.
Download at http://www.salery.biz
Op 4-feb-2007, om 18:22 heeft Mark Smith het volgende geschreven:
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,
the library needs to let the client know that it's "Abbey Road", as
unicode or plain text, depending on how the original tag was
encoded, so the client can display it properly.
I guess what I'm asking is what most developers would prefer to be
returned when using the library.
Best,
Mark
On 4 Feb 2007, at 17:03, David Bovill wrote:
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
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
