byte-interview.html - en to hr translation catalogue (72 entries)

note: type: Content of: <title>
en: BYTE Interview with Richard Stallman - GNU Project - Free Software Foundation
hr: Intervju časopisa BYTE s Richardom Stallmanom - Projekt GNU - Zaklada za slobodan softver

note: type: Content of: <div><h2>
en: BYTE Interview with Richard Stallman
hr: Intervju časopisa BYTE s Richardom Stallmanom

note: type: Content of: <div><p>
en: Stallman is widely known as the author of EMACS, a powerful text editor that he developed at the <abbr title="Massachusetts Institute of Technology">MIT</abbr> Artificial Intelligence Laboratory.  It is no coincidence that the first piece of software produced as part of the GNU project was a new implementation of EMACS.  GNU EMACS has already achieved a reputation as one of the best implementations of EMACS currently available at any price.
hr: Stallman je poznat kao autor EMACS-a, moćnog programa za uređivanje teksta kojeg je razvio u laboratoriju za umjetnu inteligenciju <abbr title="Tehnološki institut u Massachusettsu">MIT</abbr>-a. Nije slučajnost da je prvi primjerak softvera proizvedenog kao dio projekta GNU bila nova izvedba EMACS-a. GNU EMACS već je stekao glas jedne od najboljih trenutno dostupnih izvedbi EMACS-a bez obzira na cijenu.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: We read your GNU Manifesto in the March 1985 issue of Dr. Dobb's.  What has happened since? Was that really the beginning, and how have you progressed since then?
hr: <strong>BYTE</strong>: Pročitali smo vaš GNU manifest u izdanju časopisa Dr. Dobb's iz ožujka 1985. Što se nakon toga dogodilo? Je li to bio pravi početak i kako ste od tada napredovali?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: The publication in Dr. Dobb's wasn't the beginning of the project.  I wrote the GNU Manifesto when I was getting ready to start the project, as a proposal to ask computer manufacturers for funding.  They didn't want to get involved, and I decided that rather than spend my time trying to pursue funds, I ought to spend it writing code.  The manifesto was published about a year and a half after I had written it, when I had barely begun distributing the GNU EMACS.  Since that time, in addition to making GNU EMACS more complete and making it run on many more computers, I have nearly finished the optimizing C compiler and all the other software that is needed for running C programs.  This includes a source-level debugger that has many features that the other source-level debuggers on Unix don't have.  For example, it has convenience variables within the debugger so you can save values, and it also has a history of all the values that you have printed out, making it tremendously easier to chase around list structures.
hr: <strong>Stallman</strong>: Objava u Dr. Dobb'su nije bila početak projekta. GNU manifest sam napisao dok sam se pripremao započeti projekt, kao prijedlog kojim bih od proizvođača računala zatražio financiranje. Nisu se željeli uključiti, pa sam odlučio da bih trebao, umjesto trošenja svojeg vremena na prikupljanje financijskih sredstava, vrijeme iskoristiti za pisanje koda. Manifest je objavljen oko godinu i po nakon što sam ga napisao, dok sam tek počeo distribuirati GNU EMACS. Od tada, uz rad na tome kako bih GNU EMACS upotpunio i prilagodio ga radu na mnogo više računala, gotovo sam dovršio optimiziranje C prevodioca i svega ostalog softvera koji je potreban za pokretanje programa pisanih u C-u. To uključuje program za traženje pogrešaka na razini izvornog koda koji ima mnogo osobina koje drugi programi te vrste na Unixu nemaju. Na primjer, ima podesne varijable u tražitelju grešaka tako da možete sačuvati vrijednosti, a ima i sačuvane sve vrijednosti koje ste ispisali, što ga čini iznimno prikladnim za rad sa strukturama listi.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: You have finished an editor that is now widely distributed and you are about to finish the compiler.
hr: <strong>BYTE</strong>: Dovršili ste uređivač teksta koji je sada široko rasprostranjen, a pred dovršetkom ste i prevodioca.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I expect that it will be finished this October.
hr: <strong>Stallman</strong>: Očekujem da će biti završen u listopadu.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: What about the kernel?
hr: <strong>BYTE</strong>: Što je s jezgrom?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I'm currently planning to start with the kernel that was written at MIT and was released to the public recently with the idea that I would use it.  This kernel is called TRIX; it's based on remote procedure call.  I still need to add compatibility for a lot of the features of Unix which it doesn't have currently.  I haven't started to work on that yet.  I'm finishing the compiler before I go to work on the kernel.  I am also going to have to rewrite the file system.  I intend to make it failsafe just by having it write blocks in the proper order so that the disk structure is always consistent.  Then I want to add version numbers.  I have a complicated scheme to reconcile version numbers with the way people usually use Unix.  You have to be able to specify filenames without version numbers, but you also have to be able to specify them with explicit version numbers, and these both need to work with ordinary Unix programs that have not been modified in any way to deal with the existence of this feature.  I think I have a scheme for doing this, and only trying it will show me whether it really does the job.
hr: <strong>Stallman</strong>: Trenutno planiram započeti s jezgrom koja je napisana na MIT-u i nedavno objavljena javnosti s namjerom da bih ju koristio. Ta jezgra nazvana je TRIX; zasnovana je na pozivu udaljene procedure (engl. <i>remote procedure call</i>. Još moram nadodati kompatibilnost za mnogo Unixovih osobina koje trenutno nema. Još nisam počeo raditi na tome. Dovršavam program za prevođenje (kompilator) prije nego počnem raditi na jezgri. Morat ću i iznova napisati datotečni sustav. Namjeravam ga učiniti otpornim na greške na način da upisuje blokove odgovarajućim redosljedom kako bi struktura diska uvijek bila postojana. Zatim želim dodati brojeve verzija. Imam složen plan za usklađivanje brojeva verzija s načinom na koji ljudi obično koriste Unix. Morate biti u mogućnosti odrediti imena datoteka bez brojeva verzija, ali ih također morate moći označiti s eksplicitnim brojevima verzija, a oba načina moraju raditi s uobičajenim Unix programima koji nisu ni na koji način promijenjeni kako bi se nosili s takvim osobinama. Mislim da imam plan za to učiniti, a tek kad ga iskušam vidjet ću hoće li to zaista djelovati.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Do you have a brief description you can give us as to how GNU as a system will be superior to other systems? We know that one of your goals is to produce something that is compatible with Unix.  But at least in the area of file systems you have already said that you are going to go beyond Unix and produce something that is better.
hr: <strong>BYTE</strong>: Možete li nam ukratko opisati kako će GNU kao sustav biti nadmoćan ostalim sustavima? Znamo da je jedan od vaših ciljeva proizvesti nešto što je kompatibilno s Unixom. Ali, barem u području datotečnih sustava, već ste rekli da ćete nadmašiti Unix i proizvesti nešto bolje.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: The C compiler will produce better code and run faster.  The debugger is better.  With each piece I may or may not find a way to improve it.  But there is no one answer to this question.  To some extent I am getting the benefit of reimplementation, which makes many systems much better.  To some extent it's because I have been in the field a long time and worked on many other systems.  I therefore have many ideas to bring to bear.  One way in which it will be better is that practically everything in the system will work on files of any size, on lines of any size, with any characters appearing in them.  The Unix system is very bad in that regard.  It's not anything new as a principle of software engineering that you shouldn't have arbitrary limits.  But it just was the standard practice in writing Unix to put those in all the time, possibly just because they were writing it for a very small computer.  The only limit in the GNU system is when your program runs out of memory because it tried to work on too much data and there is no place to keep it all.
hr: <strong>Stallman</strong>: C prevodilac će proizvoditi bolji kod i biti brži. Program za traženje grešaka je bolji. Za svaki dio mogu, a i ne moram, pronaći način da ga poboljšam, ali na to pitanje ne postoji samo jedan odgovor. Do određene mjere imam povlasticu reimplementacije, što omogućuje značajno poboljšanje mnogih sustava. Do određene mjere to je i zato što sam već dugo vrijeme u tom polju i radio sam na mnogim sustavima, stoga donosim sa sobom mnogo ideja. Jedan način na koji će sustav biti bolji je i taj što će praktično sve u sustavu raditi s datotekama bilo koje veličine, linijama bilo koje veličine, s bilo kojim znakovima koji se u njima pojavljuju. Unix sustav je u tom smislu vrlo loš. Nije ništa novo u načelu softverskog inženjeringa da ne biste trebali imati proizvoljna ograničenja. No pri pisanju Unixa umetanje tih ograničenja bila je cijelo vrijeme uobičajena praksa, vjerojatno jednostavno zato što je pisan za vrlo malo računalo. Jedino ograničenje sustava GNU je ono kada vašem programu ponestane memorije jer je pokušao raditi s previše podataka za čije držanje je ponestalo mjesta.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: And that isn't likely to be hit if you've got virtual memory.  You may just take forever to come up with the solution.
hr: <strong>BYTE</strong>: A to se vjerojatno neće dogoditi ako imate virtualnu memoriju. Može vam trebati vječnost da pronađete rješenje.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Actually these limits tend to hit in a time long before you take forever to come up with the solution.
hr: <strong>Stallman</strong>: Ta ograničenja su, zapravo, sklona pogoditi vas daleko ranije od vječnosti koja vam je potrebna da biste pronašli rješenje.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Can you say something about what types of machines and environments GNU EMACS in particular has been made to run under? It's now running on VAXes; has it migrated in any form to personal computers?
hr: <strong>BYTE</strong>: Možete li reći nešto o tome na kojim je vrstama strojeva i okruženjima GNU EMACS predviđen da bude pokretan? Sada radi na VAX strojevima; je li prešao u bilo kojem obliku na osobna računala?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I'm not sure what you mean by personal computers.  For example, is a Sun a personal computer? GNU EMACS requires at least a megabyte of available memory and preferably more.  It is normally used on machines that have virtual memory.  Except for various technical problems in a few C compilers, almost any machine with virtual memory and running a fairly recent version of Unix will run GNU EMACS, and most of them currently do.
hr: <strong>Stallman</strong>: Nisam siguran što podrazumijevate pod osobnim računalima. GNU EMACS zahtijeva barem jedan megabajt slobodne memorije, a poželjno je i više. Uobičajeno se koristi na strojevima koji posjeduju virtualnu memoriju. Osim uslijed različitih tehničkih problema u nekoliko C prevodilaca, gotovo svaki stroj s virtualnom memorijom na kojem je pokrenuta novija verzija Unixa može pokrenuti GNU EMACS, većina njih to trenutno može.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Has anyone tried to port it to Ataris or Macintoshes?
hr: <strong>BYTE</strong>: Je li ga itko pokušao prenijeti na Atari ili Macintosh računala?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: The Atari 1040ST still doesn't have quite enough memory.  The next Atari machine, I expect, will run it.  I also think that future Ataris will have some forms of memory mapping.  Of course, I am not designing the software to run on the kinds of computers that are prevalent today.  I knew when I started this project it was going to take a few years.  I therefore decided that I didn't want to make a worse system by taking on the additional challenge of making it run in the currently constrained environment.  So instead I decided I'm going to write it in the way that seems the most natural and best.  I am confident that in a couple of years machines of sufficient size will be prevalent.  In fact, increases in memory size are happening so fast it surprises me how slow most of the people are to put in virtual memory; I think it is totally essential.
hr: <strong>Stallman</strong>: Atari 1040ST još uvijek nema dovoljno memorije. Očekujem da će ga sljedeći Atarijev stroj moći pokrenuti. Također mislim da će buduća Atari računala imati neki oblik mapiranja memorije. Naravno, ja ne projektiram softver da bi mogao raditi na računalima koja danas prevladavaju. Kada sam pokretao projekt znao sam da će za njega biti potrebno nekoliko godina. Stoga sam odlučio da ne želim napraviti sustav lošijim preuzimanjem dodatnog izazova da ga učinim pogodnim za rad u trenutnom ograničenom okružju. Siguran sam da će za nekoliko godina prevladavati strojevi dovoljne veličine. U stvari, povećanja veličine memorije događaju se tako brzo da me čudi kako su ljudi tako tromi u dodavanju virtualne memorije; mislim da je to iznimno bitno.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: I think people don't really view it as being necessary for single-user machines.
hr: <strong>BYTE</strong>: Mislim da ljudi ne misle da je to neophodno za jednokorisničke strojeve.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: They don't understand that single user doesn't mean single program.  Certainly for any Unix-like system it's important to be able to run lots of different processes at the same time even if there is only one of you.  You could run GNU EMACS on a nonvirtual-memory machine with enough memory, but you couldn't run the rest of the GNU system very well or a Unix system very well.
hr: <strong>Stallman</strong>: Ne razumiju da samo jedan korisnik ne znači i samo jedan program. Svakako je za bilo koji Unixu sličan sustav važno da bude u mogućnosti pokretati mnogo različitih programa istovremeno, čak i za samo jednog korisnika. S dovoljno memorije mogli biste pokrenuti GNU EMACS na stroju bez virtualne memorije, ali ne biste mogli naročito dobro pokretati ostatak GNU sustava ili Unix sustava.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: How much of LISP is present in GNU EMACS? It occurred to me that it may be useful to use that as a tool for learning LISP.
hr: <strong>BYTE</strong>: Koliko je LISP prisutan u GNU EMACS-u? Pomislio sam da bi moglo biti korisno koristiti ga kao alat za učenje LISPa.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: You can certainly do that.  GNU EMACS contains a complete, although not very powerful, LISP system.  It's powerful enough for writing editor commands.  It's not comparable with, say, a Common LISP System, something you could really use for system programming, but it has all the things that LISP needs to have.
hr: <strong>Stallman</strong>: To svakako možete učiniti. GNU EMACS posjeduje potpun, iako ne naročito moćan, LISP sustav. Dovoljno je moćan za pisanje naredbi editora. Nije usporediv s, recimo, općim LISP sustavom, nečim što biste uistinu mogli koristiti za programiranje sustava, ali ima sve što je potrebno za LISP.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Do you have any predictions about when you would be likely to distribute a workable environment in which, if we put it on our machines or workstations, we could actually get reasonable work done without using anything other than code that you distribute?
hr: <strong>BYTE</strong>: Možete li pretpostaviti kada bi bilo vjerojatno da distribuirate funkcionalno okruženje u kojem bismo, ako bismo ga stavili na naše strojeve i radne stanice, mogli zapravo napraviti nešto bez da koristimo išta drugo osim koda koji distribuirate?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: It's really hard to say.  That could happen in a year, but of course it could take longer.  It could also conceivably take less, but that's not too likely anymore.  I think I'll have the compiler finished in a month or two.  The only other large piece of work I really have to do is in the kernel.  I first predicted GNU would take something like two years, but it has now been two and a half years and I'm still not finished.  Part of the reason for the delay is that I spent a lot of time working on one compiler that turned out to be a dead end.  I had to rewrite it completely.  Another reason is that I spent so much time on GNU EMACS.  I originally thought I wouldn't have to do that at all.
hr: <strong>Stallman</strong>: Stvarno je teško reći. Moglo bi se to dogoditi za godinu dana, ali, naravno, moglo bi potrajati i duže. Zamislivo je i da traje kraće, ali to više nije previše vjerojatno. Mislim da će prevodilac biti dovršen za mjesec ili dva. Jedini preostali velik dio posla koji moram učiniti je rad na jezgri. Isprva sam predvidio da bi za GNU moglo biti potrebno nešto oko dvije godine, ali prošlo je dvije i po, a ja još nisam gotov. Dio razloga za kašnjenje je to što sam proveo dosta vremena u radu na jednom prevodiocu koji se pokazao kao slijepa ulica. Morao sam ga napisati u potpunosti ispočetka. Drugi razlog je taj što sam utrošio previše vremena na GNU EMACS. Prvotno sam mislio da to uopće neću trebati učiniti.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Tell us about your distribution scheme.
hr: <strong>BYTE</strong>: Recite nam nešto o vašem planu distribucije.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I don't put software or manuals in the public domain, and the reason is that I want to make sure that all the users get the freedom to share.  I don't want anyone making an improved version of a program I wrote and distributing it as proprietary.  I don't want that to ever be able to happen.  I want to encourage the free improvements to these programs, and the best way to do that is to take away any temptation for a person to make improvements nonfree.  Yes, a few of them will refrain from making improvements, but a lot of others will make the same improvements and they'll make them free.
hr: <strong>Stallman</strong>: Ne stavljam softver i priručnike u javno vlasništvo, a razlog za to je što želim da svi korisnici dobiju slobodu dijeljenja. Ne želim da itko napravi poboljšanu inačicu programa kojeg sam napisao i da je distribuira kao vlasničku. Ne želim da ikada bude moguće da se to dogodi. Želim potaknuti slobodna poboljšanja tih programa, a najbolji način da to učinim je da uklonim bilo kakvo iskušenje da netko poboljšanje učini neslobodnim. Da, neki će se suzdržati od izrade poboljšanja, ali mnogi drugi će učiniti ista ta poboljšanja i učinit će ih slobodnima.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: And how do you go about guaranteeing that?
hr: <strong>BYTE</strong>: A kako ćete to jamčiti?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I do this by copyrighting the programs and putting on a notice giving people explicit permission to copy the programs and change them but only on the condition that they distribute under the same terms that I used, if at all.  You don't have to distribute the changes you make to any of my programs&mdash;you can just do it for yourself, and you don't have to give it to anyone or tell anyone.  But if you do give it to someone else, you have to do it under the same terms that I use.
hr: <strong>Stallman</strong>: Učinit ću to zadržavanjem autorskih prava i stavljanjem napomene kojom dajem ljudima izričitu dozvolu da umnožavaju programe i mijenjaju ih, ali jedino pod uvjetom da, ako ih distribuiraju, čine to pod istim uvjetima koje sam ja koristio. Ne morate distribuirati izmjene koje učinite na bilo kojem mojem programu&mdash;možete to učiniti za sebe i nikome ne dati ili reći o tome. No ako ih ipak date nekome, morate to učiniti pod istim uvjetima pod kojima to činim ja.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Do you obtain any rights over the executable code derived from the C compiler?
hr: <strong>BYTE</strong>: Zadržavate li kakva prava nad izvršnim kodom izvedenim C prevodiocem?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: The copyright law doesn't give me copyright on output from the compiler, so it doesn't give me a way to say anything about that, and in fact I don't try to.  I don't sympathize with people developing proprietary products with any compiler, but it doesn't seem especially useful to try to stop them from developing them with this compiler, so I am not going to.
hr: <strong>Stallman</strong>: Zakon o autorskim pravima ne daje mi autorska prava nad proizvodom C prevodioca, stoga mi ne daje način na koji bih rekao bilo što o tome, a to zapravo niti ne pokušavam. Ne slažem se s ljudima koji razvijaju vlasničke proizvode bilo kojim prevodiocem, ali ne čini se naročito korisnim pokušati ih zaustaviti u razvijanju proizvoda tim prevodiocem, stoga ih niti neću pokušavati zaustaviti.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Do your restrictions apply if people take pieces of your code to produce other things as well?
hr: <strong>BYTE</strong>: Primjenjuju li se vaša ograničenja i ako se uzme dio vašeg koda kako bi se stvorilo nešto drugo?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Yes, if they incorporate with changes any sizable piece.  If it were two lines of code, that's nothing; copyright doesn't apply to that.  Essentially, I have chosen these conditions so that first there is a copyright, which is what all the software hoarders use to stop everybody from doing anything, and then I add a notice giving up part of those rights.  So the conditions talk only about the things that copyright applies to.  I don't believe that the reason you should obey these conditions is because of the law.  The reason you should obey is because an upright person when he distributes software encourages other people to share it further.
hr: <strong>Stallman</strong>: Da, ako s promjenama ugrade značajniji dio. Ako su to samo dvije linije koda, to nije ništa; autorska prava na to se ne primjenjuju. Suštinski, odabrao sam ove uvjete da, kao prvo, budu primijenjena autorska prava, što je ono što svi softverski škrci koriste kako bi zaustavili svakoga da išta čini, a onda na to dodajem napomenu kojom prepuštam dio tih prava. Stoga uvjeti govore samo o onome na što se autorska prava odnose. Ne smatram da bi zakon trebao biti razlog zbog kojeg poštujete ove uvjete. Razlog zbog kojeg biste ih trebali poštovati je taj što čestita osoba kada distribuira softver potiče druge ljude da ga dijele dalje.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: In a sense you are enticing people into this mode of thinking by providing all of these interesting tools that they can use but only if they buy into your philosophy.
hr: <strong>BYTE</strong>: U određenom smislu navodite ljude na ovaj način razmišljanja pružanjem svih ovih zanimljivih alata koje mogu koristiti, ali samo ako se slažu s vašom filozofijom.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Yes.  You could also see it as using the legal system that software hoarders have set up against them.  I'm using it to protect the public from them.
hr: <strong>Stallman</strong>: Da. Mogli biste isto tako gledati na to kao na korištenje pravnog sustava, kojeg su postavili softverski škrci, protiv njih. Koristim ga kako bih zaštitio javnost od njih.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Given that manufacturers haven't wanted to fund the project, who do you think will use the GNU system when it is done?
hr: <strong>BYTE</strong>: S obzirom na činjenicu da proizvođači nisu željeli financirati projekt, što mislite tko će koristiti GNU sustav kada bude završen?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I have no idea, but it is not an important question.  My purpose is to make it possible for people to reject the chains that come with proprietary software.  I know that there are people who want to do that.  Now, there may be others who don't care, but they are not my concern.  I feel a bit sad for them and for the people that they influence.  Right now a person who perceives the unpleasantness of the terms of proprietary software feels that he is stuck and has no alternative except not to use a computer.  Well, I am going to give him a comfortable alternative.
hr: <strong>Stallman</strong>: Nemam pojma, ali to nije važno pitanje. Moja je namjera omogućiti ljudima da odbace lance koji dolaze uz vlasnički softver. Znam da ima ljudi koji to žele. Doduše, mogu postojati i drugi, koji to ne žele, ali oni nisu moja briga. Žao mi je i njih i ljudi koji su pod njihovim utjecajem. Trenutno, osoba koja uočava neugodu uvjeta koje vlasnički softver postavlja, osjeća da je zaglavljena i da nema izbora osim da ne koristi računalo. Pa, ja ću joj dati ugodnu alternativu.

note: type: Content of: <div><p>
en: Other people may use the GNU system simply because it is technically superior.  For example, my C compiler is producing about as good a code as I have seen from any C compiler.  And GNU EMACS is generally regarded as being far superior to the commercial competition.  And GNU EMACS was not funded by anyone either, but everyone is using it.  I therefore think that many people will use the rest of the GNU system because of its technical advantages.  But I would be doing a GNU system even if I didn't know how to make it technically better because I want it to be socially better.  The GNU project is really a social project.  It uses technical means to make a change in society.
hr: Drugi ljudi mogu koristiti GNU sustav jednostavno zato jer je tehnički nadmoćan. Na primjer, moj C prevodilac proizvodi kod koji je jednako dobar kao kod bilo kojeg C prevodioca kojeg sam vidio. Uz to, GNU EMACS se općenito smatra daleko nadmoćnijim komercijalnim konkurentima. Također, GNU EMACS nitko ne financira, ali ga svatko koristi.Stoga mislim da će mnogi ljudi koristiti ostatak sustava GNU zbog njegovih tehničkih prednosti. No, pravio bih GNU sustav čak i kada ne bih znao kako ga učiniti tehnički boljim, zato jer želim da bude društveno bolji. Projekt GNU je uistinu društveni projekt. On koristi tehnička sredstva kako bi napravio promjenu u društvu.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Then it is fairly important to you that people adopt GNU.  It is not just an academic exercise to produce this software to give it away to people.  You hope it will change the way the software industry operates.
hr: <strong>BYTE</strong>: Tada vam je prilično važno da ljudi prihvate GNU. On nije samo akademska vježba da bi se proizveo softver koji bi bio predan ljudima. Nadate se da će promijeniti način na koji djeluje softverska industrija.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Yes.  Some people say no one will ever use it because it doesn't have some attractive corporate logo on it, and other people say that they think it is tremendously important and everyone's going to want to use it.  I have no way of knowing what is really going to happen.  I don't know any other way to try to change the ugliness of the field that I find myself in, so this is what I have to do.
hr: <strong>Stallman</strong>: Da. Neki kažu da ga nitko nikada neće koristiti jer nema neki atraktivan korporativni logo na sebi, a drugi kažu da misle da je iznimno bitan i da će ga svatko htjeti koristiti. Nemam načina da predvidim što će se zapravo dogoditi. Ne znam nijedan drugi način da pokušam promijeniti ružnoću područja u kojem sam se našao, stoga je ovo to što moram učiniti.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Can you address the implications? You obviously feel that this is an important political and social statement.
hr: <strong>BYTE</strong>: Možete li procijeniti dosege? Očito ovo smatrate važnim političkim i društvenim očitovanjem.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: It is a change.  I'm trying to change the way people approach knowledge and information in general.  I think that to try to own knowledge, to try to control whether people are allowed to use it, or to try to stop other people from sharing it, is sabotage.  It is an activity that benefits the person that does it at the cost of impoverishing all of society.  One person gains one dollar by destroying two dollars' worth of wealth.  I think a person with a conscience wouldn't do that sort of thing except perhaps if he would otherwise die.  And of course the people who do this are fairly rich; I can only conclude that they are unscrupulous.  I would like to see people get rewards for writing free software and for encouraging other people to use it.  I don't want to see people get rewards for writing proprietary software because that is not really a contribution to society.  The principle of capitalism is the idea that people manage to make money by producing things and thereby are encouraged to do what is useful, automatically, so to speak.  But that doesn't work when it comes to owning knowledge.  They are encouraged to do not really what's useful, and what really is useful is not encouraged.  I think it is important to say that information is different from material objects like cars and loaves of bread because people can copy it and share it on their own and, if nobody attempts to stop them, they can change it and make it better for themselves.  That is a useful thing for people to do.  This isn't true of loaves of bread.  If you have one loaf of bread and you want another, you can't just put your loaf of bread into a bread copier.  You can't make another one except by going through all the steps that were used to make the first one.  It therefore is irrelevant whether people are permitted to copy it&mdash;it's impossible.
hr: <strong>Stallman</strong>: To je promjena. Pokušavam promijeniti način na koji ljudi pristupaju znanju i informacijama općenito. Mislim da je pokušati posjedovati znanje, pokušati kontrolirati hoće li ljudima biti dozvoljeno da ga koriste, ili pokušati zaustaviti druge ljude da ga dijele, čin sabotaže. To je djelovanje koje donosi dobit osobi koja to čini, po cijenu osiromašenja cjelokupnog društva. Jedna osoba dobija jedan dolar uništavajući blago vrijedno dva dolara. Mislim da osoba koja posjeduje savjest ne bi učinila nešto takve vrste, osim možda ako bi joj u suprotom bio ugrožen život. A naravno, ljudi koji to rade prilično su bogati; mogu samo zaključiti da su bezobzirni. Volio bih vidjeti da ljudi budu nagrađeni za pisanje slobodnog softvera i za poticanje drugih da ga koriste. Ne želim vidjeti da ljudi budu nagrađeni za pisanje vlasničkog softvera jer to zapravo nije doprinos društvu. Načelo kapitalizma je ideja da ljudi uspiju steći novac proizvodeći stvari i stoga su, da tako kažemo, automatski potaknuti da rade ono što je korisno. Međutim, to ne funkcionira kada se radi o posjedovanju znanja. Potaknuti su da zapravo ne čine ono što je korisno, a ne potiče se ono što je zapravo korisno. Mislim da je važno reći da se informacija razlikuje od materijalnih objekata, kao automobila i štruca kruha, jer je ljudi mogu umnožavati i dijeliti samostalno i, ako ih nitko ne pokušava zaustaviti, mogu je promijeniti i učiniti boljom za sebe. To je korisna stvar koju ljudi mogu učiniti. To nije istina u slučaju štruca kruha. Ako imate jednu štrucu kruha i želite još jednu, ne možete je samo iskopirati. Ne možete napraviti još jednu, osim da prođete kroz sve korake koji su bili potrebni da se izradi prva. Stoga je bespredmetno je li ljudima dozvoljeno da je umnože&mdash;to je nemoguće.

note: type: Content of: <div><p>
en: Books were printed only on printing presses until recently.  It was possible to make a copy yourself by hand, but it wasn't practical because it took so much more work than using a printing press.  And it produced something so much less attractive that, for all intents and purposes, you could act as if it were impossible to make books except by mass producing them.  And therefore copyright didn't really take any freedom away from the reading public.  There wasn't anything that a book purchaser could do that was forbidden by copyright.
hr: Knjige su donedavno tiskane samo na tiskarskim strojevima. Bilo je moguće ručno napraviti primjerak za sebe, ali nije bilo praktično jer je trebalo uložiti puno više rada nego koristeći tiskarski stroj, a proizvelo je i nešto toliko neprivlačnije da je, za sve namjere i svrhe, moglo biti smatrano nemogućim proizvesti knjige drugačije nego masovnom proizvodnjom. Stoga autorska prava nisu stvarno oduzimala slobodu čitateljskoj publici. Nije postojalo ništa što bi kupac knjige mogao učiniti, a što je bilo zabranjeno autorskim pravima.

note: type: Content of: <div><p>
en: But this isn't true for computer programs.  It's also not true for tape cassettes.  It's partly false now for books, but it is still true that for most books it is more expensive and certainly a lot more work to Xerox them than to buy a copy, and the result is still less attractive.  Right now we are in a period where the situation that made copyright harmless and acceptable is changing to a situation where copyright will become destructive and intolerable.  So the people who are slandered as &ldquo;pirates&rdquo; are in fact the people who are trying to do something useful that they have been forbidden to do.  The copyright laws are entirely designed to help people take complete control over the use of some information for their own good.  But they aren't designed to help people who want to make sure that the information is accessible to the public and stop others from depriving the public.  I think that the law should recognize a class of works that are owned by the public, which is different from public domain in the same sense that a public park is different from something found in a garbage can.  It's not there for anybody to take away, it's there for everyone to use but for no one to impede.  Anybody in the public who finds himself being deprived of the derivative work of something owned by the public should be able to sue about it.
hr: Ali to ne vrijedi za računalne programe. Ne vrijedi niti za kasete s magnetskom trakom. Djelomično je nevažeće sada i za knjige, ali još uvijek je točno da je za većinu knjiga skuplje i svakako potrebno daleko više rada da ih se fotokopira, nego da se kupi primjerak, a rezultat je još uvijek manje privlačan. Trenutno smo u razdoblju gdje se situacija u kojoj su autorska prava bila bezopasna i prihvatljiva mijenja u situaciju u kojoj će autorska prava postati destruktivna i neprihvatljiva. Stoga ljudi koji su žigosani kao &ldquo;pirati&rdquo; su u stvari ljudi koji pokušavaju učiniti nešto korisno što im je zabranjeno da učine. Zakoni o autorskim pravima su u potpunosti osmišljeni kako bi pomogli ljudima da imaju kontrolu nad korištenjem nekih informacija za njihovu vlastitu korist. Međutim, nisu osmišljena kako bi pomogla ljudima koji žele osigurati da informacija bude dostupna javnosti i zaustaviti druge da je uskrate javnosti. Mislim da bi zakon trebao priznati vrstu djela koja su u vlasništvu javnosti, što je drugačije od javnog vlasništva u istom smislu u kojem je javni park drugačiji od nečeg pronađenog u kanti za smeće. Nije tamo zato da bi bilo tko to mogao uzeti, tamo je zato da bi svatko to mogao koristiti, bez da itko to ometa. Bilo tko u javnosti tko se nađe u situaciji da mu je uskraćeno djelo izvedeno iz djela koje je u vlasništvu javnosti trebao bi imati mogućnost podići tužbu.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: But aren't pirates interested in getting copies of programs because they want to use those programs, not because they want to use that knowledge to produce something better?
hr: <strong>BYTE</strong>: Ali, nisu li pirati zainteresirani za dobivanje kopija zato jer žele koristiti te programe, a ne zato jer žele koristiti to znanje kako bi proizveli nešto bolje?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I don't see that that's the important distinction.  More people using a program means that the program contributes more to society.  You have a loaf of bread that could be eaten either once or a million times.
hr: <strong>Stallman</strong>: Ne vidim to kao važnu razliku. Više ljudi koji koriste program znači da taj program više doprinosi zajednici. Imate štrucu kruha koju je moguće pojesti ili jednom ili milijun puta.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Some users buy commercial software to obtain support.  How does your distribution scheme provide support?
hr: <strong>BYTE</strong>: Neki korisnici kupuju vlasnički softver kako bi dobili podršku za njega. Kako vaš distribucijski plan osigurava podršku?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I suspect that those users are misled and are not thinking clearly.  It is certainly useful to have support, but when they start thinking about how that has something to do with selling software or with the software being proprietary, at that point they are confusing themselves.  There is no guarantee that proprietary software will receive good support.  Simply because sellers say that they provide support, that doesn't mean it will be any good.  And they may go out of business.  In fact, people think that GNU EMACS has better support than commercial EMACSes.  One of the reasons is that I'm probably a better hacker than the people who wrote the other EMACSes, but the other reason is that everyone has sources and there are so many people interested in figuring out how to do things with it that you don't have to get your support from me.  Even just the free support that consists of my fixing bugs people report to me and incorporating that in the next release has given people a good level of support.  You can always hire somebody to solve a problem for you, and when the software is free you have a competitive market for the support.  You can hire anybody.  I distribute a service list with EMACS, a list of people's names and phone numbers and what they charge to provide support.
hr: <strong>Stallman</strong>: Sumnjam da su ti korisnici zavedeni i ne razmišljaju jasno. Svakako je korisno imati podršku, ali kada počnu razmišljati o tome kako to ima veze s prodajom softvera ili sa softverom koji je vlasnički, u tom trenutku se zavaravaju. Nema jamstva da će vlasnički softver dobiti dobru podršku. Jednostavno to što prodavači kažu da pružaju podršku ne znači da će ona biti odgovarajuća. Isto tako mogu i propasti. Zapravo, ljudi smatraju da GNU EMACS ima bolju podršku od komercijalnih EMACSa. Jedan od razloga je i to što sam vjerojatno bolji haker od ljudi koji su napisali ostale EMACSe, ali drugi razlog je da svi imaju izvorni kod i postoji mnogo ljudi koji su zainteresirani kako da nešto učine s njim, tako da ne trebate moju podršku. Čak i sama besplatna podrška koja se sastoji od mojih ispravaka pogrešaka u programu koje mi ljudi prijavljuju i uključivanja tih ispravaka u sljedeća izdanja dala je ljudima dobru razinu podrške. Uvijek možete zaposliti nekoga da vam riješi problem, a kada je softver slobodan tada imate konkurentno tržište podrške. Možete zaposliti bilo koga. Uz EMACS distribuiram listu usluga, listu imena i telefonskih brojeva ljudi i cijenu po kojoj nude podršku.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Do you collect their bug fixes?
hr: <strong>BYTE</strong>: Prikupljate li njihove ispravke grešaka?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Well, they send them to me.  I asked all the people who wanted to be listed to promise that they would never ask any of their customers to keep secret whatever they were told or any changes they were given to the GNU software as part of that support.
hr: <strong>Stallman</strong>: Pa, oni mi ih šalju. Tražio sam od svih ljudi koji su željeli biti na listi da obećaju da nikada neće tražiti bilo koju od svojih stranaka da taji išta što joj je rečeno ili bilo koje izmjene koje su joj dane za GNU softver kao dio te podrške.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: So you can't have people competing to provide support based on their knowing the solution to some problem that somebody else doesn't know.
hr: <strong>BYTE</strong>: Dakle, ljudi ne mogu pri davanju podrške biti konkurentni na osnovi njihovog poznavanja rješenja za neki problem za koje netko drugi ne zna.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: No.  They can compete based on their being clever and more likely to find the solution to your problem, or their already understanding more of the common problems, or knowing better how to explain to you what you should do.  These are all ways they can compete.  They can try to do better, but they cannot actively impede their competitors.
hr: <strong>Stallman</strong>: Ne. Mogu si konkurirati na temelju toga da budu domišljati i time da imaju veću vjerojatnost pronaći rješenje vašeg problema, ili da već poznaju više čestih problema, ili da znaju bolje objasniti vam što trebate učiniti. To su sve načini na koji se mogu natjecati. Mogu pokušati biti bolji, ali ne mogu zapravo ometati svoje konkurente.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: I suppose it's like buying a car.  You're not forced to go back to the original manufacturer for support or continued maintenance.
hr: <strong>BYTE</strong>: Pretpostavljam da je to kao kupovina automobila. Niste prisiljeni ići kod proizvođača po podršku ili redovno održavanje.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Or buying a house&mdash;what would it be like if the only person who could ever fix problems with your house was the contractor who built it originally? That is the kind of imposition that's involved in proprietary software.  People tell me about a problem that happens in Unix.  Because manufacturers sell improved versions of Unix, they tend to collect fixes and not give them out except in binaries.  The result is that the bugs don't really get fixed.
hr: <strong>Stallman</strong>: Ili kao kupovina kuće&mdash;kako bi bilo kada bi jedina osoba koja bi ikada mogla popraviti nešto na vašoj kući bio onaj tko ju je sagradio? To je ta vrsta nametanja koja je prisutna kod vlasničkog softvera. Ljudi mi govore o problemu koji se događa s Unixom. Budući da proizvođači prodaju poboljšane verzije Unixa, običavaju sakupljati ispravke i ne davati ih, osim kao binarni kod. Posljedica toga je da se pogreške u programima zapravo ne ispravljaju.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: They're all duplicating effort trying to solve bugs independently.
hr: <strong>BYTE</strong>: Međusobno podvostručuju rad pokušavajući ispraviti greške svaki zasebno.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Yes.  Here is another point that helps put the problem of proprietary information in a social perspective.  Think about the liability insurance crisis.  In order to get any compensation from society, an injured person has to hire a lawyer and split the money with that lawyer.  This is a stupid and inefficient way of helping out people who are victims of accidents.  And consider all the time that people put into hustling to take business away from their competition.  Think of the pens that are packaged in large cardboard packages that cost more than the pen&mdash;just to make sure that the pen isn't stolen.  Wouldn't it be better if we just put free pens on every street corner? And think of all the toll booths that impede the flow of traffic.  It's a gigantic social phenomenon.  People find ways of getting money by impeding society.  Once they can impede society, they can be paid to leave people alone.  The waste inherent in owning information will become more and more important and will ultimately make the difference between the utopia in which nobody really has to work for a living because it's all done by robots and a world just like ours where everyone spends much time replicating what the next fellow is doing.
hr: <strong>Stallman</strong>: Tako je. Evo još jednog problema koji pomaže smjestiti problem vlasničke informacije u društvenu perspektivu. Pomislite na krizu osiguranja od odgovornosti. Kako bi dobila bilo kakvu naknadu od društva, ozlijeđena osoba mora angažirati odvjetnika i podijeliti novac s tim odvjetnikom. To je glup i neučinkovit način pomaganja ljudima koji su žrtve nesreća. A uzmite u obzir i vrijeme koje ljudi ulažu u guranje da oduzmu posao svojoj konkurenciji. Pomislite na olovke koje su pakirane u velika kartonska pakiranja koja koštaju više od olovaka&mdash;samo kako bi se osiguralo da olovka ne bude ukradena. Ne bi li bilo bolje kada bismo jednostavno stavili besplatne olovke na svako raskrižje? I pomislite na svaku naplatnu kućicu koja ometa promet. To je divovski društveni fenomen. Ljudi pronalaze način dolaska do novca tako da ometaju društvo. Jednom kada mogu ometati društvo, mogu biti plaćeni kako bi ostavili ljude na miru. Gubitak svojstven posjedovanju informacije postat će sve važniji i na kraju će tvoriti razliku između utopije u kojoj nitko zapravo ne mora zarađivati za život jer sve rade roboti i svijeta kao što je naš, gdje svatko provodi mnogo vremena radeći iznova ono što onaj do njega već radi.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Like typing in copyright notices on the software.
hr: <strong>BYTE</strong>: Kao pisanje napomena o autorskim pravima na softver.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: More like policing everyone to make sure that they don't have forbidden copies of anything and duplicating all the work people have already done because it is proprietary.
hr: <strong>Stallman</strong>: Više kao nadziranje svakoga kako bi se osiguralo da nemaju zabranjene kopije bilo čega i ponovno odrađivanje rada koji su ljudi već odradili, zato jer je vlasnički.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: A cynic might wonder how you earn your living.
hr: <strong>BYTE</strong>: Cinik bi se mogao zapitati kako zarađujete za život.

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: From consulting.  When I do consulting, I always reserve the right to give away what I wrote for the consulting job.  Also, I could be making my living by mailing copies of the free software that I wrote and some that other people wrote.  Lots of people send in $150 for GNU EMACS, but now this money goes to the Free Software Foundation that I started.  The foundation doesn't pay me a salary because it would be a conflict of interest.  Instead, it hires other people to work on GNU.  As long as I can go on making a living by consulting I think that's the best way.
hr: <strong>Stallman</strong>: Savjetovanjem. Kada savjetujem, uvijek zadržavam pravo da objavim ono što sam napisao pri savjetovanju. Također, mogao bih zarađivati za život šaljući kopije slobodnog softvera kojeg sam napisao i nekog kojeg su drugi napisali. Mnogi pošalju 150 dolara za GNU EMACS, ali sada taj novac ide Zakladi za slobodan softver koju sam pokrenuo. Zaklada mi ne isplaćuje plaću jer bi to bio sukob interesa. Umjesto toga, upošljava druge ljude da rade na GNU-u. Sve dok mogu zarađivati za život savjetovanjem, mislim da je to najbolji način.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: What is currently included in the official GNU distribution tape?
hr: <strong>BYTE</strong>: Što je trenutno uključeno na službenoj kaseti GNU distribucije?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Right now the tape contains GNU EMACS (one version fits all computers); Bison, a program that replaces <abbr title="Yet Another Compiler Compiler">YACC</abbr>; MIT Scheme, which is Professor Sussman's super-simplified dialect of LISP; and Hack, a dungeon-exploring game similar to Rogue.
hr: <strong>Stallman</strong>: Trenutno kaseta sadrži GNU EMACS (ista verzija odgovara za sva računala); Bison, program koji zamjenjuje <abbr title="Yet Another Compiler Compiler">YACC</abbr>; MIT Scheme, koji je iznimno pojednostavljeni dijalekt LISPa profesora Sussmana; i Hack, igru istraživanja labirinta sličnu igri Rogue.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: Does the printed manual come with the tape as well?
hr: <strong>BYTE</strong>: Dolazi li uz kasetu i tiskani priručnik?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: No.  Printed manuals cost $15 each or copy them yourself.  Copy this interview and share it, too.
hr: <strong>Stallman</strong>: Ne. Tiskani priručnici stoje 15 dolara po primjerku ili ih umnožite sami. Umnožite ovaj intervju i dijelite ga, također.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: How can you get a copy of that?
hr: <strong>BYTE</strong>: Kako se može dobiti primjerak toga?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: Write to the Free Software Foundation, 675 Massachusetts Ave., Cambridge, MA 02139.
hr: <strong>Stallman</strong>: Pišite Zakladi za slobodan softver, 675 Massachusetts Ave., Cambridge, MA 02139.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: What are you going to do when you are done with the GNU system?
hr: <strong>BYTE</strong>: Što ćete raditi kada dovršite GNU sustav?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I'm not sure.  Sometimes I think that what I'll go on to do is the same thing in other areas of software.
hr: <strong>Stallman</strong>: Nisam siguran. Ponekad mislim da će to biti ista stvar koju radim, ali u drugim oblastima softvera.

note: type: Content of: <div><p>
en: <strong>BYTE</strong>: So this is just the first of a whole series of assaults on the software industry?
hr: <strong>BYTE</strong>: Dakle, ovo je tek prvi od cijelog niza napada na softversku industriju?

note: type: Content of: <div><p>
en: <strong>Stallman</strong>: I hope so.  But perhaps what I'll do is just live a life of ease working a little bit of the time just to live.  I don't have to live expensively.  The rest of the time I can find interesting people to hang around with or learn to do things that I don't know how to do.
hr: <strong>Stallman</strong>: Nadam se da je tako. No možda ću jednostavno lagodno živjeti radeći malo vremena samo kako bih živio. Ne moram živjeti luksuzno. Ostatak vremena mogu provoditi u druženjima sa zanimljivim ljudima koje pronađem ili u učenju kako raditi nešto što još ne znam.

note: type: Content of: <div><div><p>
en: Please send general FSF &amp; GNU inquiries to <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.  There are also <a href="/contact/">other ways to contact</a> the FSF.  Broken links and other corrections or suggestions can be sent to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.
hr: Molimo šaljite općenite FSF &amp; GNU upite na <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.  Postoje također i <a href="/contact/">drugi načini kontaktiranja</a> FSF-a. Prekinute poveznice i druge ispravke ili prijedloge možete poslati na <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.

note: type: Content of: <div><p>
en: This page is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nd/4.0/">Creative Commons Attribution-NoDerivatives 4.0 International License</a>.
hr: Ovo djelo je dano na korištenje pod licencom <a rel="license" href="http://creativecommons.org/licenses/by-nd/4.0/deed.hr">Creative Commons Imenovanje-Bez prerada 4.0 međunarodna</a>.

note: TRANSLATORS: Use space (SPC) as msgstr if you don't want credits. type: Content of: <div><div>
en: *GNUN-SLOT: TRANSLATOR'S CREDITS*
hr: <b>Prijevod</b>: Nevenko Baričević, 2013.

note: timestamp start type: Content of: <div><p>
en: Updated:
hr: Vrijeme zadnje izmjene:
