Re: I'm sure glad I didn't buy a Mac Mini!

In article <-uednSADavGry0PanZ2dnUVZ_gOdnZ2d@xxxxxxxxxxx>,
"Hasta La Vista" <noemail@xxxxxxxxx> wrote:
"C Lund" <clund@xxxxxxxxxxxxxxxxxxx> wrote in message
news:clund-34950B.11365217032008@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
An example of "usually works, sorta" is when I send an email to
somebody using Outlook. If that email contains european
characters,
such as æ, ø, or å, there's a pretty good chance that Outlook
will
replace them with chinese characters. This is because of MS's
crappy
implementation of UTF-8. I think this might also be a problem
with
Word.
It might be an example if it actually were true.
It *is* true. Try googling the topic and you'll find others who
experience the same things. Hey, I'll even google one for you:
It's not true for me,
So what?
So what you said about me is not true. Why does that fail to make an
impact on you?
It's not any less true
What you claimed about me is untrue and will continue to be untrue no matter
what else you write. IOW, you've eliminated all possibility that you made a
mistake and are just an unrepentant liar.

Is that you, edwin? Sure seems that way.

And no, it is not untrue. No amount of squirming will make it untrue.

Or you ought to update your software.
Why should I? This is not a problem that affects maccies.
It's only a problem that affects people who use Outlook and who also get
email from you. I begin to see why filters were created! :-D

It's a problem for Windows users who try to deal with UTF-8 charsets.

Or
just take the easy solution.
I did; that's why I use a mac. B)
Just to make problems for Outlook? :-D

No, MS made those problems.

Or maybe you don't exchange much data with
continental europeans.
I don't, but it works for me nonetheless. On more than one system.
Then how do you know it works for you?
Because it works when I do use it.

Or so you say, edwin. But your word means little.

You didn't find a problem with Windows, you found a problem with
Outlook,
which is merely an application running on Windows.
I know you read G Graves post on the topic. This is more than Outlook.
No, it's just Outlook. George was trying to have an old version of Word
recognize formatting commands from a new version of Word.
Why would that make any difference?
The people who wrote the program couldn't look into the future to see how
the document formatting commands would change.

And yet the folks at Apple are able to write apps that can handle old
files.

The current version of Pages can
read documents written by ClarisWorks (which is an outdated,
discontinued app from the early 90s). Why can't new versions of Word
read docs made by old versions of Word?
It can. The problem was George trying to get an OLD VERSION of Word to
understand the output of a new version of Word.

However, the Outlook users who sometimes get scrambled characters in
emails from maccies are not using old versions of Outlook.

Now, one could discuss whether the problem lies with Windows or in all
MS software that runs on Windows (or maybe just some of it),
We already know that the problems you and George brought up are
application
problems, not Windows problems.
Let's call them MS problems instead.
No, let's not call them anything but what they are.

What they are are MS problems. MS simply isn't competent.

You seemed to have ignored that your reference gave you an easy way
around
your problem, namely to use ISO-8859-1 instead of UTF - 8.
You shouldn't have to use a workaround *at all*. On the mac, this kind
of stuff Just Works?. No workaround necessary.
No workaround is necessary if you switch to using ISO- 8859 -1 to begin
with, instead of looking for a way to convert from UTF - 8 afterwards.
So now you're saying that the maccie who sends the file has to adjust
his/her output so MS's faulty software can read it?
No, just choose a different character set, if your readers are having a
problem with your messages.

Why should I have to compensate for MS's sloppy programming? If my
readers don't have a competent email client, then maybe they should
get one that is.

The MS software I'm using has no problem with reading UTF-8.

Or so you say, edwin.

Besides, "using ISO" when the document you're looking at is UTF-8
involves stuff like this:
[program listing snipped]
This might look like an "easy way around" to somebody using Windows,
but to us maccies, this is an unacceptable kludge.
If I had the problem you're talking about, I would have used the easy
solution that you're ignoring, namely to send my documents out in ISO-
8859 -1 instead having the recipient convert it from UTF - 8 to ISO-
8859 -1.
But that still means having to work your way around MS's faulty
software that "usually works, sorta".
No it doesn't. I didn't have any problem reading your UTF -8 output.

In this instance.

It means YOU have a problem with YOUR messages, and YOU ought to change your
character set instead of trying to convince the people who get your emails
to change their computers.

Nope. It means you got lucky.

Keep digging that hole. ;)
You're the one holding the shovel, not me.

edwin, you were born with a shovel in your hand.

--
C Lund, folk.uio.no/clund/
.

Relevant Pages

  • Re: Im sure glad I didnt buy a Mac Mini!
    ... replace them with chinese characters. ... No. I'm not using Windows. ... It's only a problem that affects people who use Outlook and who also get ... recognize formatting commands from a new version of Word. ...
    (comp.sys.mac.advocacy)
  • Re: Strange Characters When Viewing Outlook Express messages
    ... Messages Received in Outlook Express Have Different Characters in the ... messages in the default encoding format regardless of the actual encoding ... changed something with whatever they use to produce the emails. ...
    (microsoft.public.windowsxp.general)
  • Re: Im sure glad I didnt buy a Mac Mini!
    ... somebody using Outlook. ... replace them with chinese characters. ... Explain how you having a problem sending UTF-8 to someone besides me makes ... It's a problem for Windows users who try to deal with UTF-8 charsets. ...
    (comp.sys.mac.advocacy)
  • Re: Outlook express special characters
    ... |> In windows "98" Outlook Express, If I want to type for example ... |> an accent as in my name Andre I hold the Alt key while typing ... for é the two characters are ' and e. ... | Ken Blake - Microsoft MVP Windows: ...
    (microsoft.public.windowsxp.general)
  • Re: OE6 failing to deleiver mail to one particular domain
    ... As for the loss of lead characters in my messages. ... "Jim Pickering" wrote in message ... > HTML-based e-mail messages that are sent from Outlook Express may be ... >> We will work to resolve this issue in future versions of the SPAMfighter ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)