Localisation is too hard for Gmail

Re:Localisation is too hard for Gmail by wodenokoto on Wednesday October 21, 2020 @01:45PM (#24850230)

So what do you do when a en_GB user creates a folder named Trash and switches to en_US and her “bin” folder now needs to be displayed as Trash? How do you resolve her saved searches and labeled items in a way such that the user can also tell them apart?

[ Parent | on HN ]

Re:Localisation is too hard for Gmail by thesuitonym on Wednesday October 21, 2020 @02:34PM (#24850693)

Labels should reference GUIDs behind the scenes. If a user does this, they will just be unsure which one is the actual Trash label. When searching, Gmail should give results from both labels.

[ Parent | on HN ]

Re:Localisation is too hard for Gmail by PaulDavisThe1st on Wednesday October 21, 2020 @02:57PM (#24850887)

or more generally, user-provided names should never be the canonical identifier for any resource.

for example, don't (canonically) identify accounts with usernames. that way when "joesmith" becomes "josephbarnes", the user can just change their username and everything keeps working (because it's really all user ID 19829).

any "name" you get from a user should always be considered nothing more than a non-canonical label for a resource with some other persistent and canonical identifier.

[ Parent | on HN ]

Re:Localisation is too hard for Gmail by xyzzy_plugh on Wednesday October 21, 2020 @03:50PM (#24851356)

As another poster points out, this won't work for e.g. IMAP usage.

[ Parent | on HN ]

Re:Localisation is too hard for Gmail by earthboundkid on Thursday October 22, 2020 @01:03AM (#24855048)

Yes, although to be fair, JMAP is a thing and Google has had a decade and a half to improve IMAP if they cared.

[ Parent | on HN ]

Re:Localisation is too hard for Gmail by dash2 on Wednesday October 21, 2020 @02:26PM (#24850613)

Maybe use reserved words? This doesn't seem like an impossible obstacle to surmount.

[ Parent | on HN ]