Prev: Only load actually visible items?
Next: Trouble with initialization vector (IV) for AES
From: Harlan Messinger on 22 Jun 2010 07:12
Zach wrote:
> "Harlan Messinger" <h.usenetremoverthis(a)gavelcade.com> wrote in message
> news:88atadFebdU2(a)mid.individual.net...
> < snipped>
>> As I said, you need to know what the file's encoding is rather than
>> randomly trying things.
>
> Sorry, you didn't read my previous post? When you load a file to Word,
> Word does the sorting out bit, subsequently you can select the encoding
> with which to file the page in Word to a new file. That only takes a
> minute, and isn't randomly trying things.

It's not that I didn't see it. It's that I didn't realize that you would
consider the hack to be a satisfactory solution, or that as long as you
have something that "works", you are averse to acquiring a greater
understanding of the work you are doing.
From: Zach on 22 Jun 2010 10:12


"Harlan Messinger" <h.usenetremoverthis(a)gavelcade.com> wrote in message
news:88bk56FfqmU1(a)mid.individual.net...
> Zach wrote:
>> "Harlan Messinger" <h.usenetremoverthis(a)gavelcade.com> wrote in message
>> news:88atadFebdU2(a)mid.individual.net...
>> < snipped>
>>> As I said, you need to know what the file's encoding is rather than
>>> randomly trying things.
>>
>> Sorry, you didn't read my previous post? When you load a file to Word,
>> Word does the sorting out bit, subsequently you can select the encoding
>> with which to file the page in Word to a new file. That only takes a
>> minute, and isn't randomly trying things.
>
> It's not that I didn't see it. It's that I didn't realize that you would
> consider the hack to be a satisfactory solution, or that as long as you
> have something that "works", you are averse to acquiring a greater
> understanding of the work you are doing.

If you had asked me whether I attempted to acquire greater
understanding about the issue, I would have have given you
an answer. What you did, assuming how I behaved, whilst not
knowing so, is called "projecting", don't do it, bad habit.



From: Harlan Messinger on 22 Jun 2010 11:03
Zach wrote:
>
>
> "Harlan Messinger" <h.usenetremoverthis(a)gavelcade.com> wrote in message
> news:88bk56FfqmU1(a)mid.individual.net...
>> Zach wrote:
>>> "Harlan Messinger" <h.usenetremoverthis(a)gavelcade.com> wrote in
>>> message news:88atadFebdU2(a)mid.individual.net...
>>> < snipped>
>>>> As I said, you need to know what the file's encoding is rather than
>>>> randomly trying things.
>>>
>>> Sorry, you didn't read my previous post? When you load a file to
>>> Word, Word does the sorting out bit, subsequently you can select the
>>> encoding with which to file the page in Word to a new file. That only
>>> takes a minute, and isn't randomly trying things.
>>
>> It's not that I didn't see it. It's that I didn't realize that you
>> would consider the hack to be a satisfactory solution, or that as long
>> as you have something that "works", you are averse to acquiring a
>> greater understanding of the work you are doing.
>
> If you had asked me whether I attempted to acquire greater
> understanding about the issue, I would have have given you
> an answer. What you did, assuming how I behaved, whilst not
> knowing so, is called "projecting", don't do it, bad habit.

Wow--you're OUTSPOKEN about your lack of interest in genuinely
understanding what you are doing. Be sure to put that on your CV so
prospective employers will know what to expect.
From: Arne Vajhøj on 22 Jun 2010 21:53
On 22-06-2010 03:54, Zach wrote:
> "Harlan Messinger" <h.usenetremoverthis(a)gavelcade.com> wrote in message
> news:88atadFebdU2(a)mid.individual.net...
> < snipped>
>> As I said, you need to know what the file's encoding is rather than
>> randomly trying things.
>
> Sorry, you didn't read my previous post? When you load a file to Word,
> Word does the sorting out bit, subsequently you can select the encoding
> with which to file the page in Word to a new file. That only takes a
> minute, and isn't randomly trying things.

Given that the same N bytes can more than one valid content
by assuming different encodings, then it is impossible
to detect encoding with 100% certainty.

If you need certainty, then you need to know the encoding.

If you can live with a guess then there are certain ways
of doing that.

Programmers tend to like to know.

Word users may be perfectly happy with 99% accuracy.

Arne

From: Zach on 23 Jun 2010 04:30
"Arne Vajh�j" <arne(a)vajhoej.dk> wrote in message
news:4c216914$0$277$14726298(a)news.sunsite.dk...
> On 22-06-2010 03:54, Zach wrote:
>> "Harlan Messinger" <h.usenetremoverthis(a)gavelcade.com> wrote in message
>> news:88atadFebdU2(a)mid.individual.net...
>> < snipped>
>>> As I said, you need to know what the file's encoding is rather than
>>> randomly trying things.
>>
>> Sorry, you didn't read my previous post? When you load a file to Word,
>> Word does the sorting out bit, subsequently you can select the encoding
>> with which to file the page in Word to a new file. That only takes a
>> minute, and isn't randomly trying things.
>
> Given that the same N bytes can more than one valid content
> by assuming different encodings, then it is impossible
> to detect encoding with 100% certainty.
>
> If you need certainty, then you need to know the encoding.
>
> If you can live with a guess then there are certain ways
> of doing that.
>
> Programmers tend to like to know.
>
> Word users may be perfectly happy with 99% accuracy.
>
> Arne
>
Thank you for your concern. The casus is described in the
opening post, q.v. During the weekend I needed to get the
job done and went for a quick fix. After the weekend with
everyone back at work I was abe to contact the company
from which I had purchased the addresses and receive
total certainty about te encoding.

> Given that the same N bytes can more than one valid content
> by assuming different encodings, then it is impossible
> to detect encoding with 100% certainty.

Right. That was the problem.

Regards,
Zach.


First  |  Prev  | 
Pages: 1 2
Prev: Only load actually visible items?
Next: Trouble with initialization vector (IV) for AES