This project is read-only.

Localization: Managing .po files for large projects

Topics: Francais (French), Localization, Writing modules
May 3, 2012 at 12:07 PM

We've been working on a fairly large project within Orchard which consists of a 15 or so modules and this will grow significantly. We're now pulling together things to get ready for a beta release, and need to make sense of our "to-do" list for localization (fr-FR and en-US for now). Anyway, I was wondering what processes people were following when managing localization across their Orchard applications....specifically.

* How to identify all the strings that can be translated (i.e. wrapped in a T("my string")  method)

* How to identify which strings haven't been translated to the target culture yet

I was thinking we would write a regex search of our project folders to locate all T() strings and then cross reference that against the installed .po files for that module and list what was missing. Now the tool on is great, but it only works for the known Orchard modules....before I go further I thought I'd check if

a) there was a better approach I could take to manage this or

b) is there a tool like the one on that has been made available to download...? If not could it be? 

Any help would be much appreciated.



May 3, 2012 at 12:57 PM
Edited May 3, 2012 at 12:58 PM

First there could be a distinction between public modules and private ones.

  • Public modules: those could go to the central localization tool at Their strings should be extracted with the Vandelay Industries Translation Manager module, the .po files sent to Bertrand who will (or won't if it's not a good idea for some reason) upload them to the online tool so they can be localized to all languages.
  • Private modules: those have to be managed separately. You can go essentially the same route: extracting strings to .po files, then translating them...
    • By hand-editing the files (not really recommended)
    • Or using the online tool, but hosted yourself. The online tool is a module too, written by Bertrand and you can get it from (it will also feature polite-informal distinction in translations, once Bertrand evaluates my pull request with the path, *nudge-nudge wink-wink*)

Edit: now with the Codeplex design change lists do look pretty awkward...

May 3, 2012 at 7:40 PM

Fantastic. Thanks :)

Yes they are for private modules...I'm going to try going the orchardpo route :) 


Dec 17, 2013 at 2:28 PM
A really good tool for managing big amounts of po files is poeditor. It has a very simple interface and lots of useful features for translators: API, translation memory, comments, reference language. It has a nice trial period to test out and quite good packages. I totally recommend it.