hej elijah, Am Donnerstag, den 19.10.2006, 12:03 -0600 schrieb Elijah Newren: > On 10/19/06, Andre Klapper <ak-47 gmx net> wrote: > Yeah, I wanted to word it to handle both cases but still make sure > that people install debuginfo packages in both cases. :-) good idea. > I'm not sure the best way of doing that. Here's an alternative > wording for the second sentence: > > "This extra bit of information they asked for is a stack trace (also > known as a backtrace), and it is important that the stack trace you > obtain contains debugging symbols." > > Not sure which is better or if someone else has an alternative > suggestion. Thoughts? good proposal, i'd prefer that new one here. > > perhaps something like this?: > > "You need to install additional debug packages to get the requested > > so-called "debugging symbols" for the program that crashed. > > Hmm...I'm not a fan of the "so-called" part of the sentence. ;-) > Also, if the user could have been worried about reinstalling, wouldn't > they also have worries about what additional packages would do? Maybe > we should change this to something like: > > "You need to install debug packages for the program that crashed. > These debug packages are additional packages that do not affect the > operation of your existing program, but provide debugging symbols > needed by developers to help pinpoint problems when they occur." that one looks very good, but "operation" sounds pretty techie, and i'd change "pinpoint", because i had to look that up. ;-)) something like this perhaps?: "You need to install debug packages for the program that crashed. These debug packages are additional packages that do not affect your existing program, but provide debugging symbols needed by developers. This makes it possible to find the exact place in the program code where that problem occurs, and to fix it." > > Most likely > > you also need to install debug packages for some of the program's major > > dependencies. > > Installing debug packages for GNOME's major libraries like glib, gtk+, > > and gnome-vfs is also a good idea (note that distros often rename these > > to e.g. glib2, gtk2, and gnome-vfs2 to allow parallel installation with > > GNOME 1.x libraries), because most of the GNOME programs depend on those > > major libraries and make use of their functionality." > > I like your changes here. fine. > > #3 > > "You can then cut-and-paste it from bug-buddy into your bug report." > > > > we always have and had a "Copy" button in the left bottom corner, right? > > whatever "cut-and-paste" means, let's make it easy and say > > > > "You can then click on Bug-Buddy's "Copy" button and after that, you can > > paste the information into your bug report." > > The general idea sounds fine, but I don't see any copy button. Am I blind? i'm still stuck with gnome2.12 (suse10.1) here, so i don't know the simplified bug-buddy-2.16, but bug-buddy-2.12 had a "copy" and a "save" button. if bug-buddy 2.16 does not have this anymore, then it would perhaps be good to bring that "Copy" button back in to make it easier for users that are not "control+c/+v" or "highlight&middle-click" savvy. see attached screenshot. cheers, andre -- mailto:ak-47 gmx net | failed! http://www.iomc.de
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil