Quadrapassel encoding error in Help document
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
yelp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: yelp
Using Lucid kernel 2.6.32-12-generic #17-Ubuntu SMP Fri Feb 5 08:16:30 UTC 2010 x86_64 GNU/Linux and Help 2.28.0. When accessing Quadrapassel (2.29.6) Help document I get
"This page contains the following errors:
error on line 417 at column 1451: Encoding error
Below is a rendering of the page up to the first error."
This occurs when I try to go to "2.6 Scoring Points"
I also get
"This page contains the following errors:
error on line 417 at column 1458: PCDATA invalid Char value 2
Below is a rendering of the page up to the first error."
No documentation is displayed for parts 2.5, 2.6, 2.7 as they don't seem to exist.
ProblemType: Bug
Architecture: amd64
Date: Fri Feb 12 18:25:07 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/yelp
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100206)
NonfreeKernelMo
Package: yelp 2.28.0+
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: yelp
Uname: Linux 2.6.32-12-generic x86_64
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!
When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.