[KS] TECHNICAL note

[Frank Hoffmann]

Dear Deberniere, dear KS List Subscribers:

Just a TECHNICAL note responding to your below quoted request (since 
I do whatever necessary related to *technical* issues for the KS 
List):

List Home page:
http://koreaweb.ws/ks/

Here you find a SEARCH engine for the list archives on this page. 
SEARCH window is on that main page.

 From here you can also subscribe and un-subscribe, and once 
subscribed, you can change various settings (subscription options).
--> http://koreaweb.ws/mailman/listinfo/koreanstudies_koreaweb.ws

Furthermore, there is a link to the list ARCHIVES:
http://koreaweb.ws/pipermail/koreanstudies_koreaweb.ws/
Clicking at e.g. Professor Ledyard's last posting, you will see all 
the Korean and Chinese letters and characters just fine.
SAMPLE posting:
http://koreaweb.ws/pipermail/koreanstudies_koreaweb.ws/2010-October/008191.html


Solution for your email:
You may want to check your own computer settings. Even with systems 
that are several years old, there should not be any problem reading 
East Asian characters in messages received from our KS List (in 
email). Maybe you have your encoding somehow set to some local Korean 
encoding instead of Unicode? Or you are using a non-Unicode font in 
your email program. Try some standard new font that came with your 
computer's OS install, e.g. Times New Roman or Arial, that should 
sure work (for all East Asian and other scripts).

One last unrelated note:
Please be aware that, if you try to post to the list from an EMAIL 
ADDRESS that you are *not* subscribed with to the list, then this 
message will automatically bounce. Computers are very unkind and 
harsh and oftentimes insulting machines.


Best wishes,
Frank



>One technical request to list members: please give the Romanization 
>of any Hangeul or Chinese characters used in the text of the email, 
>as these characters always appear as question marks or other random 
>symbols when the digest reaches my email account, and it's not 
>always possible to tell from the context what they're supposed to 
>be, and using the "encoding" function does nothing. I'm sure there 
>are others with the same problem.
>
>Many thanks,
>
>Deberniere Torrey


-- 
--------------------------------------
Frank Hoffmann
http://koreaweb.ws