X-KDE-text=true vs X-KDE-IsAlso=text/plain

[Andras Mantia]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

 My only concerns is that X-KDE-Text is backported to 3.1, while X-KDE-IsAlso
is not, and we want Quanta to work on both 3.1 and 3.2. Removal of X-KDE-Text
now would cause some ifdef's in our code, but I have to investigate the
amount of work need to be done. And of course, those who are text files
(X-KDE-text=true) should all have X-KDE-IsAlso=text/plain otherwise we will
nothing and the text file detection won't work.
OK, I verified. We use the X-KDE-Text in two places, one is already compiled 
only on KDE 3.1 (the local backport of KMimeType::findFormatByFileContent), 
the other one is a simple check in case of non-local files, so using 
X-KDE-IsAlso is fine, if:
- - KMimeType::findFormatByFileContent starts to use it, but the result of the 
function is the same as before (this is anyway required due to the BC)
- - all mimetypes which had X-KDE-text=true will have X-KDE-IsAlso=text/plain

Andras

On Tuesday 18 November 2003 13:38, Waldo Bastian wrote:
> Hi Andras,
>
> I was thinking to get rid of X-KDE-text and just use the more generic
> X-KDE- IsAlso instead. Do you foresee any problems with that?
>
> We currently have the situation that some mimetypes have "X-KDE-text=true"
> set, but not X-KDE-IsAlso=text/plain. That seems a bit strange. (text/html
> for example)
>
> Cheers,
> Waldo

- --
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/ugjETQdfac6L/08RAtrPAKDMM0kgzNC5xr6Hx91z89FWChF2rgCghWJf
uM63YPH2PhxvKXsSczcy1M4=
=ACoN
-----END PGP SIGNATURE-----