[Rumpus-talk] Rumpus problem(?)

[John O'Fallon]

First of all, the general problem is one of character encoding.   
Character encoding refers to how characters are represented.  For  
example, in one encoding, the number 1 might refer to the letter "a",  
while in another, "a" might be represented by the number 112.

There are several character encodings in use.  Common encodings  
include "Latin-1" and "UTF-8".  If you take a stream of text that was  
encoded in "Latin-1", and try to display it in "UTF-8", you end up  
with garbage characters being displayed.

Virtually all modern character encodings use ASCII as their starting  
point, which is why common English characters pretty much always  
display correctly.  In other words, if you display a block of text  
using the wrong encoding, the letters a-z and numbers will still be  
displayed correctly, but extended characters will become garbled.

When a Web page is delivered, the server tells the browser what  
encoding the page should be used to display the page.  So in most  
cases, we don't see this problem in the Rumpus WFM.  Since you are  
having the problem in the Web interface, you'll need to send details  
(including the server address and a test name and password) to "support at maxum.com 
".

In FTP, there is no reliable way for the server to signal to the  
client what encoding should be used.  The most common encoding today  
(and increasing in popularity) is UTF-8, and that's the encoding  
Rumpus uses.  In the FTP client, make sure you specify "UTF-8" for  
text encoding, and everything should work fine.

John

On Mar 4, 2010, at 10:07 AM, Lars-Olof Thid wrote:

> The problem occurs in Web browsers and FTP clients. The e-mail  
> messages show the correct filnames.