Hello Trent,
I am familiar with this framework and this approach requires the end-user to localize their own application...and approach that we thought was wrong.
An approach like that is surely not completely wrong in my eyes, because nobody would keep you from including some localized messages into the framework or deliver a few localized messages (tables or xml-files) with the framework. This is what you do right now, but unfortunately without an easy way for the developer to modify a message, label or whatsoever. Not to speak of the end-user... Or a translation while in context...
As I have already mentioned, you could technically do this already using SQL Server or an external XML file. In regards to the internal SF keys...this is more than likely not going to be something that is going to happen anytime soon as addressed in my previous post.
After thinking about your suggestion I found it would possibly be a very hard way. ;-)
And I don't want to have it right now, but it would be nice to have something useful into one of the next generations of SF, maybe 2.0?
In regards to the SF keys coming from SQL Server, the bottom line is that the keys just need to be in whatever localization source you are using...including the SF ones.
I let the app at startup look for the appropriate xml-files and if no localization is found this way, my app tries to using SQL tables instead. Until now, while at development and learning the possibilities of the framework. ;-)
So if you were to extract the keys into your own SQL Server messaging tables, then set your localization environment to pull from SQL Server instead, the SF assemblies would look in that SQL Server message store...thus, allowing you to change them.
So far, so good. :-)
You would just have to open up the XML localization files, copy out the keys, and add them to your localization solution...
You are kidding me! :-)
This would be more work than it is worth of... But a nice joke anyway! :-)
...this would require a lot of work and I recommend against this as there could be some other issues as well, but that would at least be an option if you MUST have it this way right now.
You say it clearly: A lot of work. So much work that I'm due to retirement before at the end of the work for that single task, I guess. ;-)
This is why I was asking for something for the next generation of SF.
I'm sure you will surprise us with something really great! :-)
Thanks and friendly greetings,
Ralph