William A. Rowe, Jr. wrote:
At 02:35 PM 8/1/2004, Stas Bekman wrote:
John Rowe wrote:
Please define "canonicalize"
In the context of case-insensitive file systems, it's often the case
that a file is given the canonical name that it was created with
("MyFile") with all other capitalisations ("myfil
At 02:35 PM 8/1/2004, Stas Bekman wrote:
>John Rowe wrote:
>>>Please define "canonicalize"
>>
>>In the context of case-insensitive file systems, it's often the case
>>that a file is given the canonical name that it was created with
>>("MyFile") with all other capitalisations ("myfile", "myfilE") b
John Rowe wrote:
Please define "canonicalize"
If the same thing can be referred to by a number of different names and
the convention is that one is the "one true", or canonical, name and the
others are mere aliases then canonicalisation (or canonicalization for a
non-Brit) is the process of trans
> Please define "canonicalize"
If the same thing can be referred to by a number of different names and
the convention is that one is the "one true", or canonical, name and the
others are mere aliases then canonicalisation (or canonicalization for a
non-Brit) is the process of translating a name i
from httpd.h:
struct request_rec {
...
/* XXX: What does this mean? Please define "canonicalize" -aaron */
/** The true filename, we canonicalize r->filename if these don't
match */
char *canonical_filename;
I'm asking the same question. It looks like it's only different from
'filen