|
本帖最后由 yu273393352 于 2011-7-8 19:51 编辑
第一条:请大家直接发邮件,跟贴可以,但是别再帖子上写你需要什么软件请发邮件给我什么的内容,请你直接发送邮件给我,这么多内容不要是看帖子的话肯定会有漏掉的,再次感谢大家
相信大家也就知道ALM 11(QC11)中文版7个资料——也就是帮助文档是那七个,大家也都在网上苦苦等待寻找,我就把它上传上来,供大家共享。
他们就是
AML中文更新说明文档
AML中文教程说明文档
AML中文用户指南说明文档
AML中文管理员指南说明文档
AML中文组件用户指南说明文档
AML中文最佳升级实践说明文档
HP Business Process Testing用户指南
可见图
————————————————————————————————————————————————————————————————————————————————————————
下面的就是大家期待已久的ALM11汉化包,也就是中文版了,什么都不说,详细看图 ,和帮助解释文档,不会的再来问我
汉化软件
其实ALM11安装后软件里源文档ReadMe中的Multilingual Support就已经说的很清楚了,建议大家多学习学习英文,对大家有好处的
汉化说明中
这是浏览页面
http://update.external.hp.com/qualitycenter/qc110/others/generator/index.html
这是下载地址
http://update.external.hp.com/qualitycenter/qc110/others/generator/ClientMSIGeneratorSetup.exe
HP Application Lifecycle Management 11.00 Readme
Software version: 11.00
Publication date: October 2010 Second Edition
This file provides information about HP Application Lifecycle Management (ALM) 11.00:
Documentation
What's New
Installation Instructions and System Requirements
Notes and Limitations
Additional Notes and Limitations - Performance Center
Multilingual Support
HP Software Support
Legal Notices
具体的原文就是
Multilingual Support
Internationalization Limitations:
You cannot type Japanese characters in the ALM Login window Password field or in the Document Generator.
Workaround: Paste text from the clipboard.
Opening and updating a project that contains characters different from those set in the ClientOSLocale or ClientOSAdvanceLocale may cause irreversible damage.
The InputLanguage inserted from an external component to ALM must be the same as the ClientOSLocale and ClientOSAdvanceLocale. For example, you cannot insert a QuickTest Professional script that contains Japanese characters in a client that runs on an OSLanguage with ClientOSLocale or ClientOSAdvanceLocale that is not Japanese.
When sending mail that contains non-English characters from the Quality Center client, it must be sent from the ClientOSLocale and ClientOSAdvanceLocale that are the same as the mail characters locale.
To send mail that contains non-English characters, the MailServerVersion and MailClientVersion mail server must support non-English characters.
To display non-English characters, the OSLanguage needs to include the proper fonts for the language.
The SiteAdminDBCollation and ProjectDBCollation must be set to the same language as the data insert. For example, inserting Japanese characters in a Korean collation is not supported.
The Spell Checker tool is available only in English.
Due to a problem in the JDBC driver's specific version, using Chinese and Japanese collation in MS-SQL may cause an error while executing some actions.
You cannot create Quality Center projects with Thai characters in the project name.
The number of double-byte characters you can enter in a ALM edit box may be more limited than the number of characters specified in the relevant error messages. The number of characters that can actually be used depends on the database definitions and the character set collation that is being used. For example, one character can occupy 3 bytes when using Japanese characters with a database that is defined to work with UTF8.
When you generate a document in the Document Generator that includes test scripts with non-English characters, these characters may appear as random ASCII text.
Workaround: Select As Icons for the Document Generator Attachment Embedding Options (and not As expanded text).
ALM/Quality Center versions 9.2 and later support LDAP authentication using non-English character sets. Previously, login failed when passwords for LDAP-authenticated users contained non-English characters. To use non-English character sets, set the LDAP_CHARSET parameter in Site Administration to Default or add the relevant value listed in the Basic Encoding Set list (http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html).
Hebrew locale: On Hebrew locale client machines, to ensure that ALM memo fields (for example, Description, Comments, Rich Text) are displayed properly, configure the following settings in the Control Panel > Regional and Language Options window:
Windows Vista or 7: Set Languages For Non-Unicode Programs (Administrative tab) and Current Format (Format tab) to "Hebrew".
Windows XP: Set Languages For Non-Unicode Programs (Advanced tab) and Standards and formats (Regional Options tab) to "Hebrew".
Localization Limitations:
QuickTest Professional migration: In localized versions, QuickTest Professional 11.00 migration fails.
To display a localized UI, the OSLanguage of the client must use the same language as ALM.
The UI language is defined by the ALM Platform server and only one language can be defined per server.
Vista: ALM Language Pack must be installed and operated on Windows where Windows native language (MLU*) is identical to the MUI* language.
An ALM project created in an English edition cannot be upgraded to a localized edition.
In the French localized version on Windows XP (SP3), you may not be able to export defects to Microsoft Excel. |
|