Inoffizielles deutsches Xbase-Forum

Subject: =?UTF-8?B?QmVuYWNocmljaHRpZ3VuZyDDvGJlciBuZXVlIEFudHdvcnQg4oCUIOKAnk5ldWUg?= =?UTF-8?B?Rm9yZW5zb2Z0d2FyZeKAnA==?=
From: <post@xbaseforum.de>

Und was Dein Subject anbelangt: Das musst Du umwandeln mit UTF8->ANSI.
Entsprechende Beispiele dazu findest Du in der Alaska-Newsgroup.

#INCLUDE "DLL.CH"

PROCEDURE MAIN
LOCAL cUTF8 := "=?UTF-8?B?QmVuYWNocmljaHRpZ3VuZyDDvGJlciBuZXVlIEFudHdvcnQg4oCUIOKAnk5ldWUg?= =?UTF-8?B?Rm9yZW5zb2Z0d2FyZeKAnA==?="

LOCAL cMBtoW
LOCAL cWToMB
LOCAL nWideChars
LOCAL cPlainUnicode
LOCAL nCodepage
LOCAL nBytes
LOCAL cAnsi

/*
Guenter Beyes
Freitag, 10. M㱺 2006 12:10
public.xbase++.generic
Re: UTF-8 conversion
*/

// UTF-8 code-page identifier.
#DEFINE CP_UTF8 65001
/*

hier fängt es schon an ... wie/was/wo identifier
ich möchte UTF-8 -> deutsch

*/

cMBtoW := DllPrepareCall( "kernel32.dll", DLL_STDCALL, "MultiByteToWideChar" )

cWToMB := DllPrepareCall( "kernel32.dll", DLL_STDCALL, "WideCharToMultiByte" )

// First convert UTF-8 to plain Unicode:

// Add string terminator just to be safe.
cUTF8 += chr(0)

// Get number of resulting wide characters.
nWideChars := DllExecuteCall( cMBtoW, CP_UTF8, 0, cUTF8, -1, 0, 0 )

// Provide a sufficient buffer.
cPlainUnicode := space( 2*(nWideChars + 1) )

// Do the conversion.
nWideChars := DllExecuteCall( cMBtoW, CP_UTF8, 0, cUTF8, -1,;
                              @cPlainUnicode, nWideChars+1 )

// Strip Unicode string terminator.
// (NOT, because it's needed in the  next step. )
// cPlainUnicode := left( cPlainUnicode, 2*(nWideChars - 1) )

// Now convert plain Unicode to ANSI,
// using the current ANSI code page:

// Get current ANSI code-page identifier.

nCodepage := DllCall( "kernel32.dll", DLL_STDCALL, "GetACP" )

// Get number of resulting bytes.
nBytes   := DllExecuteCall( cWToMB, nCodepage, 0, cPlainUnicode, -1,;
                            0, 0, 0, 0 )

// Provide a sufficient buffer.
cAnsi   := space( nBytes + 1 )

// Do the conversion.
nBytes   := DllExecuteCall( cWToMB, nCodePage, 0, cPlainUnicode, -1,;
                            @cAnsi, nBytes+1, 0, 0 )

// Strip ANSI string terminator.
cAnsi := left( cAnsi, nBytes - 1 )

// Finito.

? cAnsi     // -> cUTF8

RETURN

UTF-8 (Abk. für 8-bit Unicode Transformation Format) ist die am weitesten verbreitete Kodierung für Unicode-Zeichen.

MarshallSoft SMTP/POP3/IMAP XBase++ email component library (SEE4XB) uses a simple API to send and receive mail, including HTML, MIME Base64 and quoted-printable encoded attachments, from within an application. Supports all versions of Alaska XBase++. Knowledge of Winsock and TCP/IP is not needed. Features of SEE4XB include: Send email with inline HTML, GIF, TIF, JPG, BMP and Rich Text attachments. Supports ISO-8859 and UTF-8 character coding.

brandelh hat geschrieben:

MIME Base64 and quoted-printable encoded attachments

Code := XseeIntegerParam(0, SEE_QUOTED_PRINTABLE, QUOTED_HTML)

Jimmy,

> >while german Xbase++ Forum have installed new "phpBB" Ver. 3
> >the "Subject" with SEE32 have change.

> >=?UTF-8?B?WGJhc2UtRm9ydW06IE5ldWUgU29mdHdhcmUsIEZvcmVudHJlZmZlbiBpbSBGcsO8?=
> >=?UTF-8?B?aGphaHIgMjAwOQ==?=

This means that the Subject line was Base64 encoded, because of the "ü" in
the text was represented as an UTF-8 character. To convert it back, use a
routine to "decode" Base64 encoded text, like "FromBase64()" from ASINet
or "XbBase64Decode()" from Xb2Net.

First, you need to take both of the strings between the "?B?" and the "?=",
and combine them, then decode that string, and because the "ü" is UTF-8
encoded, you need to use OT4Xb's "cUtf8ToAnsi()" function to convert the
resulting string to ANSI -- or use "cUtf8ToOEM()" for OEM.

If a subject line starts with "=?ISO-8859-1?" (or something similar)
instead of "=?UTF-8?", you won't need the cUtf8ToAnsi() function. The
character set description isn't case sensitive, so it could also be
"=?utf-8?" or "=?iso-8859-2?" etc. If a subject line continues with
"?Q?" instead of "?B?", you need to use "FromQP()" from ASINet (or a
homegrown function) instead of FromBase64()"/"XbBase64Decode()".

Because that particular Subject line is longer than 75 characters, it was
encoded in two parts that you need to combine. Longer text might even be
split into three or four lines. The basic format for "encoded words is
this: "=?" + Character-Set + "?" + Encoding + "?" + Encoded-Text + "?="
For more details, see: RFC 2047.

-- Andreas

--- ---
Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net
415 Gute Street or: Andreas@DDPSoftware.com
Owosso, MI 48867-4410 or: Andreas@Aerospace-History.net
Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net
--- ---