Investigating
[View this post in your web browser. It contains formatting and images that don't appear in email.]
@hans_onepicture Whether the map display works or not could depend on the username (user) in the Windows account. My Windows username contains an umlaut ("ü").
Excellent discovery! I tested 8 diacritical marks and 1 ligature in Windows account usernames, and some worked and some didn’t. This explains why the bug reports mostly came from the same European countries, with a few from South America and other countries.
So the workaround is to create a username without any diacritical marks.
Looking at the Unicode representations, all of the problem-causing diacritical marks have code points starting with U+00, while the non-problematic marks and ligatures don’t:
It’s pretty clear that some software component invoked by the Map module has a bug in its handling of Unicode strings. Given that similar bugs haven’t cropped up in other parts of LR, this strongly suggests the problem is somewhere in the third-party components such as the Google Maps JSON library. I think that library caches map data in hidden folders inside C:\Users\<username>\AppData, and the caching could be getting tripped up by the bug in the Unicode handling.
As of some months ago, Adobe hadn’t updated that component -- it was many years out-of-date. And the engineer who originally wrote that part of LR is likely long gone from the team.
Tested on LR 16.0 / Windows 11 running in the US region with US English.
Show previous replies
Show more replies
Sign up
Already have an account? Login
To post, reply, or follow discussions, please sign in with your Adobe ID.
Sign inSign in to Adobe Community
To post, reply, or follow discussions, please sign in with your Adobe ID.
Sign inEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
AdChoices