On 5/2/06 12:33 AM, Joe Andrieu [EMAIL PROTECTED] wrote:
The idea of mapping between languages however is not as crazy or hard as
some of you think.
Joe, that may be, but figuring out and documenting mappings between natural
languages is a linguistics research topic far outside the focus of
Before honoring Tantek's suggestion to move this to the Bad Topics list, I
hope I can clarify some misunderstanding and admit a few mistakes on my
part.
Part of this exploration is well grounded in a current engineering problem
I'm engaged in. Despite attestations that what I'm talking about is a
On May 1, 2006, at 5:59 PM, Tantek Çelik wrote:
The problem with AppleScript is that it is actually not that
readable/writable (even in English *by* native English readers).
AppleScript has a superficial resemblance/reuse of English terms which
makes
it look a lot easier than it actually is
From: Tantek Çelik Sunday, April 30, 2006 6:56 PM
To: microformats-discuss
Subject: Re: [uf-discuss] Microformats vs XML
On 4/30/06 6:20 PM, Karl Dubost [EMAIL PROTECTED] wrote:
And your page has class names in English when you are using another
language. -1
[snip]
Thus with
Why not just specify or xml:lang attribute on the Microformat?
e.g.
a rel=reference href=http://www.microformats.org/wiki/hcard-profile;
xml:lang=fr
Carte de langue pour hCarte à hCard/a
class = profile xml:lang=fr
dl
dt id='nom-et-prenoms' ref='fn'nom-et-prenoms/dt
ddLe nom et
On May 1, 2006, at 3:33 AM, Joe Andrieu wrote:
All without any requirement of seeing or using English except the one
reference to hCard in the title of the profile.
And all the HTML. The problem is that we need a shared language in
order to communicate, and machines are bad at translation.
xml:lang is already used within each microformat. For those who don't
know, you can mix-and-match language attributes within the same
document. So it is possible to have something like:
div class=vcard xml:lang=en
span class=fnBrian Suda/span
org class=org xml:lang=frFoo Bar/org
/div
The
hmm, ok - i can see why the mix and match may not work in the case where you
override with a new xml:lang attribute in a child element :(
Option 2 then :)
Steven Livingstone
http://stevenR2.com
-- Original Message --
From: Steven Livingstone [EMAIL
On May 1, 2006, at 1:33 AM, Joe Andrieu wrote:
The current microformat model is certainly better than POX, but I
think it
still leaves something to be desired.
Certainly. Its not perfect, but it works.
This approach still requires that
everyone uses the Microformats Approved(r)
This may start to address it :
http://www.w3.org/TR/ltli/
Steven Livingstone
http://stevenR2.com
-- Original Message --
From: Ryan King [EMAIL PROTECTED]
Reply-To: Microformats Discuss microformats-discuss@microformats.org
Date: Mon, 1 May 2006
Steven,
Interesting document, but it appears to only address languages in *content*,
rather than in the markup itself. Though the document refers to Language
Tags, AFAIK, those are tags in the content (similar to rel-tag perhaps),
rather than angle-bracketed tags.
If I have misread the
Ryan,
This is an excellent description of the larger problem (that goes far
beyond, and is perhaps independent of microformats).
I'd say this is worthy of an FAQ entry, as I can see this question being
raised again (I believe Karl himself raised it some time ago before).
Thanks,
Tantek
On
Le 06-05-02 à 03:24, Ryan King a écrit :
Internationalization in protocols and formats is a big problem.
Much bigger than microformats. Maybe we'll be able to advance
things in microformats, even if only a little.
I'm curious– has anyone here had experience with Internationalizing
a data
On 5/1/06 3:27 PM, Karl Dubost [EMAIL PROTECTED] wrote:
Le 06-05-02 à 03:24, Ryan King a écrit :
Internationalization in protocols and formats is a big problem.
Much bigger than microformats. Maybe we'll be able to advance
things in microformats, even if only a little.
I'm curious has
And all the HTML. The problem is that we need a shared language in
order to communicate, and machines are bad at translation. At some
point before parsing, all multi-lingual class names would need to be
translated to a lingua franca that can be understood by all
machines. There is no good
Hi Tantek - it's still in very early stages, so it's exact scope may not yet be
fully defined, however, it does explicitly talk of data structures [1] which
for me is more about the definition than the content.
Steven Livingstone
http://stevenR2.com
[1]
16 matches
Mail list logo
