On 25. mai 2013 16:32, Sebastian Lipp wrote: > On 2013-05-24 04:22, Gaute Hope wrote: >> On 24. mai 2013 13:59, Sebastian Lipp wrote: >>> Just tried to install (via gem) and run it via rbenv under ruby >>> 1.9.3-p327 and 1.9.3-p392. With both I have the problem that characters >>> like Umlauts are not show correctly. For example: "รค" becomes "\xe4". >> >> Don't have the chance to go investigate much atm, but it could be >> related to RMail and the usual lack of correct UTF-8 handling. I would >> suggest you open an issue here though: >> >> https://github.com/sup-heliotrope/sup/issues?state=open >> >> otherwise it can easily disappear away.. > > Do you thing my description is good enough to open a new issue? > >> If you are bold enough #61 >> (https://github.com/sup-heliotrope/sup/pull/61) have initial Mail >> support for ruby 2.0, it would be interesting to see if the problem is >> present there. > > After bundle install and the branch's checkout it failed to load syck. A > `gem i syck` later it fails With > > syck has been removed > > /home/bacuh/.rbenv/versions/2.0.0-p0/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in > `require': > > /home/bacuh/.rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/rmail-1.0.0/lib/rmail/address.rb:694: > invalid multibyte escape: /\A[\200-\377\w!$%&\'*+\/=?^_\`{\}|~#-]+/m > (SyntaxError) > > If you have a quick resolution for that I can go on and see if the > encoding problems still exist on this branch.
The pull request hasn't been merged into the official repo yet, so you'd have to grab it from my repo: git://github.com/gauteh/sup.git (neither syck nor rmail is required) Yes, I think so, these issues are diffuse.. but they re-appear all the time. With a test-email to reproduce the issue things get easier. Regards, Gaute _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk