[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: [KOffice 1.2] app/vnd.kde.{kword,kspread,kpresenter,kformula,kchart,kivio,kontour,karbon}
From:       Nicolas Goutte <nicog () snafu ! de>
Date:       2002-05-27 13:35:35
[Download RAW message or body]

Well, for inside the document (i.e. in maindoc.xml) it is not much a problem I 
think.

Now that we have a namespace declaration, we can test the attribute xmlns 
instead of testing mime. The namespace is suppose to stay the same quite 
long. Therefore we can leave the attribute mime to its old value and 
compatibility with KOffice 1.1 will remain. In future versions, the mime 
attribute could then be removed because of its redundancy.

As for the external mime type, yes, this is a problem, as we would want to 
make it work with KDE 3.0. However, if it is the same scenario as last year, 
we will end up with a KOffice 1.2 that will only work with KDE 3.1.

Can we not somehow make KOffice 1.2 accept the two versions of the mime type?

Have a nice day/evening/night!

On Monday 27 May 2002 00:54, Marc Mutz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> David Faure wrote:
> > On Sunday 26 May 2002 21:21, Marc Mutz wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Hi!
> >>
> >> Please find attached the registrations for the KOffice 1.2 mime
>
> types.
>
> >> Their texts are equal except for the names of applications and the
>
> file
>
> >> extensions, so you only need to read one.
> >
> > Hmm, seems you're assuming we guaranteed this change would be made for
> > 1.2 (or maybe are you volunteering for doing the change?)
>
> No and no. But I noted in the draft version that I had made the change
> to the magic file in anticipation of you (plural) changing that. You
> didn't compain ;-) Time enough there was...
>
> > It's quite a tricky issue, since the mimetypes are in kdelibs, the XML
> > contain a mimetype name, for the main doc and for embedded objects,
>
> etc.
>
> > etc. This will also be yet another cause of incompatibilities with
>
> 1.1, so
>
> > we'll need to take care of it when "saving as 1.1" and in Werner's
>
> script.
>
> > It needs to be well thought of, and is some work.
>
> Well, if you don't do it for 1.2, you'll have the same problem for
> 1.3/2.0 and then you have to care for 1.1 _and_ the mixture that will
> then be 1.2...
>
> Since you change from tgz to zip for 1.2, this seems to be the right
> time to get this right, too.
>
> But tell me if you don't want to use vnd.kde.kapp inside the document
> itself. I don't understand how using x-kapp inside and vnd.kde.kapp
> outside the doc would be less work to get right, but then I'm only the
> editor of the reg request and write what you want me to write... :-)
>
> Marc
>
> - --
> Marc Mutz <mutz@kde.org>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE88WeU3oWD+L2/6DgRAob7AJ9WmnghY2yTwILg0lXymbHa194+1wCgkmHB
> YHVOVwMdwurZDKnsPsFNNQs=
> =t55Y
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@mail.kde.org
> http://mail.kde.org/mailman/listinfo/koffice-devel


_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]