infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmad Alawsie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-16097) Remove the Google Translate button on Pootle's UI for OpenOffice
Date Fri, 23 Feb 2018 22:05:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ahmad Alawsie updated INFRA-16097:
----------------------------------
    Description: 
So whilst i was translating for OpenOffice on their Pootle server, i encountered the Google
Translate button, and found out it does not work. I have spoken with the localisation mailing
list of OpenOffice, and the admins on there told me that they would look into this.

I raised the issue on GitHub, on Pootle's repository, and was told that the removal of that
button should be up to the people who manage their own Pootle deployment (link at: https://github.com/translate/pootle/issues/6799).
I have done reasearch and found out that since Pootle is Open Source too, I have then realised
there is absolutely no point with this Google Translate button at all. This is my reason...
Firstly, The Pootle documentation
http://docs.translatehouse.org/projects/pootle/en/stable-2.7.2/features/machine_translation.html
states this is a paid service, with fees listed at
https://cloud.google.com/translate/pricing

The fact that it is a paid service complicates things a lot. Not much
for the amount (it's 20$ per million characters; still, it would be a
large amount if you consider all strings and all languages), but for the
paperwork needed for the ASF to an expenditure "per use" of this kind.

So based on this, i believe the Google translate button should be removed all in all, for
the UI of Pootle to not contain non-functional buttons/features.

  was:
So whilst i was translating for OpenOffice on their Pootle server, i encountered the Google
Translate button, and found out it does not work. I have spoken with the localisation mailing
list of OpenOffice, and the admins on there told me that they would look into this. 

I raised the issue on GitHub, on Pootle's repository, and was told that the removal of that
button should be up to the people who manage their own Pootle deployment. I have done reasearch
and found out that since Pootle is Open Source too, I have then realised there is absolutely
no point with this Google Translate button at all. This is my reason... Firstly, The Pootle
documentation
http://docs.translatehouse.org/projects/pootle/en/stable-2.7.2/features/machine_translation.html
states this is a paid service, with fees listed at
https://cloud.google.com/translate/pricing

The fact that it is a paid service complicates things a lot. Not much
for the amount (it's 20$ per million characters; still, it would be a
large amount if you consider all strings and all languages), but for the
paperwork needed for the ASF to an expenditure "per use" of this kind.

So based on this, i believe the Google translate button should be removed all in all, for
the UI of Pootle to not contain non-functional buttons/features.


> Remove the Google Translate button on Pootle's UI for OpenOffice
> ----------------------------------------------------------------
>
>                 Key: INFRA-16097
>                 URL: https://issues.apache.org/jira/browse/INFRA-16097
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Translate
>            Reporter: Ahmad Alawsie
>            Priority: Minor
>
> So whilst i was translating for OpenOffice on their Pootle server, i encountered the
Google Translate button, and found out it does not work. I have spoken with the localisation
mailing list of OpenOffice, and the admins on there told me that they would look into this.
> I raised the issue on GitHub, on Pootle's repository, and was told that the removal of
that button should be up to the people who manage their own Pootle deployment (link at: https://github.com/translate/pootle/issues/6799).
I have done reasearch and found out that since Pootle is Open Source too, I have then realised
there is absolutely no point with this Google Translate button at all. This is my reason...
Firstly, The Pootle documentation
> http://docs.translatehouse.org/projects/pootle/en/stable-2.7.2/features/machine_translation.html
> states this is a paid service, with fees listed at
> https://cloud.google.com/translate/pricing
> The fact that it is a paid service complicates things a lot. Not much
> for the amount (it's 20$ per million characters; still, it would be a
> large amount if you consider all strings and all languages), but for the
> paperwork needed for the ASF to an expenditure "per use" of this kind.
> So based on this, i believe the Google translate button should be removed all in all,
for the UI of Pootle to not contain non-functional buttons/features.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message