Distro News

Ubuntu's UK English locale uses three conflicting names for trash across GNOME shell

Key Takeaway

Ubuntu's British English translation inconsistently labels the deleted files location as Trash, Rubbish Bin, and Wastebasket depending on which UI element a user interacts with.

Summary

Ubuntu users with their system set to UK English encounter inconsistent terminology for the system's deleted files container, with the dock hover label reading 'Trash', the file manager window titled 'Rubbish Bin', and the empty action labeled 'Empty Wastebasket'. The same context menu simultaneously offers to 'Delete From Wastebasket' and 'Restore From Rubbish Bin' for identical operations. This fragmentation stems from Ubuntu's translations being split across GNOME upstream, third-party extensions, and Ubuntu's own integrations, each maintained by separate teams with different conventions.

GNOME's British English translation guidance specifies that 'Trash should be translated to Wastebasket', which accounts for one of the variants. The US English locale maintains consistent 'Trash' labeling throughout the interface. The inconsistency represents a localization papercut rather than a functional bug, though it introduces minor cognitive friction as users must mentally map between terms for the same location.

Where the terminology diverges

  • Dock hover label: Displays 'Trash' rather than a localized British English term, diverging from GNOME's translation guidance.
  • Files window title: Opens as 'Rubbish Bin' in the file manager, introducing a second distinct term for the same location.
  • Action bar button: Shows 'Empty Wastebasket', which follows GNOME's official British English guidance but conflicts with the window title.
  • Context menu items: Simultaneously presents 'Delete From Wastebasket' and 'Restore From Rubbish Bin' in the same menu, mixing two of the three terms.
  • Confirmation dialog: Headers ask 'Empty Wastebasket?' while the affirmative button reads 'Empty Rubbish Bin', creating a third inconsistency within a single workflow.

Why it matters

This case illustrates how fragmented translation maintenance across upstream projects, downstream distributions, and third-party extensions can degrade user experience even when each component functions correctly in isolation. For Ubuntu specifically, it highlights the ongoing challenge of maintaining coherent localization at scale, particularly for English variants that receive less scrutiny than non-English translations. Distribution maintainers and localization teams may need to audit cross-component terminology consistency more systematically, especially as GNOME continues to refine its translation guidelines.

Original reference: www.omgubuntu.co.uk →