If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[fileAlreadyExistsError] '_files' directory is more confusing than necessary

NEW
Unassigned

Status

()

Core
DOM
11 years ago
5 years ago

People

(Reporter: timeless, Unassigned)

Tracking

Trunk
x86
SunOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
47 cbiesinger 1.2 fileAlreadyExistsError=%S could not be saved, because a file already exists with the same name as the '_files' directory.\n\nTry saving to a different location.

I see no reason not to write '%S_files' (or %1$S_files as it would have to be).

Out of curiosity, is there anything that prevents the line from being something like:
fileAlreadyExistsError=%1$S could not be saved because a file named %1$S_files already exists, this name is needed for a directory to store associated files.\n\nTry saving with a different name or to a different location.

personally, I'd rather just use:
fileAlreadyExistsError=Can not save because a file named %S_files already exists, this name is needed for a directory to store associated files.\n\nTry saving with a different name or to a different location.
Assignee: general → nobody
QA Contact: ian → general
(Assignee)

Updated

5 years ago
Component: DOM: Other → DOM
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.