Apache OpenOffice (AOO) Bugzilla – Issue 126987
Preview field does not properly display min scale width setting
Last modified: 2016-05-29 18:04:38 UTC
Created attachment 85558 [details] Screenshot of preview field showing incorrect scale width with 1% When entering the minimum scale width setting on 1% the preview field viewer does not update to reflect a 1% scale width. The preview field does change from the 100% default but this change is not a reflection of a 1% scale. Steps to recreate: 1. Select Format from the menu bar then Character option 2. On the Position tab click into the Scale width field and enter 1% 3. The Preview Field will change but it doesn't change to a 1% scale. 4. If you click the up arrow or enter 2% you will notice the Preview Field properly updates to a 2% scale. I was able to recreate this with versions 4.1.2 and 4.1.1 running on Windows 7 and Windows 10 machines. After additional follow-up testing I found that if you navigate to the Font tab from the Character menu and select the font size of 13 (Default should be 12) then you will see the Preview Field update to the correct 1% scale width.
Created attachment 85559 [details] Screenshot Preview Field accurately displays 2% scale width
The behavior of the Preview Field not displaying at a 1% scale is inconsistent with other word processor products such as Microsoft Word. Microsoft Word's preview box accurately displays the scale width at 1%.
The text properly scales at 1% after entering the value however the Preview field does not reflect the 1% scale.
With AOO 4.1.2 x86 on Windows 10 Pro x64, I confirm the behavior. In Writer, the Format > Character ... > Position > Rotation/scaling > Scale width setting of 1% appears the same as no scaling in the preview, but is enacted in the text. Of course, it is impossible to see what the result is and how it differs from an adjacent 2% scaling. (Zoom doesn't reveal it at any available magnification.) QUESTION With these edge cases like this, would it be helpful to collect Caveats and FAQ about details of some of these dialogs and what they do on the documentation wiki pages? This could link to the issues (and vice versa) and also provide guidance long before there might be anything done about cases of this kind in the implementation. It would also provide a stable place to direct people to from bugzilla issues, mailing lists, and the Community Forum. Would that be an useful first step?