Of course with real filenames some of these translations will produce the same results.
- (name,8 + '/' + extension),10
- (name + '/' + extension),10
- (name + '_' + extension),10
- (name,8 + '_' + extension),10
- (name,8 + '/' + extension,3),10
- (name + '/' + extension),10
- (name + '_' + extension),10
- (name,8 + '_' + extension,3),10
- name + '/' + extension,3
- name + '_' + extension,3
- name + '/' + extension
- name + '_' + extension
- extension + '.' + name (The dot being directory Separator)
- extension + '.' + name,10 (The dot being directory Separator)
- name + '.' + extension (The dot being directory Separator)
- name,10 + '.' + extension (The dot being directory Separator)
- name
.
).
/
) and the bit after the original dot.
(Using method 1)
/
and the bit after dot gives very_lon/html
To get round this problems in Webster looks in the driectory specified first. If the file is not their it looks in directories of the same name with the addition of a number between 2 and 4.
e.g. The file $.file.books.AtoZ
will be searched for in the following places.
books2directory would never be searched.
$in the filename)
Relative links are translated correctly, with the exception of URLs starting with tilde (~
) which strictly speaking should use a specified directory in a users home directory. The username being immediately after the tilde (~
).
As RISC OS has no concept of users, all URLs starting in a tilde (~
) are taken to have a / at the front making them absolute, i.e. they then point to a directory or file starting with a tilde.