The Podcast With No Name (Steph+Suw), Episode 2 [en]

[fr] Nouvel épisode du podcast conversationnel que je fais avec mon amie Suw Charman.

Long, long overdue, here is Steph and [Suw](’s Podcast With No Name, episode 2, February 15th, 2007. Some rough shownotes, with some links. Hope you enjoy it, and let us know what you think. We’re down to 35 minutes! *Show notes might suffer updates…*

* conferences: [LIFT’07]( and [Freedom of Expression](
* not everybody has the internet (God, I need to stop laughing so loud when we’re recording)
* mobile phones in other cultures (e.g. Nigeria)
* “technology overload” at LIFT’07 [turned into “internet addiction”]( (interesting [Stefana Broadbent](
* note-taking on a computer: expected in some contexts, but feels really out-of-place in others (cultural issue)
* do we end up publishing our handwritten notes? trade-offs: handwritten and rewriting vs. direct blogging ([Steph’s crappy workshop notes](
* scanning vs. [photographing written material](, document management and shredding
* GTD status update ([inbox zero](…)
* [FOWA]( coming up and other fun London stuff
* Wedding 2.0 will be blogged on [CnV](, but will there be a webcast?
* technology as a way to stretch our [Dunbar number](’s_number), wedding 2.0 with IRC backchannel and crackberries galore
* the [Wedding Industrial Complex](, trying to find an affordable venue in Dorset
* IRC or SL would be cheaper, but is SL a registered venue?
* physical words for “virtual” places
* gap between us heavy users, and people who get a few e-mails a day, book holidays online and that’s it
* exploring how new tools could help us — most people aren’t curious about new stuff
* winning over new users: finding holes in people’s processes
* [Facebook]( is really cool, very usable, and for keeping in touch with people you know (has smart walls and smart feeds)
* who’s on Facebook? on the non-desire to join new social networks…
* [LinkedIn]( for business
* Facebook as a mashup to keep up with what your friends are upto — but isn’t that what blogs are for?
* outlet overload, tools need to talk to each other ([holes in buckets](, profile multiplication, Facebook share bookmarklet to “push” stuff
* clumsy wrap-up and episode three when we manage!

Did you miss [episode 1](

**Note:** PodPress seems to have collapsed, so here is a [direct link to the 14Mb mp3 file]( just in case.

Similar Posts:

Steph+Suw Podcast: First! [en]

[fr] Suw et moi avons enfin enregistré le fameux podcast-conversation dont nous parlons depuis notre première rencontre, en mai 2004. C'est en anglais et c'est assez long, mais on s'en est pas trop mal sorties pour une première!

Each time [Suw]( and I meet, we talk about recording a podcast together. [We met for the first time in June 2004](, and if I believe the [Podcasting and Beercasting Thoughts]( I wrote a little less than a year later, that was indeed when we first started talking about using audio to record conversations.

I’m definitely sure that we talked about it at [BlogTalk 2]( I don’t think Skype was in the air then, but we talked about hooking up our phones to some audio recording device, and left it at that. At that time, people were getting excited about “audioblogging” (did we already talk about “podcasting” back then? It seems a long, long time ago) and we agreed that were audio really became interesting was in rendering conversations. (See the [Podcasting and Beercasting Thoughts]( post for more about that.)

Anyway, now we have [Skype](, and [Call Recorder]( (which reminds me, I need to write up a post about the ethics of recording audio conversations), and we finally got round to doing it. It’s a bit long-ish (40 minutes — not surprising if you know us!) and has been slightly edited in that respect, but honestly, it’s not too bad for a start.

Here is roughly what we talked about.

– [San Francisco](, web geek paradise
– City sizes (see this [London-SF superimposition map](
– Segways
– The cat/geek Venn diagram ([Twitter error message](
– I really want a Wii
– IRC screen names
– The difficulties of pronouncing S-u-w
– When geeks name children: A unique identifier or anonymity?
– Stalkers and geoinformation
– Perceptions of security
– Giving out your phone number and address, and personal boundaries
– Airport security ([background…](
– Risk and expectations of risk
– Death, religion, and the medical industry
– Naming our podcast… something about blondes, apparently
– Clueless marketeering from the Fabric nightclub in London
– The repercussions of having a blog that people think is influential (even if
you don’t think it is)

Let us know what you liked and didn’t like! [View Suw’s post about this podcast.](

Similar Posts:

If You Missed Hearing My Voice… [en]

[fr] Quelques mots au sujet de la différence entre contenu audio et textuel, de ma tentative de m'organiser à la GTD, et mes aventures avec Apple.

Here’s [another pretty crappy audio post]( [5min49]. I promise I’ll try to get better at this content-wise.

Today’s related links:

– [Podcasting and Beercasting Thoughts](
– [Suw]( and [Kevin](
– [43folders](
– [photos of my GTD stuff](
– [The Apple Situation](

Tickler File and A-Z reference

Stuff I’ll blab about next time:

– RSI update (podcasting++)
– chronic vs. acute pain
– Odeo and related stuff (audio comments?)
– things that are on my to-do list (like upload tons of photos to Flickr)
– … (anything you’d like to hear me speak about?)

Similar Posts:

Life and Trials of a Multilingual Weblog [en]

Here is an explanation of how I set up WordPress to manage my bilingual weblog. I give all the code I used to do it, and announce some of the things I’d like to implement. A “Multilingual blogging” TopicExchange channel is now open.

[fr] J'explique ici quelles sont les modifications que j'ai faites à WordPress pour gérer le bilinguisme de mon weblog -- code php et css à l'appui. Je mentionne également quelques innovations que j'ai en tête pour rendre ce weblog plus sympathique à mes lecteurs monolingues (ce résumé en est une!) Un canal pour le weblogging multilingue a été ouvert sur TopicExchange, et vous y trouverez peut-être d'autres écrits sur le même sujet. Utilisez-le (en envoyant un trackback) si vous écrivez des billets sur le multinguisme dans les weblogs!

My weblog is bilingual, and has been since November 2000. Already then, I knew that I wouldn’t be capable of producing a site which duplicates every entry in two languages.

I think this would defeat the whole idea of weblogging: lowering the “publication barrier”. I feel like writing something, I quickly type it out, press “Publish”, and there we are. Imposing upon myself to translate everything just pushes it back up again. I have seen people try this, but I have never seen somebody keep it up for anything nearing four years (this weblog is turning four on July 13).

This weblog is therefore happily bilingual, as I am — sometimes in English, sometimes in French. This post is about how I have adapted the blogging tools I use to my bilingualism, and more importantly, how I can accommodate my monolingual readers so that they also feel comfortable here.

First thing to note: although weblogging tools are now ready to be used by people speaking a variety of languages (thanks to a process named “localization”), they remain monolingual. Language is determined at weblog-level.

With Movable Type, I used categories to emulate post-level language awareness. This wasn’t satisfying at all: I ended up with to monstrous categories, Fran√ßais and English, which didn’t help keep rebuild times down.

With WordPress, the solution is far more satisfying: I store the language information as Post Meta, or “custom field”. No more category exploitation for something they shouldn’t be used for.

Before I really got started doing the exciting stuff, I made a quick change to the WordPress admin interface. If I was going to be adding a “language” custom field to each and every post of mine, I didn’t want to be doing it with the (imho) rather clumsy “Custom Fields” form.

In edit.php, just after the categorydiv fieldset, I inserted the following:

<fieldset id="languagediv">
      <legend>< ?php _e('Language') ?></legend>
	  <div><input type="text" name="language" size="7"
                     tabindex="2" value="en" id="language" /></div>

(You’ll probably have to move around your tabindex values so that the tabbing order makes sense to you.)

I also tweaked the wp-admin.css file a bit to keep it looking reasonably pretty, adding the rule below:

#languagediv {
	height: 3.5em;
	width: 5em;

and adding #languagediv everywhere I could see #poststatusdiv, so that they obeyed the same rules.

In this way, I have a small text field to edit to set the language. I pre-set it to “en”, and have just to change it to “fr” if I am writing in French.

We just need to add a little piece of code in the form processing script, post.php, just after the line that says add_meta($post_ID):

 // add language
	$_POST['metakeyselect'] = 'language';
        $_POST['metavalue'] = $_POST['language'];

The first thing I do with this language information is styling posts differently depending on the language. I do this by adding a lang attribute to my post <div>:

<div class="post" lang="<?php $post_language=get_post_custom_values("language"); $the_language=$post_language['0']; print($the_language); ?>">

In the CSS, I add these rules: {
  content: " [fr] ";
  font-weight: normal;
} {
  content: " [en] ";
  font-weight: normal;
background-color: #FAECE7;

I also make sure the language of the date matches the language of the post. For this, I added a new function, the_time_lg(), to my-hacks.php. I then use the following code to print the date: <?php the_time_lg($the_language); ?>.

Can more be done? Yes! I know I have readers who are not bilingual in the two languages I use. I know that at times I write a lot in one language and less in another, and my “monolingual” readers can get frustrated about this. During a between-session conversation at BlogTalk, I suddenly had an idea: I would provide an “other language” excerpt for each of my posts.

I’ve been writing excerpts for each of my posts for the last six months now, and it’s not something that raises the publishing barrier for me. Quickly writing a sentence or two about my post in the “other language” is something I can easily do, and it will at least give my readers an indication about what is said in the posts they can’t understand. This is the first post I’m trying this with.

So, as I did for language above, I added another “custom field” to my admin interface (in edit-form.php). Actually, I didn’t stop there. I also added the field for the excerpt to the “simple controls” posting page that I use (set that in Options > Writing), and another field for keywords, which I also store for each post as meta data. Use at your convenience:

<fieldset style="clear:both">
<legend><a href=""
title="<?php _e('Help with excerpts') ?>"><?php _e('Excerpt') ?></a></legend>
<div><textarea rows="1" cols="40" name="excerpt" tabindex="5" id="excerpt">
<?php echo $excerpt ?></textarea></div>
<fieldset style="clear:both">
<legend><?php _e('Other Language Excerpt') ?></legend>
<div><textarea rows="1" cols="40" name="other-excerpt"
tabindex="6" id="other-excerpt"></textarea></div>
<fieldset style="clear:both">
<legend><?php _e('Keywords') ?></legend>
<div><textarea rows="1" cols="40" name="keywords" tabindex="7" id="keywords">
<?php echo $keywords ?></textarea></div>
<!-- I moved around some tabindex values too -->

I inserted these fields just below the “content” fieldset, and styled the #keywords and #other-excerpt textarea fields in exactly the same way as #excerpt. Practical translation: open wp-admin.css, search for “excerpt”, and modify the rules so that they look like this:

#excerpt, #keywords, #other-excerpt {
	height: 1.8em;
	width: 98%;

instead of simply this:

#excerpt {
	height: 1.8em;
	width: 98%;

I’m sure by now you’re curious about what my posting screen looks like!

To make sure the data in these fields is processed, we need to add the following code to post.php (as we did for the “language” field above):

// add keywords
	$_POST['metakeyselect'] = 'keywords';
        $_POST['metavalue'] = $_POST['keywords'];
   // add other excerpt
	$_POST['metakeyselect'] = 'other-excerpt';
        $_POST['metavalue'] = $_POST['other-excerpt'];

Displaying the “other language excerpt” is done in this simple-but-not-too-elegant way:


    <div class="other-excerpt" lang="<?php print($the_other_language); ?>">
    <?php print($the_other_excerpt); ?>

accompanied by the following CSS:

background-color: #FAECE7;
background-color: #FFF;
div.other-excerpt:before {
  content: " [" attr(lang) "] ";
  font-weight: normal;

Now that we’ve got the basics covered, what else can be done? Well, I’ve got some ideas. Mainly, I’d like visitors to be able to add “en” or “fr” at the end of any url to my weblog, and that would automatically filter out all the content which is not in that language — maybe using the trick Daniel describes? In addition to that, it would also change the language of what I call the “page furniture” — titles, footer, and even (let’s by ambitious) category names. Adding language sensitivity to trackbacks and comments could also be interesting.

A last thing I’ll mention in the multilingual department for this weblog is my styling of outgoing links if they are written in a language which is not my post language, using the hreflang attribute. It’s easy, and you should do it too!

Suw (who has just resumed blogging in Welsh) and I have just set up a “Multilingual blogging” channel on TopicExchange — please trackback it if you write about blogging in more than one language!

Similar Posts: