[Sugar-devel] [IAEP] [SLOB] meeting reminder
Tony Anderson
tony_anderson at usa.net
Sun Apr 3 01:45:04 EDT 2016
I can't imagine the process is so simple. The overwritten translations
were probably on translate.sugarlabs.org.
Sugar developers need to determine which Pootle files to install in an
image. Each individual Sugar activity has an independent set of
translations which needs to be updated into a new version of the Activity.
As Sugar, we need a process to handle this. I strongly believe it is a
mistake to do perform localization directly on the Pootle server. It
would be better
to do the localization at the locale and verify it by use by the native
language speakers (primary school children). Update for activities is to
submit new po
files in an updated version of the acitivity (version += 1). This
process is under git version control. These updates, once vetted, can be
updated on translate.sugarlabs.org. On a new Sugar release, OLPC or
someone determines which activities and which versions of those
activities to include in the image.
Tony
On 04/03/2016 11:59 AM, Dave Crossland wrote:
>
> On 2 April 2016 at 23:46, Sebastian Silva <sebastian at fuentelibre.org
> <mailto:sebastian at fuentelibre.org>> wrote:
>
> The translators hired by the Ministry of Education were surprised
> and distressed when they started noticing Edgar was /overwriting
> /the updated translations they were doing.
>
>
> It seems Pootle is currently configured to encourage such surprise and
> distress.
>
> It has a 'propose an update' mode ("suggest") and a 'instantly
> overwrite' mode ("Submit") and today 'submit' is the default action:
>
> http://imgur.com/L2TXdCw
>
> Does anyone know if Pootle can be configured to default to 'suggest',
> and to use Access Control Lists
> <https://en.wikipedia.org/wiki/Access_control_list> to ensure that
> only trusted translators can approve suggestions, so that such
> surprise and distress can not happen?
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20160403/08471de9/attachment.html>
More information about the Sugar-devel
mailing list