Databases
StackOverflow2013
Postsdbo
POjapanese email subject encoding
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POjapanese email subject encoding
    primarykey
    data
    text
    <p>Aparently, encoding japanese emails is somewhat challenging, which I am slowly discovering myself. In case there are any experts (even those with limited experience will do), can I please have some guidelines as to how to do it, how to test it and how to verify it?</p> <p>Bear in mind that I've never set foot anywhere near Japan, it is simply that the product I'm developing is used there, among other places.</p> <p>What (I think) I know so far is following:<br> - Japanese emails should be encoded in ISO-2022-JP, Japanese JIS codepage 50220 or possibly SHIFT_JIS codepage 932<br> - Email transfer encoding should be set to Base64 for plain text and 7Bit for Html<br> - Email subject should be encoded separately to start with "=?ISO-2022-JP?B?" (don't know what this is supposed to mean). I've tried encoding the subject with </p> <pre><code>"=?ISO-2022-JP?B?" + Convert.ToBase64String(Encoding.Unicode.GetBytes(subject)) </code></pre> <p>which basically gives the encoded string as expected but it doesn't get presented as any japanese text in an email program<br> - I've tested in Outlook 2003, Outlook Express and GMail </p> <p>Any help would be greatly appreciated</p> <hr> <p>Ok, so to post a short update, thanks to the two helpful answers, I've managed to get the right format and encoding. Now, Outlook gives something that resembles the correct subject:<br> <code>=?iso-2022-jp?B?6 Japanese test に各々の視点で語ってもらった。 6相当の防水?=</code></p> <p>However, the exact same email in Outlook Express gives subject like this:<br> <code>=?iso-2022-jp?B?6 Japanese test 縺ｫ蜷・・・隕也せ縺ｧ隱槭▲縺ｦ繧ゅｉ縺｣縺溘・ 6逶ｸ蠖薙・髦ｲ豌ｴ?=</code></p> <p>Furthermore, when viewed in the Inbox view in Outlook Express, the email subject is even more weird, like this:<br> <code>=?iso-2022-jp?B?6 Japanese test ??????????????? 6???????=</code></p> <p>Gmail seems to be working in the similar fashion to Outlook, which looks correct.</p> <p>I just can't get my head around this one.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMakoto
    1. USdanijels
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POjapanese email subject encoding
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POjapanese email subject encoding
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POjapanese email subject encoding
      1. This table or related slice is empty.
      1. VTUpMod
    1. COyour assumptions are right, but I'm not sure about the syntax sorry.
      singulars
      1. POjapanese email subject encoding
      1. USRobert Gould
    2. COI'm just wondering, why can't you just use UTF-8?
      singulars
      1. POjapanese email subject encoding
      1. USTamas Czinege
    3. COYou "could" use UTF-8, but the reality in Japan, is that UTF-8 is still a second class citizen by far. Most japanese machines and documents I've encountered at government sties, businesses and schools here in Japan are still SHIFT_JIS.
      singulars
      1. POjapanese email subject encoding
      1. USRobert Gould
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload