mamarx

<?php

namespace Acme\YourBundle\Translation;

use Symfony\Bundle\FrameworkBundle\Translation\Translator as BaseTranslator;

class PhraseTranslator extends BaseTranslator
{
    public function trans($id, array $parameters = array(), $domain = 'messages', $locale = null)
    {

mamarx

Today we looked out for a nice tool to improve our translation workflow for an iOS app. In the past we made good experiences with PhraseApp for our Symfony2 app (see this post). So we decided to try it for iOS developement. As it turned out it works like a charme with iOS Localizable Strings as well.

Our workflow looks like this:

1. Engineers add new translations keys to the code

   NSLocalizedString(@"ACMELoginButton", @"Login button title")

2. We run a script that uses genstrings to generate the strings from the source code
3. We push the new strings as Base locale to PhraseApp
4. The translators get notified about the new strings and can translate them in the PhraseApp backend

mamarx

Keybase proof

I hereby claim:

• I am mamarx on github.
• I am marx (https://keybase.io/marx) on keybase.
• I have a public key whose fingerprint is 65CB DBEE 3D19 5EB8 1BA0 A5F3 7AE0 C20E AC6E FE20

To claim this, I am signing this object: