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

List:       kde-i18n
Subject:    Re: Fwd: kfm not resolving URI correctly
From:       Dawit Alemayehu <adawit () earthlink ! net>
Date:       1999-03-21 23:08:40
[Download RAW message or body]

Hello,

On Sun, 21 Mar 1999, Torben Weis wrote:
[snipped]
>> The format stated by Mr. Smith is indeed valid.  If you look at RFC 1738,  the
>> scheme specific part of any URL ( BNF expression ) is
>> 
>>  //<user>:<password>@<host>:<port>/<url-path>
>> 
>> where the scheme ( ftp, http, file etc..) and that particular scheme's parts
>> are separated by : 
>> 
>> <scheme>:<scheme-specific-part>
>> 
>> So it is a valid URL.  If you would like this can be fixed wihout you hacking
>> KURL.  However, this fix in of itself is a hack.  I have been working on
>> adding short URL support to kfm and minicli and this can be solved there if you
>> wish since it is rarely used ( this is the first time I have heard anyone
>> mention this problem !! ).  In fact, unless there is a plan to to change KURL in
>> the old kfm to KURL2 then I think it wiil have to be fixed here.  It is just a
>> matter of adding another if statement check under slotURLEntered () in kfm and
>> the same check in execute() under minicli.C.

BTW, as David pointed out clearly, my idea here will not fix the problem for
LINKS on web pages, just for user enteries.  I stand corrected.  This will
require the changes you are planning for KURL2. 


>I wrote a state machine parser for URLs that will soon come in the KURL
>of the HEAD branch. So if we want // stuff there then I have to put it
>in there.

So it will not be in KDE_1_1_BRANCH ?  Does this mean the fix will be for the
for KDE 2.0 and not KDE 1.1.1 ?  Just wondering... 

>I really should read this RFC more often but it is sooooo boring
>sometimes.

No argument here.  If you want to get to the meat of it, just skip or
skim the first two sections of the spec and read sections 3 and 4 of RFC 1808. 
It only will take few minutes of your time, unless of course you read and
comprehend slow like me.  Here is one of the better URL's for RFC
documents:http://www.faqs.org/rfcs/  and you can find RFC 1808
here:http://www.faqs.org/rfcs/rfc1808.html.

Later,
Dawit A.

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