Bug 456092

Summary:	Scan area size unit should not be translated to inch since we do not have the conversion
Product:	[Applications] Skanlite	Reporter:	Jigé <broumpf-i>
Component:	general	Assignee:	Kåre Särs <kare.sars>
Status:	CONFIRMED ---
Severity:	wishlist
Priority:	NOR
Version First Reported In:	22.04.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jigé 2022-06-28 17:22:37 UTC

Hi,

In the user interface I cannot change the unit for the width and height of the scanned zone. Currently it's : inches.

I suspect it *should* be millimeters (mm).

A4 is ISO and uses the metric system. `scanimage -L` reports these values in millimeters. In KSaneCore/option.h there's a UnitMilliMeter but no inch one in the enum OptionUnit. And all the rules on my desktop are engraved in centimeters and millimeters. Though I agree it would be very convenient for our friends in the US to optionaly be able to set this unit as inches. 

Thanks and best regards

Comment 1 Kåre Särs 2022-06-28 19:06:33 UTC

Thanks for the report.

When using the test backend I can only see imperial units in the scan resolution (DPI) but that unit is basically everywhere... For me the scan-area size is in mm...

What locale do you have? could it be a translation error?
What scanner/backend do you have could it be something from the backend?

Comment 2 Jigé 2022-06-29 09:15:36 UTC

Hi,
Scanner is Epson V370. Locale is us_US.UTF-8 (sorry). It does work with millimeters now... I need to launch it like this (e.g.) :

  $ LC_MEASUREMENT="fr_FR.UTF-8" skanlite &

I had thought the locale could be the issue… I keep it as us_US.UTF-8 to use the qwerty keyboard, to avoid bad or incomplete translations and so that I can share error messages with others, linux being mostly developed in the english language. Plus LC_MEASUREMENT seems to be seldom used. But, anyway, I suppose it should be used. In this regard, the software works as expected.

Thank you.

Comment 3 Kåre Särs 2022-06-29 11:49:09 UTC

Hmm... I guess there might be a translation error, because we do not have mm to inch conversion anywhere...