2013/2/6 Nico Cesar
<address@hidden>
On 05/02/13 22:52, Carolina Flores wrote:
>
> El 5 de febrero de 2013 17:47, Adrián <
address@hidden
>
> Hola,
>
> por lo que parece fsf.org <http://fsf.org> no está traducida al español:
>
>
https://www.fsf.org/?set_language=es
>
> ¿Hay algún plan? propongo empezar a organizar la traducción.
>
>
> Hola.
>
> Hace un tiempo teníamos un equipo. Todo lo traducido se colocó aquí
>
https://www.fsf.org/es pero no fue posible coordinar con Matt Lee para
> pasarlo al sitio oficial.
>
> La verdad, al final nos desmotivamos y dejamos de preguntar. Sería bueno
> reactivarlo.
Una pena. Por lo que tengo entendido Plone tiene las herramientas necesarias para soportar múltiples idiomas sin problema.
That's a great idea. I was talking to Libby about this proposal early
in the morning. But we both agree that we need a good work flow before
starting. Making the supporter on time is uphill right now, if we add
www.fsf.org translation could be worst. Don't get me wrong I'm the
number one fan of having the site in Spanish, but I don't want to make
my work even more chaotic. Remember that I'm a sysadmin here, my job
description does not include the Spanish translations. I'll be asking
John about which possibilities does the FSF for this kind of tasks.
Solving the technical and organizational problems, there is no limit on
our expansion.
I totally understand your point. I particular like the idea of a setup in which a
git repository contains the latest translations files and the webserver pulls time
to time the latest files, in order to get on place the latest translation/s. Basically
the translators just need to update the files and push them to the repo, everything
else happens automatically.
AFAIK,
fsf.org is running Plone, it must be some easy way to attack this
issue with some pluging / extension (I am not so familiar with Plone, but I saw
some multilangue sites runnning it).