>I'm currently struggling with the Russian translation. Andrej Borodkin >has sent me the ru.po file, but because of the Cyrillic alphabet, the >Russian translation requires a different character set (Windows-1251). >Accordingly I have added a meta tag to the Ringlink HTML output that >lets the browsers know which character set to use, and I have added the >following headers to the emails: > > MIME-Version: 1.0 > Content-type: text/plain; charset=Windows-1251 > >But this is new stuff to me, and if anybody on this list has any >experience to share about handling different character sets, I'd >appreciate some advise. > >"Ringlink Demo" has been updated with the changes mentioned above, so if >you want to check it out, you can either submit a Russian test ring or >change the ring language of "Demoring" to Russian. Back in the old days, when Webring.org worked (before Yahoo!), I maintained a CGI script that would generate the code for my ring in the language of the choice of the user (subject to there being a translation; I eventually had Czech, Danish, English, French, German, Norwegian, Russian, Spanish, and Swedish translations). The solution I used was to keep the character set inside the text file that provided the information for each of the translations. The script then inserted the meta tag and header, just as you are doing. Just insert a new section in the .po files that specifies the character set and you should be ready for it. It's actually *reading* the Russian that's the hard part. :)