summaryrefslogtreecommitdiff
path: root/doc/bugs
AgeCommit message (Collapse)Author
2008-10-02renameJoey Hess
2008-10-02this is a wishlist todo item, rename tooJoey Hess
2008-10-02responseJoey Hess
2008-10-02thoughtsJoey Hess
2008-10-02pingJoey Hess
2008-10-02closeJoey Hess
2008-10-02move to todo, responseJoey Hess
2008-10-02typoJoey Hess
2008-10-02fix bug closureJoey Hess
2008-10-01inline: Fix handling of rootpage that doesn't exist.Joey Hess
It makes sense to use bestlink to determine which page rootpage refers to, but if no page matches, just use the raw value.
2008-10-01(no commit message)Plareplane
2008-09-30interesting bugJoey Hess
2008-09-29(no commit message)http://josephturian.blogspot.com/
2008-09-28responsechrysn
2008-09-27editpage: Be more aggressive (and less buggy) about cleaning up temporary ↵Joey Hess
files rendered during page preview.
2008-09-27thoughtsJoey Hess
2008-09-27(no commit message)Plareplane
2008-09-27(no commit message)http://smcv.pseudorandom.co.uk/
2008-09-27Beautify urls used in various places. (smcv)Joey Hess
2008-09-27typoJoey Hess
2008-09-27(no commit message)intrigeri
2008-09-26decode utf-8 in recentchanges_link parameterJoey Hess
2008-09-26update: possible solutionchrysn
2008-09-26some problem remainschrysn
2008-09-25close bugs for just fixed tag creation issueJoey Hess
2008-09-25git: Fix handling of utf-8 filenames in recentchanges.Joey Hess
Seems that the problem is that once the \nnn coming from git is converted to a single character, decode_utf8 decides that this is a standalone character, and not part of a multibyte utf-8 sequence, and so does nothing. I tried playing with the utf-8 flag, but that didn't work. Instead, use decode("utf8"), which doesn't have the same qualms, and successfully decodes the octets into a utf-8 character. Rant: Think for a minute about fact that any and every program that parses git-log, or git-show, etc output to figure out what files were in a commit needs to contain this snippet of code, to convert from git-log's wacky output to a regular character set: if ($file =~ m/^"(.*)"$/) { ($file=$1) =~ s/\\([0-7]{1,3})/chr(oct($1))/eg; } (And it's only that "simple" if you don't care about filenames with embedded \n or \t or other control characters.) Does that strike anyone else as putting the parsing and conversion in the wrong place (ie, in gitweb, ikiwiki, etc, etc)? Doesn't anyone who actually uses git with utf-8 filenames get a bit pissed off at seeing \xxx\xxx instead of the utf-8 in git-commit and other output?
2008-09-23Add keepextension parameter to htmlize hook. (Willu)Joey Hess
2008-09-23Print a debug message if a page has multiple source files.Joey Hess
2008-09-23mergedJoey Hess
2008-09-23* Responsehttp://ptecza.myopenid.com/
2008-09-23bug report on funny characters in the namechrysn
2008-09-22bug report with patchhttp://smcv.pseudorandom.co.uk/
2008-09-22(no commit message)http://smcv.pseudorandom.co.uk/
2008-09-22Reference patches to beautify redirection URLshttp://smcv.pseudorandom.co.uk/
2008-09-21Add second, related, patch.http://www.cse.unsw.edu.au/~willu/
2008-09-21Add patchhttp://www.cse.unsw.edu.au/~willu/
2008-09-21Add a new bug when using source highlightinghttp://www.cse.unsw.edu.au/~willu/
2008-09-19progress: Display an error if the progress cannot be parsed, and allow the ↵Joey Hess
percent parameter to only optionally end with "%".
2008-09-19* Additionhttp://ptecza.myopenid.com/
2008-09-19* Responsehttp://ptecza.myopenid.com/
2008-09-19Responsehttp://www.cse.unsw.edu.au/~willu/
2008-09-19* More clear about my upgradehttp://ptecza.myopenid.com/
2008-09-19* No progresshttp://ptecza.myopenid.com/
2008-09-17responseJoey Hess
2008-09-16(no commit message)http://thewordnerd.info/
2008-09-15(no commit message)http://josephturian.blogspot.com/
2008-09-15(no commit message)http://josephturian.blogspot.com/
2008-09-15user errorJoey Hess
2008-09-14fix linksJoey Hess
2008-09-14cannot reproduceJoey Hess