This useful thread shows how to dump all translated strings into a file which can later be parsed by the i18n:extract task, unfortunately it creates huge files, and needs to be disabled in production environments for performance reasons.

After a quick search through the code, I  have patched my code to only dump untranslated strings to the i18n.temp file.

Here’s the patch for lib/vendor/symfony/lib/i18n/sfMessageFormat.class.php

// found, but untranslated
 if (empty($target))
 {
+          file_put_contents(sfConfig::get('sf_app_template_dir').'/i18n.temp.php',"<?php __('$string'); ?>\n",FILE_APPEND);
 return $this->postscript[0].$this->replaceArgs($string, $args).$this->postscript[1];
 }
 return $this->replaceArgs($target, $args);

(I would have posted this in reply to the original comment, but I couldn’t find the original post for some reason)

1. Edit plugins/sfSimpleForumPlugin/config/schema.yml, add the culture field to the sf_simple_forum_category table :

lang:     { type: varchar, size: 7 }

My thinking is that only the categories need an added lang field, as all forums belong to a category, and all posts belong to a forum, so the language of a post is implicit in its forum and category. Note I’m using ‘lang’ and not ‘culture’ here, as culture seems to have a specific meaning in symfony, and is used when an object can exist with several cultures, so a category would exist in all languages. However in this case, the french site could have a diferent set of categories to the english site, so it’s not appropriate to use the field name ‘culture’.

2. Add culture to the test data :

sfSimpleForumCategory:
  c1:
    name:        Public Boards
    description: We talk about stuff here.
    rank:        1
    culture:     en_GB
  c2:
    name:        Miscellaneous
    description: Secret matters
    rank:        2
    culture:     en_GB
  c3:
    name:        Alleatoire
    description: Les choses alleatoires
    rank:        1
    culture:     fr_FR

3. Select by culture when getting list of all categories in plugins/sfSimpleForumPlugin/lib/model/plugin/PluginsfSimpleForumForumPeer.php:

public static function getAllOrderedByCategory()
{
  $c = new Criteria();
  $c->addJoin(self::CATEGORY_ID, sfSimpleForumCategoryPeer::ID);
  $c->add(sfSimpleForumCategoryPeer::LANG, sfContext::getInstance()->getUser()->getCulture());
  $c->addAscendingOrderByColumn(sfSimpleForumCategoryPeer::RANK);
  $c->addAscendingOrderByColumn(self::RANK);return self::doSelectJoinCategoryLeftJoinPost($c);
}

4. Add culture to admin interface in plugins/sfSimpleForumPlugin/modules/sfSimpleForumCategoryAdmin/config/generator.yml :

list:
  title: Category Administration

  display: [=name, description, rank, lang]
edit:
  title: Edit category "%%name%%"
  display: [name, description, rank, _lang, _forums]

5. Add set_culture partial in plugins/sfSimpleForumPlugin/modules/sfSimpleForumCategoryAdmin/templates/_lang.php :

< ?php
use_helper('Utils');
$cultures = array('en_GB' => 'English', 'fr_FR' => 'French', 'de_DE' => 'German');
echo select_culture_tag('sf_simple_forum_category[lang]', $sf_simple_forum_category->getLang(), $cultures, array('id' => 'lang'));

6. add select_culture_tag function in apps/backend/lib/helper/UtilsHelper.php :

function select_culture_tag($name, $selected = null, $cultures = array(), $options = array())
{
$c = new sfCultureInfo(sfContext::getInstance()->getUser()->getCulture());
if (! is_array($cultures)) {
$cultures = $c->getCultures();
}

if ($culture_option = _get_option($options, 'cultures'))
{
foreach ($cultures as $key => $value)
{
if (!in_array($key, $culture_option))
{
unset($cultures[$key]);
}
}
}

asort($cultures);

$option_tags = options_for_select($cultures, $selected);

return select_tag($name, $option_tags, $options);
}

7. Rebuild model and you’re good to go:

symfony propel:build-model

I’ve been playing around with Symfony recently, with some interesting results.
One frustrations for me was the lack of documentation explaining how to store translations in a database. While symfony provides a way to localise records in the DB, the default method of using XLIFF files for site translation seemed more complicated than necessary.
As I couldnt find any information about implementing a admin interface to manage site translations, I’ve implemented this myself, what follows is a description of the steps to do this. If there are better ways to do this, I’d love to know, I’m new to symfony, so still learning.

