Site structure
Version 7.x > Site structure > Localization of Custom Table Data View modes: 
User avatar
Certified Marketer 13
Certified Marketer 13
nbushnell-bluemodus - 6/5/2013 9:10:34 AM
Localization of Custom Table Data
I have a custom table with a list of job titles and I use this table to populate drop down list through out my site. Now I need to localize these titles. The only way I have found to do this is to use UI Culture and Resource Strings. I place the resource string key in the Custom Table and then every time I use that string I have to use a macro or ResHelper.GetString to get the actual information. This is little messy and time consuming if my Custom Table has very many rows.

A second option would be to move the Custom Table data into a New Document Type and then store these titles in the Content Tree. This is not ideal either as it clutters up the tree but the translation part is easier. I wonder if there is another approach where it would be more straight forward to localize custom table data.


User avatar
Kentico MVP
Kentico MVP
Brenden Kehren - 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.