Overview
Blueprint Enterprise supports selected non-English Windows operating systems and SQL Server environments. Localization settings can affect language packs, Unicode data, regional formats, report output, filenames, and communication between Print Scouts and Blueprint servers.
Confirm the exact Blueprint version, Windows Server version, SQL Server version, and language configuration before deployment.
Prerequisites
Confirm that the operating system and SQL Server versions are supported by the Blueprint release.
Confirm which language packs are installed on the Blueprint servers and client workstations.
If you create a Print Scout installation package on a non-English server, install the matching language pack on each workstation where the package will run.
Confirm the Windows regional settings on the Analyst, Collector, Administrator workstation, and Print Scout machines.
For Unicode-sensitive deployments, ask Technical Support to validate the Windows System Accounts language before production rollout.
Test representative user names, group names, filenames, currency values, and dates before deployment.
Solution
Install the required language packs
Install the required language packs on the Blueprint servers and client workstations.
When a Print Scout package is created on a non-English server, the corresponding language pack must be available on the client workstation where the package will run. Without the required language pack, the package may fail to run.
Configure regional settings
In a mixed-language environment, Blueprint Administrator and reports use the regional settings of the local computer.
Verify the following settings on each administrator workstation:
Number format
Currency symbol
Date format
Language and regional format
A user viewing data from an Analyst in another country may need to change the local currency symbol to match the currency used by the Analyst environment.
Validate Unicode and System Accounts
Test user identity data, filenames, and Print Scout communication using the actual language configuration planned for production.
Important: Internal support testing found that Windows System Accounts needed to use English to correctly encode and decode the UserIdentity.dat file in a Turkish-language deployment. Treat this as a Technical Support validation requirement for Unicode-sensitive environments, not as a universal substitute for version-specific testing.
Review Chinese-language limitations
Blueprint Administrator does not support alphabetical sorting for lists containing Chinese characters.
Reports may not export correctly to PDF or RTF on Chinese operating systems. As a workaround, export the report to Word format and print it to PDF using Acrobat. Other report-printing workflows should be tested before deployment.
Validate filenames
When importing files into Blueprint Administrator, confirm that the filename displays correctly.
If a filename contains characters that the operating system does not support, Blueprint may not import the file. Use supported filenames for installation media, imported files, reports, and operational data.
Validate server names and communication
Print Scouts may be unable to communicate with Blueprint servers whose names contain unsupported foreign characters.
If this occurs, open the Blueprint Server Configuration tool and change the Server Host Name/Address value to the server’s IP address. Test communication again after saving the change.
Validation
Complete the following tests before production deployment:
Install or run a Print Scout package on a representative localized workstation.
Confirm that user identity data is recorded correctly.
Import files containing the characters used by the organization.
Confirm that user names, group names, and filenames display correctly.
Review currency, date, and number formatting in Blueprint Administrator and reports.
Test report export to PDF, RTF, and Word on the localized operating system.
Test Print Scout communication using the configured server hostname.
If hostname communication fails, repeat the test using the server IP address.
Document any language-specific limitations for administrators and support staff.
Notes
Do not assume that a localization behavior from one Blueprint release applies unchanged to another release.
Keep the current Blueprint Planning and Installation Guide for the deployed version with the implementation records.
If product version, operating system, SQL Server version, language pack, or System Accounts configuration is ambiguous, contact Pharos Technical Support before proceeding.