Kaoani is a Japanese smiley face, usually animated and bouncing up and down. They may be gif images or text art images. I think they began as text art, using Japanese fonts, and become graphic images using animation.
Screen capture from SmilChat.
I’ve assumed emojis came from emoticons, the ASCII text smileys. But, I’ve got a new theory now.
Did emojis really start as wingding/ webding fonts and evolve into their current versions, dragging along the yellow smiley along the way?
I don’t see how emojis have much in common with the emoticons. An emoji is far more an image than a smiley.
What do you think?
Input is a typeface for code, designed by David Jonathan Ross and released by Font Bureau.
Source: Input: Fonts for Code
Why do we use fonts not designed for readers? Fancy fonts are nice for creating images with text or using as titles and headers. Think about the fonts book publishers have been using for generations of books and people.
Mashable: Why your Email Font is Ruining your Life
I’m hoping this brings back the ASCII art fonts, or better versions of them. My favourite is still FixedSys partly because I know how it will work and partly because it shows up bold rather than thin and faded.
Adding ASCII art to the source code (the HTML files) may not interest people who don’t look at source code.
The source code is an easy place to add ASCII art because those files open in plain text, no formatting or fancy fonts. So, the ASCII art shows up without much extra work, almost none in fact.
If you access your HTML files you can add ASCII art yourself, without the plugins. (See above). But, not everyone wants to do that.
WP Figlet is all about adding text created in ASCII art fonts (figlets). It even lets you choose which figlet fonts you want to use. The auto suggestions creates a figlet in your source code like this (you choose your own words):
It does work.
Source Code (although not updated in 4 years, also works). If you are timid about mucking around in the HTML files then either of these plugins will work for you. Source Code lets you choose to have the ASCII art in your header or footer. However, I found it did need the extra HTML code for keeping the formatting after I saved my text image.
One thing I dislike about Source Code is the lack of artist credit (artist initials). I checked several of the ASCII images available with the plugin and none had artist credits. I used my own ASCII image with my initials.
Don’t be bashful about getting into your own source code. Skip the plugins and just do it yourself. Once you access the file it’s very simple to add the ASCII art with the code for notes. (See the first image in this post, no reason you can’t do that yourself).
Which image shows the ASCII art better? One is a screen capture of ASCII art I posted as text to a blog. To display it as text rather than an image file (png, jpg or gif) I have to be satisfied with those lines running through it and the gaps too. I don’t like it, but so far it’s the best solution I have found to the problem of displaying text in an HTML world. I prefer using screen capture to display the ASCII art so it can show as I created it, in the text file.
Likely this is getting confusing for anyone who has not had the problem of making ASCII art work to be shown on the Internet.
I used to post ASCII art to HubPages and other online sites. I seldom do now because several people were leaving comments about the images being posted as an image file instead of as a text file (which they could grab with cut and paste – using without permission or assuming ASCII art is all free to take).
Well, I had set it up to display as an image gallery, just like photos, paintings and so on. The artist does not bring paint cans to the gallery and try to recreate all his or her work for the display. I see the ASCII art the same way.
Mainly, it is very difficult to get the ASCII art to display in plain text. Each site uses different software, HTML code and fonts. Every time I want to post ASCII art as text I would have to figure out how it will work on each individual site and sections on the site itself could be different. I did find some things which worked, sort of.
For blogs I found a plugin which displays the text in the right format but, it leaves it choppy looking, with bare lines between. I don’t like the look of it – but it is the best I have found so far. I’m still using it on this blog and my other blogs if I post a few ASCII art pictures I find on the web.
At this point I am done with trying to post text files anywhere online but in an actual text file which can be a clickable link from the HTML web page. Keep it simple.
If people want to complain they can go ahead and do so. But, no one should complain without offering me a solution to the problem of posting text in an HTML environment. If you don’t have a real solution, you should not complain about the solution I have found.
I’ve been making ASCII art since 1998. I’m a great fan of the FixedSys font. It is a monospace font which works very well for illustrating with text. The individual characters are plain and straight up and down, without many flourishes. (Plain fonts, without flourishes are called sans-serif). FixedSys is also a text which displays on the dark side. This is nice compared to some monospace fonts which give a very light, thin display.
However, Windows Vista was the first new computer I bought where I noticed the FixedSys font is missing. I looked for it, tried other font options, but was not really happy. So I went online to see what people were writing about it.
I now know that FixedSys has been given an upgrade of sorts and is now known as Consolas. I found Consolas and gave it a try. It is nice, smoother than the old FixedSys. But, I am a bit of a traditionalist, loyal to whatever I liked first.
While searching I found the font called FixedSys Excelsior. It is like the old fashioned FixedSys but it is less smooth than the new Consolas font. You can see a pretty drastic difference in the two fonts when I show them in an ASCII art illustration of the Canadian flag.