<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">What e-mail client are you using? I've been using Mail.app and (with the exception of your e-mail) I've been getting all the breves today, just fine.<div><br></div><div><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Larry</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">---</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Larry Gillick</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Assistant Professor</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Digital and Broadcast Media</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">/ Arts Communication</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Shenandoah University</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">---</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Cell: 252-412-7511</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Google IM: Gillick</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Skype: GillickL</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">SL: Ed Stockton</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Twitter: Gillick</div></div><div><br class="webkit-block-placeholder"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"> </div><br><div><div>On Sep 13, 2009, at 5:43 PM, Michael Rank wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Not being a professional Koreanist (far from it!) I don't want to risk my life in the War of the Breves but may I point out that all the letters with breves have come out as question marks ? on my computer - a Mac - and I believe Frank Hoffmann uses a Mac too!<br><br>Michael (keeping head well under parapet...)<br><br><br><blockquote type="cite">Message: 5<br></blockquote><blockquote type="cite">Date: Sun, 13 Sep 2009 16:39:44 -0400<br></blockquote><blockquote type="cite">From: Frank Hoffmann <<a href="mailto:hoffmann@koreaweb.ws">hoffmann@koreaweb.ws</a>><br></blockquote><blockquote type="cite">Subject: Re: [KS] The Mystery of the Breve<br></blockquote><blockquote type="cite">To: <a href="mailto:koreanstudies@koreaweb.ws">koreanstudies@koreaweb.ws</a><br></blockquote><blockquote type="cite">Message-ID: <<a href="mailto:20090913163944.zgyrr8x3r4c0wwos@koreaweb.ws">20090913163944.zgyrr8x3r4c0wwos@koreaweb.ws</a>><br></blockquote><blockquote type="cite">Content-Type: text/plain;<span class="Apple-tab-span" style="white-space:pre"> </span>charset=UTF-8;<span class="Apple-tab-span" style="white-space:pre"> </span>DelSp="Yes";<span class="Apple-tab-span" style="white-space:pre"> </span>format="flowed"<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Dear Brother Anthony, and others:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sorry to be so direct, but I feel that THIS should really not anymore<br></blockquote><blockquote type="cite">be one of the points to be discussed on the<br></blockquote><blockquote type="cite">transcription/transliteration issue.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">It was done before, but here again the technical basics:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">(a) First, the problems listed (mostly limited for non-informed users)<br></blockquote><blockquote type="cite">will go away within the next couple of years, as soon as old and<br></blockquote><blockquote type="cite">outdated software and older computers have been replaced by newer<br></blockquote><blockquote type="cite">script/program versions (of message boards, email software, etc.) and<br></blockquote><blockquote type="cite">operating systems (such as Mac OS X or Windows XP and later). Of<br></blockquote><blockquote type="cite">course, when to replace or update outdated hard- and software is an<br></blockquote><blockquote type="cite">individual choice.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">(b) As was pointed out on this list before (by myself and others), the<br></blockquote><blockquote type="cite">"new" (that is 1990s) Unicode fonts that are now standard for Windows<br></blockquote><blockquote type="cite">(starting, I believe, with Windows 2000 or XP, and with Mac OS 9) all<br></blockquote><blockquote type="cite">include br?ves as well as Hanja, Han'g?l, Hiragana, Arabic, Hebrew,<br></blockquote><blockquote type="cite">Tibetan, Bengali, and the alphabets and scripts of many other world<br></blockquote><blockquote type="cite">languages. Just look it up in the Wikipedia:<br></blockquote><blockquote type="cite"><a href="http://en.wikipedia.org/wiki/Unicode">http://en.wikipedia.org/wiki/Unicode</a> or visit the Unicode home page:<br></blockquote><blockquote type="cite"><a href="http://unicode.org">http://unicode.org</a><br></blockquote><blockquote type="cite">... QUOTE: "Unicode consists of a repertoire of more than 100,000 characters"<br></blockquote><blockquote type="cite">All these characters are in each of the standard new fonts you use --<br></blockquote><blockquote type="cite">say Arial, Times, Palatino, or Courier. However, all of us have most<br></blockquote><blockquote type="cite">likely still other older pre-Unicode fonts installed on our computers,<br></blockquote><blockquote type="cite">and only if you now reformat some text you got from someone else using<br></blockquote><blockquote type="cite">an Unicode font (or reverse), only then will you run into trouble.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">(c) You stated that in a Mac environment it is especially difficult to<br></blockquote><blockquote type="cite">type the br?ves. Well, it is not. With an US-English keyboard layout<br></blockquote><blockquote type="cite">(you can freely choose the keyboard layout in the Mac preferences)<br></blockquote><blockquote type="cite">this is what you type (might vary according to chosen keyboard layout):<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">McCune-R :<br></blockquote><blockquote type="cite"> ? --> ALT + b, then o<br></blockquote><blockquote type="cite"> ? --> ALT + b, then SHIFT + o<br></blockquote><blockquote type="cite"> ? --> ALT + b, then u<br></blockquote><blockquote type="cite"> ? --> ALT + b, then SHIFT + u<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hepburn:<br></blockquote><blockquote type="cite"> ? --> ALT + a, then o<br></blockquote><blockquote type="cite"> ? --> ALT + a, then SHIFT + o<br></blockquote><blockquote type="cite"> ? --> ALT + a, then u<br></blockquote><blockquote type="cite"> ? --> ALT + a, then SHIFT +<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">(d) Web pages using br?ves (or any other characters present in Unicode<br></blockquote><blockquote type="cite">fonts, such as Han'g?l or Chinese Characters): all that the web<br></blockquote><blockquote type="cite">designer needs to do to make this work for ALL newer web browsers<br></blockquote><blockquote type="cite">under any OS is to use UTF-8 encoding -- this is done by inserting<br></blockquote><blockquote type="cite">this line in the header:<br></blockquote><blockquote type="cite">"charset=UTF-8" (instead of, for example, "charset=iso-8859-1" for<br></blockquote><blockquote type="cite">standard older Latin encoding). The problem that Mac users sometimes<br></blockquote><blockquote type="cite">have is that websites in Korean language are often encoded in national<br></blockquote><blockquote type="cite">Korean codes (a problem you see with many Han'g?l sites), not using<br></blockquote><blockquote type="cite">Unicode character sets either but Windows-only fonts -- and THIS is<br></blockquote><blockquote type="cite">rather a problem created by the 'ignorance' of the makers of these<br></blockquote><blockquote type="cite">websites, one that will for sure also disappear rather sooner than<br></blockquote><blockquote type="cite">later. The latest version of the Mac Safari browser, by the way, deals<br></blockquote><blockquote type="cite">quite well with most of these strange setups (not so Firefox).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Best wishes,<br></blockquote><blockquote type="cite">Frank<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">========= q u o t e =========<br></blockquote><blockquote type="cite">(...)<br></blockquote><blockquote type="cite">In addition, we know that any email, blog, or web page into which we<br></blockquote><blockquote type="cite">have inserted such a special character will more often than not (more<br></blockquote><blockquote type="cite">than 50% of the time, I am told) fail to work when viewed on another<br></blockquote><blockquote type="cite">computer, even using the same browser; the special characters will<br></blockquote><blockquote type="cite">usually be seen as ? or as some kind of blob. Moreover, the text of a<br></blockquote><blockquote type="cite">500-page book composed on a PC using (say) MSWord, into which we have<br></blockquote><blockquote type="cite">carefully inserted breved characters as above, once it has been sent<br></blockquote><blockquote type="cite">to the editor or printer (not only in the US) will usually be<br></blockquote><blockquote type="cite">transported into a Mac environment. Each breved character, to say<br></blockquote><blockquote type="cite">nothing of apostrophes and the dashes if not hyphens, disappears and<br></blockquote><blockquote type="cite">someone has to go through the entire text, looking at a printout of<br></blockquote><blockquote type="cite">the original, re-inserting the breved characters etc (which is said<br></blockquote><blockquote type="cite">to be especially tricky on a Mac, I don't know). It is also not<br></blockquote><blockquote type="cite">possible to use the MSWord 'search and replace' function to introduce<br></blockquote><blockquote type="cite">as 'replace' a word with a breved letter.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">So my question is: in the light of this set of problems with breved<br></blockquote><blockquote type="cite">letters, which are with us every day and will not be going away any<br></blockquote><blockquote type="cite">time soon, (...)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">=============================<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">------------------------------<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Message: 6<br></blockquote><blockquote type="cite">Date: Sun, 13 Sep 2009 16:59:16 -0400<br></blockquote><blockquote type="cite">From: Javier Cha <<a href="mailto:javiercha@gmail.com">javiercha@gmail.com</a>><br></blockquote><blockquote type="cite">Subject: Re: [KS] The Mystery of the Breve<br></blockquote><blockquote type="cite">To: Korean Studies Discussion List <<a href="mailto:koreanstudies@koreaweb.ws">koreanstudies@koreaweb.ws</a>><br></blockquote><blockquote type="cite">Message-ID:<br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span><<a href="mailto:dffd4c960909131359t7ee5a4c0x4071d99501d9d72f@mail.gmail.com">dffd4c960909131359t7ee5a4c0x4071d99501d9d72f@mail.gmail.com</a>><br></blockquote><blockquote type="cite">Content-Type: text/plain; charset=UTF-8<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Just to add to the discussion of typing breved (is that a word?)<br></blockquote><blockquote type="cite">vowels in Windows:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Microsoft Word (the Windows editions) allows direct input of unicode<br></blockquote><blockquote type="cite">characters through conversion from the hexadecimal number to which the<br></blockquote><blockquote type="cite">character is mapped. It is a trick that has served me well for many<br></blockquote><blockquote type="cite">years now.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The hex numbers for the vowels with breve in the MR system are:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">? --> 014f<br></blockquote><blockquote type="cite">? --> 014e<br></blockquote><blockquote type="cite">? --> 016d<br></blockquote><blockquote type="cite">? --> 016c<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">To try this, open Microsoft Word; type 014f and press Alt+X. Word will<br></blockquote><blockquote type="cite">convert the hex code into the corresponding unicode character, ?.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Unfortunately this function is not implemented in other Windows<br></blockquote><blockquote type="cite">applications. Maybe there are third party tools that allow this kind<br></blockquote><blockquote type="cite">of input but I haven't researched yet. If you use the full version of<br></blockquote><blockquote type="cite">Outlook (not Outlook Express or Windows Mail) you can enable Word as<br></blockquote><blockquote type="cite">the email editor and use this feature.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Javier<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Sun, Sep 13, 2009 at 4:39 PM, Frank Hoffmann <<a href="mailto:hoffmann@koreaweb.ws">hoffmann@koreaweb.ws</a>> wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Dear Brother Anthony, and others:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Sorry to be so direct, but I feel that THIS should really not anymore be one<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">of the points to be discussed on the transcription/transliteration issue.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">It was done before, but here again the technical basics:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(a) First, the problems listed (mostly limited for non-informed users) will<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">go away within the next couple of years, as soon as old and outdated<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">software and older computers have been replaced by newer script/program<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">versions (of message boards, email software, etc.) and operating systems<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(such as Mac OS X or Windows XP and later). Of course, when to replace or<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">update outdated hard- and software is an individual choice.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(b) As was pointed out on this list before (by myself and others), the "new"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(that is 1990s) Unicode fonts that are now standard for Windows (starting, I<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">believe, with Windows 2000 or XP, and with Mac OS 9) all include br?ves as<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">well as Hanja, Han'g?l, Hiragana, Arabic, Hebrew, Tibetan, Bengali, and the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">alphabets and scripts of many other world languages. Just look it up in the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Wikipedia: <a href="http://en.wikipedia.org/wiki/Unicode">http://en.wikipedia.org/wiki/Unicode</a> or visit the Unicode home<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">page: <a href="http://unicode.org">http://unicode.org</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">... QUOTE: "Unicode consists of a repertoire of more than 100,000<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">characters"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">All these characters are in each of the standard new fonts you use -- say<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Arial, Times, Palatino, or Courier. However, all of us have most likely<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">still other older pre-Unicode fonts installed on our computers, and only if<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">you now reformat some text you got from someone else using an Unicode font<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(or reverse), only then will you run into trouble.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(c) You stated that in a Mac environment it is especially difficult to type<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the br?ves. Well, it is not. With an US-English keyboard layout (you can<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">freely choose the keyboard layout in the Mac preferences) this is what you<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">type (might vary according to chosen keyboard layout):<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">McCune-R :<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + b, then o<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + b, then SHIFT + o<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + b, then u<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + b, then SHIFT + u<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Hepburn:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + a, then o<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + a, then SHIFT + o<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + a, then u<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">?? --> ALT + a, then SHIFT +<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(d) Web pages using br?ves (or any other characters present in Unicode<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">fonts, such as Han'g?l or Chinese Characters): all that the web designer<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">needs to do to make this work for ALL newer web browsers under any OS is to<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">use UTF-8 encoding -- this is done by inserting this line in the header:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">"charset=UTF-8" (instead of, for example, "charset=iso-8859-1" for standard<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">older Latin encoding). The problem that Mac users sometimes have is that<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">websites in Korean language are often encoded in national Korean codes (a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">problem you see with many Han'g?l sites), not using Unicode character sets<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">either but Windows-only fonts -- and THIS is rather a problem created by the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">'ignorance' of the makers of these websites, one that will for sure also<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">disappear rather sooner than later. The latest version of the Mac Safari<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">browser, by the way, deals quite well with most of these strange setups (not<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">so Firefox).<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Best wishes,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Frank<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">========= q u o t e =========<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(...)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">In addition, we know that any email, blog, or web page into which we have<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">inserted such a special character will more often than not (more than 50% of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the time, ?I am told) fail to work when viewed on another computer, even<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">using the same browser; the special characters will usually be seen as ? or<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">as some kind of blob. Moreover, the text of a 500-page book composed on a PC<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">using (say) MSWord, into which we have carefully inserted breved characters<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">as above, once it has been sent to the editor or printer (not only in the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">US) will usually be transported into a Mac environment. Each breved<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">character, to say nothing of apostrophes and the dashes if not hyphens,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">disappears and someone has to go through the entire text, looking at a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">printout of the original, ?re-inserting the breved characters etc (which is<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">said to be especially tricky on a Mac, I don't know). It is also not<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">possible to use the MSWord 'search and replace' function to introduce as<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">'replace' a word with a breved letter.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">So my question is: in the light of this set of problems with breved letters,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">which are with us every day and will not be going away any time soon, (...)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">=============================<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">End of Koreanstudies Digest, Vol 75, Issue 14<br></blockquote><blockquote type="cite">*********************************************<br></blockquote><blockquote type="cite"><br></blockquote><br><br></div></blockquote></div><br></div></body></html>