New issue
Advanced search Search tips

Issue 767029 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Verify the ru and cn locales for the cloud print driver installer

Project Member Reported by pastarmovj@chromium.org, Sep 20 2017

Issue description

There are reports that on Windows with those locales the driver doesn't install.

See chrbug.com/629512 for description.

It seems there is some difference between the language codes present in the resource file of the installer and the driver and therefore the printer driver is not correctly matched for some locales. 

I thought I have checked them all but it might be that some are still not correct or windows does something weird when matching sublocales.
 
Cc: adlr@chromium.org
Components: Services>CloudPrint
Summary: Verify the ru and cn locales for the cloud print driver installer (was: Vefiry the ru and cn locales for the cloud print driver installer)
Users on  bug 629512  reported Windows 10 build 15063.

adlr: Anyone interested in taking this one?
I am happy to provide more info to whoever would like to take it. It should be relatively trivial up to the fact that you might need to spin up a VM with a localized Windows version to verify the fix.

Alternatively we either decide to drop the localization of the printer driver name (less optimal) or find a way to reference the driver in the installer that does not need to use a localized string (would be great but don't know how).
pastarmovj: If you can set me up with access to test machines/VMs with the right locales, that would be great.
I don't have one ready. What I did when I fixed that for the Spanish locale was to download a Win 7 image from my MSDN subscription and spin it up in a VM with VirtualBox on my workstation. 
It's 2018 already, and Cloud Print still doesn't work for ru locale. Please fix it!
Cloud Print Driver Installation Error.png
4.2 KB View Download
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment