Hide Forgot
rhl-cg(EN)-7.3-HTML-RHI (2002-04-05T14:34-0400) in the Introduction, "2. Document Conventions" area, pages xi and xii There seems to be an extraneous space or minor indentation leading several paragraphs. This same indentation is not present in the Red Hat 7.2 Customization Guide. It doesn't seem intentional. command <SP>Linux commands (and ... this way. This style ... filename <SP>Filenames, directory names, paths, and... This style should indicate ... applications <SP>This style should [key] <SP>A key on the keyboard is [key]-[combination] <SP>A combination of keystrokes text found on ta GUI interface <SP>A title, word, or phrase top level of a menu on a GUI screen or window <SP>When you see a word in button on a GUI screen or window <SP>This style indicates that computer output <SP>When you se text prompt <SP>A prompt, which is user input <SP>Text that the user has to
These items are listed in a variablelist which intentionally produces the format (I hope this is displayed correctly): item description item description
I understand that the intended format is like below: item description item description and this is how things looked in the 7.2 printed manual. what I was reporting is that there is an extra leading space or indentation at the beginning of "description" paragraphs... item description asd flkj asdf lkja sdfl lasdjk fl askdjf aslkdj asdlfjl lsdjslkdj woeijfsl knmovnjap lkajsdofijkl ;jasdjf l asdljow edo nwi vnodwi asl;jsdkjowiej item description laskdj l;ks djfkl;asjd fkla;sdjf la;skdjf asl; dkfj wioe laskd sldjkf lsdjflsdj lj; ladkj lsdj flasjkd lfj sdjf;l sldjkf
Ok. I understand what you are saying now. What browser are you using? I don't see the extra space in Mozilla or Netscape.
hmmm.. well I was giving page numbers for the PDF. I don't see any issue with that exact page from the html version when running lynx or konqueror either. The strange spacing shows up however when viewing the pdf in acrobat or with xpdf.
Ok. I understand even more now. This is due to a formatting problem. I have fixed it for the next release. Thanks for catching this!