trans-es September 2010

trans-es@lists.fedoraproject.org

7 participants
7 discussions

[Fedora-trans-es] [Bug 597039] New: Wrong local currency symbol for Nicaragua
by Red Hat Bugzilla 24 Nov '16

24 Nov '16

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Wrong local currency symbol for Nicaragua https://bugzilla.redhat.com/show_bug.cgi?id=597039 Summary: Wrong local currency symbol for Nicaragua Product: Fedora Localization Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: Spanish [es] AssignedTo: domingobecker(a)gmail.com ReportedBy: yn1v(a)fedoraproject.org QAContact: domingobecker(a)gmail.com CC: fedora-trans-es(a)redhat.com Estimated Hours: 0.0 Classification: Fedora Description of problem: The currency symbol for Nicaragua is wrong. Version-Release number of selected component (if applicable): I have tried in Fedora 12. I will comment if I find this in Fedora 13 as soon as I upgrade my system How reproducible: Look for the currency symbol Steps to Reproduce: 1. locale -k LC_MONETARY | grep currency_symbol Actual results: currency_symbol="$C" duo_currency_symbol="$C" Expected results: currency_symbol="C$" duo_currency_symbol="C$" Additional info: The currency symbol is C$ but in the system has been set in reverse order. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 15

[Fedora-trans-es] Traducción de páginas man
by Daniel Cabrera 01 Oct '10

01 Oct '10

Gente: A principios de este año se empezó a tratar el tema de la traducción de páginas de manual [1]. Recién ahora podemos dedicarle algo de tiempo, y por supuesto, cuantos más seamos en el proyecto, mejor. Para aquellos que quieran sumarse, nuestro plan de trabajo es el siguiente: Dado quea versión más actual en castellano de man-pages es las 1.55, mientras que la original es la 3.26, 1) Tenemos que convertir a *.po todos los archivos *.troff de man-pages-es-1.55 2) Luego tenemos que convertir a *.pot todos los archivos *.troff de man-pages-3.26 3) Una vez realizado esto, hay que actualizar los archivos *.po.es-1.55 con los archivos *.pot-3.26 4) Finalmente, emprolijar las cadenas provisorias y traducir las nuevas de los archivos finales *.po.es-3.26. Man1 ya está liquidado, y ya están "pot-ificados" los archivos *.troff de man2-3.26 [2]. Entre mañana y el lunes pensamos terminar con la "po-ificación" de man2-es-1.55, y los subo a la carpeta correspondiente. Cualquier ayuda, comentario, sugerencia, etc, será más que bienvenida. [1] http://lists.fedoraproject.org/pipermail/trans/2010-March/007174.html [2] http://logan.fedorapeople.org/Man%20pages/ Saludos, daniel.

7 12

Re: [Fedora-trans-es] Release notes
by Domingo Becker 20 Sep '10

20 Sep '10

El día 14 de septiembre de 2010 08:30, daniel cabrera <logan(a)fedoraproject.org> escribió: > Che, me fijé recién y ya terminamos de traducir las Notas del > Lanzamiento, así que las publiqué acá [1] para que podamos corregirlas > mejor. > > [1] http://logan.fedorapeople.org/F14/Release%20Notes/ > Si hay voluntarios para revisarlas, se agradece la colaboración. saludos y gracias Domingo Becker

5 8

[Fedora-trans-es] consulta por Scientific_and_Technical.po de release notes
by Domingo Becker 13 Sep '10

13 Sep '10

Alguien tuvo bloqueado el archivo Scientific and Technical, pero parece que no subió traducciones. ¿Hubo un error de transifex o realmente no hay traducciones hechas? Pregunto porque ayer no lo toqué porque lo ví bloqueado. Hoy lo he bloqueado y lo estoy traduciendo, porque la fecha límite es hoy y debemos llegar al 90%. Pero no quiero superponer el trabajo de otro con el mío. Si no lo subieron por un error, pásenmelo por email a mi dirección. saludos Domingo Becker

1 0

Re: [Fedora-trans-es] Procedure for working with guides not originally written in English
by Domingo Becker 08 Sep '10

08 Sep '10

2010/9/1 Eric "Sparks" Christensen <sparks(a)fedoraproject.org>: > > The following process has been established and is open for suggestions: > > Non-English source > | > Non-English source > in DocBook XML > | > Non-English POT > | > English PO > | English source in DocBook XML | > English POT > | > Translated POs > | > Publish English and translated > versions of the guide > That missing conversion would be done by publican, as said Paul Frields (stickster). > > As long as the source owner can find someone to translate the source > into English then our tool-chains should work. > I kindly invite the Fedora Spanish translation team to get involved in this process. We have to translate from Spanish .pot to English .po using poEdit or any other po file editor. If we succeed in this process, other docs contributors can do the same as Guillermo Gomez (gomix), and enrich the Fedora documentation with their creation. kind regards Domingo Becker (es)

3 4

Re: [Fedora-trans-es] Procedure for working with guides not originally written in English
by Domingo Becker 03 Sep '10

03 Sep '10

2010/9/3 Paul W. Frields <stickster(a)gmail.com>: > > Right on both counts. I thought there was some reason that people > wanted an English POT, but it's not required in either Publican or > Transifex. Lingua franca is a per-project concept, after all. :-) > The reason is that Fedora translation teams translate from English to whatever but not from Spanish to whatever. So we need an English .pot file to let other people to translate it. If not, the process will stop there and we will only have a Spanish and an English version of the book. The process has started already. Jared and the docs team is helping Guillermo a lot. So we will soon have a Non-English source in DocBook XML to continue with the work flow. kind regards Domingo Becker

1 0

Re: [Fedora-trans-es] Procedure for working with guides not originally written in English
by Ruediger Landmann 01 Sep '10

01 Sep '10

On 09/02/2010 01:55 AM, Eric "Sparks" Christensen wrote: > This morning I worked with gomix and dbecker on IRC (#fedora-docs) with > a non-English guide that we want to make official. Because the base > language of all our guides has been English, and our translation tools > are based on English, this was a process that had been thought about but > not spelled out... until today. > > The following process has been established and is open for suggestions: > > Non-English source > | > Non-English source > in DocBook XML > | > Non-English POT > | > English PO > | > English POT > | > Translated POs > | > Publish English and translated > versions of the guide > > The process needs to be fleshed out a bit and tools identified at > various points but this should be a good starting point. > > As long as the source owner can find someone to translate the source > into English then our tool-chains should work. From the Publican end, this could be even simpler: Non-English XML | Non-English POT | Translated POs (including English) | Publish Original version of guide plus other translations including English I'm pretty sure Transifex also doesn't care what language is used in the msgid strings in the POT file either. Cheers Rudi (sorry to anyone seeing this twice; I forgot to hit "reply all" last time)

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans-es September 2010