Welcome, new translators!
Welcome, new translators of Producing Open Source Software! This mailing list is the first place to ask for help with anything. (You've all received private emails with your username and password.) For some of you, your translation might already be under way. In that case, you should probably ask the people already working on it what's needed -- it may be that review is needed more than new translation. Here are all the new translators: Spanish: Juan Diego Pérez [EMAIL PROTECTED] Diego Gómez [EMAIL PROTECTED] Manuel Sanchez [EMAIL PROTECTED] José Manuel Puerta [EMAIL PROTECTED] Emilio Casbas [EMAIL PROTECTED] Aldo Vadillo Batista [EMAIL PROTECTED] Stone Stone [EMAIL PROTECTED] Miguel Angel Alvarez [EMAIL PROTECTED] Francisco Urbano Garcia [EMAIL PROTECTED] Persian (Farsi): Nasser Ghanemzadeh [EMAIL PROTECTED] Brazilian Portuguese: Paulo Barros [EMAIL PROTECTED] Ricardo-org [EMAIL PROTECTED] Roger Reghin [EMAIL PROTECTED] Lucas Fernandes [EMAIL PROTECTED] Eduardo Jorge [EMAIL PROTECTED] Daniel R Matos [EMAIL PROTECTED] Josenaldo de Oliveira Matos Filho [EMAIL PROTECTED] Portuguese (maybe Brazilian, not sure yet): Ari Constancio [EMAIL PROTECTED] Japanese: Yoshinari Takaoka [EMAIL PROTECTED] Best, -Karl Fogel ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
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
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
Re: [ProducingOSS commit] r955 - trunk/pt-pt
[EMAIL PROTECTED] writes: Modified: trunk/pt-pt/book.xml By the way, Ari, feel free to add your own name here as a translator, the way the other translations have done. Best, -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r955 - trunk/pt-pt
Ari Constancio [EMAIL PROTECTED] writes: It depends. Strict translation of open source would be código aberto and, indeed, it is sometimes used in institutional conferences. In ordinary conversations, I never use código aberto (always open source) but free software is translated as software livre. Karl decided to freely interchange open source software with free software, as can be seen from the title and subtitle. So, I decided to write open source software the same as free software (i.e. software livre). Confusing, right? :) You raise an interesting issue. Is every translator writing open source in the title? At least the french translation uses libre. What do you think, Karl? I think there wouldn't even be two different terms if English didn't have this stupid ambiguity. Sigh :-). But because English needed with two terms, now every language is acquiring them, even though the distinction is unnecessary. I'm not sure what to recommend, because I don't know what the two terms connote in other languages. Also, the two terms may have different relative popularity in other languages. For example, in English, the term open source has essentially won -- almost no one, outside our circle of specialists, knows what free software means. (Sorry, I know that's disappointing to some, but it's time to face the facts :-) ). But in other languages, perhaps terms like software livre are dominant and more widely used than código aberto or whatever the equivalent is for that language. You know the answer to that better than I do. I'd be fine with just software livre. Feel free to adjust the section that discusses the two English terms, to make it explain that, in English, the title of this book uses both terms, but that we may not reflect that in all languages, because there is no need to. -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Translations status inquiry.
Sebastian Menge [EMAIL PROTECTED] writes: 1. Reader finds translation on the homepage 2. starts to read, finds unpleasant things. 3. fills out a html-form on the same page 4. Translators on this list review the comments, fix them, 5. Something has to be done with old comments: delete or answer fixed It's a bit vague, but that way many ppl could contribute: No mailinglist, docbook or editing needed, just their language and submitting a html form. I have absolutely no idea about the technical side :-) Things that come to my mind are blogs or wikis. No idea how to integrate that with the static html... That's a really good idea, and it would satisfy Ari's concerns too. I'm not sure how to implement it, though. Does anyone know about existing web-based annotation sites? We need to integrate it into the generated HTML, not sure how to do that... ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Translations status inquiry.
Sebastian Menge [EMAIL PROTECTED] writes: Am Sun, 19 Aug 2007 19:26:03 +0200 schrieb Reiner Pittinger: I think that a public comment system is not necessary, as people who want to contribute already can by applying to Karl. And a comment system would not only mean more work to manage, but I could also think of many users writing e-mails like Hey, I submitted an error on line XYZ 15 Minutes ago, and you did not yet fix it. Remember this one: http://www.producingoss.com/en/managing-volunteers.html#users-to-volunteers Let's make the burden to contribute for them as low as possible ... I think I agree -- we should make it as easy as possible to comment on the translations (and on the original, for that matter). If there are too many comments to handle, we can always shut it down, but we'll never know if we don't try it. However, it will take some time to set up. I'm looking at the Django system and seeing if I can improvise something, but it'll take awhile. If any of you have the skills to set it up (especially the client-side -- I can easily set up any kind of receiver CGI or whatever on the server-side), please jump in. -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1112 - trunk/pt-pt
[EMAIL PROTECTED] writes: Log: End of 'accidental resistance' Sometimes a log message is unintentionally funny :-). -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: SVN Client for Mandrake 10.1 ?
Eko Budhi S [EMAIL PROTECTED] writes: i am trying to install SVN client for Mandrake 10.1 but get no executable yet. I have tried subversion-1.4.4-1.i386.rpm but get dependency failure ... # rpm -i /home/ekobs/subversion-1.4.4-1.i386.rpm error: Failed dependencies: apr-util = 0.9.7 is needed by subversion-1.4.4-1 db4 = 4.0.14 is needed by subversion-1.4.4-1 libcom_err.so.3 is needed by subversion-1.4.4-1 libcrypto.so.4 is needed by subversion-1.4.4-1 libdb-4.0.so is needed by subversion-1.4.4-1 libneon.so.24 is needed by subversion-1.4.4-1 libssl.so.4 is needed by subversion-1.4.4-1 neon = 0.24.7 is needed by subversion-1.4.4-1 Any idea about Java version for SVN client ? For a pure Subversion question, I highly recommend posting to [EMAIL PROTECTED] You don't have to be subscribed to that list to post to it (though you might want to subscribe anyway). By the way, it was completely okay to post here as well! But there are more Subversion experts on [EMAIL PROTECTED], and I'll bet there are some Mandrake users there who will know what to do. (You could also try just installing the dependencies. I think the dependency tree will bottom out pretty quickly.) Best, -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Error on commit ...
Eko Budhi S [EMAIL PROTECTED] writes: Now i am working on translating Ch06 ... and ready to commit, but get this failure ... Attached is the screenshot. It say : svn : Commit failed (details follow) svn MKACTIVITY request failed on '...' :400 Bad Request (http://svn.red-bean.com) Need assistance ... I have never used JavaSVN, so I can't say for sure what the problem is. Did you give it your username and password? ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS lock] /trunk/id/ch06.xml
[EMAIL PROTECTED] writes: Comment: ns0:owner xmlns:ns0=DAV:i want to commit. do i need a lock ?/ns0:owner Answer: No, you don't need a lock :-). It's better not to use SVN locking for this. ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: svn
Manuel Barkhau [EMAIL PROTECTED] writes: Incase nobody has noticed, the svn server appears to be down, or ist it just me? What symptom are you seeing, exactly? -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Translations status.
Reiner Pittinger [EMAIL PROTECTED] writes: After a long pause I will return on revising the german chapters, also my main aim when joining the project. Maybe we can enjoy a complete german translation and revision at the end of this year, as a point in time easy to remember... That would be great! Note that I will be offline for all of December, until after January 1st. So if a translation is finished in December, there may be a delay before I link to it from the front page, I hope that's okay. (Actually, though, the translators could just commit the changes to the front page anyway, when the translation is ready, so maybe it doesn't matter so much that I'll be on vacation.) -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Using Japanese (and other) translations in a talk.
I'll be giving a keynote talk at a large Japanese corporation (they're having a symposium on open-source and open-information systems) in two weeks. During the talk, I'm planning to discuss this translation project a bit. I'll show progress of all the translations, especially those that are nearly done. Yoshinari Takaoka, I'll mention your work in particular, since this is a Japanese company, and I'll point out that the more translators are working on it, the faster it will get done. (My hope is that some people there may get interested in helping out, or perhaps even interested in funding you.) I just wanted to let you know now, in case you had commits pending. The more of the translation is done, the more impressive it will be to them -- although of course what's done now is already very impressive! -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1309 - trunk/es
[EMAIL PROTECTED] writes: Log: Chapter 9: Copyright ownership: doing nothing. That's a funny log message... but I know what you meant! :-) ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [PATCH] Chapter 2
Ari Constancio [EMAIL PROTECTED] writes: I'd like to propose this tiny change in the source :) : Agreed -- please commit it directly to the English! Thanks for the suggestion, -Karl Index: ch02.xml === --- ch02.xml (revision 1352) +++ ch02.xml (working copy) @@ -25,7 +25,7 @@ to free software was that a personal itch happened to be the most frequent motivation for starting a free software project./para -paraThis is still how most free projects are started, but less so +paraThis is still how most free software projects are started, but less so now than in 1997, when Raymond wrote those words. Today, we have the phenomenon of organizationsmdash;including for-profit corporationsmdash;starting large, centrally-managed open source Cheers, Ari Constancio ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
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
Re: Question
Peng Wang [EMAIL PROTECTED] writes: Thanks very much for your message. I was able to open the files using Word and did some translation in UTF-8 format back in the summer on another computer. I don't know why it's not working on the computer I'm using now. Thanks again. I think we somehow have to convince Word (on your current computer) that these are text files. One really simple way to do that would be to rename them to .txt files while working on them, then rename back to .xml to check in the changes. For example: 1. update (TortoiseSVN update) the files 2. rename ch00.xml to ch00.txt 3. edit ch00.txt in Word 4. rename ch00.txt back to ch00.xml 5. commit the changes Does that do the trick? -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1370 - in trunk: . pl
[EMAIL PROTECTED] writes: Log: [EMAIL PROTECTED]: alpha | 2008-01-07 23:00:01 +0100 Spam protection section started. Thanks, Adam! Note that we have a convention (which I really should document) of not translating a section title until the entire section's translation is complete. That way, we can look at the Table Of Contents to see how far along the entire translation is. -Karl Modified: trunk/ (props changed) trunk/pl/ch03.xml Modified: trunk/pl/ch03.xml == --- trunk/pl/ch03.xml (original) +++ trunk/pl/ch03.xml Mon Jan 7 16:01:52 2008 @@ -305,18 +305,17 @@ !-- == subsection === -- sect2 id=spam-prevention -titleSpam Prevention/title +titleUnikanie spamu/title -paraBetween when this sentence is written and when it is published, -the Internet-wide spam problem will probably double in -severitymdash;or at least it will feel that way. There was a time, -not so long ago, when one could run a mailing list without taking any -spam-prevention measures at all. The occasional stray post would -still show up, but infrequently enough to be only a low-level -annoyance. That era is gone forever. Today, a mailing list that -takes no spam prevention measures will quickly be submerged in junk -emails, to the point of unusability. Spam prevention is -mandatory./para +paraDo czasu, gdy te słowa zostaną opublikowane, problem spamu w +Internecie zapewne urośnie dwukrotniemdash;lub przynajmniej można będzie +odnieść takie wrażenie. Jeszcze nie tak dawno temu można było prowadzić +listę dyskusyjną bez żadnych filtrów antyspamowych. Od czasu do czasu +zagubiona wiadomość pojawiła się na liście, ale działo się to na tyle +rzadko, że nie sprawiało większego kłopotu. Te czasy już minęły. Dziś lista +dyskusyjna, która nie stosuje zabezpieczeń antyspamowych, zostanie szybko +zalana śmieciowymi mailami tak, że stanie się nieużywalna. Ochrona +antyspamowa jest koniecznością./para paraWe divide spam prevention into two categories: preventing spam posts from appearing on your mailing lists, and preventing your ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1350 - trunk/es
[EMAIL PROTECTED] writes: Log: Fixed the spanish chapter6. Compilation OK. I just discovered this and another commit mail from you were accidentally filtered into my spam folder by my spamwall :-(. I've moved them out of there; hopefully future such mails will not be categorized as spam. Anyway, congratulations on finishing Chapter 6! -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1350 - trunk/es
Karl Fogel [EMAIL PROTECTED] writes: Anyway, congratulations on finishing Chapter 6! I should say: congratulations to all the translators on that team, not only the one who happened to commit a finishing revision :-). ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1374 - trunk
Ari Constancio [EMAIL PROTECTED] writes: There seems to be a conflict in this web page (trunk/translations.html): $ lynx -dump producingoss.com/translations.html [snip...] * [9]Polski (Polish) Bartek GF3rny, Jacek Medrzycki, L/ukasz Nowak, Daniel Koc .mine === * [10]Deutsch (German) Manuel Barkhau, Sebastian Menge, Reiner Pittinger * [11]EspaF1ol (Spanish) Rafael Martilotti, Alejandro Ayuso, Francisco Urbano GarcEDa, JosE9 Manuel Puerta PeF1a, Pedro AndrE9s Bonilla Polo, Christian LF3pez EspEDnola * [12]A5AC (Japanese) A8 A3 (TAKAGI Masahiro), Takaoka Yoshinari .r1374 * [13]Dansk (Danish) Mikkel Kirkgaard Nielsen Hmmm. The conflict is in your working copy only -- it's not on the site. Did you edit the file? The conflict markers are not in the repository... However, my working copy doesn't show anything strange. Do you mean that when you point your web browser at the file in your working copy, you don't see the conflicts? That might be bcause the conflict markers are also HTML special characters, so they don't display as one would expect in when viewed via the browser. -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1374 - trunk
Ari Constancio [EMAIL PROTECTED] writes: Karl, I apologize for misguiding you. I did mention my local file (trunk/translations.html) and then put the output of 'lynx -dump producingoss.com/translations.html' . No wonder you got confused :). No problem -- computers are hard, I try to avoid 'em :-). ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: French translation
Alejandro Ayuso [EMAIL PROTECTED] writes: Yes, it's very interesting this point and why did you use that wiki and not the more popular Wikibooks.org By the way, if I knew how to have a wiki-like interface for translation, but still get XML results (so we can preserve the same master format), I'd go with the wiki. I know using Subversion is not the most convenient way to do things for many people. The problem is just that converting from wiki to DocBook XML is also not easy. But if anyone knows a way to do it, I'd be happy to help switch us over to a wiki-like interface! -Karl Alejandro Ayuso Systems Engineer Linux User: 438022 My Blog: monocaffe.blogspot.com - Mensaje original De: Manuel Barkhau [EMAIL PROTECTED] Para: [EMAIL PROTECTED] CC: producingoss-translators@red-bean.com Enviado: domingo, 17 de febrero, 2008 17:21:35 Asunto: Re: French translation Bonjour mon amis, on a different note, maybe you would like to share you're experience with the wiki format vs. subversion. How much participation have you received apart from the main translators. How many translators joined you're effort, quality of their work etc. Something I especially miss with the current format, are reader statistics and feedback. ciao, Manuel ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators __ ¿Con Mascota por primera vez? Sé un mejor Amigo. Entra en Yahoo! Respuestas 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-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: French translation
Manuel Barkhau [EMAIL PROTECTED] writes: on a different note, maybe you would like to share you're experience with the wiki format vs. subversion. How much participation have you received apart from the main translators. How many translators joined you're effort, quality of their work etc. Something I especially miss with the current format, are reader statistics and feedback. Yes, please -- I also would be *very* interested to hear about the wiki experiences. If it made a difference in participation, that's an important lesson for me (and others). Thanks, -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: French translation
Bertrand Florat [EMAIL PROTECTED] writes: Just to keep you in touch, Etienne and myself moved to the Framalang wiki to finish the book translation. We plan to port all its content to docbook format once done (it's about 90 % done now). I think it could be a good idea to link the French translation from http://www.producingoss.com/fr/ to http://www.framalang.org/wiki/Producing_Open_Source_Software so people can benefit from the almost-done translation right now, and it could bring new translators. What do you think ? Done in r1411 and r1412. If you'd like to translate my notes, though, please do! They should really be in French, not English :-). -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1418 - trunk/th
[EMAIL PROTECTED] writes: Log: Thai: Translate ch00 (Topic name) Thai: Translate ch09 (Start to Free Software terminology first paragraph) Thai: Add Dictionary define (dict.txt) Yay! And welcome to the team(s)... -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: German Translation Status
Manuel Barkhau [EMAIL PROTECTED] writes: Progress, although steady, isn't as I had hoped. I've got too many things going on right now, very little time for poss. To bring this to a finish, at least from my point of view, I will finish the last chapter and as Karl suggested post that version as a draft. From there on I won't be contributing much, or rather, the translation will be in what I would consider a readable state in about 2 years, if at all. Hopefully others will pick up the work before then. Manuel, thank you for bringing the German translation so far -- to get to draft completion is a huge thing. (And perhaps the draft label just reflects high standards?) We should post it as a completed translation, I think, and label it draft mainly that others will feel free offer edits as they see fit. I think we will probably get some people, since it will get more readers once it's announced as complete. ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: German Translation Status
Karl Fogel [EMAIL PROTECTED] writes: Manuel, thank you for bringing the German translation so far -- to get to draft completion is a huge thing. (And perhaps the draft label just reflects high standards?) We should post it as a completed translation, I think, and label it draft mainly that others will feel free offer edits as they see fit. I think we will probably get some people, since it will get more readers once it's announced as complete. Okay, in r1436 I linked to the German translation from the front page, as it is complete. Please feel free to correct any grammatical errors I made in the German. Also, I am horrible at web site design, so if anyone has an idea for a better way to lay out the page (especially to include the other translations when they're done), please go for it! :-) I know the front page is kind of klunky. I'm just basically a text-only person and don't have much graphical sense. ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1450 - trunk/ja
Yoshinari Takaoka [EMAIL PROTECTED] writes: [EMAIL PROTECTED] writes: Log: - Translated Releases and Daily Development section. -- I'm ashamed to read this section ... :( ? :-) I cound not follow the discipline never mix unrelated changes in the same commit in real project, so by reading this section, I'm covered with shame. :) Heh! Well, now I know my book has an effect on someone :-). ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: French translation completed on Framabook
Etienne Savard [EMAIL PROTECTED] writes: I just want to let you know that Framabook's folks have finished the translation of the POSS book. They are now ready to start the reviewing process of the whole book. I will keep you posted on the progress. Thank you so much, that's great news! I'm CC'ing our translators list, so any French speakers there can join the review process if they want. Can you repost the URL, so they know where to look? Would you like me to link to the Framabook version from the front page yet, or should we wait until the review process is finished? Best, -Karl Fogel ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Minor change made to section on copyright assignment.
Hey folks, if you've already translated this part, you might want to
look at this change -- it adds a note about jurisdictional issues.
I tried to insert the footnote into the German translation myself, but I
might have messed it up; please correct it if so :-).
Best,
-Karl
[EMAIL PROTECTED] writes:
Author: kfogel
Date: Wed Jul 30 09:28:14 2008
New Revision: 1479
Log:
* en/ch09.xml
(Copyright Assignment and Ownership): Add a footnote about
jurisdictional differences in copyright law.
* de/ch09.xml
(Zuweisung von Urheberrechten): Try to do the same thing for the
German translation, while hoping that someone who really knows
German will make sure I've put this in the right place.
Patch by: Uwe König u.koenig{_AT_}ifu.com
(He provided the wording, I provided the placement.)
Modified:
trunk/de/ch09.xml
trunk/en/ch09.xml
Modified: trunk/de/ch09.xml
==
--- trunk/de/ch09.xml (original)
+++ trunk/de/ch09.xml Wed Jul 30 09:28:14 2008
@@ -665,7 +665,11 @@
üblicherweise ein gemeinnützige Organisation) der Inhaber aller
Urheberrechte ist. Rechtlich gesehen, ist das die am ehesten wasserdichte
Lösung, aber auch die am Aufwändigsten für die Beteiligten, weshalb nur
-wenige Projekte darauf bestehen./para
+wenige Projekte darauf bestehen.footnoteparaDie Übertragung von
+bestimmten Rechten ist, im Gegensatz zum amerikanischen copyright,
+nach deutschem Urheberrecht nicht möglich. Aus diesem Grund sollte bei
+Open-Source-Lizenzen genau geprüft werden, wie diese nach deutschem
+Recht einzuordnen sind./para/footnote/para
paraBeachten Sie, dass selbst bei einem Zentralen Inhaber des
Urheberrechts, der Code immernoch frei ist, denn Open Source Lizenzen
Modified: trunk/en/ch09.xml
==
--- trunk/en/ch09.xml (original)
+++ trunk/en/ch09.xml Wed Jul 30 09:28:14 2008
@@ -663,7 +663,11 @@
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
+burdensome for contributors; only a few projects insist on
+it.footnoteparaAlso, actual copyright transferral is subject to
+national law, and licenses designed for the United States may
+encounter problems elsewhere (e.g., in Germany, where it's apparently
+not possible to transfer copyright)./para/footnote/para
paraNote that even under centralized copyright ownership, the
codefootnoteparaI'll use code to refer to both code and
___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators
___
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1481 - trunk/zh
[EMAIL PROTECTED] writes: New Revision: 1481 Log: * ch02.xml: finished Wow, that's fast work! Thank you, Rock Sun. (I saw that you're going back and checking over later, which is great. I wish my Chinese were good enough to help you with this, but it's not... :-( ). Some of the other Chinese translators might be able to help with review, though. -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1507 - trunk/it
[EMAIL PROTECTED] writes: Log: Cambiato da giovannigiorgio Welcome, Giovanni! If you ever have questions about the translation process, just ask on [EMAIL PROTECTED] The other translators and I are all subscribed to this list. Best, -Karl Modified: trunk/it/ch01.xml Modified: trunk/it/ch01.xml == --- trunk/it/ch01.xml (original) +++ trunk/it/ch01.xml Sat Oct 4 06:16:09 2008 @@ -4,50 +4,17 @@ simplesect -paraMost free software projects fail./para +paraLa maggioranza dei progetti di software libero fallisce./para -paraWe tend not to hear very much about the failures. Only -successful projects attract attention, and there are so many free -software projects in totalfootnoteparaSourceForge.net, one popular +paraNoi tendiamo a non dare molto ascolto alla notizia di questi fallimenti. Solo i progetti che hanno successo attraggono l'attenzione e ci sono tanti progetti di software libero in totalefootnoteparaSourceForge.net, one popular hosting site, had 79,225 projects registered as of mid-April 2004. This is nowhere near the total number of free software projects on the Internet, of course; it's just the number that chose to use -SourceForge./para/footnote that even though only a small -percentage succeed, the result is still a lot of visible projects. We -also don't hear about the failures because failure is not an event. -There is no single moment when a project ceases to be viable; people -just sort of drift away and stop working on it. There may be a moment -when a final change is made to the project, but those who made it -usually didn't know at the time that it was the last one. There is -not even a clear definition of when a project is expired. Is it when -it hasn't been actively worked on for six months? When its user base -stops growing, without having exceeded the developer base? What if -the developers of one project abandon it because they realized they -were duplicating the work of anothermdash;and what if they join that -other project, then expand it to include much of their earlier effort? -Did the first project end, or just change homes?/para - -paraBecause of such complexities, it's impossible to put a precise -number on the failure rate. But anecdotal evidence from over a decade -in open source, some casting around on SourceForge.net, and a little -Googling all point to the same conclusion: the rate is extremely high, -probably on the order of 90ndash;95%. The number climbs higher if you -include surviving but dysfunctional projects: those -which emphasisare/emphasis producing running code, but which are -not pleasant places to be, or are not making progress as quickly or as -dependably as they could./para - -paraThis book is about avoiding failure. It examines not only how -to do things right, but how to do them wrong, so you can recognize and -correct problems early. My hope is that after reading it, you will -have a repertory of techniques not just for avoiding common pitfalls -of open source development, but also for dealing with the growth and -maintenance of a successful project. Success is not a zero-sum game, -and this book is not about winning or getting ahead of the -competition. Indeed, an important part of running an open source -project is working smoothly with other, related projects. In the long -run, every successful project contributes to the well-being of the -overall, worldwide body of free software./para +SourceForge./para/footnote che, anche se solo una piccola percentuale di essi ha successo il risultato è che a noi appare essere tuttavia una gran quantità. Inoltre noi non abbiamo notizia dei fallimenti perchè i fallimenti non fanno notizia. Non c'è un particolare momento in cui il progetto cessa di essere praticabile. La gente semplicemente sceglie di allontanarsene. Ci può essere un momento in cui un cambiamento finale viene fatto nel progetto, ma quelli che lo hanno fatto generalmente non sanno che quel cambiamento è l'ultimo. Non è facile stabilire quando il progetto si è esaurito. Quando non è stato lavorato per sei mesi? Quando la base di utenti ha smesso di crescere senza aver superato la base di sviluppatori? E se gli sviluppatori di un progetto lo abbandonano perchè si rendono conto che stanno duplicando il lavoro di un altromdash;e se essi si uniscono a quell'altro progetto dunque lo espandono per immettervi molto del loro sforzo primitivo. Il progetto precedente è finito o ha semplicemente cambiato casa?/para + +paraA causa di una tale complessità è impossibile stabilire il numero dei fallimenti. Ma una evidenza annedotica da più di un decennio di open source, qualche ricerca su SourceForge.net e un piccolo googling tutti puntano alla stessa conclusione: il numero è estremamente alto, probabilmente dell'ordine del 90–95%. Il numero sale se includete
Re: [ProducingOSS commit] r1512 - trunk/ru
[EMAIL PROTECTED] writes: Log: 00 page finished, ready for review. Some corrections may be needed in acknowledgments part Wow, very fast work, Vlad. I only wish I knew Russian so I could help review. However, I have added the Russian translation-in-progress to the list of translations at http://producingoss.com/translations.html now (see r1516). Best, -Karl Modified: trunk/ru/ch00.xml Modified: trunk/ru/ch00.xml == --- trunk/ru/ch00.xml (original) +++ trunk/ru/ch00.xml Wed Oct 8 04:33:14 2008 @@ -19,7 +19,7 @@ paraНа тот момент у меня не было в запасе подходящего ответа, и чем сильнее я пытался найти его, тем больше я осознавал всю сложность затронутой темы. Ведение открытого проекта не очень похоже на ведение бизнеса (представьте себя обязанным обсуждать сущность вашего продукта с группой добровольцев, с большинством из которых вы никогда не встречались!) (* прим. пер.: автор говорит об отсутствии монополии на принятие решения владельцу проекта, вместо этого прерогатива решения принадлежит активным учасникам, в бизнесе это просто абсурд! Возможна лучшая формулировка.) -Не похоже оно и, по различным причинам, ни на управление обычной некоммерческой или государственной организацией. Оно немного похоже на каждую из них, но я постепенно пришел к заключению, что свободное ПО это foreignphrasesui generis/foreignphrase. +Не похоже оно и, по различным причинам, ни на управление обычной некоммерческой или государственной организацией. Оно немного схоже с каждой из них, но я постепенно пришел к заключению, что свободное ПО это foreignphrasesui generis/foreignphrase. Есть много вещей(*области лучше) с которыми его можно выгодно(полезно) сравнивать для примера, но нет ни одной такой, к которой свободное ПО могло бы быть полностью приравнено. Мало того, даже одно предположение, что свободный програмный проект может быть @@ -45,7 +45,7 @@ программному обеспечению. В этой книге сделано усилие описать способы, которыми это может быть достигнуто. Ни одна книга не смогла бы покрыть их все, но это всего лишь начало(*)./para -paraКачественное свободное програмное обеспечение уже само по себе является достойной целью, и я надеюсь +paraКачественное свободное програмное обеспечение уже является достойной целью, и я надеюсь читатели, ищущие путей достижения этой цели, будут рады тому что здесь обнаружат(*). Но вне этого, я также надеюсь передать кое-что из безграничного удовольствия полученного от работы с командой мотивированых разработчиков свободного ПО, а также удивительно прямого взаимодействия @@ -65,7 +65,7 @@ концепциях разработки ПО, таких как исходный код, компиляторы и програмные патчи./para paraПредыдущий опыт со свободным програмным обеспечением ни в качестве разработчика, ни как пользователя не трубуется. Те кто уже работал с таким ПО, найдут хотя бы некоторые части этой книги несколько тривиальными и возможно пожелают их пропустить. -По причине настолько потенциально больших различий в опыте читателей, мною были приложены усилия, чтобы названия всех разделов были понятными, а также сообщить когда что-либо можно пропустить читателям, уже знакомым(-ых?) с материалом. +По причине настолько потенциально больших различий в опыте читателей, мною были приложены усилия озаглавить все разделы как можно яснее, а также сообщить когда что-либо можно пропустить читателям, уже знакомым(-ых?) с материалом. /para /sect1 @@ -81,46 +81,28 @@ (ulink url=http://subversion.tigris.org//). Subversion - это система контроля версий с общедоступными исходным кодом, написаная с нуля, предназначенная чтобы заменить CVS, являющююся стандартом foreignphrasede facto/foreignphrase среди систем контроля версий в собществе разработчиков свободного программного обеспечения. Проект был начат моим работодателем, организацией CollabNet (ulink url=http://www.collab.net//), в начале 2000, и слава богу, что CollabNet -усвоила буквально с самого начала каким образом нужно проводить проект, так чтобы он был подлинно совместной и распределенной работой. Уже с самого начала к нам присоединилось множество желающих; сейчас над проектом работают около пятидесяти человек и только несколько из них - сотрудники CollabNet./para +усвоила буквально с самого начала каким образом нужно проводить проект, так чтобы он был подлинно совместной и распределенной работой. Уже с самого начала к нам присоединилось множество желающих разработчиков; сейчас над проектом работают около пятидесяти человек и только несколько из них - сотрудники CollabNet./para -paraSubversion это во многом классический пример проекта с открытыми исходными текстами и я - -ended up drawing on it more heavily than I originally -expected. This was partly a matter of convenience: whenever I needed -an example of a particular phenomenon,
Re: [ProducingOSS commit] r1519 - trunk/ru
[EMAIL PROTECTED] writes: Log: quck update #1 quick, I assume you meant... I fixed up the log message like this: $ svn propedit --revprop -r1519 svn:log Best, -Karl Modified: trunk/ru/ch01.xml Modified: trunk/ru/ch01.xml == --- trunk/ru/ch01.xml (original) +++ trunk/ru/ch01.xml Thu Oct 9 20:26:52 2008 @@ -60,14 +60,10 @@ Было бы заманчивым(tempting) сказать, что причины неудач свободного ПО те же что и у коммерческих проектов. -не обладает монополией на, -не единственна -тоже характерны +Разработка свободного ПО не означает отсутствие таких проблем, как завышенные требования, расплывчатые спецификации, неэффективное управление кадрами и других +сложностей давно известных индустрии разработки. - -Конечно же, свободное ПО не обладает монополией на невыполнимые требования, расплывчатые спецификации, неэффективное управление ресурсами, -недостаточные этапы планирования или любые другие хобгоблины давно известные - в индустрии разработки ПО. На эти темы уже написаны горы литературы и, в своей книге, я постараюсь избежать повторений ранее известного. + На эти темы уже написаны горы литературы и, в своей книге, я постараюсь избежать повторений ранее известного. Об этом уже написано достаточно много и я не ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Getting help to italian translation
Giovanni [EMAIL PROTECTED] writes: I am asking you about the italian translation of your book Producing Open Source Software. Can you write for me in your answer, in other english words, the phrase Even those who disagreed with the FSF had to engage the issue, if only to stake out a different position? Sorry, Giovanni -- I saw your earlier mail (to just me), but I couldn't answer it yesterday. Anyway, it's always better to ask on this list, so I'll respond here. The sentence means: Some people did not feel that free software was a political issue, and therefore disagreed with the FSF when the FSF said it *is* a political issue. However, because the FSF raised the question of political meaning, even those people who disagreed were still forced to think about the politics of the activity -- that is, even though they might not agree with the FSF that all software should be free, the FSF still caused them to ask themselves that question. So the FSF forced people to think about it in a new way, even though not all those people came to the same position as the FSF. (stake out means to take a position; in English you can also say stake out a tent -- the stake is the little stick you put in the ground to hold a rope) Does this help? -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Getting help to italian translation
Giovanni [EMAIL PROTECTED] writes: Thank you for the exhaustive answer! It helped me! Good, I'm glad to hear it! ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1523 - trunk/ja
[EMAIL PROTECTED] writes: Log: - added conventions if japanese translators should add ー to some word. Now I have to ask: what does ー mean? ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Italian translation:a question
Giovanni [EMAIL PROTECTED] writes: hello manuel, thank you for the explanatory reply. Now the thing is more plain for me. But I need more an explanation: in the expression think free speech, not free beer the word think is a verb else a noun? What is is is meaning? Manuel is right: it's a verb. It's a shorter way of saying Think of... (as in Imagine... or Consider...) ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Italian translation. Needed help
By the way, it comes from baseball. To pitch is to throw the ball at the batter; by extension, when you pitch an idea to someone, you give them the chance to swing at it and hit it :-). Etc, etc. -Karl Giovanni [EMAIL PROTECTED] writes: OK. Thank you Ari Constanctio - Original Message - From: Ari Constancio [EMAIL PROTECTED] To: ProducingOSS translators producingoss-translators@red-bean.com Sent: Thursday, October 23, 2008 7:38 PM Subject: Re: Italian translation. Needed help On Thu, Oct 23, 2008 at 6:34 PM, Ari Constancio [EMAIL PROTECTED] wrote: Hi Giovanni, To pitch in this context would be something like to direct or to aim. Ari Constancio ... or to sell something to, to introduce to. ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1532 - trunk/it
[EMAIL PROTECTED] writes: Log: The whole chapter 1. Congratulations, Giovanni! ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1537 - trunk/it
[EMAIL PROTECTED] writes: Log: Giovanni For log messages, it's usually better to say what the change did, not just repeat the change. So Add author tags around translator name might be a good message here, for example. -Karl Modified: trunk/it/book.xml Modified: trunk/it/book.xml == --- trunk/it/book.xml (original) +++ trunk/it/book.xml Mon Oct 27 04:15:17 2008 @@ -29,7 +29,7 @@ authorfirstnameKarl/firstnamesurnameFogel/surname contrib(Author)/contrib/author authorfirstnameGerlando/firstnamesurnameTermini/surname -firstnameGiovanni/firstnamesurnameGiorgio/surname +authorfirstnameGiovanni/firstnamesurnameGiorgio/surname/author contrib(Traduzione Italiana)/contrib/author /authorgroup editorfirstnameAndy/firstnamesurnameOram/surname/editor ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1542 - trunk/it
[EMAIL PROTECTED] writes: Log: Giovanni Hmmm, I had trouble understanding what this change did. Could you describe it? (Then we should probably make the description be the new log message -- I can take care of that.) -Karl Modified: trunk/it/book.xml Modified: trunk/it/book.xml == --- trunk/it/book.xml (original) +++ trunk/it/book.xml Mon Oct 27 05:39:31 2008 @@ -1,61 +1,60 @@ -?xml version=1.0? -!DOCTYPE book SYSTEM ../tools/dtd/dblite.dtd -[ -!ENTITY dedication SYSTEM dedication.xml -!ENTITY ch00 SYSTEM ch00.xml -!ENTITY ch01 SYSTEM ch01.xml -!ENTITY ch02 SYSTEM ch02.xml -!ENTITY ch03 SYSTEM ch03.xml -!ENTITY ch04 SYSTEM ch04.xml -!ENTITY ch05 SYSTEM ch05.xml -!ENTITY ch06 SYSTEM ch06.xml -!ENTITY ch07 SYSTEM ch07.xml -!ENTITY ch08 SYSTEM ch08.xml -!ENTITY ch09 SYSTEM ch09.xml -!ENTITY appa SYSTEM appa.xml -!ENTITY appb SYSTEM appb.xml -!ENTITY appc SYSTEM appc.xml -!ENTITY appd SYSTEM appd.xml -!ENTITY copyright SYSTEM copy.xml -] -book id=poss lang=it -titleProdurre Software Open Source/title -subtitleProgettare un Software Libero di successo/subtitle - -bookinfo - edition1.0/edition - isbnISBN: 0-596-00759-0/isbn - authorgroup -authorfirstnameKarl/firstnamesurnameFogel/surname -contrib(Author)/contrib/author -authorfirstnameGerlando/firstnamesurnameTermini/surname -/author -author1firstnameGiovanni/firstnamesurnameGiorgio/surname -/author1 -contrib(Traduzione Italiana)/contrib/author - /authorgroup - editorfirstnameAndy/firstnamesurnameOram/surname/editor - pagenums272 pagine/pagenums - !-- pubdate2005/pubdate -- - copyrightyear2005, 2006, 2007/yearholderKarl Fogel, sotto licenza CreativeCommons Attribution-ShareAlike (3.0)/holder/copyright -/bookinfo - -!-- External entity refs -- -dedication; -ch00; -ch01; -ch02; -ch03; -ch04; -ch05; -ch06; -ch07; -ch08; -ch09; -appa; -appb; -appc; -appd; -copyright; - -/book +?xml version=1.0 encoding=UTF-8? +!DOCTYPE book SYSTEM ../tools/dtd/dblite.dtd [ +!ENTITY dedication SYSTEM dedication.xml +!ENTITY ch00 SYSTEM ch00.xml +!ENTITY ch01 SYSTEM ch01.xml +!ENTITY ch02 SYSTEM ch02.xml +!ENTITY ch03 SYSTEM ch03.xml +!ENTITY ch04 SYSTEM ch04.xml +!ENTITY ch05 SYSTEM ch05.xml +!ENTITY ch06 SYSTEM ch06.xml +!ENTITY ch07 SYSTEM ch07.xml +!ENTITY ch08 SYSTEM ch08.xml +!ENTITY ch09 SYSTEM ch09.xml +!ENTITY appa SYSTEM appa.xml +!ENTITY appb SYSTEM appb.xml +!ENTITY appc SYSTEM appc.xml +!ENTITY appd SYSTEM appd.xml +!ENTITY copyright SYSTEM copy.xml +] +book id=poss lang=it +titleProdurre Software Open Source/title +subtitleProgettare un Software Libero di successo/subtitle + +bookinfo + edition1.0/edition + isbnISBN: 0-596-00759-0/isbn + authorgroup +authorfirstnameKarl/firstnamesurnameFogel/surname +contrib(Author)/contrib/author +authorfirstnameGerlando/firstnamesurnameTermini/surname +/author +author1firstnameGiovanni/firstnamesurnameGiorgio/surname +/author1 +authorcontrib(Traduzione Italiana)/contrib/author + /authorgroup + editorfirstnameAndy/firstnamesurnameOram/surname/editor + pagenums272 pagine/pagenums + !-- pubdate2005/pubdate -- + copyrightyear2005, 2006, 2007/yearholderKarl Fogel, sotto licenza CreativeCommons Attribution-ShareAlike (3.0)/holder/copyright +/bookinfo + +!-- External entity refs -- +dedication; +ch00; +ch01; +ch02; +ch03; +ch04; +ch05; +ch06; +ch07; +ch08; +ch09; +appa; +appb; +appc; +appd; +copyright; + +/book ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS revprop-change] r1542 - svn:log
Giovanni [EMAIL PROTECTED] writes: Hello Karl, Goog morning! I didn't understand the mean of your email. Can you explain it to me? Good morning! (Well, evening here in London now...) I went back and changed your old log messages to be more informative. So, for example, I changed Giovanni to say Translate front matter, which is a description of the change you committed in that revision. Note that none of this affects the change itself -- it only touches the description of the change. When I did that, Subversion automatically sent out an email, showing that I had done it -- that's the email you got. (You probably got several of them, as there were several descriptions I fixed.) Does that help? Important: I noticed that the changes in italian translation aren't well reflected in the mailing list neither in the web page http://producingoss.com/it/. What is happening? I think that TortoiseSVN and/or Subversion system isn't working. Can you say to me something about? I think Christian López Espínola fixed this already (and you have probably seen his mail). Thanks, penyaskito! -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Say verb in context
Giovanni [EMAIL PROTECTED] writes: Problem solved. Excuse me. Ah, okay. Sorry I didn't get to respond to this before I got back from London. It looks like you figured it out, but don't hesitate to post if questions remain. Best, -Karl Giovanni - Original Message - From: Giovanni To: Karl Fogel Cc: producingoss-translators@red-bean.com Sent: Thursday, October 30, 2008 8:23 AM Subject: Say verb in context Hellolo Karl, please can you say to me in other words meant in this phrase: For example, it should be obvious from looking at the links to user documentation that they lead to user documentation, and not to, say, developer documentation. of the say verb Goodbye. Giovanni --- Sto utilizzando la versione gratuita di SPAMfighter! Siamo una comunità di 5,5 milioni di utenti che combattono lo spam. 407 messaggi contenenti spam sono stati bloccati con successo. La versione Professionale non ha questo messaggio. ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Italian translation question
Giovanni [EMAIL PROTECTED] writes: Thank you Ari, I considered stuff out as a verbal voice, from to stuff out. Ehehe. Heh. Yes, remember that English (like German) often splits compound verbs apart. We'll sort all that stuff out when the code is closer to being ready means something like We'll finish those other tasks when the code is closer to being done. -Karl Giovanni - Original Message - From: Ari Constancio [EMAIL PROTECTED] To: ProducingOSS translators producingoss-translators@red-bean.com Sent: Saturday, November 08, 2008 6:08 PM Subject: Re: Italian translation question On Sat, Nov 8, 2008 at 4:36 PM, Giovanni [EMAIL PROTECTED] wrote: Hello friends, please say me in other english words the phrase: We'll sort all that stuff out when the code is closer to being ready. Thanks. From http://www.thefreedictionary.com/sort+out : sort out Verb 1. to find a solution to (a problem): did they sort out the mess? 2. to take or separate (things or people) from a larger group: to sort out the wheat from the chaff 3. to organize (things or people) into an orderly and disciplined group 4. sort someone out to deal with a person, especially an awkward one 5. Informal to punish or tell off (someone) Cheers, Ari Constancio ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: More spam on this list?
Christian López Espínola [EMAIL PROTECTED] writes: On Wed, Nov 12, 2008 at 3:55 PM, Karl Fogel [EMAIL PROTECTED] wrote: Hey folks, are we getting more spam lately on producingoss-commits@ and/or [EMAIL PROTECTED] If it's a problem for anyone, I can try to do something about it... I haven't received any spam from this list. I suppose that you receive those mails as the admin, but they don't reach the list because only can post approved subscribers. As long as it's not a problem for anyone else, I won't do anything about it. The spams aren't costing me much. But if it bothers anyone, please let me know by saying something on the list -- I can do something about the problem if it's annoying other people. Best, -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: partial chapter2 italian translation is'nt reflected in http://producingoss.com/it/ web page. Help
Ari Constancio [EMAIL PROTECTED] writes: On Thu, Nov 27, 2008 at 6:59 PM, Giovanni [EMAIL PROTECTED] wrote: Please help me. Giovanni, Your latest commit shows some conflict marks. Yes. Ari is talking about regions where the same text (with minor differences) appears twice, separated like this: .mine block of text === almost same block of text .r1573 For example, here's one: .mine emphasisil buon/emphasis software nasce quando i programmatore ha interesse a vedere risolti i problemi. La rilevanza di ciò per il software libero era che il prurito personale si rivelava essere la più frequente motivazione nel far partire un progetto di software libero./para === emphasisil buon/emphasis software nasce quando i programmatore ha interesse a vedere risolti i problemi. La rilevanza di ciò per il software libero era che il prurito personale si rivelava essere la più frequente motivazione nel far partire un progetto di software libero./para .r1573 There were a few of those in your commit. I'm not sure how they happened, but if you fix them up, the Italian translation will build again. If you need help fixing them, just let me know. I'm happy to help! -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: [ProducingOSS commit] r1580 - trunk/it
Christian López Espínola [EMAIL PROTECTED] writes: Besides I wish to know how I can make little changes in my transalation and not to send to mailing list each time whole the translation. I assume that you're talking about the mails each time you commit anything. They are fine, there is no problem with sending them. Little changes makes reviewers job easier. Yes. If your text editor is working correctly, then it should only make changes to the parts of the file where you are working. Then when you commit, the commit email will only contain those changed areas, even when very small. Which is fine: a tiny mail like that is easy for everyone to digest. ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
Re: Message
Etienne Savard [EMAIL PROTECTED] writes: There is a lot of SPAM not trapped by GMail lately... Karl, could you find and ban the spammer? Wow, yes, it's a ton. Sigh. There is no way to stop the spammer -- there are many spammers, and this is an arms race I cannot win (I don't have the resources to play the game). Instead, I will change the mailing list address and transfer all of you to the new list. We will just be careful not to publish the new list's address. More soon, -Karl ___ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
