Home

Content Sources

Index

Search
  Search Features
    Front Ends
      Output Format
      KeyMatch
      Related Queries
      Filters
      Remove URLs
      OneBox Modules
    Query Settings
    Document Preview Module
    Result Biasing
    Suggestions
    Dynamic Navigation
    Language Bundles
    User Results
    Expert Search
  Secure Search
  Diagnostics

Reports

GSA Unification

GSAⁿ

Administration

More Information

Search > Search Features > Front Ends > Output Format

Use the Search > Search Features > Front Ends > Output Format tab to perform the following tasks:

• Changing the appearance of user interface pages
• Changing the language of the user interface
• Changing the HTTP Response Content-Type Header

Before Starting these Tasks

If you have multiple front ends for your search appliance, identify the front end where you want to change the appearance or language of pages. If you only use the default_frontend, determine if you want to change the appearance of pages or languages in it. If you only want to change the appearance of pages or languages for a specific group of end users, you must create a front end for this group of end users.

Changing the Appearance of User Interface Pages

There are two different tools that you can use to change the appearance of user interface pages in a front end:

• Page Layout Helper--Enables you to make changes easily to global attributes (logo, fonts, header, and footer), and to the look of the Search Box and Search Results.
• XSLT Stylesheet Editor--Enables you to make more extensive changes to the XSLT stylesheet. If the elements that you want to change are not available in the Page Layout Helper, you must use the XSLT Stylesheet Editor to change them. The Stylesheet contains sections for various components, preceded by comments so that you know whether a section can be customized. The search appliance supports UTF-8 encoding without the byte order mark (BOM) for XSLT.

To use the Page Layout Helper or the XSLT Stylesheet Editor:

1. Click Search > Search Features > Front Ends.
2. Click the Edit link next to the collection front end you want to edit.
   The Output Format Tab appears. From this Tab, you can use either the Page Layout Helper or the XSLT Stylesheet Editor.

Changing the Language of the User Interface

You can have your users' search page and search results pages in a language other than English, the default. You also can have several languages active for your users and the search appliance will present search results for an active language based on the settings detected in the end user's browser.

To make a language active using Page Layout Helper:

1. Choose the language to activate in the Language drop-down menu.
2. Click Save.
   In the Language drop-down menu, the language you activated has the word "Active" next to it.

To make an active language the default:

1. Choose an active language in the Language drop-down menu.
2. Click Make this Language the Default.

To make a language active using the XSLT Stylesheet Editor:

1. Choose the language to activate in the Language drop-down menu.
2. Click the Edit underlying XSLT code link.
   The text in the default stylesheet converts to that language.
3. In the XSLT Stylesheet Editor, make any format changes you like.
   If you are only making a language active, no changes are necessary.
4. Click Save to save as an active stylesheet.

To make languages active for a set of custom stylesheets using the XSLT Stylesheet Editor:

1. Customize the default language's stylesheet as desired using the Page Layout Helper or the XSLT Stylesheet Editor.
2. For each additional language, choose the language in the Language drop-down menu.
3. Click the Edit underlying XSLT code link.
   The text in the default stylesheet converts to that language.
4. Perform any language-specific customizations in the XSLT Stylesheet Editor.
   If you are only making a language active, no changes are necessary.
5. Click Save to save as an active stylesheet.

To remove an active language and disable the stylesheet for that language:

1. Choose the language in the Language drop-down menu.
2. Click Remove this Language.
   The stylesheet is no longer available in that language.

Changing the HTTP Response Content-Type Header

For all frontends, the default HTTP response Content-Type header value for XSLT transformed search results is text/html. It is possible to configure a frontend to return a custom Content-Type in the HTTP response headers for XSLT transformed search results. A custom Content-Type value must be of form "<type>/<subtype>" (for example "application/json"). Only alphanumeric characters and dashes are allowed in the type, and only alphanumeric characters, dashes, dots, and plus signs are allowed in the subtype.

The custom Content-Type header value is set if, and only if, XSLT transformation is performed as part of the query -- dictated by the presence and value of URL parameter proxystylesheet -- and succeeds. If XSLT transformation is not performed, or is unsuccessful, the Content-Type header value will default to text/html.

Changing the value of Search > Search Features > Front Ends > Output Format > HTTP Response Content-Type Header only changes the Content-Type header value. It does not change the content type of the search results rendered by the frontend.

To set the HTTP response Content-Type header value for a frontend:

1. Click Search > Search Features > Front Ends.
2. Click the Edit link next to the frontend you want to edit.
3. Click the Output Format tab.
4. In the HTTP Response Content-Type Header textbox enter the new Content-Type header value.
5. Click Save.

For More Information

For detailed information about changing the appearance of pages or languages in the user interface, see "Creating the Search Experience: Customizing the User Interface," which is linked to the Google Search Appliance help center.