[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: vCard3.0 and vCal2.0




I m not able to find the diff between vCal 1.0 and
vCal 2.0?

Plz put some light on this query too.
Rgds,
jenny
--- "Fish, Christopher" <cfish@xxxxxxxxxxxx> wrote:
> 
> Were you able to find out the difference between
> vCal 1.0 and cCal 2.0?
> 
> Are these compatible or competing standards with
> icalendar?
> 
> -----Original Message-----
> From: Jenny Christy [mailto:jenny_christy@xxxxxxxxx]
> 
> Sent: Friday, August 16, 2002 9:53 AM
> To: Chris Page; Priyantha
> Cc: Jenny Christy; imc-vcalendar@xxxxxxx;
> imc-vcard@xxxxxxx
> Subject: Re: vCard3.0 and vCal2.0
> 
> 
> 
> Thx Chris and Priyantha,
> Thx for ur suggestion and help.
> 
> One question is still there.
> what is difference bet vCal 1.0 and vCal 2.0???
> 
> Rgds,
> Jenny
> --- Chris Page <page@xxxxxxxx> wrote:
> > 
> > On Friday, August 16, 2002, at 02:12  AM,
> Priyantha
> > wrote:
> > 
> > > The CHARSET tag is very usefull in Multilanguage
> > capable
> > > developments...
> > 
> > But it has been eliminated in vCard 3, which is
> > really meant for
> > embedding in MIME, where the MIME Content header
> > provides the 
> > character encoding. Unfortunately, the standard
> > doesn't define any 
> > particular file format. If you just put a vCard
> into
> > a file and 
> > give it a "vcf" extension, there's no way to know
> > the encoding for 
> > certain.
> > 
> > The best you can hope for is to use a heuristic to
> > guess. Most
> > existing vCards were written by a Windows program
> > that uses the 
> > default Windows encoding, and a lot of readers
> > expect this, so 
> > unfortunately a lot of the vCard writers out there
> > are oblivious to 
> > this fact (even with vCard 2, they often omitted
> the
> > CHARSET tag). 
> > I recommend that everyone begin writing vCard
> files
> > using Unicode 
> > UTF-16. It is then fairly safe to assume that if
> you
> > see a byte 
> > order mark, or the VCARD header with zeroes every
> > other byte, then 
> > it's Unicode.
> > 
> > The standard really needs to be extended with a
> > definition for one
> > or more file formats, probably with new file
> > extensions (and file 
> > types for HFS volumes) to eliminate conflicts with
> > existing files.
> > 
> > --
> > Chris Page - Mac OS Lead, Palm Desktop - Palm,
> Inc.
> > 
> >   The most likely way for the world to be
> destroyed,
> > most experts agree,
> >   is by accident. That's where we come in; we're
> > computer professionals.
> >   We cause accidents.                           
> --
> > Nathaniel Borenstein
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> HotJobs - Search Thousands of New Jobs
> http://www.hotjobs.com


__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com