1) The press wildly inflates speculation on the new Apple (insert your favorite device here) - eg, iPad with stereo speakers, card reader, dueling cameras, supre-hires screen…all kinds of stuff

b) Then the speculators and naysayers come out, and also odd bits of personal bad news - eg, standard ram, no card reader, Steve very sick, Jony Ive possibly leaving Apple. The stock take a significant dip. Larger stock groups buy in.

iii) The products come out, the bad news is debunked, and generally the reception to the (product) is good. The stock jumps back up in a few days. Big groups sell out.

Profit!
Cynical, repeatable profit.

I expect to see an announcement card for and event soon, then hear about earnings successes in this months’ conference call, and then the event where the next iPad is announced. Maybe a thinner, DVD-less MacBook Pro (I just got a current MacBook Pro so it’s time to reveal a new one, of course).

Boom - boom - boom.

With Cook still working behind the scenes as COO, Ive still designing, Shiller still shilling, Apple continues to fire on all cylinders.

Happily, Andy Clark from Stuff and Nonsense, a UK design site, has taken upon himself to supply us a great starting point: his contract killer, a great starting point for an easily-read, socially-friendly contract that you (probably) won’t ever need a lawyer for. Of course, it probably wouldn’t be bad to run it by a lawyer in your part of the world, just in case… 

On October 7th, Facebook announced it would begin to let people download all the personal information they’ve put on Facebook. All you need to do is:

It will take a bit of time for Facebook to compile it, and once you get a note that it’s ready you’ll have to prove it’s your data, but boom - one nicely organized zip file with all your assets. You prove it’s your data by identifying friends in photos not in your account, so a hacker would have to know you fairly well to download the file.

Off you go!

This is just a bit of an interesting infographic, but as with anything on “teh interwebs”, take with some grains of NaCl. For instance, the caloric intake for an average US adult is very likely wrong. A thread on Reddit has noted that the CDC has established an average US adult male consumes “2475 calories and 1833 calories (per day) for females”, not 4000-calories per day as in the graphic. There’s a list of references in the graphic - check them out.

What this does show however is that while there’s often skewed information on the net, it can lead to good conversation and fact-checking, especially through sites like Reddit. You just have to learn which “reddits” are worth reading and which are snark-factories.

Ultimately, it seems that the goal of the Internet is actually working - that the demographic born to the Internet is smarter, more politically active and more willing to share America, but that’s another post…

It seems the initiative died last week, or month…hard to tell…and the connecting website that makes all of this possible just disappeared. It’s probably not the workload for writing, but instead I believe there was a great underestimation of how much coordination was required to get this going.

I too found myself lost for words. Hopefully should this happen again, we’ll all be better prepared. 

Until that time, I return to my regularly unscheduled schedule.

Read it.
Learn it.
Live it.

And download the PDF for when you stupidly remove the LucidaGrande.dfont from your /System/Library/Fonts/ directory.

No…I admit to nothing.

Caveats:
• This was developed for the EE 1.6x but it should be very similar in 2.1x installations
• Requires the use of jQuery for the Control Panel extension and the commercial Multi-Language Module from PutYourLightsOn.net
• This presumes 2 languages, but more can be used following the guide
• We try for pure EE-solutions whenever possible - no hacking or php/js and exposing the security
• Since we’re describing EE tags, normally they can’t be displayed inline (because the system immediately processes them). Using the code tag will ruin the reading, so when you see something like [base_path] realize the parenthesis are replaced by brackets.

Start - Setting-up the different language paths and removing the index.php from the URL:

We’re presuming you have a default language (in my case English) set in your General Preferences > Site Language setting. All you need to do is add the module, add the extra languages and add some files to make sure the [base_url] starts out of the correct path.

• Install the module (follow the directions on that - easy enough)

• Add a additional language in the module using the correct ISO 639-1 code for your extra language (en = english, nl = dutch, es = spanish, etc)

• Add a directory to the root of your site for each additional language using the matching ISO 639-1 code. This is always lower-case.

• Modify your path.php file to add 2 new variables [base_url] & [user_language]. The important bit is at the bottom:

changes to point to your default language (replace “mysite” with your site and your particular base language)

• Now add .htaccess to the root using the EXCLUDE LIST method of removing the index.php. You’re including only the directories you want the system to look into:

• The module comes with spanish and italian directory file example - use one of them and move the 3 files to the server
- index.php = you can leave alone
- .htaccess = modify the path in the Rewrite Rule to point to your desired language, in my case it’s Dutch

- path.php = modify the last lines like the above default language, but this time to add the new language path

There are enough folks out there having trouble with removing index.php - removing two of them is worth pointing out. This caught me a few times.

The module’s instructions are clear enough; there are 2 basic methods for language replacement: the tag method, where you add a tag via the module and it does the swapping:

and Conditionals based on your current [base_path]:

You’ll note that it uses the default [title] but also an alternative [title_] field. In my custom fields, right after title I’ve added a title_nl field, keeping the lowercase iso convention. This is the method of doing dynamic content - each language element having its own field (I loop through using a FieldFrame set, for example).

Links are your first enemy in multiple languages, so you need to find an alternative to [permalink] and [auto_path]. Let’s re-write that example to add a link:

So what happens here is that depending on your current [base_path], the link does away with the [title_permalink] and rebuilds the path from the root up to the article. If I had a templates directory called “site” and in there an article view page called “view”, it’d look like this:

Pagination doesn’t use [title_permalink] but rather [auto_path]. Specifically for Pagination, you’d want to add a new [paginate_base] parameter to your [entries] tag:

This points the Pagination auto links used by [if next_page] [if previous_page] to the correct language.

The next time you’ll see [auto_path] is in a site search, and unfortunately there doesn’t seem to be a similar method for a search_base. What I’ve done in this situation is to use the weblog_id to point me to the correct category link:

and then just use different results pages for each language.