Red Hat Bugzilla – Bug 478626
Last modified: 2009-01-21 16:36:40 EST
Description of problem:
Babel fish and Google translator have added some new languages
Apertium related entries are not present
Version-Release number of selected component (if applicable):
I've prepared patches for the various changes and will attach them separately.
Created attachment 328062 [details]
Google - new languages/language pairs
Google has added a number of language pairs to their service. All language pairs can be translated into others and this is reflected by the change to to="*"
Created attachment 328063 [details]
Babelfish - add zh-zh-TW pair added
Created attachment 328070 [details]
Google - fix weburl
Seems the old web page URL no longer works, this fixes it to the new expected format.
Created attachment 328071 [details]
Apertium - add stable translation pairs
Add Apertium, an OSS machine translation tool.
Created attachment 328073 [details]
Opentrad - an appertium based free service
This is another Apertium based translation tool that potentially adds a number of other free languages.
Created attachment 328075 [details]
Apertium (Unstable) - add unstable language pairs
This patch is disabled by default, allowing users to enable to unstable language pairs if they know the limitations of these pairs.
Created attachment 328076 [details]
Apertium (alpha-testing) - add testing/alpha language pairs
Again disabled by default but supplied to allow users the ability to enable if needed.
Your patches are against the installed servises.xml file, but the source tarball contains the "services.xml.in" in the "data/" subdir, which has slightly different format (mostly "to" and "tag" are swapped).
Could you provide here just a resulted (with all the patches applied) file "services.xml.in" ?
I think we should not provide such changes by patches, because the size of these patches seem bigger than the size of the original file to patch...
Ouch, quite a bit of fixing. I'll have a look at it sometime this week.
My reason for the different patches was to keep things logical and allow cherry picking changes that where approved. I'm not that worried about size. I think what might be good is to keep new services apart from changes and disabled serivices. I'll think of something.
I'm working against libtranslate in CVS so the changes should then be easy to integrate into the build system.
Created attachment 328411 [details]
Consolidated patch for services.xml.in
Created attachment 328412 [details]
Patch to libtranslate.spec including changes for service.xml.in
Apply and run. This patch should update libtranslate.spec and includes the patch to update service.xml.in. It should be all that is needed to add and update for a new release.
I've made a scratch build here:
libtranslate-0.99-18.fc10 has been submitted as an update for Fedora 10.
libtranslate-0.99-18.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update libtranslate'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-0557
libtranslate-0.99-18.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.