X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/halibut/blobdiff_plain/56a99eb648cb255aed42d929823a07913e0d743a..0dfaac7284d7f1a54e957bba4a881d93328c1630:/bk_html.c diff --git a/bk_html.c b/bk_html.c index f6091a3..e3202a5 100644 --- a/bk_html.c +++ b/bk_html.c @@ -11,27 +11,12 @@ * fragment should be used? (Though it should probably still be * _there_ even if unused.) * - * - new configurability: - * * index_text, contents_text, preamble_text, title_separator, - * nav_prev_text, nav_next_text, nav_separator, - * index_main_sep, index_multi_sep, pre_versionid, - * post_versionid - * * Some means of specifying the distinction between - * restrict-charset and output-charset. It seems to me that - * `html-charset' is output-charset, and that - * restrict-charset usually wants to be either output-charset - * or UTF-8 (the latter indicating that any Unicode character - * is fair game and it will be specified using &#foo; if it - * isn't in output-charset). However, since XHTML defaults to - * UTF-8 and it's fiddly to tell it otherwise, it's just - * possible that some user may need to set restrict-charset - * to their charset of choice while leaving _output_-charset - * at UTF-8. Figure out some configuration, and apply it. - * - * - nonbreaking spaces. - * - * - free up all the data we have allocated while running this - * backend. + * - In HHK index mode: subsidiary hhk entries (as in replacing + * `foo, bar' with `foo\n\tbar') can be done by embedding + * sub-