UX: clarify "Empty Document" to "Empty File"

Open Beginner friendly
#3,838 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
desktop

Research direction

Search the Nemo source and UI strings for "Create New Document" and "Empty Document". Update the labels to the requested "Create New File" and "Empty File", then verify the right-click file-list menu displays the new wording.

Written by the indexing model from the issue text.

Description

Distribution

Mint 22.3

Package version

nemo 6.6.3

Frequency

Always

Bug description

literally every layperson I hand out Mint laptops to stumbles over "Empty Document" not doing what they expect. They expect a Libreoffice writer document, but get a 0-length file without extension they don't know what to do with. Sometimes goes so far, they assume they can't write texts on Linux Mint.

Don't believe me, if on doubt, put it under UX test with real new users.

Steps to reproduce

right-click in the file list area and see "Create New Document" and then "Empty Document".

Expected behavior

right-click in the file list area and see "Create New File" and then "Empty File".

Additional information

Out-of-the-box templates could mitigate this issue, however the wording "Document" is inferior to "File".

nemo calls itself file browser, not document browser.

Dominant language
C
Stars
1.6k
Forks
368
Avg merge
8d 7h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo

All issues in linuxmint/nemo

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.