Re: [AD] Screen destruction documentation update |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2005-09-10, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> Besides, it makes the HTML and text output look ugly. The problem
> is, at least here, it doesn't look like:
>
> \\ text //
>
> but like:
>
> \\ text ||
>
> Really disgusting :P
Yeah, blame that on makedoc and not the artsy type who created your
font. But fixing a font is something too hard to do, right? Lets
consider this change:
Index: docs/src/makedoc/makehtml.c
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/makedoc/makehtml.c,v
retrieving revision 1.39
diff -u -p -r1.39 makehtml.c
--- docs/src/makedoc/makehtml.c 8 Sep 2005 15:20:05 -0000 1.39
+++ docs/src/makedoc/makehtml.c 12 Sep 2005 17:34:38 -0000
@@ -768,7 +768,7 @@ static void _hfputs(char *string)
p++;
if ((p == end) && (p - string > 1)) {
- fputs("<tt>`", _file);
+ fputs("<code>", _file);
string++;
continue;
} else {
@@ -778,7 +778,7 @@ static void _hfputs(char *string)
}
/* Is closing comma search active? */
if ((string[0] == 39) && end == string) {
- fputs("'</tt>", _file);
+ fputs("</code>", _file);
string++;
end = 0;
continue;
The problem with that, as I argued before, is that you loose quotes
for text browsers, and since that's the only thing for text browsers,
you are degrading the content. IIRC I did a test with <q> and the
result looked not too bad for both types of browsers, but that's
abusing the semantics of the HTML spec.
I guess this can't be avoided forever. So what type of
pretty-html-quotes you want to see? While we are on that, what do
we do about other? Like ", * or _ still in use.