.net 中的全球化和本地化有何不同？
我试图找出全球化和本地化之间有什么基本区别？但没有找到一些适当的不同，
我参考此链接
http: //msdn.microsoft.com/en-us/library/aa292205(v=vs.71).aspx
如果有人知道正确的不同，请在此处解释。
为什么他们在VS2010中给出两个不同的文件夹App_GlobalResources和App_LocalResources。
I try to find out what basic different between Globalization and Localization? but not find some proper different
i refer this link
http://msdn.microsoft.com/en-us/library/aa292205(v=vs.71).aspx
if any one know proper different please explain here.
why they give two different folder App_GlobalResources and App_LocalResources in VS2010.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
你的链接解释了它，不是吗？
而且GlobalResources和LocalResources是不同的概念。 LocalResources 文件夹包含仅适用于一页或用户控件的资源。而 GlobalResources 中的资源可以在整个应用程序中访问。请参阅此MSDN 文章
Your link explains it, isn't it?
And GlobalResources and LocalResources is a different concept. LocalResources folder contains resources which apply for one page or user control only. While resources in GlobalResources are accessible in the whole application. Refer to this MSDN article
全球化
使应用程序适应不同的文化：例如，
本地化
使应用程序适应特定的区域设置/语言：例如，翻译成法语，或更具体地说，翻译成加拿大法语。
Globalization
Adapting applications for different cultures: for example
Localization
Adapting an application for a specific locale/language: for example, translating into French, or, more specifically, Canadian French.
我一直认为基本定义应该是：全球化发生在设计过程中；全球化发生在设计过程中；全球化发生在设计过程中。本地化发生在开发过程中。即：“全球化允许本地化”。
全球化的一个例子是设计一个支持从右到左语言的文本编辑器。它并不依赖于一种特定的语言，但它满足了使应用程序足够灵活以处理此类语言的需要。
本地化的一个例子是将资源添加到特定语言的项目的过程。
I've always held that the basic definition should be: Globalization occurs during design; Localization occurs during development. I.e.: "Globalization allows Localization".
An example of Globalization is designing a text editor to support right-to-left languages. It isn't tied to one particular language, but it deals with the need to make the application flexible enough to handle such languages.
An example of Localization would be the process of adding the resources to a project for a particular language.
全球化
这是在代码中设置基础设施的过程，以便您的软件在不同的文化/语言环境中正常运行。设置基础设施意味着：
本地化
一旦基础设施到位，我们就需要为我们的全球化软件提供适当的资源，以便在不同的地区正常运行。这种提供资源的过程称为本地化。例如：
Globalization
It is the process of setting up the infrastructure in your code so that your software behaves properly in different cultures/locales.Setting up the infrastructure means:
Localization
Once the infrastructure is in place, we need to supply appropriate resources for our Globalized software to functional properly in different locales. This process of supplying resources is called localization. For eg:
您是否询问本地化（L10n）和全球化（G11n）之间的区别或者为什么有两个不同的资源文件夹？
第一个问题可以回答为：G11n 由 L10n 和国际化（i18n）组成。本地化是针对不同市场的适应（通常包括翻译文本、图形、颜色和修改 UI，以便这些更改看起来正确），而 i18n 通常考虑启用本地化（外部化字符串、图形，允许不同的日期、时间、数字、货币）等格式，采用特定语言的排序顺序等）。正如我所说，G11n 既是 L10n 又是 i18n。
为什么他们创建两个文件夹？因为有时资源（无论是字符串、图形、颜色代码）对于所有网页都是通用的。在这种情况下，您需要某种全局资源（这个名称与全球化无关，它的意思是指示应用程序范围的资源）。
但是，如果资源是特定于给定网页的，您不想弄乱全局资源文件夹，否则会造成混乱。而且，全局资源需要经过限定，以便网页知道从哪里获取它。为了让您的生活更轻松，有人创建了本地资源（作为特定网站，而不是本地化（它们都是））资源的概念。通过应用正确的命名约定，您可以更轻松地访问本地资源...
Are you asking about difference between Localization (L10n) and Globalization (G11n) or why there are two different resource folders?
The first question could be answered as: G11n consist of L10n and Internationalization (i18n). Localization is an adaptation for different markets (usually consist of translating texts, graphics, colors and modifying UI so that these changes look right), whereas i18n usually regards to enabling Localization (externalizing strings, graphics, allowing different date, time, number, currency, etc. formats, adopting sorting order to specific language, etc.). As I said, G11n is both L10n and i18n.
Why they created two folders? Because sometimes the resource (be it string, graphic, color code) is common for all web pages. In such case you need some kind of Global resources (this name has nothing to do with Globalization, it was meant to indicate application-wide resources).
However, if the resource is specific for given web page, you don't want to mess-up the Global resource folder, it would create a mess. And also, Global resources need to be qualified so that the web page know where to get it from. To make your life easier, somebody created a concept of Local (as a web site specific, not Localized (they all are)) resources. By applying correct naming convention you could access Local resources much easier...