Here are the steps to add a admin interface to manage site interface translations.

1. Add DB schema details in config/translation_schema.yml:


propel:
catalogue:
cat_id: { type: integer, size: 11, required: true, autoincrement: true, primaryKey: true }
name: { type: varchar, size: 100, required: true, default: '' }
source_lang: { type: varchar, size: 100, required: true, default: '' }
target_lang: { type: varchar, size: 100, required: true, default: '' }
date_created: { type: integer, size: 11, required: true, default: 0 }
date_modified: { type: integer, size: 11, required: true, default: 0 }
author: { type: varchar, size: 255, required: true, default: '' }
trans_unit:
msg_id: { type: integer, size: 11, required: true, autoincrement: true, primaryKey: true }
cat_id: { type: integer, size: 11, required: true, default: 1, foreignTable: catalogue, foreignRef
erence: cat_id }
source: { type: longvarchar, required: true }
target: { type: longvarchar, required: true }
comments: { type: longvarchar }
date_added: { type: integer, size: 11, required: true, default: now }
date_modified: { type: integer, size: 11, required: true, default: now }
author: { type: varchar, size: 255, required: true, default: ''}
translated: { type: boolean, required: true, default: false }


2. rebuild model: symfony propel-build-model and add the tables to your database.

CREATE TABLE `trans_unit` (
`msg_id` int(11) NOT NULL auto_increment,
`cat_id` int(11) NOT NULL default '1',
`id` varchar(255) NOT NULL default '',
`source` text NOT NULL,
`target` text NOT NULL,
`comments` text NOT NULL,
`date_added` int(11) NOT NULL default '0',
`date_modified` int(11) NOT NULL default '0',
`author` varchar(255) NOT NULL default '',
`translated` tinyint(1) NOT NULL default '0',
PRIMARY KEY (`msg_id`)
)
CREATE TABLE `catalogue` (
`cat_id` int(11) NOT NULL auto_increment,
`name` varchar(100) NOT NULL default '',
`source_lang` varchar(100) NOT NULL default '',
`target_lang` varchar(100) NOT NULL default '',
`date_created` int(11) NOT NULL default '0',
`date_modified` int(11) NOT NULL default '0',
`author` varchar(255) NOT NULL default '',
PRIMARY KEY (`cat_id`)
)


3. enable dictionary translation of interface in apps/frontend/config/i18n.yml:

prod:
default_culture: en_GB
# source: XLIFF
source: MySQL
database: mysql://user:password@host/database
debug: off
cache: on
untranslated_prefix: "[T]"
untranslated_suffix: "[/T]"
dev:
default_culture: en_GB
source: MySQL
database: mysql://user:password@host/database
debug: on
cache: off
untranslated_prefix: "[T]"
untranslated_suffix: "[/T]"


At this stage, if you’ve been using __(‘string to translate’) in your templates, you should be able to see [T]untranslated strings[/T] tagged in your development environment.

4. To check if everything is working correctly, you can manually add some data into the DB :

to define the dictionaries, you need an record in the catalogue table for each culture:

INSERT INTO `catalogue` VALUES (1,'messages.fr_FR','en_GB','fr_FR',0,1197401102,'username'),(2,'messages.de_DE','en_GB','de_DE',0,1197401129,'username'),(3,'messages.en_GB','en_GB','en_GB',0,1197397744,'username');


The translations are stores in the trans_unit table :

INSERT INTO `trans_unit` VALUES (1,3,'1','Hello %1%','Hello %1%','',1197393042,0,'',1), (79,1,'2','Hello %1%','Bonjour %1%','',1197401102,0,'',1), (154,2,'2','Hello %1%','Hallo %1%','',1197401129,0,'',1);


