To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=13807
User bh changed the following:
What |Old value |New value
================================================================================
Assigned to|bh |requirements
--------------------------------------------------------------------------------
------- Additional comments from b...@openoffice.org Fri May 21 13:42:49 +0000
2010 -------
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".
------- Additional comments from leonthere...@openoffice.org Wed Oct 13
23:40:12 +0000 2010 -------
I can't believe that in 7 (SEVEN) years, no one can figure out how to wrap the
anchor text of an HREF. That's 7 YEARS. I have run into this problem and tried
everything I can think of to work around it, but it is so fundamentally broken
that it is impossible. What is also odd is that "Insert --> Hyperlink" results
in something different than "=HYPERLINK($TARGET;$ANCHOR)" (which I have found
even more worthless than "Insert --> Hyperlink"). What is wrong with honoring
the "Cell Format --> Automatic Line Break" attribute? Why are there two
distinct ways to enter a hyperlink and two presentations of them?
THIS IS NOT AN ENHANCEMENT: THIS IS A BUG.
As a software engineer, I get the sense just from the "Insert --> Hyperlink"
dialog box that it is an afterthought mis-feature. What is the purpose of
separate "Apply" and "Close Buttons"? This dialog box is suspect because it
appears to be hand crafted and unlike the rest of the Calc style.
Finally, who is "fst" and where is the source of his magical proclamations like
"Hyperlinks can't be treated with a line break?" Where does that come from?
Does he know the difference between the HREF link target and the anchor text?
Or is he, like so many other non-developers on all the open source "support
fora" just making stuff up as he goes along because he wants to sound all smart
and stuff?
Could somebody (who actually knows something) please cite why (a) there is an
international standard that precludes line breaks in anchor text, or (b) a
compatibility issue with something that does not suck, or (c) it is such an
immensely tough coding issue that a rookie can't fix it. Just kicking the can
down the street is what makes Open Source suck: many eyes can find all the bugs
but who cares if nobody can be bothered to fix the bugs?
Is there anybody listening?
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@sc.openoffice.org
For additional commands, e-mail: issues-h...@sc.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
