On Wed, 2004-09-15 at 15:19, Paul W. Frields wrote:
On Wed, 2004-09-15 at 17:38, Mark Johnson wrote:
> Brock Organ wrote:
> > On Wed, 2004-09-15 at 16:52 -0400, Tammy Fox wrote:
> >
> >>I was about to add the common draft notice file from bug #132415, but I
> >>wanted to discuss the wording of the notice a bit more. (This was
> >>discussed on the Hardening Doc Preview thread, but I am starting a new
> >>one with a more appropriate subject.)
> >>
> >>Thoughts?
> >
> >
> > sounds good to me ...
>
> Me, too. A nice improvement:)
I also like this!
+1 for a complete consensus :)
The URL
<
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=######>
always works in my experience (for non-restricted bugs of course). If
the writer uses too long a URL, the editor can fix it without a problem.
Or for that matter, I suppose we could have a common entity:
<!ENTITY SYSTEM BZ-Q
"http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=">
And in the writer's doc:
<!ENTITY SYSTEM BUG-URL "&BZ-Q;######">
Strike SYSTEM from that usage.
But maybe that's just too much work? Not sure.
Seems simpler to go with a locally defined entity that is the bug #.
FWIW, this works:
http://bugzilla.redhat.com/XXXXXX
I think Mark is thinking of a pre-filled bug report such as the one that
I use for the SELinux FAQ. For getting proper feedback, it is
invaluable -- it prefills the product, version, and component, sets the
blocker bug and assigned to, suggests a useful title-style, should have
the latest version number embedded already, and has specific suggestions
for filling out a bug report unique to this project. However, it looks
like this:
https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core&...!
ate&form_name=enter_bug
I use a <ulink/> with descriptive link text. :)
How about:
1. If it is just a link to the bug report, then:
<!ENTITY BUG-URL "http://bugzilla.redhat.com/XXXXXX">
usage:
<ulink url="&BUG-URL;"/>
2. If it is a Really Long URL, then following the same solution to
define the entity, but usage is:
<ulink url="BUG-URL;">pre-filled bug report</ulink>
NOTE - if you use a long URL that includes '&' characters, you _must_
change them to & in the XML so that they process into the correct
characters when rendered.
- Karsten
--
Karsten Wade, RHCE, Tech Writer
a lemon is just a melon in disguise
http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41