On Mon, 07 Jul 2014 19:29:11 -0400
Daniel Staal wrote:
> Just to start the discussion: I'd say default to UTF-8 if not
> otherwise specified and can't be worked out. (How hard to work on
> 'working it out' is a question, of course.) It's the growing
> standard, as far as I can tell.
+1. UTF-8
--As of July 7, 2014 5:20:01 PM -0400, Kevin A. McGrail is alleged to have
said:
On 7/7/2014 5:09 PM, Philip Prindeville wrote:
On Jul 7, 2014, at 7:15 AM, Kevin A. McGrail wrote:
On 7/7/2014 2:28 AM, John Wilcock wrote:
Le 05/07/2014 19:08, Philip Prindeville a écrit :
As for encoding a
Replying to myself...
> full MSDOGEXE /\n\nTV[opqr]/
Seems to work. :)
Regards,
David.
So, the inevitable had to happen. The cryptolocker folks are getting
around extension blocking with this:
==
PLEASE NOTE!
In case you are not able to open the attached document, please save it
to your computer and manually a
On 7/7/2014 5:09 PM, Philip Prindeville wrote:
On Jul 7, 2014, at 7:15 AM, Kevin A. McGrail wrote:
On 7/7/2014 2:28 AM, John Wilcock wrote:
Le 05/07/2014 19:08, Philip Prindeville a écrit :
As for encoding a cyrillic small a: there are many ways to do this.
iso-8859-4, utf-8, jp2212, gb2312,
On Jul 7, 2014, at 7:15 AM, Kevin A. McGrail wrote:
> On 7/7/2014 2:28 AM, John Wilcock wrote:
>> Le 05/07/2014 19:08, Philip Prindeville a écrit :
>>> As for encoding a cyrillic small a: there are many ways to do this.
>>> iso-8859-4, utf-8, jp2212, gb2312, win1252, etc. I don’t think this
>>>
On 7/7/2014 2:28 AM, John Wilcock wrote:
Le 05/07/2014 19:08, Philip Prindeville a écrit :
As for encoding a cyrillic small a: there are many ways to do this.
iso-8859-4, utf-8, jp2212, gb2312, win1252, etc. I don’t think this
would be very efficient—there are just too many charsets possible.
