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 19:15:21 -0400
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <r7qj6e$3dt$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>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 22 Apr 2020 23:15:26 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="b30551fc867b7cc0120f8f2b50d6df23"; logging-data="3517"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+82VI5UY6mVm6r7NljzEYX"
Cancel-Lock: sha1:eMs0cF1lz7pZh0UhdAQFcCuEt+Y=
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:112178 alt.comp.freeware:326275 comp.text.xml:937

> "GS" <gs@v.invalid> wrote
>
>>>   But the format does make order extensible. So there's no
>>> reason it can't hold Base64. HTML and MIME both store it
>>> just fine. Personally I've never seen a text message package
>>> so I have no idea whether it *does* hold Base64.
>> 
>> Base64 IS plain text. The problem with using it in email is, depending on  
>> how the body text is converted, character case may be lost where all UCase  
>> becomes LCase. Best to convert B64 to Hex for email use, IMO!
>> 
>     I meant I've never seen the actual content of a text
> message. SMS. Email and HTML and Base64 are plain
> text, yes. I only meant that their formatting allows Base64
> data to be stored easily. Multipart MIME format and "data
> uri" formatting in HTML make it simple with no risk of
> mixup. It can also be simple in XML:
> <Data64> ....any length text here...</Data64>
>
>   In other words, they all have protocols for storing Base64
> data that can be identified as Base64.
>
>    I don't know what you mean about converting Base64
> to hex. Binary? The whole point of Base64 is that HTML
> and email can't have binary data. If the Base64
> gets ucased then there's something wrong with the
> email structure. 

I've had instances where writing B64 email body text with VB displays correctly 
in the new msg window, but arrives w/all UCase converted to LCase. My solution 
to preserve the original B64 is to convert each character to its Hex equivalent 
as follows:

  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.

-- 
Garry

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