jonnybot0 / emoji4unicode

Automatically exported from code.google.com/p/emoji4unicode
Apache License 2.0
0 stars 0 forks source link

font suggestions, part two of issue 134 #138

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
In issue 134, Kida-san suggested important as well as nice-to-have glyph 
changes. I am moving the nice-to-have ones here for separate discussion and 
tracking.

It would actually be nice to get these agreed and changed before February 
so that we don't need to change them after presenting to the UTC.

Quote:

The rest is more of esthetic and I do not think they are critical for Feb. 
milestone.

e-4D9   KIMONO
The current image looks like Japanese-look night gown (that tourists buy at 
souvenir stores). 
Kimino has broad obi (sash) which has a rope with a knot in the middle, and 
a straight line under 
the sash due to a turn-back of the material. The edge of the front part 
does not look prominent as 
the hem is blind, etc. Also lines tend to be straight (someone in kimono 
business said it is a beauty 
of straight lines).
http://www.niji.or.jp/home/masuya-1/sozai/topgirl.gif
http://www.takagiryoko.com/images/kimono0001.gif
http://i-ichiba.com/illust/02-ishino-36_thm.jpg
http://www.aoiweb.com/aoi2/kimono2.htm

e-052   TANGERINE
The top part should not have a dent. A leaf such as seen with the Softbank 
design will help the 
identification as tangerines in the market sometimes have leaves attached 
in Japan and US (around 
the SF Bay Area).

e-970   POT OF FOOD
Typically a hot pot has two flat handles.
http://images.google.com/images?q=土鍋

e-03E   SEEDLING
Looks like it is wilting ? I would like it to look like more vigorous! as 
they are often used to describe 
spring, freshman, a baby, etc.

e-040   CHERRY BLOSSOM
It has more apparent 5 petals like seen with the SB design.
http://images.google.com/images?hl=ja&q=桜の花

e-198   HAIRCUT
It looks really like "hair that should have been cut three month ago". It 
was good for the previous 
name but now we might want to cut his hair a bit ?

e-7E8   SHIP
I prefer the side view. It represents features of a ship better I think. 
Also you rarely see them in the 
front view.

e-978   DONUT
The original KDDI design is a donut with chocolate coating on top. The 
current design looks like 
there are two donuts, a black one on top of the other. One or two plane 
donuts instead of a black 
one might work better in BW low res.

e-B59   SLEEPING SIGN
Varied sizes of Z like seen with KDDI / SB might more look like a sleeping 
sign.

Original issue reported on code.google.com by markus.icu on 28 Jan 2009 at 1:22

GoogleCodeExporter commented 9 years ago
In my opinion:

e-03E SEEDLING -- It could be a little more perky, but I don't think it looks 
doomed... Not sure it's worth changing.

e-198 HAIRCUT -- I think it's fine, don't change.

e-970 POT OF FOOD -- don't know
But, when I search for the KDDI and SoftBank names, some of the results do look 
like 
the current glyph (without handles):
http://images.google.com/images?gbv=2&hl=en&q=鍋&btnG=Search+Images
http://images.google.com/images?q=なべ&gbv=2&hl=en&sa=G&imgsz=

e-978 DONUT -- it should be possible to make a small change to make this look 
more 
like a single torus

e-B59 SLEEPING SIGN
Varied sizes of Z like seen with KDDI / SB might more look like a sleeping 
sign.
-> I agree. SoftBank's image, minus the shadow effect, or KDDI's last animation 
frame 
(only visible in the HTML version of the chart) should be a good template.

I don't have an opinion about e-040 CHERRY BLOSSOM, e-052 TANGERINE, e-4D9 
KIMONO, e-
7E8 SHIP.

Original comment by markus.icu on 28 Jan 2009 at 10:44

GoogleCodeExporter commented 9 years ago
e-970 POT OF FOOD
Right, there are ones without handles. Typically, however, they have, and that 
is a stereotype of the cookware 
used for this cuisine. I am fine, however, with the current design.

All of the design issue listed here are about fine tuning in my view and just 
nice to have.

Original comment by k...@apple.com on 29 Jan 2009 at 1:14

GoogleCodeExporter commented 9 years ago
> All of the design issue listed here are about fine tuning in my view and just 
nice 
to have.

Right, but this is the week to change the font to our liking, and to give it 
the best 
shot for the proposal. After next Tuesday's UTC discussion, we should change 
the font 
design (and character names and code points) only as instructed by the UTC. So 
let's 
settle and implement now what we want to change, or agree to basically never 
change 
these things.

Original comment by markus.icu on 29 Jan 2009 at 5:23

GoogleCodeExporter commented 9 years ago
e-198   HAIRCUT  :  I agree with Markus. Let's leave this as is.
e-B59   SLEEPING SIGN  :  It seems there is an agreement on this one.

e-978   DONUT  :  I agree that small change will make it look like single donut. 
If making it a plane donut 
improves the recognizability on low res, it might worth trying on the other 
hand. What do you think Max ?
e-03E   SEEDLING  :  I prefer it being a bit more perky.
e-970   POT OF FOOD :  Other than points I mentioned, I think having two handles 
make it look more like a 
pot rather than a bowl.

Opinions for other emojis ?
e-4D9   KIMONO : As being a kimono lover, I feel a bit strongly about this.
e-052   TANGERINE
e-040   CHERRY BLOSSOM
e-7E8   SHIP

Talking about low res, do we care if glyphs are recognizable enough in low res 
? If so what is the target 
resolution ?  c.f. Dekome (HTML based emoji) is typically 20x20.

Original comment by kida.ya...@gmail.com on 30 Jan 2009 at 5:50

GoogleCodeExporter commented 9 years ago
These all appear to be fine-tuning style issues that don't affect either 
semantics or recognizability in the UTC 
proposal document code chart. I would like to batch these in with feedback 
collected from UTC next week.

Original comment by loft...@apple.com on 30 Jan 2009 at 6:40

GoogleCodeExporter commented 9 years ago

Original comment by markus.icu on 30 Jan 2009 at 10:47

GoogleCodeExporter commented 9 years ago

Original comment by markus.icu on 9 Feb 2009 at 8:47

GoogleCodeExporter commented 9 years ago
A number of glyph changes and refinements have been made since our earlier 
discussions. I think this is done.

Original comment by markus.icu on 27 Apr 2010 at 8:47