Closed Bug 1479208 Opened 6 years ago Closed 6 years ago

[checks] False positive "not well-formed (invalid token)" and "can't parse en-US value" reported

Categories

(Webtools Graveyard :: Pontoon, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: flod, Assigned: jotes)

Details

Attachments

(1 file)

Report received from the Georgian localizer https://pontoon.mozilla.org/ka/all-projects/all-resources/?status=missing&string=189227 Can't submit a suggestion for this string: * not well-formed (invalid token) * can't parse en-US value I'm particularly confused by the second, given that the string has been correctly parsed. And can't spot anything wrong with the string in the DTD. But in compare-locales integration? https://hg.mozilla.org/l10n/gecko-strings/file/default/suite/chrome/mailnews/start.dtd
Assignee: nobody → poke
Commit pushed to master at https://github.com/mozilla/pontoon https://github.com/mozilla/pontoon/commit/5fdb350a31fc9f6d6bb8fcbee47734531f870044 Fix bug 1479208 - Wrap CompareDTDEntity in the right qutoes (#1033)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Priority: -- → P2
Summary: Errors submitting string: "not well-formed (invalid token)" and "can't parse en-US value" → [checks] False positive "not well-formed (invalid token)" and "can't parse en-US value" reported
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: