localization strategy and variables

Steve,

Got any ideas for equivalent solution in the Tin Can world?  I imagine the user would see a separate course for each language showing up in the AMP library if they launched multiple languages but it would be great if each of those communicated back the exact same result to the LRS so once again you could run one report on the course in the Tin Can LMS and see who completed it regardless of the language they viewed it in...  If the use actually got multiple languages into the AMP library, launching any of them would report back completion status for the same course from the LMS' perspective. Any ideas or hints you have at all might be helpful.  What would be the equivalent in the Tin Can world of putting an intermediate index_lms.html file in front of the multiple, per-language directories with the language chosen on that intermediate index_lms.html file then launching the index_lms.html file inside the language-specific directory as you suggested above in the SCORM world?

Thanks