kde-playground/kdepim/messagecomposer/job/attachmentjob.cpp
2015-04-14 21:49:29 +00:00

172 lines
5.4 KiB
C++

/*
Copyright (c) 2009 Constantin Berzan <exit3219@gmail.com>
Parts based on KMail code by:
Various authors.
This library is free software; you can redistribute it and/or modify it
under the terms of the GNU Library General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at your
option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public
License for more details.
You should have received a copy of the GNU Library General Public License
along with this library; see the file COPYING.LIB. If not, write to the
Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
*/
#include "attachmentjob.h"
#include <boost/shared_ptr.hpp>
#include <KEncodingProber>
#include "contentjobbase_p.h"
#include "part/globalpart.h"
#include "singlepartjob.h"
#include "util.h"
#include <KDebug>
using namespace MessageComposer;
using namespace MessageCore;
class MessageComposer::AttachmentJobPrivate : public ContentJobBasePrivate
{
public:
AttachmentJobPrivate( AttachmentJob *qq )
: ContentJobBasePrivate( qq )
{
}
//QByteArray detectCharset( const QByteArray &data );
AttachmentPart::Ptr part;
Q_DECLARE_PUBLIC( AttachmentJob )
};
#if 0
QByteArray AttachmentJobPrivate::detectCharset( const QByteArray &data )
{
KEncodingProber prober;
prober.feed( data );
kDebug() << "Autodetected charset" << prober.encoding() << "with confidence" << prober.confidence();
// The prober detects binary attachments as UTF-16LE with confidence 99%, which
// obviously is wrong, so work around this here (most mail clients don't understand
// UTF-16LE).
const QByteArray detectedEncoding = prober.encoding();
if( prober.confidence() > 0.6 && !detectedEncoding.toLower().contains( "utf-16" ) ) {
return detectedEncoding;
} else {
kWarning() << "Could not autodetect charset; using UTF-8.";
return QByteArray( "utf-8" );
}
}
#endif
AttachmentJob::AttachmentJob( AttachmentPart::Ptr part, QObject *parent )
: ContentJobBase( *new AttachmentJobPrivate( this ), parent )
{
Q_D( AttachmentJob );
d->part = part;
}
AttachmentJob::~AttachmentJob()
{
}
AttachmentPart::Ptr AttachmentJob::attachmentPart() const
{
Q_D( const AttachmentJob );
return d->part;
}
void AttachmentJob::setAttachmentPart( AttachmentPart::Ptr part )
{
Q_D( AttachmentJob );
d->part = part;
}
void AttachmentJob::doStart()
{
Q_D( AttachmentJob );
Q_ASSERT( d->part );
if( d->part->mimeType() == "multipart/digest" ||
d->part->mimeType() == "message/rfc822" ) {
// this is actually a digest, so we don't want any additional headers
// the attachment is really a complete multipart/digest subtype
// and us adding our own headers would break it. so copy over the content
// and leave it alone
KMime::Content* part = new KMime::Content;
part->setContent( d->part->data() );
part->parse();
d->subjobContents << part;
process();
return;
}
// Set up a subjob to generate the attachment content.
SinglepartJob *sjob = new SinglepartJob( this );
sjob->setData( d->part->data() );
// Figure out a charset to encode parts of the headers with.
const QString dataToEncode = d->part->name() + d->part->description() + d->part->fileName();
const QByteArray charset = MessageComposer::Util::selectCharset( globalPart()->charsets( true ), dataToEncode );
// Set up the headers.
// rfc822 forwarded messages have 7bit CTE, the message itself will have
// its own CTE for the content
if( d->part->mimeType() == "message/rfc822" )
sjob->contentTransferEncoding()->setEncoding( KMime::Headers::CE7Bit );
else
sjob->contentTransferEncoding()->setEncoding( d->part->encoding() );
sjob->contentType()->setMimeType( d->part->mimeType() ); // setMimeType() clears all other params.
sjob->contentType()->setName( d->part->name(), charset );
if( sjob->contentType()->isText() ) {
// If it is a text file, detect its charset.
//sjob->contentType()->setCharset( d->detectCharset( d->part->data() ) );
// From my few tests, this is *very* unreliable.
// Therefore, if we do not know which charset to use, just use UTF-8.
// (cberzan)
QByteArray textCharset = d->part->charset();
if( textCharset.isEmpty() ) {
kWarning() << "No charset specified. Using UTF-8.";
textCharset = "utf-8";
}
sjob->contentType()->setCharset( textCharset );
}
sjob->contentDescription()->fromUnicodeString( d->part->description(), charset );
sjob->contentDisposition()->setFilename( d->part->fileName() );
sjob->contentDisposition()->setRFC2047Charset( charset );
if( d->part->isInline() ) {
sjob->contentDisposition()->setDisposition( KMime::Headers::CDinline );
} else {
sjob->contentDisposition()->setDisposition( KMime::Headers::CDattachment );
}
ContentJobBase::doStart();
}
void AttachmentJob::process()
{
Q_D( AttachmentJob );
// The content has been created by our subjob.
Q_ASSERT( d->subjobContents.count() == 1 );
d->resultContent = d->subjobContents.first();
emitResult();
}