efine playlist bookmarks.

x264 Guides:
x264 encoding
x264 to ffmpeg mapping
FFmpeg Guides:
FFmpeg Tips

External Links:
FFmpeg x264 encoding guide
Ubuntu FFmpeg and x264 install guide
x264 settings

yamdi stands for Yet Another MetaData Injector and is a metadata injector for FLV files. It adds the onMetaData event to your FLV files. yamdi should run under *BSD, Linux and Windows and is published under the BSD license.
features?
Some key features of yamdi are:
large file support
H.264 support
onMetaData, onLastSecond, onLastKeyframe events
low memory footprint
XML metadata output
...

Description: Every line in an M3U file is either a comment, a blank, or a resource to render. A comment line begins with the pound sign, #. Blanks are ignored. A resource is the address of a media file.
A resource address can be anything the M3U reader is capable of understanding. These include absolute filesystem paths, relative filesystem paths (with the base undefined by the file format), and URLs.

A resource can be anything the M3U reader is capable of rendering. To my knowledge these are always audio files, but there is no set reason for that to be true. However, it may not be wise to point to proprietary media formats like Real streaming audio in an M3U file, since many players will throw a user-visible error for media they cannot render.

The design philosophy of M3U is to let resource data types do the work. Players that don't understand an address or resource type usually skip the entry. The ability to reference URLs, in addition to filesystem paths, was added this way; some players (Winamp and XMMS, notably) simply added the ability to handle URLs to their M3U readers.

Support for M3U features varies wildly. iTunes, for example, will only render the first entry in an M3U file.

M3U is by far the most popular playlist format, probably due to its simplicity. It is an ad-hoc standard with no formal definition, no canonical source, and no owner.

Example:
# This is an absolute filesystem path
c:/music/foo.mp3

# This is a relative filesystem path
foo/fighters.mp3

# This is a URL
http://foofighters.com/somesong.mp3

Mime type:
audio/mpegurl (recommended)

audio/x-mpegurl
Distinguishing features: A simple list of files, one per line.
Definition URL: http://www.schworak.com/programming/music/playlist_m3u.asp
Originator: Winamp (?)
Implementations: Winamp, XMMS, many more
Metadata support: Before ID3 tags were widely supported by MP3 players, a flavor of M3U called Extended M3U was used to indicate audio metadata. Extended M3U is now obsolete. The following description of Extended M3U is copied in verbatim from Google's cache of the reverse-engineered documentation at http://hanna.pyxidis.org/tech/m3u.html, which is now a defunct URL.

hDOAP is a microformat-like convention (i.e. a dialect of XHTML containing embedded data) used to express Description of a Project (DOAP) data in XHTML. This document describes and defines the hDOAP profile. GRDDL may be used to extract machine-readable data from the document.
Status

* 2008-08-09 - unchanged apart from rewording intro to make clear this is not an official microformat (because it wasn't produced by the microformats.org process. For some reason the XSLT is no longer working with W3C service, though is ok with xsltproc - @@TODO fix.
* 2005-05-29 - almost finished, some less common elements need adding to the stylesheets, minor bug (empty release is added)

@@TODO add references to relevant docs
Creating hDOAP Documents

There are (at least) two ways of creating a hDOAP document. The first is to use an HTML editor and include the attributes for CSS as structured in this sample : redland-doap.html (describes the Redland RDF Toolkit).

The second is to create a standard DOAP file and run it through the XSLT transformation described below. The DOAP-a-matic provides a very easy way of creating the DOAP.

Those that use Firefox with the Tails extension, read no further. This is not for you. You have it given to you on a plate, you don’t know how lucky you are. This is for those of us using Camino, Safari or Omniweb.

After I mocked up an image of how Microformats detection might work in Safari, I started looking at the tools there were available. While there wasn’t anything that handled detection, Tantek did release his bookmarklets to allow hCard and hCalendar information to be exported from a page. Nothing in the region of Tails where you could view a list and choose which contacts/events you wanted, but it worked. This just left some way of handling detection, until I came across Chris Casciano’s script for NetNewsWire to Extract Microformats. It was a simple solution too – use css to style .vcard and .vevent classes differently.

So I’ve knocked up one of my own as a starting point. Here it is in action on Adactio, a rich harvest of microformats to be highlighted:

Example of the highlight microformats css in action

Here’s the file to download: expose-mf.css

It may work better with some designs than others. So far, I’ve not come

Microformats Wiki

* Blog
* Wiki
* Discuss

Search
cheat-sheet

(Redirected from cheatsheets)
Jump to: navigation, search

Brian Suda has made a PDF microformats "cheat-sheet" which you can download, free. An alternative cheat sheet is also available.

These cover:

* Address
o see adr-cheatsheet
* Geolocation
o see geo-cheatsheet
* hAtom
o see hatom-cheatsheet
* hCalendar
o see hcalendar-cheatsheet
* hCard
o see hcard-cheatsheet
* hResume
* hReview
* rel-directory
* rel-license
* rel-nofollow
* rel-tag
* VoteLinks
* XFN
* xFolk

and the datetime and include patterns.
Folding cheatsheet

Erin Caton has designed a pocket cheat sheet. Download the PDF, print double-sided and borderless, then fold it up.

Erin's cheatsheet covers hCard, hCalendar, hResume, hReview, hAtom, rel-license, rel-tag and XFN.

Here are some pictures of the folded cheatsheet.

Note issues, feedback, and suggestions on the pocket cheat sheet feedback page.

microformats resources

* buttons
* cheatsheets are handy if you need a quick reminder about a particular microformat.
* css - some handy CSS code for improving your published microformats.
* demo - a page with links for quickly demonstrating microformats working in practice.
* events
* existing-classes
* existing-rel-values
* icons
* jobs
* RFCs used by microformats
* 2D Barcodes
* shortcuts to wiki pages with long names
* spell-check dictionary
* spread-microformats
* and finally, humor!

Retrieved from "http://microformats.org/wiki/resources"

Xhtml Friends Network

XFN™ (XHTML Friends Network) is a simple way to represent human relationships using hyperlinks. In recent years, blogs and blogrolls have become the fastest growing area of the Web. XFN enables web authors to indicate their relationship(s) to the people in their blogrolls simply by adding a 'rel' attribute to their <a href> tags, e.g.:

<a href="http://jeff.example.org" rel="friend met">...

To find out how to write and use XFN, or to write a program to generate or spider it, read the following sections:

Introduction and Examples
Introduction to XFN, examples, styling suggestions, and future potential.
Getting Started
Join the XHTML Friends Network in just four easy steps!
Profile
Version 1.1 of the XFN meta data profile: the list of the values used in XFN with their significance. See the XMDP home page for more information on XHTML Meta Data Profiles.
Background
The thinking that went into the design of XFN, why particular values were chosen, and why other values were left out.
FAQ
Frequently asked questions about XFN.
XFN Tools
A collection of tools, templates, editors, communities, and other resources that let you edit XFN information. Includes the XFN Creator, among many others.
XFN and ...
How to use XFN with numerous social network services and other technologies.
What's out there?
Pointers to pages and sites which use XFN, tools, ...
How can I help?
If you would like to support XFN...
Press
Articles about or that reference XFN...
Thanks
Thanks to all those who have helped XFN with their feedback, constructive criticisms, suggestions, and inspirational uses.
Feedback
Let us know what you think about XFN.

Microformats Wiki

* Blog
* Wiki
* Discuss

Search
existing-classes

Jump to: navigation, search
Class Names Across All Microformats

Microsummaries are regularly-updated short summaries of web pages. They are compact enough to fit in the space available to a bookmark label, they provide more useful information about pages than static page titles, and they get regularly updated as new information becomes available.

Here are examples of possible microsummaries for some common types of pages:
Type of Page Possible Microsummary
auction item Honda Accord - $5000 - 1 minute left
(item name, current highest bid, and time remaining)
product for sale Linksys WRT54G - $60 - in stock
(product name, current price, and availability)
news site BBC: Chirac to sign France's job law
(latest headline)
word of the day flat-hat
(today's word)
stock quote TWX: 16.94 + 0.30
(stock price and movement)
weather report SF: showers likely
(current forecast)
tinderbox 3 burning
(status of the tree)
forum thread my first thread - 37 comments - last by Aaron
(thread name, number of comments, and last commenter)
support ticket tn79217 - in progress - J.Doe - eta: 3hrs
(ticket number, status, owner, and ETA)

alternate, appendix, bookmark, chapter, contents, copyright, current, describedby, edit, edit-media, enclosure, first, glossary, help, hub, index, last, latest-version, license, monitor, monitor-group, next, next-archive, payment, predecessor-version, prev, previous, prev-archive, related, replies, section, self, service, start, stylesheet, subsection, successor-version, up, version-history, via, working-copy, working-copy-of

TextMade is my current favorite text editor. But, while editing some files on our main Drupal server, I noticed it was leaving some ghost files around. The filenames were all prefixed with “._” so they didn’t show up in the Finder, or in normal ls -l lists. From the text that was displayed in Drupal, it looks like it was storing things like cursor position and text selection in a file that was edited by TextMate.

Normally not a big deal, but Drupal was picking them up as potential themes and modules, and dutifully listing them, and choking on the included cursor/selection info. I did some poking around and found the answer (sometimes, RTFM really helps, and TextMate has a really good built-in manual). Here’s the scoop:

19.4 Extended Attributes (Metadata) Starting with Tiger, OS X supports setxattr and friends. TextMate makes use of extended attributes to store the carets position, bookmarks, what text is folded and is likely to make further use of extended attributes in the future. For filesystems which do not natively support extended attributes (like network mounted disks), OS X instead stores the extra information in a file named ._�filename�, where �filename� is the name of the original file. Since not all users think that this extra (hidden) file is worth having in order for TextMate to remember state, it is possible to disable the use of extended attributes by quitting TextMate and running the following from the shell: defaults write com.macromates.textmate OakDocumentDisableFSMetaData 1

So, the strange files, named “._whateverFileIWasEditing.php” are created by TextMate when editing files on a non MacOSX-Tiger system. Like, say, a MacOSX Panther Server volume mounted via Appleshare. Easy fix, but it probably could have been a checkbox rather than a hidden defaults value.

I don’t think it is hyperbole to say that HTML5 will change the way that you think about web development. I welcome many of the changes as they make development easier, and the user experience richer. With any change, though, there is certain to be a bit of trepidation and controversy. One addition that certainly is not without its controversy is the Microdata specification, but I believe the benefits of this very simple specification are going to change how you look at your mark-up in the very near future.

What this script does is look up the standardized spelling for artists. As ever I work on a playlist you create. In this case the playlist “__Fix Arists” (without the quotes) I’d suggest adding to this list manually rather than trying to automate it. Both for safety (because it’s easy to undo if you just have a single artist in there) but also it just keeps things simple. If you need you could easily add in a routine to work on a selection. I’ll put that in the script but comment it out.

The single best way to make Google aware of all your videos on your website is to create and maintain a Video Sitemap. Video Sitemaps provide Google with essential information about your videos, including the URLs for the pages where the videos can be found, the titles of the videos, keywords, thumbnail images, durations, and other information. The Sitemap also allows you to define the period of time for which each video will be available. This is particularly useful for content that has explicit viewing windows, so that we can remove the content from our index when it expires.