Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
4 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Original file line | Diff line number | Diff line change |
---|---|---|---|
|
@@ -3,18 +3,13 @@ | ||
http://tmail.rubyforge.org/ | http://tmail.rubyforge.org/ | ||
|
|
||
Mikel Lindsaar maintainer | Mikel Lindsaar maintainer | ||
Trans assitant developer | Minero Aoki original developer | ||
Minero Aoki original developer | |||
|
|
||
== RUBY 1.9 COMPATIBILITY | == RUBY 1.9 COMPATIBILITY | ||
|
|
||
Note... as of 1.2.5, TMail is not compatible with Ruby 1.9.1. We are now using rchardet | Note... as of 1.2.5, TMail is not compatible with Ruby 1.9.1. For 1.9.1 + compatibility, | ||
to compare encodings and there is work to do for Ruby 1.9.1 due to it's encoding | I suggest you look at Mail (https://github.com/mikel/mail). Mail is used by ActionMailer | ||
capability. | in Rails 3.0 and beyond and is ready to handle your email sending and parsing needs. | ||
|
|||
For 1.9.1 + compatibility, I suggest you look at Mail (https://github.com/mikel/mail/tree) | |||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
mikel
Author
Owner
|
|||
while this is a work in progress, it is what I am working on to replace TMail for Ruby | |||
1.9 and beyond. | |||
|
|
||
== DESCRIPTION: | == DESCRIPTION: | ||
|
|
||
|
I'm not planning on implementing it in TMail.
I am now working on Mail, which is a new mail library. This is released and in production. My new efforts will be going into Mail.
Please let me know if you want to work on an FFI parser in TMail. It is a tonne of work. The tmail internals are quite complex and there are many many touch points on encodings you would have to handle. Also, I do not believe the parser is encoding aware at all... so you would have to fix this as well.
Mikel