In message <4e8a36bad5tim(a)timil.com>
Tim Hill <tim(a)timil.com> wrote:
In article <f7712b7c0611221358p188f19bp1f79f9924541318b(a)mail.gmail.com>,
Christopher Bazley <cs99cjb(a)gmail.com> wrote:
> What I don't understand is why NetSurf, which could easily recognise
> the text between it and </script>. Perhaps it is purism on the part of
> the developers?
Similarly, NetSurf displays the content of php tags if they (erroneously)
appear in a file of type HTML, e.g.:
<? include('file') ?>
is displayed as
in NetSurf. That's a simple example, php code which generates (e.g.) a
page counter can look a mess.
Bug or Feature?
I had a handful of text files (PoVRay source code) which used constructs
such as <0.0, 1.0, 1.2> for storing vector data. And initially, Netsurf
mistakenly treated these as tags and swallowed them up. As I recall, the fix
was to replace the leading < with < before passing the text file to be
displayed. I'm wondering if that same fix is interfering where it shouldn't
- it was supposed to only apply to the rendering of plain text files, AFAIR.
(Sample at http://www.simon-smith.org/raytracing/fantasy_pool.html
The grass is not, in fact, always greener on the other side of the fence.
Fences have nothing to do with it. The grass is greenest where it is
watered. When crossing over fences, carry water with you and tend the grass
wherever you may be." - Robert Fulghum