GNOME Bugzilla – Bug 64628
Konqueror XBEL bookmark importing/exporting
Last modified: 2004-12-22 21:47:04 UTC
I've already mentioned this on the galeon-devel list. I just thought it'd be better to make it 'official' here so that it wouldn't be lost :) Like Galeon, Konqueror uses an XBEL format for bookmarks. Since I use multiple browsers, I store my bookmarks in Konqueror and then use Keditbookmarks to export them to Netscape format for Netscape, Mozilla and Opera. For Galeon, I like to use the XBEL import filter to directly import Konqueror's bookmarks. This works well, but unfortunately this doesn't import the bookmark favicons as well. This may sound trivial, but I like to use my own icons to easy and quickly navigate through my bookmarks. Overall, I would like to see better Galeon compatibility with Konqueror and Nautilus, in the spirit of GNOME consistency and GNOME/KDE interoperability. It would be great if all three could have a common bookmark file (Galeon and Konq already use XBEL; I don't know about Nautilus), which can be accessed by all three browsers simultaneously. A change to the file by one browser would be quickly recognised and implemented by the others.
Ric, what about to use XBEL format in 1.2 ?
Yes, that was the original plan ;) I left it because I didn't see too much interest about it. The XBEL import/export code is nearly enough: I have to implement alias saving/loading, fix this bug and I need to install Konqueror and test that we follow the format well.Maybe I also need to do some changes to the bookmarks code to keep arbitrary XML data if we want to be truly compliant with the spec. I'm a bit busy atm, I'll see if I can start with this this weekend...
using XBEL would not help in any way for the favicon handling the XBEL format does not have any provisions for the site provided bookmark icon in its standard dtd , you can only add it as a cutsom attribut so anything implemented would be legacy until the XBEL format is fixed for that , there is no clean way to do this this has been the case few months ago, i am not aware of any change in this regard but i maybe wrong
> > the XBEL format does not have any provisions for the site provided bookmark icon in its standard dtd , you can only add it as a cutsom attribut so anything implemented would be legacy < < Actually, that's what I meant - custom icons. Sorry, I should've been a bit clearer. For example, In my bookmarks I have a "GNU/Linux" folder. I have manually assigned a little Tux icon to it, so that in Konq it shows up as the icon with the name of the folder next to it. In Galeon, you can either see the name of the folder, or a picture, not both (unless the picture is a favicon from a site). One thing I noticed about Konq's bookmarks.xml file is the omission of the full path for bookmark/folder icons, unless the icon is neither a favicon (from a web site) nor a built-in KDE icon. The Tux icon (which came with KDE) mentioned above is simply referred to as "tux" in the bookmark file - the full path of the file is not specified. The default icon used for bookmarks in Konqueror is simply referred to as "www" in bookmarks.xml. Built-in KDE icons are referred to only by name, without a full path or extension. Favicons are in the format "favicons/www.smh.com.au" (for example).
yaneti: using XBEL will not help with the icons/favicons but it will not make it harder... am I wrong? We can store things like the icon, create toolbar attribute, etc as custom metadata. Our current XBEL exporter already does this. However: do we want to use XBEL as our default bookmark format? Please, let me know your opinions, I'm not sure. Using XBEL we only get enahnced interoperability with Konqueror. This is a big win, IMHO. But we achieve this enhancing our bookmarks exporter/importer a bit too.
sure, personally i think we should have switched some time ago, for a long time i thought we had, but i guess i was wrong
oops forgot to say all i hade to say ric, you may remember i wanted to use the icon attribute (in the still forthcomming XBEL 1.1 specification) for the remote favicon location. i still think this would be the only beneficial use of this attribute because of all the cross platform/implementation issues what do you think, should we do this?
Yes, I think we should. What does kde use that attribute for? We should try to be compatible with it, as far as posible. BTW: I need xbel files produced with konqueror to test. I don't feel like compiling all the kde and qt libs just for testing this (and I can't find rh6 rpms).
erm since favicons are completely independent from bookmarks now i dont see why we'd want this. WONTFIX for now, please reopen if you still (after my favicon keyfile stuff) feel it's appropiate..