Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: GS <gs@v.invalid>
Newsgroups: alt.comp.os.windows-10,alt.comp.freeware,comp.text.xml
Subject: Re: What's a decent XML editor specifically for editing/viewing SMS messages copied from Android to Windows?
Date: Wed, 22 Apr 2020 21:35:39 -0400
Organization: A noiseless patient Spider
Lines: 44
Message-ID: <r7qrdg$dkg$1@dont-email.me>
References: <r7nasv$jm2$1@news.mixmin.net> <r7nbr7$87t$1@dont-email.me> <r7nd1a$p0o$1@news.mixmin.net> <r7nm0u$foc$1@dont-email.me> <r7o98k$pvk$1@news.mixmin.net> <r7ocpj$a0j$1@dont-email.me> <r7oi1o$d5e$1@news.mixmin.net> <r7oma5$hem$1@dont-email.me> <r7pd1k$opl$1@dont-email.me> <r7q8vl$1l7$1@dont-email.me> <r7qa7g$9rq$1@dont-email.me> <r7qj6e$3dt$1@dont-email.me> <r7qmqm$m43$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 23 Apr 2020 01:35:44 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="b30551fc867b7cc0120f8f2b50d6df23"; logging-data="13968"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18pu7LAWER4AOvT7CLIS853"
Cancel-Lock: sha1:hA2jP3+QRbn3sXTM31hPQamjkAo=
X-Antivirus-Status: Clean
X-Newsreader: MesNews/1.08.06.00-gb
X-Antivirus: Avast (VPS 200421-2, 04/21/2020), Outbound message
X-Face: G"ln~:.wBqHZznO'(lJjjprxGYAjIF7#^u)lx,@"H'F#uXm%j`T6kxat5rq092aW;K*#<!y <6K)wt3HjA)V"XV`W3}Qts*D['Jm:qqpgttEl^wk@9{HJglN-Q'.91Af~ySM>m4jZ(2aW$34N&B&E@ j~tjGV-aC18j1y>zi.\[ZGXsd
X-ICQ: 543516788
Xref: csiph.com alt.comp.os.windows-10:112183 alt.comp.freeware:326277 comp.text.xml:939

> "GS" <gs@v.invalid> wrote
>
>>  Garry
>>  R2Fycnk=
>>  52324679636E6B3D
>> 
>> ..which all are plain text strings. Otherwise the B64 string arrives as
>> "r2fycnk="! The reason for the need is because the B64 string is the  result 
>> of encrypting a license profile and outputting the result (byte data) in B64 
>>  so it behaves like a string when being processed as a plain text file.
>> 
>   I see what you mean. The problem there is that you're
> sending it in the plain text section. If you want it treated
> as Base64 it needs to be demarcated.  Though it still shouldn't
> lcase. Maybe you're using spellcheck? Your method is probably
> best for a short string. If you want to actually send base64 you
> need to use multi-part format and do it like so:
>
> --UNIQUE_BOUNDARY_STRING_HERE
> Content-Type: image/jpeg;
>  name="pic.jpg"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;
>  filename="pic.jpg"
>
>    Then you put the base64, followed by another
> boundary marker. Otherwise there's no way for
> the client to know you intend it to be interpreted
> as base64.
>
>  You can see samples if you look at an email with
> attachments. 

Actually, it goes as body text in a new msg via the user's default mail app 
using ShellExecute's mailto: arg. This puts the 'Send' action as user choice 
because I refuse to send anything not user authorized.

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion