Internationalization of Squid

• Goal: To make Squid error pages available in many languages.

• Status: Translations needed.

• Version: 2.5+ (langpacks), 3.1+ (auto-negotiate, CSS)

• Download: http://www.squid-cache.org/Versions/langpack/

• Coordinator: AmosJeffries. Anyone can contribute translations.

Volunteer Translation Moderators

Several people have volunteered their time to check and confirm translations to keep their language(s) updated.

How can I contribute?

Suggest a translation fix

• How we do translations and how you can join in is detailed at Translations/Basics

  What you need to know to make useful translations is at Translations/Guidelines

Become a language moderator

We really need people familiar enough with each language listed above to verify and approve/reject the general suggestions. Please contact AmosJeffries directly about becoming a moderator.

How does this affect my installed Squid?

Any Squid is able to use the pre-translated langpack tarballs, but the auto-negotiate and CSS features are not planned for back-porting.

Any existing Squid which have been configured with error_directory in their squid.conf will not be affected. If you have used this method to provide your own language translations please consider joining the translation effort by submitting your language as outlined above, and then upgrading to the langpack or 3.1 with auto-negotiate.

• Squid older than 3.1 without an explicit error_directory entry have a default one. This may need overriding to use the new files.

What has been done?

• More languages and new page translations
• HTML 4.01 strict standards compliance
• Provides error pages matched to visitors own browser language settings.
• Provides direct control of error page display using CSS.

So how can I do this upgrade?

Manual Install

Squid-3.1 admin just need to follow these steps:

• Check that your preferred default language is available for auto-translated pages. The ones installed can be seen in your squid error directory as a bunch of folders named after their ISO codes: (en, en-gb, etc.).

• Add error_default_language option to squid.conf with the code/folder-name for the language. This will provide a suitable default language if none can be negotiated with the browser.

• Remove error_directory from squid.conf

• Optional: download newest translations and languages package

• Make any CSS changes you need to /etc/squid/errorpage.css for display.

Reconfigure or restart squid.

• Languages specified by their full name (ie English) are not able to be auto-negotiated. They are now deprecated and due for removal as soon as ISO coded versions are made available.

Debian and Ubuntu

The error pages bundle is available as a package squid-langpack starting with Debian Squeeze or Ubuntu Karmic Koala.

Install that package and update your squid.conf settings as above. Noting that the error page files are now installed under /usr/share/squid-langpack

Troubleshooting

Now I keep getting: "Unable to load default error language files. Reset to backups."

The language code you have entered in squid.conf for error_default_language does not match any of the currently installed error page translations.

Check that you spelled it correctly, it must match the ISO codes used for one of the sub-directory names in your squid errors directory.

• This only affects the backup language, the one used if the users preferred is not available.

What about the custom ERR_MY_PAGE files I made?

Yes Squid can still present them. Even while presenting localized copies of the basic error pages.

Your custom templates should for now go into the templates/ directory when using the localization. They will need unique names, so as not to clash with the default pages.

CategoryFeature