European handsets do support e-moji.
As to how, I used the specifics, but I don't have the details with me.
I only so far have used e-moji in JSky in Japan and with i-mode in Europe
and so haven't needed to check if i-mode in Europe and Japan use the same
e-moji representation method.
.... anyone know? I do not remember if I knew.
JSky e-moji and i-mode Europe e-moji are different though. Besides
technical stuff. some of the JPhone emoji say JPhone and are animated!
But I do know that handling e-moji with dynamic pages was painful but
doable and a learning experience ... and thats life. Static pages are "no
problemo."
ROM space is probably no problem... but testing is.... and the more features
the more testing... the longer the launch will be delayed. ( Unless you
prefer featureful buggy phones) Thats what makes some DoCoMo phones strong.
While JPhone was busy sticking junky cameras in all their phones.... DoCoMo
was doing i-appli. While JPhone tried to support 30k i-appli with a non-
public API, DoCoMo kept them down to 10k with a public API.... its all about
cutting features to increase performance, and decrease debugging time. Take it a
little slower and do it a little better... thats sometimes a good idea ...
Also the docs are much more concise and direct from DoCoMo than
from JPhone ... less features means higher quality and less bugs.
(As a programmer its always tempting to add and add needed stuff...
but in reality simplicity is the key to success, in the end the user often
doesn't need that extra feature you added that ends up not working.).
Lastly I've always had problems with Unicode. It seems there are a whole
fleet of related and unrelated unicode encodings out there. Which one is UTF-8
and is there more than one type of UTF-8.... it drives me nuts sometimes
trying to figure out which unicode encoding something is in when it just says
unicode. The docs list all this big-endian and little-endian stuff that
I can't be bothered to sort through. But if it is UTF-8 and there is only
1 UTF-8 I could really get to like that.
rolf van widenfelt wrote:
> does anyone know if and how the euro i-mode handsets handle emoji?
> i like Curt's idea of using a vendor-specific area of unicode,
> but i'd like to know what really happened.
>
> as an aside, i find it really disappointing to hear that the euro i-mode
> handsets don't support japanese fonts.
> the phone browser could have easily detected a "charset=Shift_JIS" meta tag
> and shown japanese characters.
> and would the extra ROM space for the full character set really cost much?
>
> -rolf
>
> Curt Sampson <cjs@cynic.net> writes:
>
> > Date: Fri, 22 Mar 2002 17:37:55 +0900 (JST)
> > From: Curt Sampson <cjs@cynic.net>
> > Subject: Re: European i-mode
> >
> >
> >
> > On Thu, 21 Mar 2002, Gustaf Rosell wrote:
> >
> > > The character set for international i-mode is to become UTF-8.
> >
> > Cool. Unfortunately, web sites in Japan are going to have to deliver
> > Shift_JIS for years, to remain compatable with old phones. Whether
> > they will gear up to provide UTF-8 instead to those phones that
> > are capable of it, I don't know. But knowing the Japanese; I rather
> > doubt it; they don't seem to care much about making Japanese-language
> > Internet content work well outside of Japan. (The widespread lack
> > of character-set-encoding specifications on Japanese web pages is
> > a case in point.)
> >
> > Actually, I suppose the gateways could always convert for the old
> > phones.
> >
> > > Currently it is actually partly an issue of typefaces in the phones and how
> > > to handle emoji/accessskeys figures.
> >
> > I'd think this isn't a big problem; Unicode does have a vendor-specific
> > area for things like this. Or who knows; if European i-Mode is also
> > offering these characters and take-up is as good there as it was
> > in Japan, these would likely be added to a future version of the
> > Unicode standard.
> >
> > > For international i-mail, it is already UTF-8.
> >
> > Cool. I hope one day that docomo fixes their gateway to accept and
> > convert UTF-8, as it does with ISO-2022-JP and EUC-JP. Right now
> > UTF-8 e-mail produces mojibaka, or at least it did when I just
> > tried it.
> >
> > cjs
>
> This mail was sent to address paul.lester@lincmedia.co.jp
> Need archives? How to unsubscribe? http://www.appelsiini.net/keitai-l/
--
-Paul Lester
paul_lester@lincmedia.co.jp
Received on Sat Mar 23 02:55:00 2002