Closed
Bug 1436010
Opened 6 years ago
Closed 1 year ago
Migration: a string including a message reference to non existing message should not be migrated
Categories
(Localization Infrastructure and Tools :: Fluent Migration, enhancement)
Localization Infrastructure and Tools
Fluent Migration
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: flod, Unassigned)
References
Details
In migration for bug 1424682 we can end up creating files that only contain references to messages that don't actually exist. These would only raise a warning in compare-locale, so these strings would be kept in the localization, and the string ID would be displayed at run-time (bug 1436009). For example, we add category-general .tooltiptext = { pane-general-title } Even if pane-general-title doesn't exist in the localized file. We should likely skip creating these if the message doesn't exist, and maybe only ignore terms references in this checks (they can be defined in a different file).
Updated•6 years ago
|
Blocks: fluent.migrate
Updated•6 years ago
|
Component: General → Python Library
Updated•6 years ago
|
No longer blocks: fluent.migrate
Component: Python Library → Fluent Migration
Product: L20n → Localization Infrastructure and Tools
Comment 1•1 year ago
|
||
Closing as WONTFIX, as the migration isn't the right place to apply this check.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•