Stellent Content Server, Руководство пользователя

Страница: 132 / 198

7-20 Stellent Content Server User Guide
Checking In Files
I
MPORTANT
C
ONSIDERATIONS
Please note the following considerations
❖
Multi-Byte Characters (page 7-20)
❖
Checking in Microsoft Office XP Files (page 7-20)
Multi-Byte Characters
You should not use multi-byte characters (for example, Japanese or Korean) in content IDs
and content types—even if Stellent Content Server is to be used in a multi-byte
environment. The values of these fields are included in the URLs of content items, and
limitations in current web technology prevent web servers and browsers from handling
URLs with multi-byte characters correctly.
If you want to use multi-byte characters in content IDs and/or content types, you need to
ask your content server system administrator if the entire content server environment—
all servers and all clients—runs on operating systems that support multi-byte languages
(for example, Japanese or Korean versions of Microsoft Windows). Otherwise errors may
occur, such as links to PDF renditions of content items not working, Dynamic Converter
failing to find content items, etc.
Checking in Microsoft Office XP Files
It is important to be aware of the following considerations when checking in Microsoft
Office XP files:
❖
If your system is using a Verity search engine prior to version 4.5.1 and you check
Microsoft Office XP files into Stellent Content Server, the native files will not be
included in the search index. This is due to limitations in the third-party search engine
technology used with Stellent Content Server.
❖
If your system is using Verity version 4.5.1 or greater, Office XP files will be indexed,
or if your system uses PDF Converter to convert Microsoft Office XP files, the PDF
versions of the files will be indexed.
Note: Check with your system administrator if you are uncertain which third-party search
engine is used by your system, and how it handles full-text indexing of files.