6/5/2013 11:32:42 PM
RE:Localization of Custom Table Data
I know, I know I shouldn't assume BUT:
I'm going to assume 2 things:
1) you already have a service that performs your localization (manual or automated).
2) you know each culture needs a unique record in your custom table.
If you import that custom table data, you could do the localization and extra record creation as you import it. If not, you could create a scheduled task to check and see if the custom table data has all available cultures, if not, send a note to someone with which ones are missing and/or create it.
If you don't need the custom table data as a document type, then leave it as is. But if you all in all, it would handle the localization the best.
Also keep in mind, using the UI Cultures, isn't a bad idea as you can dynamically change the values for the specific culture on demand and initially perform a mass update to the datatable with the culture macro. In my opinion, this would be the simplest approach.