Closed Bug 1231158 Opened 10 years ago Closed 10 years ago

Re-enable FUEL Terminology project in Pontoon

Categories

(Localization Infrastructure and Tools :: Administration / Setup, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mathjazz, Unassigned)

Details

We should re-enable the FUEL Terminology project in Pontoon: http://fuelproject.org/ We should create a new repository for it, based on (but without fuel-agriculture-bn.pot): https://github.com/birajkarmakar/Bengali-India-bn-IN-Fuel-Terminology/ It should be made available for all locales, which will then translate it and thus make it available in Pontoon Translation Memory. In addition to that, we should later on add support for annotating terminology matches in original strings and provide suggestions for these matches in the UI (should be a separate bug).
Hi Matjaz, Thanks for initiating this. I was happy to talk about FUEL in yesterday. Web: https://github.com/birajkarmakar/Bengali-India-bn-IN-Fuel-Terminology/blob/master/templates/fuel-web-bn.pot mobile : https://github.com/birajkarmakar/Bengali-India-bn-IN-Fuel-Terminology/blob/master/templates/fuel-mobile-bn.pot Desktop : http://svn.fedorahosted.org/svn/fuel/language/en/terminology/desktop/fuel-desktop-en.pot Cloud: https://github.com/birajkarmakar/Bengali-India-bn-IN-Fuel-Terminology/blob/master/templates/fuel-cloud-bn.pot These modules would be great for Mozilla. Right now Mozilla has just few words in Terminology. Gradually, this projects is being developed. Some other open source organization is still using it. I am gonna cc-ed @rajesh ranjan, founder of this project. He can share more thoughts on that.
Component: Pontoon → Administration / Setup
Flags: needinfo?(l10n)
Product: Webtools → Localization Infrastructure and Tools
Version: Trunk → unspecified
We've taken a closer look at the terminology project in FUEL, and discussed it among our team. It's not what we expect from a terminology project, as it turns out. We're intending to have a terminology that comes with different metadata, and different content. Our language resources like translation memories and, in the future, terminologies are open content, so if there's something in them that of value to FUEL, that's great. But we don't intend to invest in the support and integration of the FUEL version of the terminology project itself. Thus I'm resolving this bug as WONTFIX.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(l10n)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.