Thanks for the sanity check, Robert.
The application I'm building will return both English or French data through the identify. These are separate fields within the service. I was finding it difficult to build the logic into List.js for EN/FR as the attributes are built up looping through. I got down a path of trying to identify what field in what loop iteration is needed for English or French and it wasn't a good approach as everything changed if I added or changed a field in the config. Thus the code changes in List.js were minimized by just passing in French or English fields.
Actually, one question, but unrelated - do you have any suggestions getting NLS values into List.js? I don't think this is a good approach, but I made it work by passing NLS into the startup function.
widget.js
postCreate: function () {
this.list.startup(this.nls);
list.js
startup: function(nls) {
this.nls = nls;