Menu

#4 Encoding

2.0
accepted
2020-04-08
2014-12-23
No

Custom encoding isn't supported.
Unicode is not correctly found and set in some languedges. (Please add your languedges in comments so we can add priorities and testings).

Related

Tickets: #4

Discussion

<< < 1 2 (Page 2 of 2)
  • Araz Farhang Dareshuri

    Please try to check out our latest code, the subject encoding is believed to be implemented but yet to be tested. Please don't forget to inform us about the results

     
    • Bùi Văn Nhân

      Bùi Văn Nhân - 2017-07-22

      i'm using last version (Install-Package AIM -Version 1.0.3)
      Result subject "tiếng việt" -> "ti?ng vi?t"

       
      • Erik Rocha Witkowski

        You need to download and compile the code, since the latest code still not avaliable on Nuget.

         
  • Bùi Văn Nhân

    Bùi Văn Nhân - 2017-08-02

    I was successful.
    Thank you very much.

     
    • Mahadev B

      Mahadev B - 2017-11-14

      @Bùi Văn Nhân
      I tried with given .dll and also with nuget package AIM -Version 1.0.3. But this also did not work for me. Can you please specify which encoding you have used and is there any other propery to be set ?
      I am trying to add superscript in subject,e.g. Test™, but it is showing "Test?"

       

      Last edit: Mahadev B 2017-11-14
      • Bùi Văn Nhân

        Bùi Văn Nhân - 2017-11-14

        I downloaded and compiled the code, since the latest code is still not available on Nuget. (help from @Erik Rocha Witkowski)

         
  • Mahadev B

    Mahadev B - 2017-11-14

    I downloaded the code, compiled it and it works for me.
    I used Encoding.UTF8 for my problem.
    Thank you very much.

     
  • Putu Kusmawan

    Putu Kusmawan - 2017-11-15

    After downloading and compiling the sourcecode, I can confirm that encoding works well for Korean characters.
    Now, I am waiting for nuget package update.

    Thanks.

     
  • Jon Bush

    Jon Bush - 2018-06-18

    Subject field has wrong encoding if you set next value - "Инвойс со складами №0-ИнвСкл-00000007 от 18.06.2018"
    If you download and compile sources the error will not go away. For me helped another solution. I use "Convert.ToBase64String" with one parameter instead of "TransferEncoder.ToBase64'" in GetEncodedSubject function.

    private string GetEncodedSubject()
    {
        if (MailMessage.SubjectEncoding.Equals(Encoding.ASCII))
        {
        return MailMessage.Subject;
        }
        else
        {
            var encodingName = MailMessage.SubjectEncoding.BodyName.ToLower();
            return string.Format("=?{0}?B?{1}?=", encodingName, Convert.ToBase64String(MailMessage.SubjectEncoding.GetBytes(MailMessage.Subject)));
        }
    }
    
     

    Last edit: Jon Bush 2018-06-18
  • KIM

    KIM - 2018-12-03

    Hello, my english is not so good.

    I'm using 1.0.3.0.
    I'm Korean.

    Subject and Sender Name encoding has problem. => ??
    mailMessage.SubjectEncoding = Encoding.UTF8;
    mailMessage.Subject = "테스터"; // <= display text is "??"

    help me, please...

    Best Regards.
    KIM.

     
  • kevinpan

    kevinpan - 2018-12-18

    Works great for Chinese! Thanks!
    Holp this project will move to github.

     
  • Anderson

    Anderson - 2020-04-08

    Hello, I'm experiencing the same problem, my language is Brazilian Portuguese, and I've tested all the encods but none work for the subject, the body is ok, can someone help me? This library is perfect, it fulfills my need, but I would really need the subject spelled correctly. Thanks!

     

    Last edit: Anderson 2020-04-08
<< < 1 2 (Page 2 of 2)

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.