Okay, here are two questions regarding localizing a StrataFrame project.

1.  When you click the tasks button on the StrataFrame label control, there is a setting for "Optimize layout for localization'.  What exactly does this setting do?  I was hoping I could use it (perhaps along with some docking properties or aligment properties) to have the label always right-align with the other labels above or below it, but this does not seem to be the case.  At best this setting seems to expand the vertical height of my label and doesn't seem to do much more.

2.  Where does StrataFrame derive its list of Supported locale IDs from in the Localization & Messaging Editor tool and in the Translator tool?  It seems to be a comprehensive list (at least for me and seems to support most of the local IDs supported by Microsoft), but I do not see the Human Interface Device listed for one.  I think it is possible to create custom locale Ids in Windows, but will StrataFrame report them as available, if I do?

Here is the reason I ask this question.  We want to use the StrataFrame translation tool to allow our Publishing department to edit all of the localization keys we create on each component of our application.  Though, the translation tool doesn't allow me to choose the same language as both the translate from language and the translate to language, I have devised a way to do this by creating all of my developer keys in U.K. English and then creating the editing publishing keys (after they translate my keys) in U.S. English which is marked as the default language for my project.  Instead of choosing the U.K. English as the language I'm initially going to create all of the keys in, I'd like to create my own language, call it Developer and create my keys in that language which would better represent the process I'm trying to facilitate and build.

Does anybody have any ideas regarding what I'm trying to do?  I appreciate whatever ideas you may have.

My second question asn't exactly worded correctly, so here it is again...

2.  Where does StrataFrame derive its list of Supported locale IDs from in the Localization & Messaging Editor tool and in the Translator tool?  It seems to be a comprehensive list (at least for me and seems to support most of the local IDs supported by Microsoft), but I do not see the Human Interface Device listed for one.  I think it is possible to create custom locale Ids in Windows, but will StrataFrame report them as available, if I do?

Here is the reason I ask this question.  We want to use the StrataFrame translation tool to allow our Publishing department to edit all of the localization keys we create on each component of our application.  Though, the translation tool doesn't allow me to choose the same language as both the translate from language and the translate to language, I have devised a way to do this by creating all of my developer keys in U.K. English and submitting my keys to the Publishing team using a package I create using the translation tool.  After they translate my keys, I import the package they send me back in U.S. English which is marked as the default language for my project.  Instead of choosing the U.K. English as the language I'm initially going to create all of the keys in, I'd like to create my own language, call it Developer and create my keys in that language which

I answered these through the PM you sent me.  You are welcome to post my response if you like.

Trent's response to me is found at http://forum.strataframe.net/PrivateMessage6492-1168.aspx.  Thank you for the answers, Trent.

However, Trent never actually answered my second question.  So, please if anyone has any further ideas, I would appreciate them.

I did answer it if you will please refer back to your PM.  We retrieve this through the GLobalization settings in Windows.  If you want more information about Globalization, refer to the Globalization namespace.  StrataFrame already has a method within MessagingBasics that will populate a combo for you:

You can also have SF return all of the installed languages on Windows through the GetAllInstalledLanguages method:

But like I said, if you want more information about this, check out the Globalization namespace.

would the content in this thread be the place to look at how to implement a custom language (if such a thing exists)?

I need to create "langauges" that are customer specific.

Example customer 1 refers to an item as a "widget" while customer 2 refers to it as an "item", I need to "localize" my forms to reflect my customers specific terms. Each RBS user will be assigned to a company, and in turn they should be assigned an appropriate language. I am 99% sure I remeber this being discussed in the last class, but I cannot find anything on how to do it.

I know I could dummy it up by selecting obscure languages, but I would rather not.

Thank you as always.

Keith Chisarik

bump

Keith Chisarik

Technically this would work. You will, however, have to use a pre-existing language during the creation of the keys as we do not allow a custom language to be added. In this scenario I would recommend trying to keep the same language but using different code pages. This way you only have to overwrite the differences versus every key. For example, in the US we spell "color" ... well ... you know. But in the UK it is spelled "incorrectly" with a "u" like "colour." In this case, we would just add another language of English using the UK code page. If a key for the same language doesn't exist, it will use the base language (in this case US English).



So that the selection looks more realistic at run-time, you would have to display your own language selection dialog since this is pulled from the Globalization on the machine using the code page with our standard dialog. But you could create a collection that shows your own dialog so that you know that codepage 1033 is company A and codepage 1034 is company B, etc. But after the code page is selected and set within the application, the SF logic will take control and be the exact same from that point forward.

Great thanks I will try this method.

Keith Chisarik