Re: [tlug] Re: font/char set question

["Josh Glover" <jmglov@example.com>]

On 30/07/07, Jim Breen <jimbreen@example.com> wrote:

> Thanks for this insight into Amazon's internals.

's my job. :)

> > I'm pretty sure that our search system honours the encoding you input.
> > Tragically, the output will be in Shit_JIS, so you won't be able to
> > read it.
>
> Great pity.

Indeed suh.

> However, since the WWW form is in Shift_JIS, browsers are unlikely to send
> in field contents that are not in either ISO 646 (ASCII) or JIS X 0208.

Ah, I did not think of that. Bugger.

But as we know from my issues with Firefox quick search bookmarks and
WWWJDIC (as of yet unresolved, but I know it is a Firefox bug/feature,
and not a WWWJDIC one), browsers might do unexpected things...

> Gurupa sounds interesting. I wish they'd change their Japanese output
> overt to UTF-8.

There may be a URI param / cookie variable you can set to enable
non-b0rk3n behaviour. I'll get back to you on this; please remind me
periodically.

If not, I can hack the functionality in, though I am not certain that
I can get it past a code review from the website platform team. I can,
however, enable this functionality for UTF-8-enabled keitai, or web
browsers hitting the keitai site, if I can sell the feature to my
team. :)

Poke and prod me on this periodically until I give you an answer.

-- 
Cheers,
Josh