blocks|key|1452714|text|我会选择多个资源文件。它应该不会那么难配置。事实上，我最近回答了一个关于设置基于全局语言的资源文件和表单语言资源文件的类似问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452715|Localization+in+Visual+Studio+2008|offset|length|1452716|我认为这是最好的方法，至少对WinForm开发来说是这样。|1452717|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/355685/localization-in-visual-studio-2008#358402^0|0|0|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I'd go with the multiple resource files. It shouldn't be that hard to configure.
In fact I recently answered a similar question on setting a global language based resource files in conjunction with form language resource files.

<a href="https://stackoverflow.com/questions/355685/localization-in-visual-studio-2008#358402">Localization in Visual Studio 2008</a>

I would consider that the best approach at least for WinForm development.

blocks|key|1452774|text|%2B1个数据库|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452775|如果对数据库进行了更正，应用程序中的表单甚至可以动态地重新翻译自身。|1452776|我们使用的系统中，所有控件都在一个XML文件(每个表单一个)中映射到语言资源in，但所有in都在数据库中。|1452777|基本上，我们没有让每个控件持有ID+(实现接口，或使用VB6中的tag属性)，而是利用了这样一个事实:在.NET中，控件树很容易通过反射被发现。加载表单时的进程将构建XML文件(如果该文件丢失)。XML文件会将控件映射到它们的资源in，因此只需要填写并映射到数据库即可。这意味着，如果某些内容没有标记，或者需要将其拆分为另一个ID，则无需更改编译后的二进制文件(在英语中，可能同时用作名词和动词的某些单词可能需要转换为字典中的两个不同的单词，并且不会被重用，但在初始分配ID期间，您可能不会发现这一点)。但事实是，整个翻译过程完全独立于您的二进制代码(每个表单都必须继承自一个知道如何转换自身及其所有控件的基本表单)。|1452778|只有当使用带有插入点的阶段时，应用程序才会得到更多的参与。|1452779|数据库翻译软件是您的基本CRUD维护屏幕，具有各种工作流程选项，以方便查找丢失的翻译等。|1452780|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

+1 Database

Forms in your app can even re-translate themselves on the fly if corrections are made to the database.

We used a system where all the controls were mapped in an XML file (one per form) to language resource IDs, but all the IDs were in the database.

Basically, instead of having each control hold the ID (implementing an interface, or using the tag property in VB6), we used the fact that in .NET, the control tree was easily discoverable through reflection. A process when the form loaded would build the XML file if it was missing. The XML file would map the controls to their resource IDs, so this simply needed to be filled in and mapped to the database. This meant that there was no need to change the compiled binary if something was not tagged, or if it needed to be split to another ID (some words in English which might be used as both nouns and verbs might need to translate to two different words in the dictionary and not be re-used, but you might not discover this during initial assignment of IDs). But the fact is that the whole translation process becomes completely independent of your binary (every form has to inherit from a base form which knows how to translate itself and all its controls).

The only ones where the app gets more involved is when a phase with insertion points is used.

The database translation software was your basic CRUD maintenance screen with various workflow options to facilitate going through the missing translations, etc.

blocks|key|1452820|text|大多数开源项目都使用GetText来实现这一目的。我不知道它以前是如何以及是否在.Net项目中使用过。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1452821|entityMap|0|LINK|mutability|MUTABLE|url|http://gnuwin32.sourceforge.net/packages/gettext.htm^0|A|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Most opensource projects use <a href="http://gnuwin32.sourceforge.net/packages/gettext.htm" rel="nofollow noreferrer">GetText</a> for this purpose. I don't know how and if it's ever been used on a .Net project before.

blocks|key|1452967|text|标准资源文件更简单。但是，如果您有任何语言相关的数据，如查找表，那么您将不得不管理两个资源集。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452968|我还没有这样做，但在我的下一个项目中，我将实现一个数据库资源提供程序。我在MSDN上找到了怎么做：|1452969|http://msdn.microsoft.com/en-us/library/aa905797.aspx|offset|length|1452970|我还发现了这个实现：|1452971|DBResource+Provider|1452972|entityMap|0|LINK|mutability|MUTABLE|url|1|http://www.west-wind.com/presentations/wwDbResourceProvider/^0|0|0|0|1H|0|0|0|0|J|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|L|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|E]]|S|$5|O|P|Q|A|$R|T]]]]

Standard resource files are easier. However, if you have any language dependent data such as lookup tables then you will have to manage two resource sets.

I haven't done it, but in my next project I would implement a database resource provider. I found how to do it on MSDN:

<a href="http://msdn.microsoft.com/en-us/library/aa905797.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/aa905797.aspx</a>

I also found this implementation:

<a href="http://www.west-wind.com/presentations/wwDbResourceProvider/" rel="nofollow noreferrer">DBResource Provider</a>

