|
I hadn't thought of foreign language support when we
retricted title text to non-html. I wonder if we could
safely allow any & characters?
Doing the conversion in one place is reasonable, but
it is such a small routine it seemed simpler to duplicate
it instead. Maybe we will change that to make customization
easier.
Headers are already supported via a variable in hnrc.
The header text is prepended to every response or base
article page. We'll add footers too.
Along those lines, and your suggestion for collecting
the text in one place, we are planning to provide template
pages for most of the HyperNews output, starting with the
response and base article pages. Error messages are
another area where this would need to be done. Centralizing
all messages in one place would not be good for performance,
however, unless they were read from a file only when
needed for infrequent errors.
Allowing body documents to be protected is a problem
for http servers. Currently there is no way for a cgi
program to pass authentication info on to the server
with the body document. If a single hard-coded user and
password could be used, then there is hope, but we have
to upgrade the http.pl code to include that info. One
alternative is to restrict access to a particular domain.
I hope we can keep you a satisfied customer.
| 
Good ideas 
Norwegian characters, foreign language support
(Christian Løverås)
