Localization

This is a collection of useful tips and resources for developing Splunk apps. For an explanation of the available app types please see my earlier article on the topic. Splunk Search References and Guides Splunk publishes two excellent resources for learning and working with its search processing language (SPL):

While browsing through the registry I found the following “gem”. It illustrates nicely how programmers are not supposed to store settings in the registry: [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\MenuExt\Nach Microsoft E&xcel exportieren] @="res://C:\\PROGRA~2\\MICROS~1\\Office12\\EXCEL.EXE/3000" "Contexts"=dword:00000001 What is wrong with this? Several things:

Windows user profiles prior to Vista / Server 2008 contain localized folder names. End users expect that, of course, but admins tend to hate it because automated management becomes much more difficult. How can this dilemma be resolved? End users only see the local copy of the profile, while admins mostly have to deal with the central copy on a file server. Wouldn’t it be cool to have a “translator” component that makes sure local folders are localized while central folders are in one language only?