New to greasemonkey - unicode character problems

>> With a quick test, it looks like you can just use
UTF8...  At least,
>> Firefox trunk, GM 0.6.4
>
>Correct. The uXXXX tip certainly has the very neat
added advantage of
>not requiring additional explanations we are unable to
give about how
>to set up the unknown-to-us-editing-environment to
produce UTF8 rather
>than some other random encoding of choice. (Windows is
natively fond
>of UTF16, for instance.)

I guess the only problem that I have with this suggestion is
that I currently don't know how to lookup the unicode
(uXXXX) character equivalent any given glyph/ideogram/etc
(in case you hadn't already figured it out, I'm clueless
when it comes to the ins-and-outs of unicode).

_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

gm-ml wrote:
> I guess the only problem that I have with this
suggestion is that I
> currently don't know how to lookup the unicode (uXXXX)
character
> equivalent any given glyph/ideogram/etc (in case you
hadn't already
> figured it out, I'm clueless when it comes to the
ins-and-outs of
> unicode).

Not something you would do for paragraphs of text, but for a
few 
characters that you can type or copy-paste, the addressbar's
your 
friend: the URL

javascript:"∽".charCodeAt(0)

will display "8765"

Phil Ringnalda
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey