Issue 43249 - Inconsistent use of a word for "Measurement unit" in UI
Summary: Inconsistent use of a word for "Measurement unit" in UI
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 680m79
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa, usability
Depends on:
Reported: 2005-02-21 12:14 UTC by arthit
Modified: 2017-05-20 11:27 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.0.0
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description arthit 2005-02-21 12:14:18 UTC
in Tools -> Options of Writer,Calc,Draw,Impress

in the setting for Writer, Writer/Web, and Calc,
it use the word "Measurement unit"

- OOo Writer: General: Measurement unit
- OOo Writer/Web: View: Measurement unit
- OOo Calc: General: Measurement unit

but in the setting for Draw and Impress,
it use the word "Unit of measurement"

- OOo Impress: General: Unit of measurement
- Ooo Draw: General: Unit of measurement

Besides, the location of this setting for Writer/Web is different from others.
While other apps has this setting in '<app_name>: General',
Writer/Web has it in '<app_name>: View'.

Please consider to use the same word for the same thing,
either "Measurement unit" or "Unit of measurement". Just one.

Also, if possible, the same setting in each app should be at the "same" place.
For example, the measurement unit setting for Writer/Web should be found in OOo
'Writer/Web: General' ... just like we found the same setting for Calc in Calc
'OOo: General'
Comment 1 arthit 2005-02-21 12:15:25 UTC
May related to usability.
Comment 2 mci 2005-02-21 14:25:58 UTC
reassigned to cj

mci -> cj:

hi cj, please have a look at this and decide about further handling, thanks...
Comment 3 christian.jansen 2005-05-20 14:39:01 UTC
CJ -> EM: Please have a look at this one. Thanks.
Comment 4 e.matthis 2005-05-20 15:18:45 UTC
Cj/Liz: Reduction of this issue: Only for the wording, not for placement of strings.
In order for the wording to be fixed soon, only look at the first aspect. The
string placement cannot be dealt with in a product update (minor release), but
the string bug can. Targetting to 2.0.2

Both terms "Unit of measurement" and "Measurement unit" are incorrect, according
to US English. It should be "Unit of measure"

Definition from
"(as of length, surface, volume, dry measure, liquid measure, money, weight,
time, and the like), in general, a determinate quantity or magnitude of the kind
designated, taken as a standard of comparison for others of the same kind, in
assigning to them numerical values, as 1 foot, 1 yard, 1 mile, 1 square foot, 1
square yard, 1 cubic foot, 1 peck, 1 bushel, 1 gallon, 1 cent, 1 ounce, 1 poun,
1 hour, and the like [...]"

Liz->OS: please change English only, as follows...

Unit of ~measurement  ---> Unit of ~measure
KeyId          209670
PRJ            sd
Filename       source\ui\dlg\tpoption.src
Build          SRC680
LID            FT_METRIC
Type           fixedtext

Measurement unit --> Unit of measure
KeyId          214871
PRJ            sw
Filename       source\ui\config\optload.src
Build          SRC680
LID            FT_METRIC
Type           fixedtext

Measurement unit --> Unit of measure
KeyId          214738
PRJ            sw
Filename       source\ui\config\optdlg.src
Build          SRC680
LID            FT_METRIC
Type           fixedtext

Measurement ~unit ---> ~Unit of measure
KeyId          217576
PRJ            sc
Filename       source\ui\src\optdlg.src
Build          SRC680
LID            FT_UNIT
Type           fixedtext
Comment 5 arthit 2005-05-20 20:03:24 UTC
Thank you for the fix :)

btw, seems like the inconsistency goes deep into the code itself.
Look at LID, we have both FT_METRIC and FT_UNIT.

(I know that this cannot be fixed anytime soon, or may be will never, but still
like to mentioned about it.)
Comment 6 Oliver Specht 2005-11-22 08:06:52 UTC
Comment 7 Mathias_Bauer 2006-01-23 13:22:25 UTC
We will not finish this task in the 2.0.2 time frame -> retargetted to 3.0
Comment 8 Marcus 2017-05-20 11:27:55 UTC
Reset assigne to the default "".