Re: Starting with translation to Spanish
José Manuel Puerta [EMAIL PROTECTED] writes: Finally, I'm behind a firewall at the office and I wouldn't like to bother my administrator. Is there another way to work with apart from the SVN way? (to commit changes and so) SVN commits happen over port 80, so are you sure your firewall will block them? -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
[ProducingOSS commit] r886 - trunk/ja
Author: mumumu Date: Tue Aug 7 02:32:55 2007 New Revision: 886 Log: - fixed title, author, copyright. Modified: trunk/ja/book.xml Modified: trunk/ja/book.xml == --- trunk/ja/book.xml (original) +++ trunk/ja/book.xml Tue Aug 7 02:32:55 2007 @@ -20,7 +20,7 @@ ] book id=poss lang=ja -titleオープンソースのつくりかた/title +titleオープンソースソフトウェアのつくりかた/title subtitleフリーソフトウェアプロジェクトを成功させるコツ/subtitle bookinfo @@ -31,11 +31,13 @@ contrib(著者)/contrib/author authorfirstname正弘/firstnamesurname高木/surname contrib(翻訳者)/contrib/author +authorfirstnameYoshinari/firstnamesurnameTakaoka/surname +contrib(翻訳者)/contrib/author /authorgroup editorfirstnameAndy/firstnamesurnameOram/surname/editor pagenums272 pages/pagenums !-- pubdate2005/pubdate -- - copyrightyear2005, 2006, 2007/yearholderKarl Fogel, 高木正弘, under a CreativeCommons Attribution-ShareAlike (表示・継承) license (3.0)/holder/copyright + copyrightyear2005, 2006, 2007/yearholderKarl Fogel, 高木正弘, Yoshinari Takaoka, under a CreativeCommons Attribution-ShareAlike (表示・継承) license (3.0)/holder/copyright /bookinfo !-- External entity refs -- ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Starting with translation to Spanish
Ok. If I don't succeed I will post changes here. Thanks José Karl Fogel escribió: José Manuel Puerta [EMAIL PROTECTED] writes: Well, I'm trying to use Eclipse + SVN plug-in to perform the task. Maybe, this is the problem and it is not well configured. I will try to use TortoiseSVN. Anyway, to access Internet I need to autentificate myself through the Proxy, so maybe the problem lays in this fact. If you can't get through the firewall, an alternative is to post patches here and have another Spanish translator apply them. -Karl *La informaci�n contenida en este mensaje de correo electr�nico es confidencial y puede revestir el car�cter de reservada. * *Est� dirigida exclusivamente a la persona destinataria. * *El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no est�n autorizados y pueden ser ilegales.* *Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo. * *The information in this e-mail is confidential and may be legally privileged. * *It is intended solely for the addressee. * *Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful. * *If you are not the intended recipient, please delete this e-mail. * begin:vcard fn;quoted-printable:Jos=C3=A9 Manuel Puerta Pe=C3=B1a n;quoted-printable;quoted-printable:Puerta Pe=C3=B1a;Jos=C3=A9 Manuel org;quoted-printable:TCP Sistemas e Ingenier=C3=ADa adr:;;C/ FErnandez Caro, 7;Madrid;;28027;Spain email;internet:[EMAIL PROTECTED] title:Senior Engineer tel;work:+34 91 4062758 url:http://www.tcpsi.com version:2.1 end:vcard ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
[ProducingOSS commit] r887 - trunk/ja
Author: matakagi Date: Tue Aug 7 04:01:37 2007 New Revision: 887 Log: merge r678. Modified: trunk/ja/ch09.xml Modified: trunk/ja/ch09.xml == --- trunk/ja/ch09.xml (original) +++ trunk/ja/ch09.xml Tue Aug 7 04:01:37 2007 @@ -651,30 +651,32 @@ sect1 id=copyright-assignment titleCopyright Assignment and Ownership/title -paraThere are three ways to handle copyright ownership of free code -contributed to by many people. The first is to ignore the issue of -copyright entirely (I don't recommend this). The second is to collect -a firsttermcontributor license agreement/firstterm -(firsttermCLA/firstterm) from each person who works on the -project, explicitly granting the project the right to use that -person's code. This is usually enough for most projects, and the nice -thing is that in some jurisdictions, CLAs can be sent in by email. -The third way is to get actual copyright assignments from -contributors, so that the project (i.e., some legal entity, usually a -nonprofit) is the copyright owner for everything. This is the most -legally airtight way, but it's also the most burdensome for -contributors; only a few projects insist on it./para - -paraNote that even under centralized copyright ownership, the code -remains free, because open source licenses do not give the copyright -holder the right to retroactively proprietize all copies of the code. -So even if the project, as a legal entity, were to suddenly turn -around and started distributing all the code under a restrictive -license, that wouldn't cause a problem for the public community. The -other developers would simply start a fork based on the latest free -copy of the code, and continue as if nothing had happened. Because -they know they can do this, most contributors cooperate when asked to -sign a CLA or an assignment of copyright./para +paraThere are three ways to handle copyright ownership for free code +and documentation that were contributed to by many people. The first +is to ignore the issue of copyright entirely (I don't recommend this). +The second is to collect a firsttermcontributor license +agreement/firstterm (firsttermCLA/firstterm) from each person +who works on the project, explicitly granting the project the right to +use that person's contributions. This is usually enough for most +projects, and the nice thing is that in some jurisdictions, CLAs can +be sent in by email. The third way is to get actual copyright +assignments from contributors, so that the project (i.e., some legal +entity, usually a nonprofit) is the copyright owner for everything. +This is the most legally airtight way, but it's also the most +burdensome for contributors; only a few projects insist on it./para + +paraNote that even under centralized copyright ownership, the +codefootnoteparaI'll use code to refer to both code and +documentation, from now on./para/footnote remains free, because +open source licenses do not give the copyright holder the right to +retroactively proprietize all copies of the code. So even if the +project, as a legal entity, were to suddenly turn around and started +distributing all the code under a restrictive license, that wouldn't +cause a problem for the public community. The other developers would +simply start a fork based on the latest free copy of the code, and +continue as if nothing had happened. Because they know they can do +this, most contributors cooperate when asked to sign a CLA or an +assignment of copyright./para sect2 id=copyright-assignment-none titleDoing Nothing/title ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
[ProducingOSS commit] r889 - trunk/ja
Author: matakagi Date: Tue Aug 7 04:04:53 2007 New Revision: 889 Log: - merge r811. Modified: trunk/ja/ch07.xml Modified: trunk/ja/ch07.xml == --- trunk/ja/ch07.xml (original) +++ trunk/ja/ch07.xml Tue Aug 7 04:04:53 2007 @@ -1596,7 +1596,16 @@ subject of which releases the project will be making in the near- to medium-term future, and what features will be in them, without at first mentioning anything about dates, except for rough guesses with -wide margins of error. By nailing down feature sets early, you reduce +wide margins of errorfootnoteparaFor an alternative approach, you +may wish to read Martin Michlmayr's Ph.D. thesis citetitleQuality +Improvement in Volunteer Free and Open Source Software Projects: +Exploring the Impact of Release Management/citetitle +(ulink url=http://www.cyrius.com/publications/michlmayr-phd.html/). +It is about using time-based release processes, as opposed to +feature-based, in large free software projects. Michlmayr also gave a +talk at Google on the subject, available on Google Video at +ulink url=http://video.google.com/videoplay?docid=-5503858974016723264; +/./para/footnote. By nailing down feature sets early, you reduce the complexity of the discussion centered on any individual release, and therefore improve predictability. This also creates a kind of inertial bias against anyone who proposes to expand the definition of ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
[ProducingOSS commit] r890 - trunk/ja
Author: matakagi Date: Tue Aug 7 04:07:02 2007 New Revision: 890 Log: - merge r811, r812, r816, r817, and r818. Modified: trunk/ja/ch06.xml Modified: trunk/ja/ch06.xml == --- trunk/ja/ch06.xml (original) +++ trunk/ja/ch06.xml Tue Aug 7 04:07:02 2007 @@ -52,9 +52,11 @@ mechanisms a priority for everyone in the project.footnoteparaThere has been some interesting academic research on this topic; for example, see citetitleGroup Awareness in Distributed Software -Development/citetitle by Gutwin, Penner, and Schneider (this used to -be available online, but seems to have disappeared, at least -temporarily; use a search engine to find it)./para/footnote/para +Development/citetitle by Gutwin, Penner, and Schneider. This paper +was online for a while, then unavailable, then online again at ulink +url=http://www.st.cs.uni-sb.de/edu/empirical-se/2006/PDFs/gutwin04.pdf/. +So try there first, but be prepared to use a search engine if it moves +again./para/footnote/para /simplesect @@ -1819,13 +1821,14 @@ partly because the target audience is always ill-defined: given that most or all posts are publicly accessible, the project doesn't have full control over the impression the world gets. Someonemdash;say, a -ulink url=slashdot.org/ editormdash;may draw millions of readers' -attention to a post that no one ever expected to be seen outside the -project. This is a fact of life that all open source projects live -with, but in practice, the risk is usually small. In general, the -announcements that the project most wants publicized are the ones that -will be most publicized, assuming you use the right mechanisms to -indicate relative newsworthiness to the outside world./para +ulink url=http://slashdot.org/;slashdot.org/ulink +editormdash;may draw millions of readers' attention to a post that no +one ever expected to be seen outside the project. This is a fact of +life that all open source projects live with, but in practice, the +risk is usually small. In general, the announcements that the project +most wants publicized are the ones that will be most publicized, +assuming you use the right mechanisms to indicate relative +newsworthiness to the outside world./para paraFor major announcements, there tend to be four or five main channels of distribution, on which announcements should be made as @@ -1872,7 +1875,7 @@ entry, that entry goes onto the Freshmeat change list for the day. The change list is updated not only on Freshmeat itself, but on various portal sites (including -ulink url=slashdot.org/) which are watched eagerly by +ulink url=http://slashdot.org/) which are watched eagerly by hordes of people. Freshmeat also offers the same data via RSS feed, so people who are not subscribed to your project's own RSS feed might still see the announcement ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Starting with translation to Spanish
Hola José Welcome, I'm Alejandro, one of the two volunteers translating the book to ES. First, let me put you up to date on our progress. Chapters 00, 01 and 02 are ready. Yesterday I finished reviewing them all trying to find problems and fixing them, so I'm pretty happy with all except some issues that I still haven't been able to figure out. Right now, I'm working on ch03 and Rafael is with ch04 so if you want to start with ch05 or any of the Appendix go for it as soon as you've got your problems with SVN ready. There's a file named convenciones.txt where I've been translating some commonly used expressions so we can have a reference that will enable us to be consistent through the book. For example, open source software can be translated in many ways, so it's the best if we stick to a few translations like: software open source, software código abierto, etc. I don't know if Rafael has seen this file and his thoughts about it are welcome. Anyway, welcome and thanks for the help. Bye! Alejandro Ayuso Systems Engineer Linux User: 438022 My Blog: monocaffe.blogspot.com - Mensaje original De: José Manuel Puerta [EMAIL PROTECTED] Para: producingoss-translators@red-bean.com Enviado: martes, 7 de agosto, 2007 9:07:29 Asunto: Starting with translation to Spanish Hello all, My name is Jose, I'm from Spain and I'm new in this works so I will need some info from you. I've joined to the Spanish translation team, and I would like to know which chapters are available (I don't want to destroy other's work nor to work in the same subject as another one else) Just add I haven't work with SVN but I'm using CVS all the time, therefore SVN is not as unfamiliar as I expected. On the other hand, which kind of Spanish are we using? Is there a Spanish translation project leader? In other projects that I have participated we used to discuss lot of terms and finally a word translation list was created (project LUCAS, INSFLUG, etc). I'm not pretty sure if here you're following a similar policy. Finally, I'm behind a firewall at the office and I wouldn't like to bother my administrator. Is there another way to work with apart from the SVN way? (to commit changes and so) Thanks in advance. Best regards, José *La información contenida en este mensaje de correo electrónico es confidencial y puede revestir el carácter de reservada. * *Está dirigida exclusivamente a la persona destinataria. * *El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no están autorizados y pueden ser ilegales.* *Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo. * *The information in this e-mail is confidential and may be legally privileged. * *It is intended solely for the addressee. * *Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful. * *If you are not the intended recipient, please delete this e-mail. * Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: How to contribute to Spanish translation
Hi! My bad! I didn't make the commit of the convenciones.txt file. It's there now, please update. Aldo: I don't think anyone has started with chapter 6 so please feel free to go on. Some remarks, the id and linkend parameters aren't being translated, just the content. For example: sect2 id=some-section titleEl título sí lo traducimos/title xref linkend=some-section Hope this helps. Good luck! Bye Alejandro Ayuso Systems Engineer Linux User: 438022 My Blog: monocaffe.blogspot.com - Mensaje original De: Aldo Vadillo Batista [EMAIL PROTECTED] Para: producingoss-translators@red-bean.com Enviado: miércoles, 8 de agosto, 2007 0:13:53 Asunto: How to contribute to Spanish translation Hello everybody, My name is Aldo and I want to help with the Spanish translation. I've just read Rafael's email on which he comments that chapters from 03 to 04 have been translated. I could start translating chapter number 06 if anyone is translating it. Where is the file convenciones.txt located? Thanks, Aldo ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
[ProducingOSS commit] r896 - trunk/es
Author: alejandroayuso Date: Tue Aug 7 20:00:51 2007 New Revision: 896 Log: more of ch03... 90% Modified: trunk/es/ch03.xml Modified: trunk/es/ch03.xml == --- trunk/es/ch03.xml (original) +++ trunk/es/ch03.xml Tue Aug 7 20:00:51 2007 @@ -2119,110 +2119,123 @@ /sect2 sect2 id=bug-filtering -titlePre-Filtering the Bug Tracker/title +titlePre-filtrado del gestor de fallos/title -paraMost issue databases eventually suffer from the same problem: a -crushing load of duplicate or invalid issues filed by well-meaning but -inexperienced or ill-informed users. The first step in combatting -this trend is usually to put a prominent notice on the front page of -the bug tracker, explaining how to tell if a bug is really a bug, how -to search to see if it's already been filed, and finally, how to -effectively report it if one still thinks it's a new bug./para - -paraThis will reduce the noise level for a while, but as the number -of users increases, the problem will eventually come back. No -individual user can be blamed for it. Each one is just trying to -contribute to the project's well-being, and even if their first bug -report isn't helpful, you still want to encourage them to stay -involved and file better issues in the future. In the meantime, -though, the project needs to keep the issue database as free of junk -as possible./para - -paraThe two things that will do the most to prevent this problem -are: making sure there are people watching the bug tracker who have -enough knowledge to close issues as invalid or duplicates the moment -they come in, and requiring (or strongly encouraging) users to confirm -their bugs with other people before filing them in the tracker./para - -paraThe first technique seems to be used universally. Even projects -with huge issue databases (say, the Debian bug tracker at -ulink url=http://bugs.debian.org//, which contained 315,929 issues -as of this writing) still arrange things so that -emphasissomeone/emphasis sees each issue that comes in. It may be -a different person depending on the category of the issue. For -example, the Debian project is a collection of software packages, so -Debian automatically routes each issue to the appropriate package -maintainers. Of course, users can sometimes misidentify an issue's -category, with the result that the issue is sent to the wrong person -initially, who may then have to reroute it. However, the important -thing is that the burden is still sharedmdash;whether the user -guesses right or wrong when filing, issue watching is still -distributed more or less evenly among the developers, so each issue is -able to receive a timely response./para - -paraThe second technique is less widespread, probably because it's -harder to automate. The essential idea is that every new issue gets -buddied into the database. When a user thinks he's found a problem, -he is asked to describe it on one of the mailing lists, or in an IRC -channel, and get confirmation from someone that it is indeed a bug. -Bringing in that second pair of eyes early can prevent a lot of -spurious reports. Sometimes the second party is able to identify that -the behavior is not a bug, or is fixed in recent releases. Or she may -be familiar with the symptoms from a previous issue, and can prevent a -duplicate filing by pointing the user to the older issue. Often it's -enough just to ask the user Did you search the bug tracker to see if -it's already been reported? Many people simply don't think of that, -yet are happy to do the search once they know someone's -emphasisexpecting/emphasis them to./para - -paraThe buddy system can really keep the issue database clean, but -it has some disadvantages too. Many people will file solo anyway, -either through not seeing, or through disregarding, the instructions -to find a buddy for new issues. Thus it is still necessary for -volunteers to watch the issue database. Furthermore, because most new -reporters don't understand how difficult the task of maintaining the -issue database is, it's not fair to chide them too harshly for -ignoring the guidelines. Thus the volunteers must be vigilant, and -yet exercise restraint in how they bounce unbuddied issues back to -their reporters. The goal is to train each reporter to use the -buddying system in the future, so that there is an ever-growing pool -of people who understand the issue-filtering system. On seeing an -unbuddied issue, the ideal steps are:/para +paraMuchas de las bases de datos de fallos sufren eventualmente del mismo +problema: una cantidad devastadora de fallos duplicados o invalidos hechos +por usuarios bien intencionados pero sin experiencia o poco informados. El +primer paso para combatir esta tendencia es, por lo general, colocar un vistoso +aviso en la página principal del gestor de fallos, explicando como saber si +un bug es realmente un bug, como buscar si el bug ya
[ProducingOSS commit] r897 - trunk/ml
Author: zs Date: Tue Aug 7 22:14:03 2007 New Revision: 897 Log: several more translated Modified: trunk/ml/ch01.xml Modified: trunk/ml/ch01.xml == --- trunk/ml/ch01.xml (original) +++ trunk/ml/ch01.xml Tue Aug 7 22:14:03 2007 @@ -42,8 +42,8 @@ Memang, bahagian penting dalam menjalankan projek sumber terbuka ialah bekerja dengan lancar bersama yang lain, projek berkaitan. Dalam jangka panjang, setiap projek yang berjaya menyumbang kepada kesejahteraan keseluruhan, badan sedunia bagi perisian percuma. /para - /simplesect + simplesect para @@ -69,8 +69,8 @@ persoalan mereka untuk sementara waktu sebelum melihat sebarang faedah atas kehadiran mereka. Sebagai pembangun Jamie Zawinski menyatakan masalah ini pada peringkat awal projek Mozilla: /para -blockquote +blockquote para emphasis Sumber terbuka memang berkesan, namun ianya pasti bukan penyelesaian. @@ -80,284 +80,254 @@ /emphasis /para -para(from -emphasis role=boldulink - url=http://www.jwz.org/gruntle/nomo.html/ -/emphasis) +para(from emphasis role=boldulink + url=http://www.jwz.org/gruntle/nomo.html//emphasis) /para /blockquote para -A related mistake is that of skimping on presentation and -packaging, figuring that these can always be done later, when the -project is well under way. Presentation and packaging comprise a wide -range of tasks, all revolving around the theme of reducing the barrier -to entry. Making the project inviting to the uninitiated means -writing user and developer documentation, setting up a project web -site that's informative to newcomers, automating as much of the -software's compilation and installation as possible, etc. Many -programmers unfortunately treat this work as being of secondary -importance to the code itself. There are a couple of reasons for -this. First, it can feel like busywork, because its benefits are most -visible to those least familiar with the project, and vice versa. -After all, the people who develop the code don't really need the -packaging. They already know how to install, administer, and use the -software, because they wrote it. Second, the skills required to do -presentation and packaging well are often completely different from -those required to write code. People tend to focus on what they're -good at, even if it might serve the project better to spend a little -time on something that suits them less. xref -linkend=getting-started/ discusses presentation and packaging -in detail, and explains why it's crucial that they be a priority from -the very start of the project./para - -paraNext comes the fallacy that little or no project management is -required in open source, or conversely, that the same management -practices used for in-house development will work equally well on an -open source project. Management in an open source project isn't -always very visible, but in the successful projects, it's usually -happening behind the scenes in some form or another. A small thought -experiment suffices to show why. An open source project consists of a -random collection of programmersmdash;already a notoriously -independent-minded categorymdash;who have most likely never met each -other, and who may each have different personal goals in working on -the project. The thought experiment is simply to imagine what would -happen to such a group emphasiswithout/emphasis management. -Barring miracles, it would collapse or drift apart very quickly. -Things won't simply run themselves, much as we might wish otherwise. -But the management, though it may be quite active, is often informal, -subtle, and low-key. The only thing keeping a development group -together is their shared belief that they can do more in concert than -individually. Thus the goal of management is mostly to ensure that -they continue to believe this, by setting standards for -communications, by making sure useful developers don't get -marginalized due to personal idiosyncracies, and in general by making -the project a place developers want to keep coming back to. Specific -techniques for doing this are discussed throughout the rest of this -book./para - -paraFinally, there is a general category of problems that may be -called failures of cultural navigation. Ten years ago, even five, -it would have been premature to talk about a global culture of free -software, but not anymore. A recognizable culture has slowly emerged, -and while it is certainly not monolithicmdash;it is at least as prone -to internal dissent and factionalism as any geographically bound -culturemdash;it does have a basically consistent core. Most -successful open source projects exhibit some or all of the -characteristics of this core. They reward certain types of behaviors, -and punish others; they create an atmosphere that encourages unplanned -participation, sometimes at the expense of central coordination; they -have concepts
Re: How to contribute to Spanish translation
Aldo Vadillo Batista [EMAIL PROTECTED] writes: My name is Aldo and I want to help with the Spanish translation. I've just read Rafael's email on which he comments that chapters from 03 to 04 have been translated. I could start translating chapter number 06 if anyone is translating it. Where is the file convenciones.txt located? It's inside the Spanish translation area, at: http://svn.red-bean.com/repos/producingoss/trunk/es/convenciones.txt Welcome to the team! -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
