In message <f7712b7c0608060306qc871bafp555e99ec0e247fce(a)mail.gmail.com>
"Christopher Bazley" <cs99cjb(a)gmail.com> wrote:
On 05/08/06, Harriet Bazley <lists(a)orange.wingsandbeaks.org.uk> wrote:
> The file !Netsurf.FixFonts appears to be plain text filetyped as
> tokenised BASIC (as can be readily confirmed by changing the type to
> Data and examining it), which causes Textseek to fall over when trying
> to detokenise it - is this deliberate?
I would guess that this file is plain text to make it easier to edit
on foreign platforms, or to produce 'diffs'. Oddly, the 'KickNS' file
If 'FixFonts' is supposed to be non-tokenised BASIC then it
have file type &FD1 ('BASICTxt') on RISC OS.
Or is it the other way round?
Untokenised, plain text, is acceptable to the interpreter as filetype
BASIC, FFB. I (very) vaguely seem to recollect that from the early days
of RISC OS, where "vaguely" really does mean vague. I can not now find
it documented. Anyway FixFonts does work as it is.
If that is correct then it is up to Editors to sort out whether
de-tokenisation is required. StrongED will load a plain text BASIC file
and tokenise it on a save. Zap needs forcing into its BASTXT mode, on
saving the file remains plain text.
However there doesn't seem to be a default run action for this
type, so NetSurf would either need to define a run action  or change
the command line  used to run the program:
1) If "<Alias$@RunType_FD1>" = "" Then Set Alias$@RunType_FD1
-quit |"%0|" %*1
2) TaskWindow "Basic -quit <NetSurf$Dir>.FixFonts" -wimpslot 200K -quit
I believe file type FD1 was introduced with DeskEdit, it is not directly
supported in RISC OS itself. The icon needs adding plus as said above a
Computing with RISC OS.