News for hackers. Stuff that matters.
Re:Announcing Unicode 7.0 by buster on Tuesday June 17, 2014 @03:28PM (#7906450)
The point is that it will never happen that all codepoints are available everywhere (every font, evers OS, every device), and i certainly don't want a gazillion of pictures loaded on my smartphones little memory, just because some people think it necessary to have a symbol for poop in fonts which is never used anyway. I even consider it a total waste in my laptops 16GB of memory, to be honest. It's not a waste when it serves the real purpose of a language. A chinese word for poop? Sure. A picture of actual poop? No. And where does it stop? Can i have some dog poop and cat poop codepoints please? I'm sure elephant poop looks very different to cat poop, i want a code point for that too.

I say it again: If you want pictures and cliparts, use .png. If you want to write actual text, use fonts. It's as simple as that.

Re:Announcing Unicode 7.0 by scrollaway on Tuesday June 17, 2014 @07:39PM (#7907713)
If you think using pngs instead of fonts is going to save your oh-so-precious mobile device's memory, you got another thing coming.
Re:Announcing Unicode 7.0 by buster on Wednesday June 18, 2014 @04:06AM (#7908989)
Which only shows that you know nothing. A unicode font can come in at about 20MB, but let's add more tiny pictures and make it 100MB, so that i can see the snowman on your webpage (which would be probably 2-5 kB as png).

Why should my browser load thousands of pictures that are never used?!

Yes, it's ridiculous.

Re:Announcing Unicode 7.0 by scrollaway on Wednesday June 18, 2014 @05:47PM (#7913076)
> A unicode font can come in at about 20MB, but let's add more tiny pictures and make it 100MB

You're pulling numbers out of your ass. You also clearly don't know how font fallbacks work, despite having been told how they work in this very thread. Several times.

Re:Announcing Unicode 7.0 by buster on Thursday June 19, 2014 @01:51AM (#7914653)
No, Arial Unicode MS: 22,1 MB. https://en.wikipedia.org/wiki/Unicode_font

And you clearly don't understand that a) this thread contains unicode that my browser still doesn't show, despite your magic fallback and b) the fonts stil contain garbage that has nothing to do with fonts.