Localization

Hello,

All our WPF products use standard .NET string resources for all strings that appear in UI.  Please refer to the "Customizing String Resources" topic in the documentation that comes wih the product for details on string resources and how you can even customize them programmatically.

In addition, if you run our Sample Browser app and use the Tools menu on the upper right, you can load the String Resource Browser that lets you see all of the customizable strings for each product assembly, code snippet-related ones included.

Ok, how about <description> and <ToolTip>s declared in a .snippet file for code snippets? The tooltips are user facing, is there a mechanism for these to be localized?

Hello,

This gets a little trickier since code snippets are all stored in files (or your own custom data).  While you might be able to somehow intercept some code snippet selection and template sessions before they open, and do some casting of objects to update the descriptions/tooltips, that could get tricky. 

I'm curious to know more about what mechanism you are using to store the snippets?  Do you just use the file system?  How many snippets are there?  How many languages do you plan on localizing in?

We currently store our basic set of 7 snippets within our assembly as embedded resources.

However we may extend the functionality to let the user define their own snippets, probably using the file system.

We localize to about 8 languages.

Hello,

In that case, could you possibly have some string markers in your embedded code snippets like "$$$tooltip$$$" and then look for those and replace them with localized versions before passing the code snippet text in to our API?

If the user added their own later on, those would assume to be already localized for them.

Thanks for your suggestion, I'll try that!