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 http://orchardproject.net/localize/ 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
http://orchardproject.net/localize/ that has been made available to download...? If not could it be?
Any help would be much appreciated.