https://issues.apache.org/ooo/show_bug.cgi?id=125892

Cem Kaner <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #4 from Cem Kaner <[email protected]> ---
(In reply to oooforum from comment #3)
> As you mentioned in help file, you can input a negative value to be "into"
> the margins.
> This value depends of the paper format and also, good sense of end-user.

Many bugs can be easily dismissed as a lack of "good sense of end-user." One
risk of that is that your volunteer testers will walk away if they think that
their reports are being dismissed rather than investigated. This report,
despite the dismissal, appears to signal a coding error. The indent values
displayed don't appear to match the display of text on the screen.

Let's follow up a little. Set your page margins wide (I use Adobe pdf as my
printer. I've set page size on the printer and in OOo to 96 x 96 inches to let
me design posters). Now create some paragraphs of text and play with before and
after text indents on the Properties window or on the dialog you get from
Format| Paragraph. The values of Before text and After text can get out of
synch in these two windows. For example, I moved to a new paragraph, typed 50
in the "before text" field in the paragraph dialog, and that changed to 33.53"
in Before Text and -0.11" in "after text" and stays as 0 in First line. Then I
clicked OK and the properties window display changes from 0 in before text, 0
in after text and 0 in first line to 6.75 in before text, -26.80 in after text,
and -26.69 in first line. The text itself appears to be constrained to a text
width of about 2 characters wide (12 point) even though the left and right
margins are only 0.79" and the text display window shows an apparent page width
(looking at the ruler) of 79 inches.

There are many reasons to decide not to fix a coding error, but dismissing it
as reflecting a lack of "good sense" of a tester who is trying to demonstrate
to you a failure in a straightforward way is not consistent with how bug
reports have generally been handled in the Open Office project.

(AOO411m4(Build:9774)  -  Rev. 1614269 Windows 7)

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.

Reply via email to