Package: git-doc
X-Debbugs-Cc: [EMAIL PROTECTED]
Version: 1:1.5.6.5-1
Severity: minor
File: /usr/share/doc/git-doc/user-manual.html
$ validate /usr/share/doc/git-doc/user-manual.html
*** Errors validating /usr/share/doc/git-doc/user-manual.html: ***
Error at line 1, character 1: missing document type declaration; assuming
HTML 4.01 Transitional
[and maybe others too in that directory.]
(Mainly I wish this document used old fashioned ASCII and <pre>s, and not
U+00A0 NO-BREAK SPACE
UTF-8: c2 a0 UTF-16BE: 00a0 Decimal:  
etc. which I had to clean up for my plucker->big5 PDA:
$ < /usr/share/doc/git-doc/user-manual.html uni2ascii -ex > /tmp/GIT_UM.html
Total input characters 245668
Characters converted to escapes 0
Characters replaced with ASCII 5433
Characters deleted 0
)
P.S., in file:///usr/share/doc/git-doc/gitrepository-layout.html it says
logs
Records of changes made to refs are stored in this directory. See the
documentation on git-update-ref for more information.
Why can't git-update-ref be hyperlinked. Also just say "see
git-update-ref(1)". By the way, there are many similar "should be
hyperlinked" places on these man pages. E.g., "see git-rev-parse
documentation" in gitcore-tutorial.html. Also there: "There is a
helpful script called git commit" ... 1) standardize: git-commit, and
link to git-commit(1).
P.S., each git man page could say "I am a porcelain (high-level
command)", "I am a plumbing (low-level command)", Or "this is a ...
option". That way one need not look on git(1) to double check.
P.S., in file:///usr/share/doc/git-doc/git-bundle.html
it would be clearer if you used prompts
Machine_A$
Machine_B$ or
A$ B$
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
