Build ID: c36489be617be3e8ca25612d29afb221bc7ae6c1
CPU Threads: 2; OS Version: Linux 3.16; UI Render: default;
Locale: en-US (en_US.UTF-8); Calc: group
1. Open writer;
2. Format -> Paragraph
Notice that units are now "ch" by default instead of the units you generally use/expect with your system. Through 5.2 my default units are American Standard so I would see just 0.00" (" represents "inches"). I have no idea how how to equate "ch" to inches.
Expected: Units would be based on locale and be consistent with other settings. I just checked MS Office 2010 and it bases indent on system units so I see inches - zero clue how I'd know if interop was right if I imported something from Word that I knew was 1.25" and converted to some X ch
ALSO: This might be a separate bug but I was told to keep it in one
Same as above
Observed: "Above the line" and "below the line" now measured in "lines"
Expected: Either stick with metrics of system (again for me inches)_or move to "pt" which is what Word apparently does.
These two issues make interop quite tedious
I can't reproduce
Build ID: ea9a90d83d92076d41abfd31a1fd3a5d84b6ba92
CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL;
TinderBox: Win-x86@39, Branch:master, Time: 2016-08-26_06:19:43
Locale: es-ES (es_ES); Calc: CL
The same as in 5.2 'cm'
Maybe it's a erroneous string for inches.
Is it right in Menu/Tools/Options/LibreOffice writer/General - Measurement units?
Reproduced and is only in master.
Build ID: f7513f0f53f2d074c08610a68fb787bb379c31d4
CPU Threads: 2; OS Version: Linux 3.19; UI Render: default;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-09-02_23:58:05
Locale: en-US (en_US.UTF-8); Calc: group
Created attachment 127147 [details]
Can not reproduce on Windows 10 Pro 64-bit en-US with
Build ID: 696e83b663d4f3e00f23947613f9f3916a4dd14d
CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL;
TinderBox: Win-x86@42, Branch:master, Time: 2016-09-03_10:21:32
Locale: en-US (en_US); Calc: CL
Seems to be Linux only then... on Windows the units are my default inches--and as set in Tools -> Options -> LibreOffice Writer -> General: Settings--"Measurement unit" == "Inch"
I've been checking in Windows, and it definitely occurs, and not only in 5.3 master build, but all back to 3.3.0.
There's a checkbox right below "Measurement unit": "Enable char unit", that controls the behavior, if checked, you will see character/line units in Paragraph dialog.
Hm, there's no such checkbox in Linux.
Adjacent checkbox is missing as well: "Use square page mode for text grid".
On linux i see both checkboxes in the options dialog in a profile i've been using for only 1 month and that i never modified the measurement unit in. With a blank profile, both checkboxes are gone.
(In reply to Aron Budea from comment #5)
> There's a checkbox right below "Measurement unit": "Enable char unit", that
> controls the behavior, if checked, you will see character/line units in
> Paragraph dialog.
(In reply to Aron Budea from comment #6)
> Hm, there's no such checkbox in Linux.
> Adjacent checkbox is missing as well: "Use square page mode for text grid".
Both checkboxes depend of CJK features to be enabled (Language Settings > Languages > Asian). Also you need to close & reopen the options dialog for this setting to take effect.
The "Enable char unit" and "Use square page mode for text grid" only appear if the checkbox for Tools -> Options -> Language Settings -> Languages "Default language for the document" includes a check of the Asian list.
Controlling attribute in source is IsAsianTypographyEnabled()
If no Asian language support is enabled--the two check boxes are hidden, and do not assert.
And if an Asian language is selected--the ch / line settings in Paragraph dialog will only assert if the "Enable char unit" checkbox is selected.
Seems by default our user configuration includes selections enabling Asian and CTL--and that the checkbox for "Enable char unit" and "Use square page mode for text grid" are set active by default for builds after 3.4.6
Verified the checkbox setting, and the ch / line behavior of the Paragraph dialog "Indents and Spacing" on Windows builds 5.2.1, 5.1.5, 4.4.6, 4.3.6, 4.2.6, 4.1.6, 4.0.6, 3.6.5, 3.5.7
Through the 3.4.6 release the "Enable char unit" was not checked by default and the Paragraph dialog Indents and Spacing is not affected.
So, default is wrong--but simple work around uncheck the "Enable char unit" (Tools -> Options -> LibreOffice Writer -> General) when you are not composing in an Asian script.
Glad we were able to track down the issue, but curious why Joel enabled that checkbox. I enable it for QA work i'm doing. So the question comes down to whether it being on by default is what CJK users want by default.
I believe both character spacing and square page grid are preferred settings for composing with logograms (Hànzì, Kanji, Hanja) in CJK Asian scripts being used while editing. Otherwise, IIUC both character and grid should be disabled for text composition using phonograms/alphabets.
On Windows at least, both are set on by default with a default user profile that includes Asian (CJK) and Complex Text Language (CTL) scripts, so that unexpectedly causes issue with spacings in the Paragraph dialog--even though a CJK script is not actually being used for the paragraph.
Yes it seems that if CJK and CTL are both enabled, "Enable char unit" is enabled and if only CJK is enabled, "Enable char unit" isnt enabled. So this seems to be the route of the bug.
I didn't enable anything and had never seen this behavior before a recent master build. This was seen with a fresh profile.
Minding the settings mentioned above, this occurs in 3.3 as well, adjusting earliest version and removing regression-related keywords.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!