Deprecate i18n building for XUL client
Bug #1757455 reported by
Chris Sharp
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Right now, our building process for i18n requires string translation for our XUL client. Unfortunately for us, the version of translate-toolkit on Ubuntu 16.04 (and similar-vintage Debian, probably) assumes a newer version of XUL than our ancient one and those tools no longer work for that. Since we are deprecating the XUL client altogether, we should remove XUL strings from our i18n files.
tags: | added: i18n removexul |
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
milestone: | 3.next → 3.3-beta1 |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Working branch: user/bshum/ remove- xul-i18n
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ bshum/remove- xul-i18n
This branch removes the makefile targets of dtds2pot and props2pot from the newpot target. This means that future newpot runs to get new translation template changes will skip over the dtds and property files.
The original XUL client translation files will still exist and can still be translated for the time being. We will just no longer compare them to update changes for XUL client (which shouldn't be changing anyways).
Pullrequest tagged for next Evergreen release.