> HTML does not (AFAIK) distinguish between tabs and other whitespace.
> It will (by default) collapse all such characters into a single one
> or (with the right css) display them as-is, but css provides no way
> to say "treat tabs as N spaces" (or no way i have wver seen). My
> point being - in the web ui, i don't think this is possible without
> filtering the text.
A quick and dirty solution was adding this to the CSS config:
pre {
-o-tab-width: 4;
-moz-tab-width: 4;
tab-width: 4;
}
However, providing a hook to allow filtering the text before displaying
it (well, sending to the browser) may be a good idea and actually
better than adding any flag or config variable for tab stops. With a
filter anyone can implement whatever eye candy they want for displaying
content in the web UI (line numbers or syntax colouring would come to
mind for program sources), it has no effect on the actual revision
control functionality of Fossil, and with an empty filter being the
default it is completely backward compatible.
Of course, I really don't know how Fossil is organised internally, so
it's very easy for me to say 'just add a hook for a filter' even if in
reality it would be a major undertaking, so I think it's better if I
just shut up.
Zoltan
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
