Localization

Sep 14, 2010 at 10:04 PM

Do we plan to support other locales than en-us in the CTP release? Right now all the strings in the PowerShell scripts are hard-coded in English.

Sep 14, 2010 at 10:05 PM
Don't bother, it isn't going to be needed.

On Tue, Sep 14, 2010 at 11:04 PM, dotnetjunky <notifications@codeplex.com> wrote:

From: dotnetjunky

Do we plan to support other locales than en-us in the CTP release? Right now all the strings in the PowerShell scripts are hard-coded in English.

Read the full discussion online.

To add a post to this discussion, reply to this email (nupack@discussions.codeplex.com)

To start a new discussion for this project, email nupack@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Coordinator
Sep 14, 2010 at 10:06 PM
Edited Sep 19, 2010 at 6:15 AM

Not for the first CTP, but we probably need to for the RTM. Please log a bug to change all hard-coded strings to use resources. Thanks!

Sep 15, 2010 at 12:13 AM

Could we perhaps skip localization for v1 and let customer need and use drive what localization we do as we go forward?

Coordinator
Sep 15, 2010 at 12:23 AM

I’ll follow up on this. I don’t think so though, because we’re still included as part of MVC 3 and eventually Visual Studio, so we’ll have to be localized. However, perhaps that work is not done here, but done by Microsoft (aka outside the foundation).