So we'll check in the "en" .po more for consistency than because we might
actually "translate" some of the default strings to English.

So when adding a UI-visible string we should follow this pattern, and then
manually run the fab task?

-Rick



On Mon, Aug 5, 2013 at 8:41 AM, Justin Walgran <notifications@github.com>wrote:

> In opentreemap/treemap/locale/en/LC_MESSAGES/django.po:
>
> > @@ -0,0 +1,298 @@
> > +# SOME DESCRIPTIVE TITLE.
>
> The .po files are the translation files. They are generated by a static
> analysis tool but are completed by a human translator. The cool part is
> that you can re-run the tool when you add a new translatable string and it
> will update the .po files without overwriting any existing work done by the
> translators.
> … <#1404e7f545a4d3b1_>
> On Friday, August 2, 2013, Rick Mohr wrote: In
> opentreemap/treemap/locale/en/LC_MESSAGES/django.po: > @@ -0,0 +1,298 @@ >
> +# SOME DESCRIPTIVE TITLE. This looks like an auto-generated file. Should
> we really be checking it in? — Reply to this email directly or view it on
> GitHub<https://github.com/azavea/OTM2/pull/138/files#r5563040> .
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/azavea/OTM2/pull/138/files#r5577622>
> .
>



-- 
Rick Mohr, Software Developer

Azavea |  340 N 12th St, Ste 402, Philadelphia, PA
rmohr@azavea.com  | T 215.701.7504  | F 215.925.2663
Web azavea.com <http://www.azavea.com/>  |  Blog
azavea.com/blogs<http://www.azavea.com/Blogs>
| Twitter @azavea <http://twitter.com/azavea>