diff options
| author | Simon Tatham <anakin@pobox.com> | 2004-06-27 12:23:38 +0000 |
|---|---|---|
| committer | Simon Tatham <anakin@pobox.com> | 2004-06-27 12:23:38 +0000 |
| commit | d9b0f4031a36b4a7348b21e6a0933f0417e22ab3 (patch) | |
| tree | 505997c13af236b2d9ca0fdde893d721ae1333b7 /wcwidth.c | |
| parent | 765012cad1a36c9bb3094c66d055a3b612e4c3a2 (diff) | |
| download | halibut-d9b0f4031a36b4a7348b21e6a0933f0417e22ab3.zip halibut-d9b0f4031a36b4a7348b21e6a0933f0417e22ab3.tar.gz halibut-d9b0f4031a36b4a7348b21e6a0933f0417e22ab3.tar.bz2 halibut-d9b0f4031a36b4a7348b21e6a0933f0417e22ab3.tar.xz | |
Fix up the restrict_charset and output_charset configuration for the
HTML backend. After an argument with James in which it transpired
that we each thought it was absolutely obvious which one
\cfg{html-charset} ought to map to, and each of us was thinking of a
different one, I've decided that this implies it _isn't_ obvious,
and hence there is no single \cfg{html-charset} directive at all.
Instead, we have \cfg{html-restrict-charset} and \cfg{html-output-
charset}, and any naive user who `just wants to change character
set' is just going to have to RTFM and figure out which one they
mean.
[originally from svn r4313]
Diffstat (limited to 'wcwidth.c')
0 files changed, 0 insertions, 0 deletions