I feel that this is all increasingly off-topic for this list. The issues you are raising are basic programming and the understanding of message body content (and presumably the K-9 code). I don't think that they are really relevant to a list focused on the use of K-9.
I think it might help for you to get a deeper understanding of message content internals, and perhaps a more complete view of the K-9 code (since that's what you have indicated you are working from). In general, I would assume that K-9 is doing things correctly, so work through that code to figure out what it's doing. If you want a better understanding of why, then read up on the topic overall (maybe starting with the RFC I referenced earlier). > Date: Tuesday, August 25, 2015 11:56:09 -0700 > From: [email protected] > > What I don't get is why is the message fragment in the list of > messages correct? This string is correct all the way up to the > point of being displayed by openMessage, or whatever it is that > displays it. > > On Tuesday, August 25, 2015 at 10:41:51 AM UTC-7, > [email protected] wrote: >> >> So, I need to encode my string that represents the body? Or >> convert the text body to something else? Is there a way I can >> specify what type of encoding the text body has? >> >> On Monday, August 24, 2015 at 2:18:33 PM UTC-7, Richard wrote: >>> >>> These are various forms of character encodings. >>> >>> For the "=2E" see RFC1521 >>> >>> <https://www.ietf.org/rfc/rfc1521.txt> >>> >>> For "=E2=80=A6", the client you are using to generate the >>> message isn't leaving those as three, separate, period >>> characters (dec-46). Rather it is turning it into the >>> non-standard ascii ellipsis. See: >>> >>> <http://www.fileformat.info/info/unicode/char/2026/index.htm> >>> >>> >>> I didn't look up your "=E2=80=9C", but suspect that the >>> generating client is turning quotes (dec-34 or dec-39) into >>> "smart quotes", which, again, aren't standard ascii. >>> >>> In short, the message text you generated/are dealing with isn't >>> clean ascii text (only 128 characters are represented in base >>> ascii). You need to understand the various encodings >>> ascii/utf-8, etc, and handle them as is best in your >>> environment. >>> >>> >>> > Date: Monday, August 24, 2015 13:53:12 -0700 >>> > From: [email protected] >>> > >>> > Some more notes. ... becomes "=E2=80=A6" and quotation marks >>> > become "=E2=80=9C" there is also this issue where in the >>> > middle of a word there is a line break "like th= >>> > is". >>> > >>> > On Monday, August 24, 2015 at 1:49:05 PM UTC-7, >>> > [email protected] wrote: >>> >> >>> >> So I am using a TextBody as the body of my message in K9. The >>> >> issue is that while my text looks correct when it is created >>> >> it runs into troubles later on. So lets say my text is >>> >> "lorem ipsum." On the inbox screen the preview would say >>> >> the subject, who it's from and "lorem ipsum." Clicking on >>> >> the message then takes me to that message which is now >>> >> "lorem ipsum=2E" what in the world is causing this? It >>> >> seems to be only for . and ... but I am not sure. Any help? >>> >>> ------------ End Original Message ------------ >>> >>> ------------ End Original Message ------------ -- -- You received this message because you are subscribed to the K-9 Mail Users List. To post to this group, send email to [email protected] To unsubscribe, email [email protected] To report an issue with K-9 Mail, visit http://code.google.com/p/k9mail/issues/list For more options, visit this group at http://groups.google.com/group/k-9-mail --- You received this message because you are subscribed to the Google Groups "K-9 Mail" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
