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

List:       kde-i18n
Subject:    Re: Fwd: kfm not resolving URI correctly
From:       Torben Weis <weis () troll ! no>
Date:       1999-03-21 21:22:41
[Download RAW message or body]

Hi,

On Sun, 21 Mar 1999, Dawit Alemayehu wrote:

> On Sun, 21 Mar 1999, David Faure wrote:
> > This sounds strange to me.
> > Is "//www.kde.org/" a good URL ?
> 
> It is a valid URL.  However, I much like you have never heard of anyone who
> uses it.  I can easily fix this in slotURLEntered() and execute() in kfm &
> minicli respectively for the KDE 1.1.1 release, but for konqueror I think  it
> should be dealt with in KURL2 as Torben suggested unless there is plan to
> replace the exisitng KURL to KURL2 for KDE 1.1.1 also.

KURL2 is very different so I see no chance to replace KURL in KDE 1.1.1
since many apps are designed to work with the KURL shortcomings :-(
So maybe you could make something compile but wether it really works
reliable is a difficult question.

Bye
Torben

> 
> Cheers,
> Dawit A.
> 
> > ----- Forwarded message from Hume Smith <hclsmith@glinx.com> -----
> > 
> > Date: 	Sat, 20 Mar 1999 22:48:28 -0400 (AST)
> > subject: kfm not resolving URI correctly
> > to: faure@kde.org
> > from: hclsmith@glinx.com (Hume Smith)
> > 
> > i had reported this back with kde-1.0, but i guess it got missed.
> > 
> > my kfm (calls itself 1.167) still mishandles URIs that lack the scheme (eg \
> > "//www.kde.org/").  i use these frequently on my site ( \
> > <URL:http://www.glinx.com/~hclsmith/> ).  This form is permitted by several RFCs \
> > (eg 1808 section 4 and 2396 section 5.2; also either 1630 or 1738 if memory \
> > serves) and is recognised by most browsers (Nessie, Messie, and Opera). 
> > 
> > 
> > 
> > --
> > <URL:http://www.glinx.com/~hclsmith/>
> > 
> > 
> > ----- End forwarded message -----
> > 
> > -- 
> > David FAURE
> > david.faure@insa-lyon.fr, faure@kde.org
> > http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
> > KDE, Making The Future of Computing Available Today
> 


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