Translation memory

[GoogleCodeExporter]

This is an enhancement, not a bug.

It would be great if the tools included a Translation Memory tool
This could all be Java based with a simple XML based DB even.

Also would be good if the process of making translated_msgs XLF files could be 
automated too as part of the tools, but that can certainly be scripted higher 
up.

But main thing is the Translation Memory i think.

As it is when you have a sprint and make lots of changes its hard to know what 
extracted messages need changes.

Apparently Translation Memory is the way for the system to remember what has 
changed and so needs to be translated, which is a brute force approach but also 
is resilient.

Original issue reported on code.google.com by ged...@gmail.com on 18 Jun 2010 at 12:17

[GoogleCodeExporter]

Original comment by kai.hu...@gmail.com on 25 Oct 2010 at 10:27

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

This is outside the scope of the Closure Templates project.

Original comment by kai.hu...@gmail.com on 30 Aug 2011 at 7:40

• Changed state: WontFix