Using something similar to echo __('Hello %1%', array('%1%' => $username) in your templates should give you the correct translations.

Next I wanted to add an admin interface so an admin user can edit these translations without having to upload an XLIFF file. Here’s the trans_unit generator.yml file I used:

generator:
class: sfPropelAdminGenerator
param:
model_class: TransUnit
theme: default
list:
title: "Translation list"
max_per_page: 50
display: [_lang, =source, target, comments, translated]
filters: [source, _translated, _catfilter]
object_actions:
_edit: ~
_delete: ~
sort: source
fields:
source: { params: disabled=false }
translated: { params: disabled=false type: boolean }
_lang { params: lang }
catfilter { name: language }
create:
title: "create Translation"
display: [source, comments]
fields:
source: { params: disabled=false size=80, type: input_tag }
comments: { params: disabled=false size=80x5, type: textarea_tag }
actions:
_list: ~
_save: ~
_delete: ~
edit:
title: "Edit Translation"
display: [_cat, source, target, comments]
fields:
source: { params: disabled=false size=80, type: input_tag }
target: { params: disabled=false size=80, type: input_tag }
comments: { params: disabled=false size=80x5, type: textarea_tag }
actions:
_list: ~
_save: ~
_delete: ~


the aim was to add the source string for all cultures simultaneously, but only mark the string as translated once the translation has been added. This allows the admin to search for untranslated strings. This is what I added in trans_unit/actions.class.php:

class trans_unitActions extends autotrans_unitActions
{

protected function updateTransUnitFromRequest()
{
$trans_unit = $this->getRequestParameter('trans_unit');
$this->trans_unit->setTranslated(1);
parent::updateTransUnitFromRequest();
}
protected function addFiltersCriteria($c)
{
if (isset($this->filters['source_is_empty']))
{
$criterion = $c->getNewCriterion(TransUnitPeer::SOURCE, '');
$criterion->addOr($c->getNewCriterion(TransUnitPeer::SOURCE, null, Criteria::ISNULL));
$c->add($criterion);
}
else if (isset($this->filters['source']) && $this->filters['source'] !== '')
{
$c->add(TransUnitPeer::SOURCE, '%' . $this->filters['source']. '%', Criteria::LIKE);
}
if (isset($this->filters['translated_is_empty']))
{
$criterion = $c->getNewCriterion(TransUnitPeer::TRANSLATED, '');
$criterion->addOr($c->getNewCriterion(TransUnitPeer::TRANSLATED, null, Criteria::ISNULL));
$c->add($criterion);
}
else if (isset($this->filters['translated']) && $this->filters['translated'] !== '')
{
$c->add(TransUnitPeer::TRANSLATED, $this->filters['translated']);
}
if (isset($this->filters['cat_is_empty']))
{
$criterion = $c->getNewCriterion(TransUnitPeer::CAT_ID, '');
$criterion->addOr($c->getNewCriterion(TransUnitPeer::CAT_ID, null, Criteria::ISNULL));
$c->add($criterion);
}
else if (isset($this->filters['cat_id']) && $this->filters['cat_id'] !== '')
{
$c->add(TransUnitPeer::CAT_ID, $this->filters['cat_id']);
}
}
}


This gives the interface shown in the following screenshot.

PS. thanks to WordConstructor

I found this page, which was helpful, but I have dozens of mailboxes that I wanted to import, so I needed an automated solution.

Try the following at your own risk, I’m not responsable for any lost mail. You do backup, don’t you ?

1. in Mail.app, select all your folders, ctrl click and select “Remove deleted messages” (or whatever it is in English – I see “Eliminer les messages suprimés”)

2. Close Mail.app

3. Make a copy of your mailbox :

$ cp -r ~/Library/Mail ~/mail-bak

4. Make a list of all mailboxes you want to copy :

$ cd ~/mail-bak
$ find . -name mbox | grep -v Deleted > mbox.list
$ find . -name Incoming_Mail >> mbox.list
(Incoming_Mail is the name of the inbox where IMAP mail is stored)

5. Copy the mail over to Thunderbird’s mail directory

$ cat mbox.list | while read line ; do newfile=`echo $line | sed 's/ /_/g' | sed 's/^\.\///g' | sed 's/\//-/g'`; cp "$line" /Users/gareth/Library/Thunderbird/Profiles/xxxxxxxx.default/Mail/Local\ Folders/$newfile ; done

this will create a folder with the name equal to the path where the mbox file was found. Its a bit messy, but at least you know which folder is which, and you can rename after.

After this, start Thunderbird, and you should see all your new folders in the ‘Local Folders’ subfolder

good luck

Update – removed links as theres no good reason to link to the spam sites that have since bought these domain names