This puzzles me ...
It seems to be generally accepted in the GT forums that 'non-english' characters, eg: Éßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýÿ, cannot be used in the names of directories and files.
Nevertheless, I have used these characters in a testbed directory using flatfile Links. Provided they are url-encoded, there is no detectable problem building under FreeBSD.
Also I notice that the Open Directory uses them -- check out http://dmoz.org/...f5es_de_Professores/
Should I not be using them, even if they seem to work in practice.
Is there something I don't know about?
Is this OS-dependent (eg: OK under Unix, not OK under Windows)?
By the way, the urlencode sub is
# --------------------------------------------------------
# Escapes a string to make it suitable for printing as a URL.
#
my($toencode) = shift;
$toencode =~ s/([^a-zA-Z0-9_\-.])/uc sprintf("%%%02x",ord($1))/eg;
$toencode =~ s/\%2F/\//g;
return $toencode;
}
It seems to be generally accepted in the GT forums that 'non-english' characters, eg: Éßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýÿ, cannot be used in the names of directories and files.
Nevertheless, I have used these characters in a testbed directory using flatfile Links. Provided they are url-encoded, there is no detectable problem building under FreeBSD.
Also I notice that the Open Directory uses them -- check out http://dmoz.org/...f5es_de_Professores/
Should I not be using them, even if they seem to work in practice.
Is there something I don't know about?
Is this OS-dependent (eg: OK under Unix, not OK under Windows)?
By the way, the urlencode sub is
Code:
sub urlencode { # --------------------------------------------------------
# Escapes a string to make it suitable for printing as a URL.
#
my($toencode) = shift;
$toencode =~ s/([^a-zA-Z0-9_\-.])/uc sprintf("%%%02x",ord($1))/eg;
$toencode =~ s/\%2F/\//g;
return $toencode;
}