I've been looking at INTL and trying to follow Steve's design patterns, nice stuff!

Our new Team Leader doesn't like the string translation, because he says that in a previous application he translated (FoxPro 2.6) there was a requirement to translate the same source string differently in different contexts.
Out of the box, INTL doesn't do that.

So I'm wondering if what the T/L says is correct.
If so then we need to have one translation per occurrence of the string, and use the cWhere field to locate the appropriate translation. We also need to modify INTLTOOL to write one record in Strings.dbf for each occurrence when doing the hard work of populating the table for us.

BTW: This is from the same guy who doesn't use object references, but stores the name as a string (and uses macro expansion or EVAL I presume) because cleaning up references is a problem.
He also won't sanction the use of VFP 8 because there's no service pack and he won't use an MS product until SP1.

I'm not in his team so it doesn't apply to me :)