-
Notifications
You must be signed in to change notification settings - Fork 16
Troubleshooting language support
The one of WebOne features is character encoding converting support. Currently all Internet is using UTF-8 text encoding, which is common for all languages (including emoji). But in 1990s Web browsers & Web sites were used older character sets (code pages) for each language and system. WebOne can convert UTF-8 to such code pages.
To view content in your language using a retro Web browser, you need:
- Fonts with language support (consider use an localized OS).
- A browser with particular code page support (or UTF-8 support).
- For all Latin, Greek or Cyrillic languages, most browsers from 1990s have proper support.
- Chinese/Japan/Korean and Middle-East languages are also somewhere supported.
- WebOne, running on a properly-configured server OS.
Hint: Microsoft Windows 3.1 "for Central and Eastern Europe", Windows 95 "Pan European" and English Windows 98/2000+ have support for Cyrillic and Eastern-Europe languages if installed with proper locale selected
Hint: Apple MacOS 9 is providing proper multi-language support via Language Kits. If you still see incorrect characters, try run Language Register from Utilities folder, and register correct language for web browser application file.
By default, WebOne is serving clients with the encoding, used on source Web server. Just not changes it. The exception is older browsers like listed below, for which it returns content in system code page:
- NCSA Mosaic (Windows): 1251-1258.
- NCSA Mosaic (Macintosh): 10000-10082.
- Netscape Navigator 3 and earlier, MS Internet Explorer 3 and earlier (Windows): 1251-1258.
- Netscape Navigator 3 and earlier, MS Internet Explorer 3 and earlier (Macintosh): 10000-10082.
- Netscape Navigator 3 and earlier (OS/2 Warp): 850/851/866/etc.
- All MS-DOS web-browsers, like DosLynx and xChaos Arachne: 850/851/866/etc.
Microsoft Internet Explorer 4 (and newer), Netscape Communicator 4 (and newer), Mozilla, Opera, etc does support UTF-8, so they are serving with source encoding disregarding which is it.
Open http://localhost:8080/!codepages/, and scroll to the bottom. You should see something:
The example is related to Russia, Ukraine, Belarus and partially Bulgaria, Serbia, North Macedonia (they also use CP1251, but not CP866).
If code page names are valid for your language, the language support is probably correct. You should be able to read web sites without code-page problems. In some cases you'll be need to manually select correct encoding via browser's menu (if automatic detection fails).
This means that the server OS is incorrectly configured for locale. The most spreaded situation is an unlocalized "English" configuration of system, which results in these default encodings:
It is valid for browsing sites on Western European languages (English, French, German, Spain, etc), but only. To add support for other languages, it's need to configure proxy server OS or WebOne self.
On Linux try to google manuals for your distribution, and set LOCALE
environment for entire OS. If it's not possible, configure systemd service file:
$ su
# nano /etc/systemd/system/webone.service
Add an instruction into service configuration:
[Service]
Environment="LANG=ru_RU.UTF-8"
Ctrl+X, Save.
# systemctl daemon-reload
# service webone restart
On Windows, open Regional Settings in Control Panel, and set Default system language. Then reboot Windows.
The another way is to edit codepage.conf
file of WebOne, and change universal placeholders to real code page numbers.
An example for CIS Cyrillic conditions:
-
AddOutputEncoding=Windows
=>AddOutputEncoding=1251
-
AddOutputEncoding=DOS
=>AddOutputEncoding=866
-
AddOutputEncoding=Apple
=>AddOutputEncoding=10007
- Release Archive
- Websites edits / Syntax of traffic edits
- Known bugs / Report a new bug
- Windows installation
- Linux installation
- macOS installation
- Android installation
- Configuration file
- Command line arguments
Usage:
- Installing the Root Certificate
- YouTube playback
- Using with ViewTube
- Using with virtual machines
- Using with FTP servers
- Using with MSN Messenger
Web standards timeline:
Troubleshooting guides:
Developer corner: