Closed Bug 1364467 Opened 8 years ago Closed 8 years ago

[configuration] define how l10n-merge should work

Categories

(Localization Infrastructure and Tools :: General, enhancement)

Product:
Localization Infrastructure and Tools
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Pike, Assigned: Pike)

Details

In the new configuration world, is there a well defined canonical behavior on how l10n-merge should work? In particular, for [[paths]] reference = "browser/branding/official/locales/en-US/**" l10n = "{l}browser/branding/official/**" we might not find out what's {l} at the time when we hand things down, or that that's the intended behavior. Needs more thought and comments.
This was solved in bug 1368025.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.