On Tue, 14 Aug 2018, Sven Schreiber wrote:
Am 14.08.2018 um 17:39 schrieb Allin Cottrell:
> On Fri, 10 Aug 2018, Sven Schreiber wrote:
>
> The easiest way to get this used by browsers is to insert a reference as
> the second line of the gfn file:
>
> <?xml-stylesheet type="text/xsl" href="gfn2html.xsl"?>
Ah, clever!
> That's easy enough to do with a little shell script, and I've processed
> these three as a sample:
>
> criteria.gfn
> corresp.gfn
> delayspectral.gfn
Seems to work OK.
> I don't think there's any bad fallout from inserting this line. If that's
> confirmed I can go ahead and batch-process all the gfns.
OK, but there are two remaining issues:
1. Newly incoming (or updated) packages need to get this extra line as well.
For the future could this somehow be incorporated into the "gretlcli.exe
--makepkg" command (and its equivalent on Linux)?
Could be, though I don't think it would be difficult to inject the
line in question when a gfn is uploaded to the server, if it's not
already present in the XML.
2. Then there are the zip format packages. With the exception of
'Threshold_Panel' and 'dhurdle' (and anything else?), all of these have
PDF
help files. My proposal would be to put those pdf files manually into a
subdirectory
http://ricardo.ecn.wfu.edu/gretl/cgi-bin/current_fnfiles/unzipped/pdf/ - the
package moderators including myself can take care of that I think. And then
add a link to current_fnfiles/unzipped/pdf/<pkgname>.pdf to the description
field of the package listing. This latter step would involve changing the
dynamic web code for SHOW_FUNCS, but not much I guess.
Yes, something like that should work. Also I think the "extract the
PDF to such-and-such a place" step could be automated (on upload, or
probably better, on approval).
Allin