This is my WORKING adaptation of your nice CODE.
#-#############################################
# The Config-Variables of: Text-Translation
#-#############################################
# Your language
#
# 1 = English
# 2 = German
# 3 = Latvian
# 4 = Russian
# and so on ...
#
# Add your personal translation as a part of the [-brackets-]
# Don't change any word outside the [-brackets-]
$config{'lang'} = 1;
$config{'charset'} = {
1 => 1252, # English
2 => 1250, # German
3 => 1257, # Latvian
4 => 1251 # Russian
};
...
#-#############################################
# Edit your Page-Header (if needed)
#-#############################################
sub disp_header {
print <<EO_HTML;
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"Multimedia file viewing and clickable links are available for registered members only!! You need to
or
!!
">
<html>
<head>
EO_HTML
print qq|<meta http-equiv="Content-Type" content="text/html; charset=windows-$config{'charset'}->{$form{'lang'}}
" />|;
print <<EO_HTML;
<style>....
I've been trying with charset=utf-8, but it is not working. Maybe because both server and client runs on windows OS,
and Windows is not unicode system, you can see properly only one language group, but if your machine should display
at the same time text with different codepages (as for me - Latvian and Russian), you will see only your native text.
I think for my situation it is standart decision.
On the other hand we can use unicode charset in the head on our page, but all the standard symbols in this case should be written like in this way: Пo-pycckи but this is not editable text!
I don't know, is it possible to make web-server transfer in unicode not in ASCII, but all html code will be twice bigger.
So in our case using *.pl files in utf-8 helps to keep our text readable, but for transfering we are forced to use charsets.