blocks|key|1668048|text|我们使用多语言支持的自定义提供程序，并将所有文本放在一个数据库表中。它工作得很好，除非我们在不更新web应用程序的情况下更新数据库中的文本时，有时会遇到缓存问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1668049|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We use a custom provider for multi language support and put all texts in a database table. It works well except we sometimes face caching problems when updating texts in the database without updating the web application.

blocks|key|1668117|text|你可以使用像Sisulizer这样的商业工具。它将为每种语言创建附属程序集。你唯一需要注意的就是不要混淆表单类名(如果你使用了混淆器)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1668118|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sisulizer.com/^0|6|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can use commercial tools like <a href="http://www.sisulizer.com/" rel="nofollow noreferrer">Sisulizer</a>. It will create satellite assembly for each language. Only thing you should pay attention is not to obfuscate form class names (if you use obfuscator).

blocks|key|1453130|text|我一直在找，我找到了这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1453131|如果你使用WPF或Silverlight，你的方法可以使用WPF+LocalizationExtension有很多原因。|offset|length|1453132|它是开源的，它是免费的(并将保持免费)是一个真正稳定的状态|1453133|在Windows应用程序中，您可以执行以下操作：|1453134|public+partial+class+App+:+Application++
{++
+++++public+App()++
+++++{+++++++++++++
+++++}++
+
+++++protected+override+void+OnStartup(StartupEventArgs+e)++
+++++{++
+++++++++Thread.CurrentThread.CurrentCulture+=+new+System.Globalization.CultureInfo("de-DE");+;++
+++++++++Thread.CurrentThread.CurrentUICulture+=+new+System.Globalization.CultureInfo("de-DE");+;++
+
++++++++++FrameworkElement.LanguageProperty.OverrideMetadata(++
++++++++++++++typeof(FrameworkElement),++
++++++++++++++new+FrameworkPropertyMetadata(++
++++++++++++++++++XmlLanguage.GetLanguage(CultureInfo.CurrentCulture.IetfLanguageTag)));++
++++++++++base.OnStartup(e);++
++++}++
}+|code-block|syntax|javascript|1453135|我认为在Wep页面上，这种方法可能是相同的。|1453136|祝好运!|1453137|entityMap|0|LINK|mutability|MUTABLE|url|http://wpflocalizeextension.codeplex.com/^0|0|T|P|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I´ve been searching and I´ve found this:
If your using WPF or Silverlight your aproach could be use <a href="http://wpflocalizeextension.codeplex.com/" rel="nofollow noreferrer">WPF LocalizationExtension</a> for many reasons.
IT´s Open Source
It´s FREE (and will stay free)
is in a real stabel state
In a Windows Application you could do someting like this:
<pre><code>public partial class App : Application 
{ 
 public App() 
 { 
 } 
 
 protected override void OnStartup(StartupEventArgs e) 
 { 
 Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo(&quot;de-DE&quot;); ; 
 Thread.CurrentThread.CurrentUICulture = new System.Globalization.CultureInfo(&quot;de-DE&quot;); ; 
 
 FrameworkElement.LanguageProperty.OverrideMetadata( 
 typeof(FrameworkElement), 
 new FrameworkPropertyMetadata( 
 XmlLanguage.GetLanguage(CultureInfo.CurrentCulture.IetfLanguageTag))); 
 base.OnStartup(e); 
 } 
} 
</code></pre>
And I think on a Wep Page the aproach could be the same.
Good Luck!

blocks|key|1453187|text|我强烈推荐使用ResourceDirectories+(resx)和{x：ResXManager+}标记的静态工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1453188|ResXManager作为visual+studio或独立应用程序的外接程序工作。|1453189|entityMap|0|LINK|mutability|MUTABLE|url|https://marketplace.visualstudio.com/items?itemName=TomEnglert.ResXManager^0|11|B|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I highly recommend <a href="https://marketplace.visualstudio.com/items?itemName=TomEnglert.ResXManager" rel="nofollow noreferrer">ResXManager</a> tool which works with ResourceDirectories (resx) and {x:static} markup.
ResXManager works as addin for visual studio or standalone application.

I'll soon be working on a large c# project and would like to build in multi-language support from the start. I've had a play around and can get it working using a separate resource file for each language, then use a resource manager to load up the strings.

Are there any other good approaches that I could look into?

Best way to implement multi-language/globalization in large .NET project

数据库

Windows

我很快就会在一个大型的c#项目中工作，并希望从一开始就构建多语言支持。我有一个办法，可以为每种语言使用单独的资源文件，然后使用资源管理器加载字符串。有没有其他好的方法可以让我研究一下？

问在大型.NET项目中实现多语言/全球化的最佳方式
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在大型.NET项目中实现多语言/全球化的最佳方式EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在大型.NET项目中实现多语言/全球化的最佳方式
EN