本文介绍了使Visual Studio生成伪语言(qps-ploc)附属程序集的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经生成了应用程序资源文件的伪本地化版本(例如,Order Summary and Payment被本地化为[[[[[Òŕd̂ër̊ S̀úm̂m̈år̀ý ân̈d̊ P̀áŷm̈e̊ǹt́]]]]]),以便我们可以在获取实际翻译之前测试本地化错误.

I've generated pseudo-localized versions of an app's resource files (for example Order Summary and Payment is localized as [[[[[Òŕd̂ër̊ S̀úm̂m̈år̀ý ân̈d̊ P̀áŷm̈e̊ǹt́]]]]]) so that we can test for localizability bugs ahead of getting actual translations.

我已使用qps-ploc资源标识符为它们命名,以匹配现有的伪语言环境标识符,例如我的Details.resx的伪本地化版本命名为Details.qps-ploc.resx.

I have named them using the qps-ploc resource identifier to match the existing pseudo-locale identifier, e.g. my pseudo-localized version of Details.resx is named Details.qps-ploc.resx.

但是,当我将这些resx文件添加到项目中时,Visual Studio会忽略它们.如果我使用真实"语言代码(例如Details.fr-FR.resx)重命名它们,则Visual Studio确实会创建一个以此语言代码命名的子文件夹,并构建附属程序集.

However when I add these resx files to the project, Visual Studio ignores them. If I rename them using a "real" language code (such as Details.fr-FR.resx) then Visual Studio does create a subfolder named with this language code and builds the satellite assembly.

所以在我看来,Visual Studio拒绝qps-ploc(甚至没有生成警告).我是否缺少某些东西,或者谁能建议一种方法来将这些qps-ploc资源构建为我的Visual Studio项目的一部分?

So it looks to me like Visual Studio rejects qps-ploc (without even a build warning). Am I missing something or can anyone suggest a way to get these qps-ploc resources built as part of my Visual Studio project?

推荐答案

在我的ASP.NET Web应用程序中,带有.resx文件(不是编译的资源dll)的qps区域设置工作正常,但是,我确实找到了此MS文章,在注册表中启用伪语言环境.也许会有所帮助.

The qps- locales work fine in my ASP.NET web application with .resx files (not compiled resource dll), however, I did find this MS article on enabling pseudo locales in the registry. Perhaps it will help.

使用伪语言环境用于本地化测试

此外,您可能希望按照本MS文章中的说明创建自定义语言环境:

Additionally, you may wish to create custom locales, as given in this MS article:

如何:创建自定义文化

最诚挚的问候.

这篇关于使Visual Studio生成伪语言(qps-ploc)附属程序集的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-11 22:47