Closed Bug 1390111 Opened 8 years ago Closed 8 years ago

mobile/android/base unescaping should handle \' and \u0027

Categories

(Webtools Graveyard :: Pontoon, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: jotes)

Details

Attachments

(1 file)

Pootle escapes ' as \u0027 while pontoon escapes it as \' for Android DTD files. Bah, bad Android, no cookie. On unescaping, pontoon should take both encodings and map them to '. Probably same for ", too.
Assignee: nobody → m
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
The \u0027 & \u0022 characters now look good in Pontoon, but they appear in the downloadable TMX translation memory. For example, in: https://pontoon.mozilla.org/ca/firefox-for-android/ca.firefox-for-android.tmx The characters \u0027 & \u0022 should be also unescaped in the TMX.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: m → poke
Commit pushed to master at https://github.com/mozilla/pontoon https://github.com/mozilla/pontoon/commit/682cec26cd02c05dd0604e3c6542b6a5c16a2ddf Fix bug 1390111: Unescape Android quotes in TM (#738) Handling of different escape sequences for mobile Android strings was fixed in eb5f8d5. However, data migration in 4537eac only covered the Translation model, leaving out TranslationMemoryEntry. See bugs 1390111 and 1390113 for more details.
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
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: