Language Considerations for Full Text Indexing
Language Support for Full Text Indexing and Searching
The index server (the ProjectWise Design Integration Server that is hosting and maintaining the text index catalog) must have language support installed for the languages your users will be using in full text searches. Windows supports most of the common languages by default, except some Eastern Asian or complex right-to-left reading languages. Additional language support can be installed through Regional and Language Options in the Control Panel.
Setting the Locale for Language Recognition
The index server always uses the system locale as its base for language recognition, and then attempts to correctly determine the language from the text the user provides in the text-based search. In some cases, the index server may make an incorrect determination about the language, resulting in not finding documents or returning an error. To maximize the index server's ability to recognize the correct language being used in a search, it is recommended that you set the system locale on the index server to match the language most commonly used in your documents.
To change the system locale:
Setting the Language for Non-Unicode Programs
Windows Search performs a lexical analysis of the document contents, using the language set as the Language for non-Unicode programs on the index server computer.
If the full text index catalog is not being maintained on the main ProjectWise Design Integration Server computer (for example, if you have set up a head / tail server configuration), it is recommended that you set the Language for non-Unicode programs to the same language on both the main ProjectWise Design Integration Server computer, and the secondary ProjectWise Design Integration Server computer on which the full text index catalog is being maintained.
To set the language for non-Unicode programs: