>> It's great that you pointed out this real-life problem you are having,
>> because it's just one of those things that "<alt>" could fix.

I'm a bit worried by your tone, Risto, because it comes across as if you're
trying to "disprove" me. I was making an observation that definitely does agree
with that part of your premise (whether or not it agrees with your solution).

>> Secondly, HTTP Content Negotiation, as well as the draft's mechanism,
>> only works for external documents. Surely you don't mean that the author
>> should prepare a number of different versions of a large document, just
>> because it happens to contain a couple of phrases in a couple of
>> different languages?

Well, I am suggesting caution against a "Christmas tree" attitude, i.e.,
cautioning against hanging every possible ornament on XHTML. A markup language
can't be all things to all people.

I suspect by the time XHTML2 is matured, non-Latin fonts will be much more
commonplace. (But does device independence preclude us from assuming this?)

I would be interested in hearing the perspective of someone with more
knowledge about internationalization and device independence.

>> I'm interested to see how you solve this with "a scripting solution".

Unfortunately, I don't have a programming background. I'm a "high-level" guy.

>> It's also interesting to see, that you don't think multilanguage
>> documents are common...

I never said that, nor do I agree with it.

- Ed.