Mailinglist Archive: yast-devel (191 mails)

< Previous Next >
Re: [yast-devel] Tiny URL for "People were very unhappy because I only wrote..."
  • From: "Rajko M." <rmatov101@xxxxxxxxxxx>
  • Date: Sat, 8 Mar 2008 08:19:44 -0600
  • Message-id: <200803080819.45111.rmatov101@xxxxxxxxxxx>
On Friday 07 March 2008 04:25:03 am Stefan Hundhammer wrote:
On Friday 07 March 2008 01:43, Rajko M. wrote:
[http://very-long-url#section Some name here]
Shows up in text as link 'Some name here' with mark that is external
link. First blank after URL is for Mediawiki software sign that URL is
done and the rest to the ']' is the name that should appear in a text.

Well, yes, but the problem we have is that we often refer to the bug
reporting FAQ in Bugzilla. That's where we have that long link. AFAICS the
Wiki names the anchors according to the section heading, and since those
section headings are the questions, the anchor will be the full question
(with special characters escaped).

Not using the question as the section heading would OTOH make the TOC
pretty useless - we'd have to use something very short which would not be
very descriptive for the respective question.


CU

Not tested much on openSUSE wiki:
http://en.wikipedia.org/wiki/Help:Section#Section_linking

I tested in the Sandbox:
<span id="123">
= pre test =
</span>

which works as the link from another wiki page:
[[sandbox#123]] or [[sandbox#123|bugfaq 1]]

The only problem with complete link with section included is that any change
to section title will break the link. Link that points to non existant part
after # will bring up the top of article. Which means that no edit to section
titles is allowed, even correction of grammar or spelling errors.
More flexible method of linking is using IDs, but then if one want to rearange
IDs because some sections where inserted it will mess previosly created
links. Probably the most flexible way to refere to question is this:
http://en.opensuse.org/Bug_Reporting_FAQ
see "Why is bug description "see subject" bad idea?"

This way if question is changed than it is easy to copy and paste new



I looked at the page and it seems that is possible to shorten section titles.
Some examples:
--------------------------------------------------------------------------
1.1.5 People got mad at me because I entered "Install SUSE x.y-Beta-z" in
Bugzilla's "how to reproduce" field. Why?

1.1.5 Why is "Install openSUSE <version>" usless in "how to reproduce" field?
1.1.5 Why "Install openSUSE <version>" doesn't help as "how to reproduce"?
--------------------------------------------------------------------------
1.1.6 People were very unhappy because I only wrote "see subject" in the
Bugzilla bug description - but my subject really explains it all! Isn't it
pure nitpicking to insist on bug reporters repeating that in the description
field?

1.1.6 Why is bug description "see subject" bad idea?
--------------------------------------------------------------------------
1.2.2 Don't I become the bug owner when I change a bug's status away from
NEEDINFO to ASSIGNED (with Accept bug (change status to ASSIGNED) in the
Bugzilla bug details page)?

1.2.2 Am I bug owner if I use "Accept bug"?

This is not clear anyway. "Accept bug" should change status and owner, or it
doesn't work as the expression "Accept bug" suggests.
--------------------------------------------------------------------------
1.2.3 Why is it important that I set a bug status away from NEEDINFO to
ASSIGNED? Isn't that the bug owner's responsibility?

1.2.3 Why is important to change a bug status to ASSIGNED after providing
information?
--------------------------------------------------------------------------
1.3.1 Should I mark a bug as VERIFIED or CLOSE it when I see that the problem
is solved in a new version or with the updates?

1.3.1 What to do if problem is solved in a new program version or after
update?

[TBD]
:-) So, what is going to be delivered?
--------------------------------------------------------------------------
etc.

--
Regards, Rajko.
See http://en.opensuse.org/Portal
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >