[ProducingOSS commit] r1357 - trunk/pt-pt

2008-01-02 Thread ari . constancio
Author: ari.constancio
Date: Wed Jan  2 04:37:04 2008
New Revision: 1357

Log:
* pt-pt/ch04.xml: Translate titles of finished sections

Modified:
   trunk/pt-pt/ch04.xml

Modified: trunk/pt-pt/ch04.xml
==
--- trunk/pt-pt/ch04.xml(original)
+++ trunk/pt-pt/ch04.xmlWed Jan  2 04:37:04 2008
@@ -1,4 +1,4 @@
-chapter id=social-infrastructure
+chapter id=social-infrastructure
 
 titleInfra-estrutura Social e Política/title
 
@@ -194,7 +194,7 @@
 
 !--  SECTION == --
 sect1 id=consensus-democracy
-titleConsensus-based Democracy/title
+titleDemocracy com Base em Consenso/title
 
 paraHá medida que os projectos vão envelhecendo, tendem a deixar o
 modelo da ditadura benevolente e a partirem para sistemas mais abertamente
@@ -547,7 +547,7 @@
 
 !--  SECTION == --
 sect1 id=written-rules
-titleWriting It All Down/title
+titleColocar Tudo por Escrito/title
 
 paraNalgum ponto o número de convenções e acordos a voar no vosso
 projecto pode tornar-se de tal modo elevado que necessitará 

___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators


[ProducingOSS commit] r1358 - trunk/pt-pt

2008-01-02 Thread ari . constancio
Author: ari.constancio
Date: Wed Jan  2 04:50:58 2008
New Revision: 1358

Log:
* pt-pt/ch0{3,5,6,7,8,9}.xml: Change titles of unfinished sections back to 
English

Modified:
   trunk/pt-pt/ch03.xml
   trunk/pt-pt/ch05.xml
   trunk/pt-pt/ch06.xml
   trunk/pt-pt/ch07.xml
   trunk/pt-pt/ch08.xml
   trunk/pt-pt/ch09.xml

Modified: trunk/pt-pt/ch03.xml
==
--- trunk/pt-pt/ch03.xml(original)
+++ trunk/pt-pt/ch03.xmlWed Jan  2 04:50:58 2008
@@ -1,6 +1,6 @@
 chapter id=technical-infrastructure
 
-titleInfra-estrutura Técnica/title
+titleTechnical Infrastructure/title
 
 simplesect
 

Modified: trunk/pt-pt/ch05.xml
==
--- trunk/pt-pt/ch05.xml(original)
+++ trunk/pt-pt/ch05.xmlWed Jan  2 04:50:58 2008
@@ -641,7 +641,7 @@
 
 !--  subsection == --
 sect1 id=contracting
-titleContratação/title
+titleContracting/title
 
 paraO trabalho contratado necessita de ser cuidadosamente
 tratado em projectos de software livre. Idealmente deseja que o

Modified: trunk/pt-pt/ch06.xml
==
--- trunk/pt-pt/ch06.xml(original)
+++ trunk/pt-pt/ch06.xmlWed Jan  2 04:50:58 2008
@@ -1,6 +1,6 @@
-chapter id=communications
+chapter id=communications
 
-titleComunicações/title
+titleCommunications/title
 
 simplesect
 

Modified: trunk/pt-pt/ch07.xml
==
--- trunk/pt-pt/ch07.xml(original)
+++ trunk/pt-pt/ch07.xmlWed Jan  2 04:50:58 2008
@@ -1,6 +1,6 @@
 chapter id=development-cycle
 
-titleCriar Pacotes, Publicar e Desenvolvimento Diário/title
+titlePackaging, Releasing, and Daily Development/title
 
 simplesect
 

Modified: trunk/pt-pt/ch08.xml
==
--- trunk/pt-pt/ch08.xml(original)
+++ trunk/pt-pt/ch08.xmlWed Jan  2 04:50:58 2008
@@ -1,6 +1,6 @@
 chapter id=managing-volunteers
 
-titleGerir Voluntários/title
+titleManaging Volunteers/title
 
 simplesect
 

Modified: trunk/pt-pt/ch09.xml
==
--- trunk/pt-pt/ch09.xml(original)
+++ trunk/pt-pt/ch09.xmlWed Jan  2 04:50:58 2008
@@ -1,6 +1,6 @@
 chapter id=legal
 
-titleLicenças, Direitos de Autor e Patentes/title
+titleLicenses, Copyrights, and Patents/title
 
 simplesect
 

___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators


[ProducingOSS commit] r1355 - trunk/pt-pt

2008-01-02 Thread ari . constancio
Author: ari.constancio
Date: Wed Jan  2 04:25:10 2008
New Revision: 1355

Log:
* pt-pt/ch02.xml: Change titles of unfinished sections back to English

Modified:
   trunk/pt-pt/ch02.xml

Modified: trunk/pt-pt/ch02.xml
==
--- trunk/pt-pt/ch02.xml(original)
+++ trunk/pt-pt/ch02.xmlWed Jan  2 04:25:10 2008
@@ -1,6 +1,6 @@
 chapter id=getting-started
 
-titleComeçar/title
+titleGetting Started/title
 
 simplesect
 
@@ -125,7 +125,7 @@
 
 !--  subsection == --
 sect2 id=look-around
-titleMas, primeiro, olhe em volta/title
+titleBut First, Look Around/title
 
 paraBefore starting an open source project, there is one important
 caveat:/para
@@ -159,7 +159,7 @@
 
 !-- == SECTION === --
 sect1 id=starting-from-what-you-have
-titleComeçar com o que tem/title
+titleStarting From What You Have/title
 
 paraYou've looked around, found that nothing out there really fits
 your needs, and decided to start a new project./para
@@ -228,7 +228,7 @@
 
 !--  subsection == --
 sect2 id=choosing-a-name
-titleEscolha um bom nome/title
+titleChoose a Good Name/title
 
 paraPut yourself in the shoes of someone who's just heard about your
 project, perhaps by having stumbled across it while searching for
@@ -299,7 +299,7 @@
 
 !--  subsection == --
 sect2 id=mission-statement
-titleTenha uma afirmação clara de Missão/title
+titleHave a Clear Mission Statement/title
 
 paraOnce they've found the project's web site, the next thing people
 will look for is a quick description, a mission statement, so they can
@@ -353,7 +353,7 @@
 
 !--  subsection == --
 sect2 id=state-freedom
-titleAfirme que o projecto é Livre/title
+titleState That the Project is Free/title
 
 paraThose who remain interested after reading the mission statement
 will next want to see more details, perhaps some user or developer
@@ -392,7 +392,7 @@
 
 !--  subsection == --
 sect2 id=features-and-requirements
-titleCaracterísticas e Lista de Requisitos/title
+titleFeatures and Requirements List/title
 
 paraThere should be a brief list of the features the software
 supports (if something isn't completed yet, you can still list it, but
@@ -448,7 +448,7 @@
 
 !--  subsection == --
 sect2 id=development-status
-titleEstado de Desenvolvimento/title
+titleDevelopment Status/title
 
 paraPeople always want to know how a project is doing.  For new
 projects, they want to know the gap between the project's promise and

___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators


[ProducingOSS commit] r1360 - trunk/es

2008-01-02 Thread ecasbas
Author: ecasbas
Date: Wed Jan  2 10:39:11 2008
New Revision: 1360

Log:
Noisy Minority translated

Modified:
   trunk/es/ch06.xml

Modified: trunk/es/ch06.xml
==
--- trunk/es/ch06.xml   (original)
+++ trunk/es/ch06.xml   Wed Jan  2 10:39:11 2008
@@ -871,42 +871,41 @@
 sect2 id=noisy-minority
 titleEl efecto Ruido Minoritario/title
 
-paraIn any mailing list discussion, it's easy for a small minority
-to give the impression that there is a great deal of dissent, by
-flooding the list with numerous lengthy emails.  It's a bit like a
-filibuster, except that the illusion of widespread dissent is even
-more powerful, because it's divided across an arbitrary number of
-discrete posts and most people won't bother to keep track of who said
-what, when.  They'll just have an instinctive impression that the topic
-is very controversial, and wait for the fuss to die down./para
-
-paraThe best way to counteract this effect is to point it out very
-clearly and provide supporting evidence showing how small the actual
-number of dissenters is, compared to those in agreement.  In order to
-increase the disparity, you may want to privately poll people who have
+paraEn cualquier discusion de una lista de correo, es fácil para una pequeña 
minoría
+dar la impresión de que hay un gran acuerdo de contrariead, esto es inundando 
la lista
+con numerosos y largos emails. Es igual a hacer una maniobra obstruccionista, 
excepto que
+la ilusión de la disensión general es incluso más poderosa, porque está 
dividida entre 
+un número arbitrario de posts discretos y a la mayoría de la gente no le 
importa seguir
+la pista de quién ha dicho que, cuando. Sólo tienen una impresión instintiva 
de que el 
+tema es muy controvertido, y esperan a que el escándalo disminuya.
+/para
+
+paraLa mejor manera de contrarrestar este efecto es indicarlo muy claramente 
+y proporcionar pistas respaldadas mostrando cómo de pequeño es el número actual
+de disidentes comparado a los que están en acuerdo. Para incrementar la 
disparidad,
+puedes querer encuestar de manera privada a la gente que ha estado la mayor 
parte
+del tiempo en silencio, pero que sospechas que estarán de acuerdo con la 
mayoría.
 been mostly silent, but who you suspect would agree with the majority.
-Don't say anything that suggests the dissenters were deliberately
-trying to inflate the impression they were making.  Chances are they
-weren't, and even if they were, there would be no strategic advantage
-to pointing it out.  All you need do is show the actual numbers in a
-side-by-side comparison, and people will realize that their intuition
-of the situation does not match reality./para
-
-paraThis advice doesn't just apply to issues with clear
-for-and-against positions.  It applies to any discussion where a fuss
-is being made, but it's not clear that most people consider the issue
-under discussion to be a real problem.  After a while, if you agree that
-the issue is not worthy of action, and can see that it has failed to
-get much traction (even if it has generated a lot of mails), you can
-just observe publicly that it's not getting traction.  If the Noisy
-Minority effect has been at work, your post will seem like a breath of
-fresh air.  Most people's impression of the discussion up to that
-point will have been somewhat murky: Huh, it sure feels like there's
-some big deal here, because there sure are a lot of posts, but I can't
-see any clear progress happening.  By explaining how the form of the
-discussion made it appear more turbulent than it really was, you
-retrospectively give it a new shape, through which people can recast
-their understanding of what transpired./para
+No digas nada que sugiera que los disidentes estaban intentando 
deliberadamente inflar
+la impresión que estaban creando. Oportunidades que no tuvieron, e incluso si 
las tuvieron
+no había una ventaja estratégica para señalarla. Todo lo que necesitas es 
mostrar el
+número actual en una comparación cara-a-cara, y la gente se dara cuenta que su 
intuición
+de la situación no coincidía con la realidad.
+/para
+
+paraEste consejo no sólo se aplica a temas con una clara posición 
a-favor-en-contra.
+Se aplica a cualquier discusión donde hay un alboroto, pero no esta claro que 
la mayoría
+de la gente considere ese tema bajo discusión que sea un problema real. 
Despues de todo,
+si estas de acuerdo en que el tema no es digno de acción, y puedes ver que ha 
fallado
+en atraer la atención (incluso si ha generado muchos mails), puedes observar 
públicamente
+que no está teniendo tracción. Si el efecto ruido minoritario ha funcionado, 
tu post
+parecerá un soplo de aire fresco. La mayoría de la impresión de la gente de la 
discusión
+se dará cuenta de que ese punto habrá sido algo turbio: Huh, seguro que 
sienten como
+que hay un gran acuerdo aqui, porque seguramente hay un montón de posts, pero 
no puedo
+ver que esté habiendo 

ProducingOSS translation ToC guideline

2008-01-02 Thread Karl Fogel
Ari Constancio just reminded me of something I'd been meaning to ask:

Can we translate each section/chapter heading only *after* the
corresponding section/chapter is finished?  That way, anyone can look
at the table of contents to see how far along that translation is.

For example, the German version (http://producingoss.com/de/) seems to
following this convention, and thus one can easily see that it is
almost finished now, with only part of Chapter 9 still to do.

A long time ago, I talked with a few translators privately about using
this convention, but I forgot to bring it up after we created this
mailing list.  Sorry for the oversight.

If we're agreed on this convention, I'll document it on the
translations web page.

Thanks,
-Karl

Ari Constancio [EMAIL PROTECTED] writes:
 Karl,

 I just watched your presentation on Principles of Participation for
 Open Information Communities (great!) and, concerning the
 ProducingOSS translation effort, I noticed you mentioned the table of
 contents as an indicator of translation progress.

 I was not aware of that and, sometime ago, I changed titles on the
 table of contents without having any translation inside.  I'll change
 back the titles of the untranslated sections back to English.

 Probably this guideline should be made explicit.

 Cheers, Ari Constancio

___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators


Re: ProducingOSS translation ToC guideline

2008-01-02 Thread Emilio
Agreed. Easy way to see the current state.



Thanks

Emilio.


- Mensaje original 
De: Karl Fogel [EMAIL PROTECTED]
Para: producingoss-translators@red-bean.com
Enviado: miércoles, 2 de enero, 2008 20:13:51
Asunto: ProducingOSS translation ToC guideline

Ari Constancio just reminded me of something I'd been meaning to ask:

Can we translate each section/chapter heading only *after* the
corresponding section/chapter is finished?  That way, anyone can look
at the table of contents to see how far along that translation is.

For example, the German version (http://producingoss.com/de/) seems to
following this convention, and thus one can easily see that it is
almost finished now, with only part of Chapter 9 still to do.

A long time ago, I talked with a few translators privately about using
this convention, but I forgot to bring it up after we created this
mailing list.  Sorry for the oversight.

If we're agreed on this convention, I'll document it on the
translations web page.

Thanks,
-Karl

Ari Constancio [EMAIL PROTECTED] writes:
 Karl,

 I just watched your presentation on Principles of Participation for
 Open Information Communities (great!) and, concerning the
 ProducingOSS translation effort, I noticed you mentioned the table of
 contents as an indicator of translation progress.

 I was not aware of that and, sometime ago, I changed titles on the
 table of contents without having any translation inside.  I'll change
 back the titles of the untranslated sections back to English.

 Probably this guideline should be made explicit.

 Cheers, Ari Constancio

___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators






   
__ 
¿Chef por primera vez?
Sé un mejor Cocinillas. 
http://es.answers.yahoo.com/info/welcome___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators


[ProducingOSS commit] r1362 - trunk/pt-pt

2008-01-02 Thread ari . constancio
Author: ari.constancio
Date: Wed Jan  2 18:35:42 2008
New Revision: 1362

Log:
* pt-pt/ch02.xml: Delete extraneous words

Modified:
   trunk/pt-pt/ch02.xml

Modified: trunk/pt-pt/ch02.xml
==
--- trunk/pt-pt/ch02.xml(original)
+++ trunk/pt-pt/ch02.xmlWed Jan  2 18:35:42 2008
@@ -51,8 +51,7 @@
 resolver o emphasisseu/emphasis problema. Está sendo escrito para resolver 
 o emphasispróprio/emphasis problema do autor, sendo depois partilhado com 
 todos, tal como se de uma doença se tratasse e o software fosse o medicamento 
-cuja distribuição se destinasse à total erradicação da epidemia./para
-eradicate the epidemic./para
+cuja distribuição se destinasse à total erradicação da epidemia./para
 
 paraThis chapter is about how to introduce a new free software
 project to the world, but many of its recommendations would sound

___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators