Closed Bug 1321271 Opened 8 years ago Closed 2 years ago

migration module should port partially translated messages

Categories

(Localization Infrastructure and Tools :: Fluent Migration, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Pike, Unassigned)

References

Details

Take FTL.Entity( id=FTL.Identifier('urlbar-textbox'), traits=[ FTL.Member( FTL.Keyword('placeholder', 'xul'), LITERAL_FROM( 'browser/chrome/browser/browser.dtd', 'urlbar.placeholder2', ) ), FTL.Member( FTL.Keyword('accesskey', 'xul'), LITERAL_FROM( 'browser/chrome/browser/browser.dtd', 'urlbar.accesskey', ) ), ] ), and only one of the two source entities exists. We shall not break. My preferred outcome would be to generate a partial target entity, so that we don't loose existing translation work. The generated file would create a compare-locales error, but still, I think. In the case of a missing source for a CONCAT, I think we should fail through. The generated string needs-work, after all. Hopefully TM catches a bit in this case.
No longer blocks: fluent.migrate
Component: Python Library → Fluent Migration
Product: L20n → Localization Infrastructure and Tools
No longer blocks: 1291693

Closing as unnecessary.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.