Hard G, like “Graphics”. Obviously.
I just found this combinatorial comment trapped in my spam filter. It’s interesting to see how the raw script is composed, so they can randomly select phrases, perhaps to throw off spam filters; this one was obviously a misfire.
It’s like a Choose-Your-Own-Adventure or Ad-Lib, but for spam. 🙂
I was impressed that it did have some minimal contextualization, automatically pulling in the title of my previous post and of my blog itself (“Annotators Anonymous � Reinventing Fire”), but was disappointed that they don’t have some sort of topic map to try to pull in related terms to truly customize the comment in a more sophisticated way.
It’s much longer than a typical spam, and pretty repetitive, with several greeting intros, so I assume that in addition to selecting phrases, whole paragraphs were included or removed. It’s not clear if this was posted by a bot, or by a human who was meant to manually select the phrases and context; I hope for the sake of some underpaid person that it was a bot.
I’m rather skeptical about the topic of the link they chose, to “burberry outlet”, which seems to be some sort of knockoff purse vendor, and is unlikely to appeal to my audience; I’d have preferred something like a knockoff electronics shop in China, which would have had at least minimal appeal.
It linked to songsketches.com (a relatively cool domain name, presumably once populated with more compelling content), and it was posted by “email@example.com” (IP address 184.108.40.206) on 2014/04/05 at 11:22 am ET.
Some of my favorite highlights:
- It asks if I get a lot of spam, and how I combat it (very meta!)
- There is a section with a variety of smileys and winkies, giving them the emotional range of a fine actor
- The adjective options (and there are a lot of them!) are all very positive and encouraging, a touch I appreciate and which flatters my ego.
C+ for content, D for spelling (quite a few errors, which I’d guess would make the spam more detectable, and which frankly grates on my nerves), F for execution. However, I will give them a passing grade overall, because they did show their work.
My name is Doug Schepers… and I’m an annotator.
You might be an annotator, too. If you think you might be, you should come to our support workshop in San Francisco in April.
Several times recently, people have asked on IRC how they can use nice fonts with SVG. My answer in the long-ago past, when Adobe’s excellent SVG Viewer plugin roamed the Earth, was to use SVG Fonts directly embedded in the SVG file… but that’s no longer practical with the current varied browser support.
Authoring tools, like Inkscape and Adobe Illustrator, should simply manage this for authors, but until that happens, I thought I’d share a relatively simple workflow that has helped others. (Warning: I will use the words font and typeface with careless abandon to semantics in this article, though I know the difference. I’m afraid the more sensitive souls among you may suffer apoplectic righteous indignation.)
I will walk you through this workflow step-by-step, but if you get lost, just look at the source code… it’s pretty self-explanatory.
- Find a font you like. For this example, I chose Riesling, an Art Deco typeface by “Bright Ideas”. I made sure the font was free and didn’t have any restrictions for online or commercial use.
- Upload the font to FontSquirrel’s
@font-facegenerator, and download the resulting package. This contains the webfonts, as well as some sample files (though not an example of how to use the files in SVG).
- Copy the resulting webfont files (
*.svg) into the same directory as the SVG file that will reference them. (Note: do not confuse the SVG file in the FontSquirrel package for a content file; it is an SVG font, with no rendering content.)
- Copy the CSS
@font-facestyle rule from the FontSquirrel package file (“stylesheet.css”), and put it in your SVG’s <style> element.
- Optionally, for local testing, install the original TTF file as a system font, and add the
localvalue to the
- Add a style rule for
textelements, using the resulting
font-family. In my example, I also created a style rule for
- No, really, that’s it. You’re done.
Here is the resulting SVG using webfonts:
A Word on the Future of SVG Fonts
Since I’ve mentioned SVG Fonts a couple of times, I thought I’d leave you with a final note about what the future seems to hold for them.
SVG Fonts were added in SVG 1.0, way back in 1999, as a way to embed fonts in the same file, using vectors and all the capabilities of SVG, including separate fill and stroke (which could be gradients or other paint sources), and even exotic features like clip-paths, animation, and so on; Jérémie Patonnier has a great article on the topic. As cool as this is, it doesn’t necessarily work well with existing font engines… The Adobe SVG Viewer had support for SVG Fonts, and Opera and WebKit added support for the less-powerful SVG Tiny 1.2 subset as well; but Mozilla and Microsoft decided not to add support for SVG Fonts, and that limits their usefulness. It doesn’t seem likely that SVG2 (being developed now) will include SVG Fonts, not necessarily even the more limited subset (though there is not yet consensus in the SVG Working Group).
In practical usage, SVG Fonts were once the only way to use webfonts on iOS devices (e.g. the iPhone and iPad), which is why FontSquirrel includes them in their font-face package; but this is no longer the case, and iOS 4.2 added support for TTF fonts, which reportedly perform better. I expect this use of SVG Fonts to dwindle away… people will naturally want to use as few font formats as possible.
But for all of you out there who, like me, love the cool things you can do with SVG Fonts that aren’t possible in traditional outline font formats, don’t despair! Even as I write this, a proposal is being prepared by the SVG glyphs for OpenType Community Group to add a subset of SVG to OpenType, for more interesting typeface capabilities.
SVG Fonts are dead! Long live SVG Fonts!
This week is our first Geek Week at W3C. The idea is to have a week where we improve our skills, collaborate with each other on prototypes and fun projects that help W3C, and to come up for air from our everyday duties. I’m working on a few projects, some small and some larger.
One of my projects is to make a plugin for Thunderbird, my email client of choice, which exposes the Archived-At email message header field, normally hidden, as a hyperlink. This is useful for W3C work because we often discuss specific email messages during teleconferences (“telcons”), and we want to share links to (or otherwise find or browse to) the message in W3C’s email archives. It’s also handy when you are composing messages and want to drop in links referring to other emails. (I do way too much of both of these.)
I’ve made extensions for Firefox before, but never for Thunderbird, so this was an interesting project for me.
There has been a heated argument recently on the W3C Canvas API mailing list between accessibility advocates and browser vendors over a pretty tricky topic: should the Canvas API have graphical “objects” to make it more accessible, or should authors use SVG for that? I think it’s a false dichotomy, and I offer a proposal to suggests a way to improve the accessibility potential of the Canvas 2D API by defining how SVG and the Canvas 2D API can be used together.
This brings together some ideas I’ve had for a while, but with some new aspects. This is still a rough overview, but the technical details don’t seem too daunting to me.
Last week, I published the first draft (and subsequent updates) of the Web Interface specification, which defines touch events. This is the first spec from the new W3C Web Events Working Group.
Peter-Paul Koch (PPK) gave it a positive initial review. Apparently, others thought it was news-worthy as well, because there were a few nice write-ups in various tech sites. Naturally, cnet’s Shank scooped it first (he has his ear to the ground), and it was fairly quickly picked up by macgasm, electronista, and Wired webmonkey.
I thought I’d go into a few of the high-level technical details and future plans for those who are interested.
Continue reading “Getting In Touch”
Text in SVG is text. Visually, you can use webfonts like WOFF or SVG Fonts (where they are supported, like in Opera or the iPhone) to make it look cool, and you can style both the stroke and fill to make it all fancy, or apply filters to pop it out or make it glow or give it a dropshadow, but it’s not just a raster image like many text headers… it’s human- and machine-readable text, as nature intended.
So, SVG is translatable, right?
Continue reading “Translation Services at a Loss for Words”
Mozilla is holding an Open Web Games competition. I expect that many of the games will be use the Canvas API, since many programmers are more familiar with the imperative programming mode, and there are some games libraries that have been developed for Canvas or adapted from existing drawing or gaming libraries.
But I’m calling for SVG developers and designers to step up to the plate, as well. SVG has a lot of features that make it easier out of the box to build interfaces, animations, and even games. There is a scene graph, and the DOM event model that gives you free hit detection for pointer events, for example. And I’d love to see someone make an open-web game that’s both accessible and fun…
To help developers along, I thought I’d share a few free, open-source SVG resources that could be useful in building games:
Continue reading “SVG Game Resources”
With SVG being integrated more and more into HTML5, both included via
<img> elements, and inline in the same document, some natural questions about SVG and CSS are receiving more focus. This includes box model questions like background and border, and pointer events.
I’m interested in comments from the community on what direction SVG should take.