en to unknown language translation catalogue (734 entries)

note: (title) (secondary)
en: TortoiseSVN
target: TortozSVN

note: (subtitle)
en: A Subversion client for Windows
target: Subverzioni klijent za Vindouz

note: TRANSLATORS: "$MajorVersion$.$MinorVersion$.$MicroVersion$" is a literal value and should not be translated (subtitle)
en: Version $MajorVersion$.$MinorVersion$.$MicroVersion$
target: Verzija $MajorVersion$.$MinorVersion$.$MicroVersion$

note: (edition)
en: First
target: Prvi

note: (surname)
en: Küng
target: King

note: (firstname)
en: Lübbe
target: Lube

note: (surname)
en: Large
target: Lardž

note: (title)
en: Preface
target: Uvod

note: (para)
en: Do you work in a team?
target: Da li radite u timu?

note: (para)
en: Has it ever happened that you were working on a file, and someone else was working on the same file at the same time? Did you lose your changes to that file because of that?
target: Da li vam se ikad desilo da ste radili na fajlu, i da je neko drugi radio na istom fajlu u isto vreme? Da li ste zbog toga izgubili vaše izmene tog fajla?

note: (para)
en: Have you ever saved a file, and then wanted to revert the changes you made? Have you ever wished you could see what a file looked like some time ago?
target: Da li ste ikada sačuvali fajl i onda poželeli da vratite izmene koje ste uradili? Da li ste ikada poželeli da možete da vidite kako je fajl izgledao pre nekog vremena?

note: (para)
en: Have you ever found a bug in your project and wanted to know when that bug got into your files?
target: Da li ste ikada našli bag u svom projektu i želeli da znate kada je bag nastao u vašim fajlovima.

note: (para)
en: If you answered <quote>yes</quote> to one of these questions, then TortoiseSVN is for you! Just read on to find out how TortoiseSVN can help you in your work. It's not that difficult.
target: Ako odgovorite <quote>da</quote> na ova pitanja,TortozSVN je za vas! Nastavite sa čitanjem da bi ste našli kako vam TortozSVN može pomoći u poslu. To nije tako teško.

note: (title)
en: Audience
target: Auditorijum

note: (para)
en: This book is written for computer literate folk who want to use Subversion to manage their data, but are uncomfortable using the command line client to do so. Since TortoiseSVN is a windows shell extension it's assumed that the user is familiar with the windows explorer and knows how to use it.
target: Ova knjiga je napisana za poznavaoce kompjutera koji žele da koriste Subverziju da upravljaju svojim podacima, a nije im zgodno da koriste programe koji to rade iz komandne linije. Kako je TortozSVN proširenje vindouz školjke uzima se da je korisnik upoznat sa vindouz pretraživačem i zna kako ga koristiti.

note: (title)
en: Reading Guide
target: Vodič za čitanje

note: (para)
en: This <xref linkend="tsvn-preface"/> explains a little about the TortoiseSVN project, the community of people who work on it, and the licensing conditions for using it and distributing it.
target: <xref linkend="tsvn-preface"/> objašnjava osnove TortozSVN projekta, zajednicu ljudi koji rade na njemu, i uslove licence za korišćenje i distribuciju.

note: (para)
en: The <xref linkend="tsvn-introduction"/> explains what TortoiseSVN is, what it does, where it comes from and the basics for installing it on your PC.
target:  <xref linkend="tsvn-introduction"/> objašnjava šta je TortozSVN, šta radi, odakle dolazi i osnove za instalaciju na PC.

note: (para)
en: In <xref linkend="tsvn-basics"/> we give a short introduction to the <emphasis>Subversion</emphasis> revision control system which underlies TortoiseSVN. This is borrowed from the documentation for the Subversion project and explains the different approaches to version control, and how Subversion works.
target: U <xref linkend="tsvn-basics"/> dali smo kratak uvod u <emphasis>Subverzija</emphasis> revizioni kontrolni sistem koji pokriva TortozSVN. Ovo je pozajmljeno iz dokumentacije za projekat Subverzije i objašnjava rezličite pristupe kontroli verzija, i kako Subverzija radi.

note: (para)
en: Even most Subversion users will never have to set up a server themselves. The next chapter deals with how to set up such a server, and is useful for administrators.
target: Većina Korisnika Subverzije neće nikada sami podešavati server. Sledeće poglavlje se bavi postupkom podešavanja servera i korisno je za administratore.

note: (para)
en: The chapter on <xref linkend="tsvn-repository"/> explains how to set up a local repository, which is useful for testing Subversion and TortoiseSVN using a single PC. It also explains a bit about repository administration which is also relevant to repositories located on a server.
target: Poglavlje <xref linkend="tsvn-repository"/> objašnjava kako podesiti lokalno spremište, koje je korisno za testiranje Subverzije i TortozSVN koristeći jedan PC. Ono takođe objašnjava nešto malo o administriranju spremišta što je relevantno za spremišta locirana na serveru.

note: (para)
en: The <xref linkend="tsvn-dug"/> is the most important section as it explains all the main features of TortoiseSVN and how to use them. It takes the form of a tutorial, starting with checking out a working copy, modifying it, committing your changes, etc. It then progresses to more advanced topics.
target: <xref linkend="tsvn-dug"/> je najvažniji deo jer objašnjava sve glavne mogućnosti TortozSVN i kako ih koristiti. U obliku je tutorijala, počinje proverom radne kopije, njenim izmenama, urezivanjem vaših izmena itd. Nastavlja se naprednijim temama.

note: (para)
en: <xref linkend="tsvn-subwcrev"/> is a separate program included with TortoiseSVN which can extract the information from your working copy and write it into a file. This is useful for including build information in your projects.
target: <xref linkend="tsvn-subwcrev"/> je poseban program pridodat TortozSVN koji može izdvojiti informacije iz vaše radne kopije i upisati ih u fajl. Ovo je korisno za uključivanje razvojne informacije u vaš projekat.

note: (para)
en: The <xref linkend="tsvn-howto"/> section answers some common questions about performing tasks which are not explicitly covered elsewhere.
target: <xref linkend="tsvn-howto"/> deo odgovara na neka opšta pitanja o primeni zadataka koji nisu eksplicitno pokriveni bilo gde.

note: (para)
en: The section on <xref linkend="tsvn-automation"/> shows how the TortoiseSVN GUI dialogs can be called from the command line. This is useful for scripting where you still need user interaction.
target: Deo <xref linkend="tsvn-automation"/> prikazuje kako TortozSVN GUI dijalozi mogu biti pozvani iz komandne linije. Ovo je korisno za pravljenje skripta tamo gde je još potrebna interakcija korisnika.

note: (para)
en: The <xref linkend="tsvn-cli"/> give a correlation between TortoiseSVN commands and their equivalents in the Subversion command line client <literal>svn.exe</literal>.
target: <xref linkend="tsvn-cli"/> daje korelaciju između TortozSVN komandi i njihovih ekvivalenata u Subverzija klijenta komandne linije <literal>svn.exe</literal>.

note: (title)
en: TortoiseSVN is free!
target: TortozSVN je besplatan!

note: (para)
en: TortoiseSVN is free. You don't have to pay to use it, and you can use it any way you want. It is developed under the GNU General Public License (GPL).
target: TortozSVN je besplatan. Vi ne morate da platite da bi ga koristili, možete ga koristiti kako god želite. Razvijen je pod GNU Generlnom Javnom Licencom (GJL)

note: (para)
en: TortoiseSVN is an Open Source project. That means you have full access to the source code of this program. You can browse it on this link <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/"><citetitle>http://tortoisesvn.tigris.org/svn/tortoisesvn/</citetitle></ulink>. (Username:guest, for password hit enter) The most recent version (where we're currently working) is located under <filename>/trunk/</filename> the released versions are located under <filename>/tags/</filename>.
target: TortozSVN je projekat Otvorenog Koda. To znači da imate pun pristup izvornom kodu programa. Možete ga potražiti na linku <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/"><citetitle>http://tortoisesvn.tigris.org/svn/tortoisesvn/</citetitle></ulink>. (Korisnik:guest, za lozinku pritisnite enter) Najskorija verzija (gde je izrada u toku)locirana je na <filename>/trunk/</filename> realizovana verzija je pod <filename>/tags/</filename>.

note: (title)
en: Community
target: Zajednica

note: (para)
en: Both TortoiseSVN and Subversion are developed by a community of people who are working on those projects. They come from different countries all over the world and joined together to create wonderful programs.
target: I TortozSVN i Subverzija su razvijeni od zajednice ljudi koji rade na tim projektima. Oni dolaze iz raznih zemalja iz celog sveta i udružuju se da zajedno naprave izvanredne programe.

note: (title)
en: Acknowledgments
target: Zahvalnosti

note: (para)
en: for founding the TortoiseSVN project
target: za osnivanje TortozSVN projekta

note: (term)
en: Stefan Küng
target: Stefan Kung

note: (para)
en: for the hard work to get TortoiseSVN to what it is now
target: za težak rad da se TortozSVN dovede do onog šta je sada

note: (term)
en: Lübbe Onken
target: Lube Onken

note: (para)
en: for the beautiful icons, logo, bug hunting, translating and managing the translations
target: za lepe ikone, logo, lovljenje bagova, prevođenje i upravljanjem prevodima

note: (term)
en: Simon Large
target: Simon Lardž

note: (para)
en: for helping with the documentation and bug hunting
target: za pomaganje u dokumentaciji i traženju bagova

note: (term)
en: The Subversion Book
target: Knjiga Subverzija

note: (para)
en: for the great introduction to Subversion and its chapter 2 which we copied here
target: za veliki uvod u Subverziju i poglavlje 2 koje smo kopirali ovde

note: (term)
en: The Tigris Style project
target: Tigris stil projekat

note: (para)
en: for some of the styles which are reused in this documentation
target: za neke stilove koje su preuzete u ovu dokumentaciju

note: (term)
en: Our Contributors
target: Naši dopisnici

note: (para)
en: for the patches, bug reports and new ideas, and for helping others by answering questions on our mailing list.
target: za zakrpe, report bagova i nove ideje, i za pomaganje drugima odgovaranjem na pitanja na našoj poštanskoj listi.

note: (term)
en: Our Donators
target: Naši donatori

note: (para)
en: for many hours of joy with the music they sent us
target: za mnogo časova uživanja u muzici koju su nam slali

note: (title)
en: Terminology used in this document
target: Terminologija korišćena u ovom dokumentu

note: (para)
en: To make reading the docs easier, the names of all the screens and Menus from TortoiseSVN are marked up in a different font. The <guilabel>Log Dialog</guilabel> for instance.
target: Da bi se olakšalo čitanje dokumenata imena svih ekrana i Menija u TortozSVN su obeležena u različitom pismu. Na primer <guilabel>Dialog dnevnika</guilabel>

note: (para)
en: A menu choice is indicated with an arrow. <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Show Log</guimenuitem></menuchoice> means: select <emphasis>Show Log</emphasis> from the <emphasis>TortoiseSVN</emphasis> context menu.
target: Izbor menija prikazana strelicom. <menuchoice><guimenu>TortozSVN</guimenu><guimenuitem>Dnevnik prikaza</guimenuitem></menuchoice> means: select <emphasis>Dnevniik prikaza</emphasis>iz <emphasis>TortozSVN</emphasis> meni sadržaja.

note: (para)
en: Where a local context menu appears within one of the TortoiseSVN dialogs, it is shown like this: <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Save As ...</guimenuitem></menuchoice>
target: Tamo gde se lokalni kontekstni meni  pojavljuje u okviru TortozSVN dijaloga, to je prikazano kao: <menuchoice><guimenu>Kontekstni Meni</guimenu><guimenuitem>Upamti kao ...</guimenuitem></menuchoice>

note: (para)
en: User Interface Buttons are indicated like this: Press <guibutton>OK</guibutton> to continue.
target: Dugme korisničkog interfejsa prikazano je kao: Pritisni<guibutton>DA</guibutton> da nastavi.

note: (para)
en: User Actions are indicated using a bold font. <keycap>Alt+A</keycap>: press the <keycap>Alt</keycap>-Key on your keyboard and while holding it down press the <keycap>A</keycap>-Key as well. <action>Right-drag</action>: press the right mouse button and while holding it down <emphasis>drag</emphasis> the items to the new location.
target: Korisničke akcije su prikazane korišćenjem masnog pisma. <keycap>Alt+A</keycap>: pritisni <keycap>Alt</keycap>-Taster na tastaturi i dok ga držite pritisnite <keycap>A</keycap>-tasterl. <action>Desno vučenje</action>:pritisnite desno dugme miša i dok ga držite  <emphasis>vucite</emphasis>stavku na novu lokaciju.

note: (para)
en: System output and keyboard input is indicated with a <literal>different</literal> font as well.
target: Sistemski izlaz i ulaz sa tastature označen je sa <literal>različitim</literal> pismom takođe.

note: (para)
en: Important notes are marked with an icon.
target: Važne zabeleške su označene ikonom.

note: (para)
en: Tips that make your life easier.
target: Saveti koji vam čine život lakšim.

note: (para)
en: Places where you have to be careful what you are doing.
target: Mesta gde treba da brinete  šta radite.

note: (para)
en: Where extreme care has to be taken, data corruption or other nasty things may occur if these warnings are ignored.
target: Tamo gde je izuzetna briga preduzeta, uništavanje podataka ili druge loše stvari mogu se javiti ako se upozorenja ignorišu.

note: (title)
en: Introduction
target: Uvod

note: (primary)
en: version control
target: kontrola verzije

note: (para)
en: Version control is the art of managing changes to information. It has long been a critical tool for programmers, who typically spend their time making small changes to software and then undoing or checking some of those changes the next day. Imagine a team of such developers working concurrently - and perhaps even simultaneously on the very same files! - and you can see why a good system is needed to <emphasis>manage the potential chaos</emphasis>.
target: Kontrola verzija je umetnost upravljanja izmenama informacija.To je dugo bio kritičan alat za programere, koji tipično troše svoje vreme praveći male izmene softvera zatim vraćaju ili proveravaju te izmene sledećeg dana. Zamislimo tim takvih ljudi koji rade istovremeno - i možda čak simultano na vrlo sličnim fajlovima! - i vi možete videti zašto je potreban dobar sistem da <emphasis>upravljanje potencijalnim haosom</emphasis>.

note: (title)
en: What is TortoiseSVN?
target: Šta je TortozSVN?

note: (para)
en: TortoiseSVN is a free open-source client for the <firstterm>Subversion</firstterm> version control system. That is, TortoiseSVN manages files and directories over time. Files are stored in a central <firstterm>repository</firstterm>. The repository is much like an ordinary file server, except that it remembers every change ever made to your files and directories. This allows you to recover older versions of your files and examine the history of how and when your data changed, and who changed it. This is why many people think of Subversion and version control systems in general as a sort of <quote>time machine</quote>.
target: TortozSVN je beplatan klijent otvorenog koda za <firstterm>Subverzioni</firstterm> sistem kontrole verzija. Dakle, TortozSVN upravlja fajlovima i imenicima prekovremeno. Fajlovi su smešteni u centralnom <firstterm>spremištu</firstterm>. Spremište je u mnogome kao pravi fajl server, osim što pamti svaku promenu ikada napravljenu na vašim fajlovima i imenicima. Ovo vam  dozvoljava da pozovete stare verzije vaših fajlova i proučite istoriju kako i kada su podaci promenjeni, i ko ih je promenio. Zbog toga mnogi ljudi  o Subverziji i sistemima kontrole verzija uopšteno misle da su to <quote>vremenske mašine</quote>.

note: (para)
en: Some version control systems are also software configuration management (SCM) systems. These systems are specifically tailored to manage trees of source code, and have many features that are specific to software development - such as natively understanding programming languages, or supplying tools for building software. Subversion, however, is not one of these systems; it is a general system that can be used to manage <emphasis>any</emphasis> collection of files, including source code.
target: Neki sistemi kontrole verzija su takođe softver sistemi upravljanja konfiguracijom (SUK). Ovi sistemi su specijalno priagođeni da upravljaju stabla izvornog koda, i imaju mnoge osobine specifične za razvoj softvera - kao što je prirodno razumevanje programskih jezika, ili snabdevanjem alatima za izradu softvera. Subverzija, međutim, nije jedan od tih sistema; ona je opšti sistem koji se može koristiti da upravlja <emphasis>svaki</emphasis> skup fajlova, obuhvatajući i izvorni kod.

note: (title)
en: TortoiseSVN's History
target: TortozSVN istorija

note: (para)
en: In 2002, Tim Kemp found that Subversion was a very good version control system, but it lacked a good GUI client. The idea for a Subversion client as a Windows shell integration was inspired by the similar client for CVS named TortoiseCVS.
target: U 2002 Tim Kemp je našao da je Subverzija bila jako dobar sistem kontrole verzija, ali je nedostajao dobar GUI klijent. Ideja za Sbverzioni klijent kao Vindouz integrisanu školjku inspirisana je sličnim klijentom za CVS imenom TortozCVS.

note: (para)
en: Tim studied the source code of TortoiseCVS and used it as a base for TortoiseSVN. He then started the project, registered the domain <literal>tortoisesvn.org</literal> and put the source code online. During that time, Stefan Küng was looking for a good and free version control system and found Subversion and the source for TortoiseSVN. Since TortoiseSVN was still not ready for use then he joined the project and started programming. Soon he rewrote most of the existing code and started adding commands and features, up to a point where nothing of the original code remained.
target: Tim je proučio izvorni kod TortozCVS i iskoristio ga kao osnovu za TortozSVN. On je zatim započeo sa projektom, registrujući domen <literal>tortoisesvn.org</literal> i stavio je izvorni kod onlajn. U to vreme, Stefan King je tražio dobar i besplatan sistem kontrole verzija i našao Subverziju i izvorni kod za TortozSVN. Pošto TortozSVN još nije bio spreman za korišćenje on se pridružio projektu i počeo da programira. Uskoro je prepisao većinu postojećeg koda i počeo da dodaje komande i mogućnosti, sve do tačke gde ništa od originalnog koda nije ostalo.

note: (para)
en: As Subversion became more stable it attracted more and more users who also started using TortoiseSVN as their Subversion client. The user base grew quickly (and is still growing every day). That's when Lübbe Onken offered to help out with some nice icons and a logo for TortoiseSVN. And he takes care of the website and manages the translation.
target: Što je Subverzija postajala stabilnija privlačila je sve više korisnika koji su počeli da koriste TortozSVN kao Subverzioni klijent. Korisnička osnova raste brzo (i još uvek raste svaki dan). To je od kad je Lube Onken  ponudio da pomogne sa lepim ikonama i logom za TortozSVN. On vodi brigu o vebsajtu i upravlja prevodima.

note: (title)
en: TortoiseSVN's Features
target: TortozSVN osobine

note: (para)
en: What makes TortoiseSVN such a good Subversion client? Here's a short list of features.
target: Šta čini TortozSVN tako dobrim Subverzionim klijentom? Ovde je kratka lista osobina.

note: (term)
en: Shell integration
target: Integracija školjke

note: (primary)
en: Windows shell
target: Vindouz školjka

note: (primary)
en: explorer
target: pretraživač

note: (para)
en: TortoiseSVN integrates seamlessly into the Windows shell (i.e. the explorer). This means you can keep working with the tools you're already familiar with. And you do not have to change into a different application each time you need functions of the version control!
target: TortozSVN se bešvno integriše u Vindouz školjku (tj. pretraživač). Ovo znači da možete nastaviti rad sa alatom sa kojim ste već familijarni. Vi ne morate da ulazite u drugačiju aplikaciju svaki put kada vam trebaju funkcije iz kontrole verzija!

note: (para)
en: And you are not even forced to use the Windows Explorer. TortoiseSVN's context menus work in many other file managers, and in the File/Open dialog which is common to most standard Windows applications. You should, however, bear in mind that TortoiseSVN is intentionally developed as extension for the Windows Explorer. Thus it is possible that in other applications the integration is not as complete and e.g. the icon overlays may not be shown.
target: I niste čak ni obavezni da koristite Vindouz Eksplorer. TortozSVNov kontekst meni radi u mnogim drugim fajl menadžerima, i u Fajl/Otvori dijalogu koji je zajednički za većinu standardnih Vindouz aplikacija. Vi treba, međutim, imati na umu da TortozSVN namerno razvijen kao proširenje za Vindouz Eksplorer. Zbog toga je moguće da u drugim aplikacijama integracija nije kompletna i npr. ikone za prekrivanje možda neće biti prikazane.

note: (term)
en: Icon overlays
target: Ikone prekrivači

note: (para)
en: The status of every versioned file and folder is indicated by small overlay icons. That way you can see right away what the status of your working copy is.
target: Status svakog verzionisanog fajla i imenika označen je prekrivanjem ikonom. Na taj način možete videti status vaše radne kopije.

note: (term)
en: Easy access to Subversion commands
target: Lak pristup Subverzionim komandama.

note: (para)
en: All Subversion commands are available from the explorer context menu. TortoiseSVN adds its own submenu there.
target: Sve Subverzione komande su dostupne iz eksplorerovog kontekstnog menija. TortozSVN dodaje svoj submeni onde.

note: (para)
en: Since TortoiseSVN is a Subversion client, we would also like to show you some of the features of Subversion itself:
target: Kako je TortozSVN Subverzioni klijent, mi bismo voleli da prikažemo neke osobine same Subverzije:

note: (term)
en: Directory versioning
target: Verzionisanje imenika

note: (para)
en: CVS only tracks the history of individual files, but Subversion implements a <quote>virtual</quote> versioned filesystem that tracks changes to whole directory trees over time. Files <emphasis>and</emphasis> directories are versioned. As a result, there are real client-side <command>move</command> and <command>copy</command> commands that operate on files and directories.
target: CVS obeležava samo istoriju individualnih fajlova, dok Subverzija implementira<quote>virtualni</quote> verzionisani fajlsistem koji beleži promene celog stabla  imenika prekovremeno. Fajlovi <emphasis>i</emphasis> imenici su verzionisani. Kao reziltat, postoji prava klijent-strana <command>premesti</command> i <command>kopiraj</command> komande koje rade na fajlovima i imenicima.

note: (term)
en: Atomic commits
target: Atomsko urezivanje

note: (para)
en: A commit either goes into the repository completely, or not at all. This allows developers to construct and commit changes as logical chunks.
target: Urezivanje ili ide u spremište kompletno, ili ništa. Ovo omogućava ljudima iz razvoja da naprave i urežu izmene kao logičke delove.

note: (term)
en: Versioned metadata
target: Verzionisani metapodaci

note: (para)
en: Each file and directory has an invisible set of <quote>properties</quote> attached. You can invent and store any arbitrary key/value pairs you wish. Properties are versioned over time, just like file contents.
target: Svaki fajl i imenik ima dodat nevidljivi skup <quote>osobina</quote>. Vi možete smisliti i smestiti bilo koji ključ/vrednost par koji želite. Osobine se verzionišu prekovremeno, upravo kao sadržaji fajla.

note: (term)
en: Choice of network layers
target: Izbor mrežnih slojeva

note: (para)
en: Subversion has an abstracted notion of repository access, making it easy for people to implement new network mechanisms. Subversion's <quote>advanced</quote> network server is a module for the Apache web server, which speaks a variant of HTTP called WebDAV/DeltaV. This gives Subversion a big advantage in stability and interoperability, and provides various key features for free: authentication, authorization, wire compression, and repository browsing, for example. A smaller, standalone Subversion server process is also available. This server speaks a custom protocol which can be easily tunneled over ssh.
target: Subverzija ima apstraktnu ideju pristupa spremištu, čineći ga lakim da ljudi inplementiraj u nove mrežne mehanizme.Subverzioni <quote>napredni</quote> mrežni serverje modul za apač veb server, koji govori varijantu HTTP zvanu VebDAV/DeltaV. To daje Subverziji veliku prednost u stabilnosti i operatibilnosti, i omogućava razne ključne osobine besplatno: autentikaciju, autorizaciju, compresiju, i pretraživanje spremišta, na primer.Mali, samostalni Subverzioni server proces je takođe dostupan. Ovaj server govori uopbičajeni protokol koji može biti lako provučen kroz ssh.

note: (term)
en: Consistent data handling
target: Skladno rukovanje podacima

note: (para)
en: Subversion expresses file differences using a binary differencing algorithm, which works identically on both text (human-readable) and binary (human-unreadable) files. Both types of files are stored equally compressed in the repository, and differences are transmitted in both directions across the network.
target: Subverzija izlaže fajl razlike koristeći binarni diferencijalni algoritam, koji radi identično na tekst (ljudski čitljivim) i binarnim (ljudski nečitljivim) fajlovima. Oba tipa fajlova su smeštena jednako komprimovani u spremištu, i razlike su prenete u oba smera kroz mrežu.

note: (term)
en: Efficient branching and tagging
target: Efikasno grananje i označavanje

note: (para)
en: The cost of branching and tagging need not be proportional to the project size. Subversion creates branches and tags by simply copying the project, using a mechanism similar to a hard-link. Thus these operations take only a very small, constant amount of time, and very little space in the repository.
target: Cena grananja i označavanja ne treba da bude proporcionalno veličini projekta. Subverzija stvara grane i značke jednostavnim kopiranjem projekta, koristeći mehanizam sličan čvrstim linkovima. Zato ove operacije uzimaju veoma mali, konstantan iznos vremena, i veoma mali prostor u spremištu.

note: (term)
en: Hackability
target: Hakerabiliti

note: (para)
en: Subversion has no historical baggage; it is implemented as a collection of shared C libraries with well-defined APIs. This makes Subversion extremely maintainable and usable by other applications and languages.
target: Subverzija nema istrijski prtljag; ona je implementirana kao kolekcija deljivih C biblioteka sa dobro definisanim APIjem. To čini Subverziju ekstremno podržavajućom i iskoristivom  od drugih aplikacija i jezika.

note: (title)
en: Installing TortoiseSVN
target: Instaliranje TortozSVN

note: (title)
en: System requirements
target: Zahtevi sistema

note: (para)
en: TortoiseSVN runs on Windows 2000 SP2, Windows XP or higher. Windows 98, Windows ME and Windows NT4 are no longer supported since TortoiseSVN 1.2.0, but you can still download the older versions if you really need them.
target: TortozSVN radi na Vindouz 2000 SO2, Vindouz XP ili viši, Vindouz ME i Vindouz NT4 više nisu podržani od TortozSVN 1.2.0, ali još možete preneti stare verzije ako su vam stvarno potrebne.

note: (para)
en: If you encounter any problems during or after installing TortoiseSVN please refer to <xref linkend="tsvn-faq"/> first.
target: Ako naiđete na bilo kakav problem posle instaliranja TortozSVN molim obratite se <xref linkend="tsvn-faq"/> najpre.

note: (title)
en: Installation
target: Instalacija

note: (primary)
en: install
target: instaliraj

note: (para)
en: TortoiseSVN comes with an easy to use installer. Double click on the installer file and follow the instructions. The installer will take care of the rest.
target: TortozSVN dolazi sa instalatorom koji je lak za upotrebu. Dvostruko kliknite na instalator fajl  i pratite instrukcije. Instalator će brinuti o ostalom.

note: (para)
en: You need Administrator privileges to install TortoiseSVN.
target: Potrebne su vam Administratorske privelegije da instalirate TortozSVN.

note: (title)
en: Language Packs
target: Jezički paketi

note: (primary)
en: language packs
target: jezički paketi

note: (primary)
en: translations
target: prevodi

note: (para)
en: The TortoiseSVN user interface has been translated into many different languages, so you may be able to download a language pack to suit your needs. You can find the language packs on our <ulink url="http://tortoisesvn.net/translation_status"><citetitle>translation status page</citetitle></ulink>. And if there is no language pack available yet, why not join the team and submit your own translation ;-)
target: TortozSVN korisnički interfejs je preveden na mnoge različite jezike, tako da možete da prenesete jezički paket koji vam je potreban. Jezičke pakete možete naći na <ulink url="http://tortoisesvn.net/translation_status"><citetitle>translation status page</citetitle></ulink>. I ako jezički paket još nije dostupan, zašto se ne priključiti timu i podnesete svoj lični prevod; -)

note: (para)
en: Each language pack is packaged as a <literal>.exe</literal> installer. Just run the install program and follow the instructions. Next time you restart, the translation will be available.
target: Svaki jezički paket je spakovanu kao <literal>.exe</literal> instalacija. Samo izvršite instalacioni program i sledite instrukcije. Sledeći put kad restartuje kompjuter prevod će biti dostupan.

note: (title)
en: Spellchecker
target: Pravopiskontrola

note: (primary)
en: spellchecker
target: pravopiskontrola

note: (primary)
en: dictionary
target: rečnik

note: (para)
en: TortoiseSVN includes a spell checker which allows you to check your commit log messages. This is especially useful if the project language is not your native language. The spell checker uses the same dictionary files as <ulink url="http://openoffice.org"><citetitle>OpenOffice</citetitle></ulink> and <ulink url="http://mozilla.org"><citetitle>Mozilla</citetitle></ulink>.
target: TortozSVN uključuje kontrolu pravopisa koja vam dozvoljava da kontrolišete vaše poruke dnevnika urezivanja. Ovo je naročito korisno ako jezik projekta nije vaš maternji jezik. Kontrolor pravopisa koristi iste fajlove rečnika kao <ulink url="http://openoffice.org"><citetitle>OpenOffice</citetitle></ulink> i <ulink url="http://mozilla.org"><citetitle>Mozilla</citetitle></ulink>.

note: (para)
en: The installer automatically adds the US and UK English dictionaries. If you want other languages, the easiest option is simply to install one of TortoiseSVN's language packs. This will install the appropriate dictionary files as well as the TortoiseSVN local user interface. Next time you restart, the dictionary will be available too.
target: Instalacija automatski dodaje US i UK Engleski rečnik. Ako želite druge jezike, najlakša mogućnost je da instalirate jedan od TortozSVN jezičkih paketa. To će instalirati odgovarajuće fajlove rečnika kao i TortozSVN lokalni korisnički interfejs. Po restartovanju kompjutera rečnik će takođe biti dostupan.

note: (para)
en: Or you can install the dictionaries yourself. If you have OpenOffice or Mozilla installed, you can copy those dictionaries, which are located in the installation folders for those applications. Otherwise, you need to download the required dictionary files from <ulink url="http://wiki.services.openoffice.org/wiki/Dictionaries"><citetitle>http://wiki.services.openoffice.org/wiki/Dictionaries</citetitle></ulink>
target: Ili možete instalirati rečnik sami. Ako imate OpenOfis ili Mozilu instalirane možete kopirati njihove rečnike, koji su smešteni u instalacionom imeniku tih aplikacija. Inače, potrebno je da prenesete željene fajlove rečnika sa <ulink url="http://wiki.services.openoffice.org/wiki/Dictionaries"><citetitle>http://wiki.services.openoffice.org/wiki/Dictionaries</citetitle></ulink>

note: (para)
en: Once you have got the dictionary files, you probably need to rename them so that the filenames only have the locale chars in it. Example: <placeholder-1/> Then just copy them to the <filename>bin</filename> sub-folder of the TortoiseSVN installation folder. Normally this will be <filename>C:\Program Files\TortoiseSVN\bin</filename>. If you don't want to litter the <filename>bin</filename> sub-folder, you can instead place your spell checker files in <filename>C:\Program Files\TortoiseSVN\Languages</filename>. If that folder isn't there, you have to create it first. The next time you start TortoiseSVN, the spell checker will be available.
target: Jednom kad imate fajlove rečnika, verovatno će trebati da ih preimenujete tako imena fajlova imaju samo lokalne karaktere. Primer:<placeholder-1/> Zatim samo ih kopirajte u <filename>bin</filename> sub-imenik TortozSVN instalacionog imenika. Normalno to će biti <filename>C:\Program Files\TortoiseSVN\bin</filename>. Ako ne želite da opterećujete <filename>bin</filename> sub-imenik, umesto toga možete smestiti kontrolne fajlove u filename>C:\Program Files\TortoiseSVN\Languages</filename>. Ako nema tog imenika, kreirajte ga. Kada sledeći put pokrenete TortozSVN, pravopisna kontrola će biti dostupna.

note: (para)
en: Check the <literal>tsvn:projectlanguage</literal> setting. Refer to <xref linkend="tsvn-dug-propertypage"/> for information about setting project properties.
target: Proverite <literal>tsvn:projectlanguage</literal> podešavanje. Pogledajte <xref linkend="tsvn-dug-propertypage"/> za informacije o podešavanju osobina projekta.

note: (para)
en: If no project language is set, or that language is not installed, try the language corresponding to the Windows locale.
target: Ako jezik projekta nije označen, ili taj jezik nije instaliran, probajte jezik koji odgovara Vindouz lokalnom jeziku.

note: (para)
en: If the exact Windows locale doesn't work, try the <quote>Base</quote> language, eg. <literal>de_CH</literal> (Swiss-German) falls back to <literal>de_DE</literal> (German).
target: Ako pravi Vindouz lokalni jezik ne funkcioniše, probajte <quote>Osnovni</quote> jezik, npr. <literal>de_CH</literal> (Švajcarska-Nemački) ide na  <literal>de_DE</literal> (Nemački).

note: (para)
en: If none of the above works, then the default language is English, which is included with the standard installation.
target: Ako ništa od navedenog ne radi, tada je uobičajeni jezik Engleski, koji je uključen u standardnu instalaciju.

note: (para)
en: If you install multiple dictionaries, TortoiseSVN uses these rules to select which one to use. <placeholder-1/>
target: Ako instalirate više rečnika. TortozSVN koristi ova pravila da izabere jedan za korišćenje.<placeholder-1/>

note: (title)
en: Basic Concepts
target: Osnovni koncept

note: (primary)
en: Subversion book
target: Subverziona knjiga

note: (para)
en: This chapter is a slightly modified version of the same chapter in the Subversion book. An online version of the Subversion book is available here: <ulink url="http://svnbook.red-bean.com/"><citetitle>http://svnbook.red-bean.com/</citetitle></ulink>.
target: Ovo poglavlje je malo izmenjena verzija istog poglavlja u Subverzionoj knjizi. Onlajn verzija Subverzione knjige je dostupna ovde:<ulink url="http://svnbook.red-bean.com/"><citetitle>http://svnbook.red-bean.com/</citetitle></ulink>.

note: (para)
en: This chapter is a short, casual introduction to Subversion. If you're new to version control, this chapter is definitely for you. We begin with a discussion of general version control concepts, work our way into the specific ideas behind Subversion, and show some simple examples of Subversion in use.
target: Ovo poglavlje je kratak, neobavezan uvod u Subverziju. Ako ste novi u kontroli verzija, ovo poglavlje je sigurno za vas. Počinjemo diskusijom o opštem konceptu kontrole verzija, rad nas vodi u specifične ideje unutar Subverzije, i prikazuje neke jednostavne primere Subverzije pri korišćenju.

note: (para)
en: Even though the examples in this chapter show people sharing collections of program source code, keep in mind that Subversion can manage any sort of file collection - it's not limited to helping computer programmers.
target: Uprkos tome što primeri u ovom poglavlju prikazuju ljudske deljive kolekcije izvornog koda programa, imajte na umu da Subverzija može upravljati bilo kojom vrstom kolekcije fajlova - nije ograničena na pomoć komputerskim programerima.

note: (title)
en: The Repository
target: Spremište

note: (primary)
en: repository
target: spremište

note: (para)
en: Subversion is a centralized system for sharing information. At its core is a <firstterm>repository</firstterm>, which is a central store of data. The repository stores information in the form of a <firstterm>filesystem tree</firstterm> - a typical hierarchy of files and directories. Any number of <firstterm>clients</firstterm> connect to the repository, and then read or write to these files. By writing data, a client makes the information available to others; by reading data, the client receives information from others.
target: Subverzija je centralizovan sistem za deljenje informcija. U srži je <firstterm>spremište</firstterm>, koje je centralno stovarište podataka. Spremište smešta informacije u obliku <firstterm>fajlsistem stabla</firstterm> - tipična hijerarhija fajlova i imenika. Bilo koji broj <firstterm>klijenata</firstterm> spaja se na spremište i čita ili upisuje u te fajlove. Upisivanjem podataka klijent omogućava da informacija bude dostupna drugima; čitanjem podataka klijent prima informacije od drugih.

note: (title)
en: A Typical Client/Server System
target: Tipični klijent/server sistem

note: (para)
en: So why is this interesting? So far, this sounds like the definition of a typical file server. And indeed, the repository <emphasis>is</emphasis> a kind of file server, but it's not your usual breed. What makes the Subversion repository special is that <emphasis>it remembers every change</emphasis> ever written to it: every change to every file, and even changes to the directory tree itself, such as the addition, deletion, and rearrangement of files and directories.
target: Dakle zašto je ovo interesantno? Zato što je pesma od definicije tipičnog fajl servera. I svakako, spremište <emphasis>je</emphasis> vrsta fajl servera, ali nije to vaš uobičajen soj. Šta čini Subverziono spremište specijalnim je da  <emphasis>ono pamti sve izmene</emphasis> ikad upisane u njega: sve izmene svakog fajla, i čak izmene samog stabla imenika, kao što je dodavanje, brisanje, i preuređenje fajlova u imenika.

note: (para)
en: When a client reads data from the repository, it normally sees only the latest version of the filesystem tree. But the client also has the ability to view <emphasis>previous</emphasis> states of the filesystem. For example, a client can ask historical questions like, <quote>what did this directory contain last Wednesday?</quote>, or <quote>who was the last person to change this file, and what changes did they make?</quote> These are the sorts of questions that are at the heart of any <firstterm>version control system</firstterm>: systems that are designed to record and track changes to data over time.
target: Kada klijent čita podatke iz spremišta, on normalno vidi samo zadnju verziju stabla fajlsistema. Ali klijent takođe ima mogućnost da vidi <emphasis>prethodno</emphasis> stanje fajlsistema. Na primer, klijent može postaviti istorijska pitanja kao,  <quote>šta je ovaj imenik sadržao prošle srede?</quote>, ili <quote>koja je poslednja osoba koja je menjala ovaj fajl, i koje izmene je uradila?</quote> Ovo je vrsta pitanja koja su srce svakog  <firstterm>sistema kontrole verzija</firstterm>: sistema koji su dizajnirani da aktivno beleže i prate izmene podataka.

note: (title)
en: Versioning Models
target: Modeli verzionisanja

note: (para)
en: All version control systems have to solve the same fundamental problem: how will the system allow users to share information, but prevent them from accidentally stepping on each other's feet? It's all too easy for users to accidentally overwrite each other's changes in the repository.
target: Svi sistemi kontrole verzija imaju da reše iste osnovne probleme: kako će sistem omogućiti korisnicima da dele informacije, ali da ih spreči da nehotično koračaju stopama jedni drugih? Veoma je lako da jedni drugima korisnici  incidentno prepišu promene u spremištu.

note: (title)
en: The Problem of File-Sharing
target: Problem Fajl-Podele

note: (para)
en: Consider this scenario: suppose we have two co-workers, Harry and Sally. They each decide to edit the same repository file at the same time. If Harry saves his changes to the repository first, then it's possible that (a few moments later) Sally could accidentally overwrite them with her own new version of the file. While Harry's version of the file won't be lost forever (because the system remembers every change), any changes Harry made <emphasis>won't</emphasis> be present in Sally's newer version of the file, because she never saw Harry's changes to begin with. Harry's work is still effectively lost - or at least missing from the latest version of the file - and probably by accident. This is definitely a situation we want to avoid!
target: Zamislimo ovaj scenario: pretpostavimo da imamo dva saradnika, Hari i Sali. Svaki odluči da uredi isti fajl iz spremišta  u isto vreme. Ako Hari prvi sačuva svoje izmene u spremište, tada je moguće (nekoliko trenutaka kasnije) da ih Sali nehotice prepiše svojom novom verzijom fajla. Pošto Harijeva verzija fajla neće biti izgubljena zauvek (jer sistem pamti sve promene), sve promene koje je uradio Hari <emphasis>neće</emphasis> biti prisutne u Salinu noviju verziju fajla, jer ona nije videla Harijeve izmene na početku rada. Harijev rad je efektivno izgubljen - ili u najmanjem nedostaje u zadnjoj verziji fajla - i verovatno mimo plana. Ovo je defintivno situacija koju želimo da izbegnemo.

note: (title)
en: The Problem to Avoid
target: Problem izbegavanja

note: (title)
en: The Lock-Modify-Unlock Solution
target: Zaključaj-Menjaj-Otključaj rešenje

note: (para)
en: Many version control systems use a <firstterm>lock-modify-unlock</firstterm> model to address this problem, which is a very simple solution. In such a system, the repository allows only one person to change a file at a time. First Harry must <emphasis>lock</emphasis> the file before he can begin making changes to it. Locking a file is a lot like borrowing a book from the library; if Harry has locked a file, then Sally cannot make any changes to it. If she tries to lock the file, the repository will deny the request. All she can do is read the file, and wait for Harry to finish his changes and release his lock. After Harry unlocks the file, his turn is over, and now Sally can take her turn by locking and editing.
target: Mnogi sistemi kontrole verzija koriste <firstterm>zaključaj-izmeni-otključaj</firstterm> model da označe ovaj problem, što je veoma jednostavno rešenje. U takvim sistemima, spremište dozvoljava samo jednoj osobi da menja fajl u isto vreme. Prvo Hari mora <emphasis>zaključati</emphasis> fajl pre nego što može da ga menja. Zaključavanje fajla je mnogo slično pozajmljivanju knjige iz biblioteke; ako Hari ima zaključani fajl, onda Sali ne može da napravi bilo kakvu izmenu na njemu. Ako ona pokuša da zaključa fajl spremište će zabraniti zahtev. Sve što može uraditi je da čita fajl i čeka da Hari završi svoje izmene i otključa fajl. Kada Hari otključa fajl, on ga vraća i Sali  ga može uzeti zaključavanjem i da ga uređuje.

note: (para)
en: The problem with the lock-modify-unlock model is that it's a bit restrictive, and often becomes a roadblock for users:
target: Problem sa zaključaj-izmeni-otključaj modelom je da je pomalo restriktiv i često postaje prepreka za korisnike:

note: (para)
en: <emphasis>Locking may cause administrative problems.</emphasis> Sometimes Harry will lock a file and then forget about it. Meanwhile, because Sally is still waiting to edit the file, her hands are tied. And then Harry goes on vacation. Now Sally has to get an administrator to release Harry's lock. The situation ends up causing a lot of unnecessary delay and wasted time.
target: <emphasis>Zaključavanje može da napravi administrativni problem.</emphasis> Ponekad Hari će zaključati fajl i zaboraviti na njega. Međutim, pošto Sali još čeka da uredi fajl, njene ruke se vezane. I onda Hari odlazi na odmor. Sada Sali ima da dobije od Administratora oslobađanje Harijevog zaključavanja. Situacija se završava uzrokujući puno nepotrebnog kašnjenja i izgubljenog vremena.

note: (para)
en: <emphasis>Locking may cause unnecessary serialization.</emphasis> What if Harry is editing the beginning of a text file, and Sally simply wants to edit the end of the same file? These changes don't overlap at all. They could easily edit the file simultaneously, and no great harm would come, assuming the changes were properly merged together. There's no need for them to take turns in this situation.
target: <emphasis>Zaključavanje može da prouzrokuje neželjenu serijalizaciju.</emphasis> Šta ako Hari uređuje početak tekst fajla, a Sali jednostavno želi da uredi kraj istog fajla? Ove izmene se uopšte ne preklapaju. Oni mogu lako da uredjuju fajl istovremeno, neće doći do velike štete, uzevši da se izmene odgovarajuće ujedine. Njima nije potrebno da se okrenu od ovakve situacije.

note: (para)
en: <emphasis>Locking may create a false sense of security.</emphasis> Pretend that Harry locks and edits file A, while Sally simultaneously locks and edits file B. But suppose that A and B depend on one another, and the changes made to each are semantically incompatible. Suddenly A and B don't work together anymore. The locking system was powerless to prevent the problem - yet it somehow provided a sense of false security. It's easy for Harry and Sally to imagine that by locking files, each is beginning a safe, insulated task, and thus inhibits them from discussing their incompatible changes early on.
target: <emphasis>Zaključavanje može da stvori lažni osećaj sigurnosti.</emphasis> Uzmimo da Hari zaključa i uređuje fajl A, dok Sali istovremeno zaključa i uređuje fajl B. Pretpostavimo da A i B zavise jedan od drugog i da izmene urađene na bilo kome semantički nisu kompatibilne. Iznenada A i B ne rade više zajedno. Zaključavajući sistem nema snage da predupredi problem - čak nekako daje osećaj lažne sigurnosti. Lako je da Hari i Sali zamisle to zaključavanjem fajlova, svako počinje siguran, izdvojen zadatak i to ga sprečava da razmatra nekompatibilne izmene učinjene ranije.

note: (title)
en: The Copy-Modify-Merge Solution
target: Kopiraj-Menjaj-Spoji rešenje

note: (para)
en: Subversion, CVS, and other version control systems use a <firstterm>copy-modify-merge</firstterm> model as an alternative to locking. In this model, each user's client reads the repository and creates a personal <firstterm>working copy</firstterm> of the file or project. Users then work in parallel, modifying their private copies. Finally, the private copies are merged together into a new, final version. The version control system often assists with the merging, but ultimately a human being is responsible for making it happen correctly.
target: Subverzija, CVS i drugi sistemi kontrole verzija koriste <firstterm>kopiraj-menjaj-spoji</firstterm> model kao alternativu zaključavanju. U ovom modelu svaki korisnički klijent čita spremište i kreira ličnu <firstterm>radnu kopiju</firstterm> fajla ili projekta. Korisnici onda rade paralelno, menjajući svoje privatne kopije. Finalno, privatne kopije se spajaju u novu, finalnu verziju. Sistem kontrole verzija često posreduje u spajanju, ali ljudi su odgovorni da učine da sve bude korektno.

note: (para)
en: Here's an example. Say that Harry and Sally each create working copies of the same project, copied from the repository. They work concurrently, and make changes to the same file <filename>A</filename> within their copies. Sally saves her changes to the repository first. When Harry attempts to save his changes later, the repository informs him that his file A is <firstterm>out-of-date</firstterm>. In other words, that file A in the repository has somehow changed since he last copied it. So Harry asks his client to <firstterm>merge</firstterm> any new changes from the repository into his working copy of file A. Chances are that Sally's changes don't overlap with his own; so once he has both sets of changes integrated, he saves his working copy back to the repository.
target: Evo primera. Recimo da Hari i Sali kreiraju radne kopije istog projekta, kopiranjem iz spremišta. Oni rade istovremeno, i prave izmene na istom fajlu <filename>A</filename> u okviru svojih kopija. Sali sačuva svoje izmene u spremište prva. Kada Hari pokuša da sačuva svoje izmene kasnije, spremište ga informiše da je njegov fajl A firstterm>zastareo</firstterm>. Drugim rečima, fajl A u spremištu ima nečije izmene od zadnjeg kopiranja. Tako Hari pita svog klijenta da <firstterm>spoji</firstterm> bilo koje nove izmene iz spremišta u njegovu radnu kopiju fajla A. Postoji šansa da Saline izmene ne prekrivaju njegove; tako da će imati oba skupa izmena integrisano, on sačuva svoju radnu kopiju nazad u spremište.

note: (title)
en: ...Copy-Modify-Merge Continued
target: ...Kopiraj-Menjaj-Spoji nastavak

note: (primary)
en: conflict
target: konflikt

note: (para)
en: But what if Sally's changes <emphasis>do</emphasis> overlap with Harry's changes? What then? This situation is called a <firstterm>conflict</firstterm>, and it's usually not much of a problem. When Harry asks his client to merge the latest repository changes into his working copy, his copy of file A is somehow flagged as being in a state of conflict: he'll be able to see both sets of conflicting changes, and manually choose between them. Note that software can't automatically resolve conflicts; only humans are capable of understanding and making the necessary intelligent choices. Once Harry has manually resolved the overlapping changes (perhaps by discussing the conflict with Sally!), he can safely save the merged file back to the repository.
target: Ali šta ako Saline izmene <emphasis>prekrivaju</emphasis> Harijeve izmene? Šta tada? Ova situacija se zove <firstterm>konflikt</firstterm>, i to obično nije veliki problem. Kada Hari traži od svog klijenta da spoji zadnje izmene u spremištu u njegovu radnu kopiju, njegova kopija fajla A je nekako označena da je u stanju konflikta: on će biti u mogućnosti da vidi oba skupa konfliktnih izmena, i ručno da izabere između njih. Primetimo da softver ne može automatski da reši konflikt; samo ljudi su sposobni da razumeju i urade neophodne inteligentne izbore. Jednom kad Hari ručno reši preklapanje izmena (možda diskusijom konflikta sa Sali!), on može bezbedno da sačuva spojen fajl nazad u spremište.

note: (para)
en: The copy-modify-merge model may sound a bit chaotic, but in practice, it runs extremely smoothly. Users can work in parallel, never waiting for one another. When they work on the same files, it turns out that most of their concurrent changes don't overlap at all; conflicts are infrequent. And the amount of time it takes to resolve conflicts is far less than the time lost by a locking system.
target: Kopiraj-menjaj-spoji model može da zvuči pomalo haotično, ali u praksi, radi ekstremno glatko. Korisnici mogu da rade paralelno, nikada ne čekaju jedan drugog. Kada rade na istim fajlovima isključeno je da njihove istovremene izmene ne budu upisane; konflikti su retki. I iznos vremena uzet za rešavanje konflikta je manji od vremena izgubljenog zaključavanjem sistema.

note: (para)
en: In the end, it all comes down to one critical factor: user communication. When users communicate poorly, both syntactic and semantic conflicts increase. No system can force users to communicate perfectly, and no system can detect semantic conflicts. So there's no point in being lulled into a false promise that a locking system will somehow prevent conflicts; in practice, locking seems to inhibit productivity more than anything else.
target: Na kraju, sve dolazi u jedan kritičan faktor: korisnička komunikacija. Kada je loša komunikacija između korisnika sintaksni i semantički konflikti rastu. Nema sistema koji će naterati korisnike da kompuniciraju perfektno, i nema sistema koji može da detektuje semantički konflikt. Tako da nije poenta da se bude umiren lažnim obećanjem da sistem zaključavanja nekako predupređuje konflikt; u praksi, zaključavanje izgleda sprečava više produktivnost nego bilo šta drugo.

note: (para)
en: There is one common situation where the lock-modify-unlock model comes out better, and that is where you have unmergeable files. For example if your repository contains some graphic images, and two people change the image at the same time, there is no way for those changes to be merged together. Either Harry or Sally will lose their changes.
target: Postoji jedna obična situacija gde zaključaj-menjaj-otključaj model je bolji, i to je gde imate ne spojive fajlove. Na primer ako vaše spremište sadrži neke grafičke slike, i dva čoveka menjaju slike u isto vreme, nema načina da se te izmene spoje zajedno. Ili Hari ili Sali će izgubiti svoje izmene.

note: (title)
en: What does Subversion Do?
target: Šta Subverzija radi?

note: (para)
en: Subversion uses the copy-modify-merge solution by default, and in many cases this is all you will ever need. However, as of Version 1.2, Subversion also supports file locking, so if you have unmergeable files, or if you are simply forced into a locking policy by management, Subversion will still provide the features you need.
target: Subverzija koristi kopiraj-izmeni-spoji rešenje uobičajeno, i u mnogim slučajevimaovo je sve što vam je potrebno. Međutim, od Verzije 1.2 Subverzija takođe podržava zaključavanje fajlova, tako da ako imate nespojive fajlove, ili ako jednostavno forsirate politiku zaključavanja preko uprave, Subverzija će još omogućavati željene osobine.

note: (title)
en: Subversion in Action
target: Subverzija u akcija

note: (title)
en: Working Copies
target: Radna kopija

note: (primary)
en: working copy
target: radna kopija

note: (para)
en: You've already read about working copies; now we'll demonstrate how the Subversion client creates and uses them.
target: Već ste čitali o radnoj kopiji; sada ćemo demonstrirati kako je Subverzioni klijent kreira i koristi.

note: (para)
en: A Subversion working copy is an ordinary directory tree on your local system, containing a collection of files. You can edit these files however you wish, and if they're source code files, you can compile your program from them in the usual way. Your working copy is your own private work area: Subversion will never incorporate other people's changes, nor make your own changes available to others, until you explicitly tell it to do so.
target: Subverziona radna kopija je obično stablo imenika u vašem lokalnom sistemu, koje sadrži kolekciju fajlova. Vi možete urediti ove fajlove kako želite, i  ako su fajlovi izvornog koda, možete kompajlirati vaš program od njih na uobičajen način. Vaša radna kopija je vaša lična privatna radna površina: Subverzija neće inkorporirati izmene drugih ljudi, niti će uraditi vaše promene dostupne drugima, sve dok joj eksplicitno ne kažete da to uradi.

note: (para)
en: After you've made some changes to the files in your working copy and verified that they work properly, Subversion provides you with commands to <emphasis>publish</emphasis> your changes to the other people working with you on your project (by writing to the repository). If other people publish their own changes, Subversion provides you with commands to merge those changes into your working directory (by reading from the repository).
target: Kada ste napravili neke izmene u fajlovima u vašoj radnoj kopiji i proverite da to radi ispravno, Subverzija vam omogućava komandama da <emphasis>publikujete</emphasis> vaše izmene drugim ljudima koji rade sa vama na vašem projektu (pisanjem u spremište). Ako drugi ljudi publikuju svoje izmene, Subverzija vam omogućava  komandama za spajanje tih izmena u vaš radni imenik (čitanjem iz spremišta).

note: (para)
en: A working copy also contains some extra files, created and maintained by Subversion, to help it carry out these commands. In particular, each directory in your working copy contains a subdirectory named <filename>.svn</filename>, also known as the working copy <firstterm>administrative directory</firstterm>. The files in each administrative directory help Subversion recognize which files contain unpublished changes, and which files are out-of-date with respect to others' work.
target: Radna kopija takođe sadrži neke ekstra fajlove, kreirane i održavane Subverzijom, dajoj  pomognu da izvuče ove komande. Posebno, svaki imenik u vašoj radnoj kopiji sadrži podimenike označene <filename>.svn</filename>, takođe poznat kao radna kopija <firstterm>administrativni imenik</firstterm>. Fajlovi u svakom administrativnom imeniku pomažu Subverziji da prepozna koji fajlovi sadrže nepublikovane izmene, i koji fajlovi su zastreli u odnosu na rad drugih.

note: (para)
en: A typical Subversion repository often holds the files (or source code) for several projects; usually, each project is a subdirectory in the repository's filesystem tree. In this arrangement, a user's working copy will usually correspond to a particular subtree of the repository.
target: Tipično Subverziono spremište često sadrži fajlove (ili izvorni kod) za više projekata; obično, svaki projekat je subimenik u stablu fajlsistema u spremištu. U ovom uređenju korisnička radna kopija obično će korespondirati posebnom podstablu spremišta.

note: (para)
en: For example, suppose you have a repository that contains two software projects.
target: Na primer, pretpostavimo da imate spremište koje sadrži dva sofverska projekta.

note: (title)
en: The Repository's Filesystem
target: Fajlsistem spremišta

note: (para)
en: In other words, the repository's root directory has two subdirectories: <filename>paint</filename> and <filename>calc</filename>.
target: Drugim rečima, koreini imenik spremišta ima dva podimenika: <filename>pejnt</filename> i <filename>kalk</filename>.

note: (para)
en: To get a working copy, you must <firstterm>check out</firstterm> some subtree of the repository. (The term <emphasis>check out</emphasis> may sound like it has something to do with locking or reserving resources, but it doesn't; it simply creates a private copy of the project for you).
target: Da biste dobili radnu kopiju morate <firstterm>preuzeti</firstterm> neko podstablo spremišta. (Termin <emphasis>preuzeti</emphasis> može zvučati kao nešto što se radi zaključavanjem ili rezervisanjem resursa, ali to nije to; to jednostavno kreira privatnu kopiju projekta za vas).

note: (para)
en: Suppose you make changes to <filename>button.c</filename>. Since the <filename>.svn</filename> directory remembers the file's modification date and original contents, Subversion can tell that you've changed the file. However, Subversion does not make your changes public until you explicitly tell it to. The act of publishing your changes is more commonly known as <firstterm>committing</firstterm> (or <firstterm>checking in</firstterm>) changes to the repository.
target: Pretpostavimo da ste napravili izmene u <filename>button.c</filename>. Kako <filename>.svn</filename> imenik pamti datum izmene fajla i originalni sadržaj, Subverzija vam  može reći da ste izmenili fajl.Čin publikovanja vaših izmena je najčešće poznat  kao  <firstterm>urezivanje</firstterm> (ili <firstterm>prijavljivanje</firstterm>) izmena u spremište.

note: (para)
en: To publish your changes to others, you can use Subversion's <command>commit</command> command.
target: Da bi publikovali vaše izmene drugima, možete koristiti Subverzionu komandu <command>ureži</command>.

note: (para)
en: Now your changes to <filename>button.c</filename> have been committed to the repository; if another user checks out a working copy of <filename>/calc</filename>, they will see your changes in the latest version of the file.
target: Sada vaše izmene u <filename>button.c</filename> su urezane u spremište; ako drugi korisnik proveri radnu kopiju  <filename>/kalk</filename>, videće vaše izmene u zadnjoj verziji fajla.

note: (para)
en: Suppose you have a collaborator, Sally, who checked out a working copy of <filename>/calc</filename> at the same time you did. When you commit your change to <filename>button.c</filename>, Sally's working copy is left unchanged; Subversion only modifies working copies at the user's request.
target: Pretpostavimo da imate  saradnika Sali, ko proverava radnu kopiju <filename>/kalk</filename> u isto vreme kad i vi. Kada urezujete vaše izmene u <filename>button.c</filename>, Salina radna kopija ostaje nepromenjena; Subverzija menja radnu kopiju samo na zahtev korisnika.

note: (para)
en: To bring her project up to date, Sally can ask Subversion to <firstterm>update</firstterm> her working copy, by using the Subversion <command>update</command> command. This will incorporate your changes into her working copy, as well as any others that have been committed since she checked it out.
target: Da bi ažurirala svoj projekat Sali mora pitati Subverzilu da <firstterm>ažurira</firstterm> njenu radnu kopiju korišćrnjem Subverzione komande <command>ažuriraj</command>. Ovo će uključiti vaše izmene u radnu kopiju isto kao što bilo koji drugi koji su urezani od provere.

note: (para)
en: Note that Sally didn't need to specify which files to update; Subversion uses the information in the <filename>.svn</filename> directory, and further information in the repository, to decide which files need to be brought up to date.
target: Zabeležite da Sali ne treba da specifira koje fajlove ažurira; Subverzija koristi informacije u <filename>.svn</filename> imeniku, i dalje informacije u spremištu, da odluči koje fajlove treba ažurirati.

note: (title)
en: Repository URLs
target: URL spremišta

note: (para)
en: Subversion repositories can be accessed through many different methods - on local disk, or through various network protocols. A repository location, however, is always a URL. The URL schema indicates the access method:
target: Subverzionom spremištu može biti pristupljeno kroz mnogo različitih metoda - na lokalnom disku, ili kroz razne mrežne protokole. Mest spremišta, međutim, je uvek na URL. URL šema označava metod pristupa:

note: (title)
en: Repository Access URLs
target: URL pristup spremištu

note: (entry)
en: Schema
target: Šema

note: (entry)
en: Access Method
target: Pristupni metod

note: (entry)
en: Direct repository access on local or network drive.
target: Direktni pristup spremištu na lokalnom mrežnom uređaju.

note: (entry)
en: Access via WebDAV protocol to Subversion-aware Apache server.
target: Pristup preko VebDAV protokola za Subverziono poznavanje Apaš servera.

note: (entry)
en: Same as <placeholder-1/>, but with SSL encryption.
target: Isto kao <placeholder-1/>,ali sa SSL enskripcijom.

note: (entry)
en: Unauthenticated TCP/IP access via custom protocol to a <placeholder-1/> server.
target: Neautentičan TCP/IP pristup preko običnog protokola ka <placeholder-1/> serveru.

note: (entry)
en: authenticated, encrypted TCP/IP access via custom protocol to a <placeholder-1/> server.
target: autentičan, šifriran TCP/IP pristup preko običnog protokola ka <placeholder-1/> serveru.

note: (para)
en: For the most part, Subversion's URLs use the standard syntax, allowing for server names and port numbers to be specified as part of the URL. The <literal>file://</literal> access method is normally used for local access, although it can be used with UNC paths to a networked host. The URL therefore takes the form <systemitem class="url">file://hostname/path/to/repos</systemitem>. For the local machine, the <literal>hostname</literal> portion of the URL is required to be either absent or <literal>localhost</literal>. For this reason, local paths normally appear with three slashes, <systemitem class="url">file:///path/to/repos</systemitem>.
target: Za mnoge delove Subverzioni URLovi koriste standardnu sintaksu dozvoljavajući serverskim imenima brojevima portova da budu specificirani kao deo URLa. <literal>file://</literal> metod pristupa se normalno koristi za lokalni pristup, takođe može se koristiti sa UNC putnjom do mrežnog domaćina. URL dakle uzima oblik  <systemitem class="url">file://hostname/path/to/repos</systemitem>. Za lokalnu mašinu <literal>hostname</literal> deo URL se zahteva da nije prisutno ili da je <literal>localhost</literal>. Iz ovog razloga lokalna putanja se normalno javlja sa tri kose crte <systemitem class="url">file:///path/to/repos</systemitem>.

note: (para)
en: Also, users of the <literal>file://</literal> scheme on Windows platforms will need to use an unofficially <quote>standard</quote> syntax for accessing repositories that are on the same machine, but on a different drive than the client's current working drive. Either of the two following URL path syntaxes will work where <literal>X</literal> is the drive on which the repository resides:
target: Takođe korisnici <literal>file://</literal> šeme na Vindouz platformama treba da koriste neoficijalnu <quote>standardnu</quote> sintaksu za pristup spremištu koja su na istoj mašini, ali na različitim uređajima od onog gde je klijentov radni uređaj. Svaka od sledeće dve sintakse URL putanja će raditi gde  je <literal>X</literal> drajv na kome  spremište obitava.

note: (para)
en: Note that a URL uses ordinary slashes even though the native (non-URL) form of a path on Windows uses backslashes.
target: Primetimo da URL koristi obične kose crte čak i kad prirodni (ne URL) oblik putanje na Vindouzu koristi obrnute kose crte.

note: (para)
en: You can safely access a FSFS repository via a network share, but you <emphasis>cannot</emphasis> access a BDB repository in this way.
target: Možete bezbedno pristupiti FSFS spremištu preko mrežne podele, ali vi <emphasis>ne možete</emphasis> pristupiti BDB spremištu na ovaj način.

note: (para)
en: Do not create or access a Berkeley DB repository on a network share. It <emphasis>cannot</emphasis> exist on a remote filesystem. Not even if you have the network drive mapped to a drive letter. If you attempt to use Berkeley DB on a network share, the results are unpredictable - you may see mysterious errors right away, or it may be months before you discover that your repository database is subtly corrupted.
target: Ne kreirajte Berkli DB spremište na mrežnom deljenom prostoru. To <emphasis>ne može</emphasis> postojati na udaljenom fajlsistemu. Čak ni ako imate mrežni drajv označen slovom drajva. Ako pokušate da koristite Berkli DB na mrežnoj podeli rezultati su nepredvidljivi - možete videti misteriozne greške ili će proći meseci dok ne ustanovite da vaša baza podataka  spremišta sa puno grešaka.

note: (title)
en: Revisions
target: Revizije

note: (primary)
en: revision
target: revizija

note: (para)
en: A <command>svn commit</command> operation can publish changes to any number of files and directories as a single atomic transaction. In your working copy, you can change files' contents, create, delete, rename and copy files and directories, and then commit the complete set of changes as a unit.
target: Operacija <command>svn ureži</command> publikuje izmene bilo kog broja fajlova i imenika kao jednu atomik transakciju. U vašoj radnoj kopiji možete menjati sadržaj fajlova, kreirati, brisati, preimenovati i kopirati fajlove i imenike i onda urežete ukupan skup izmena kao jedinicu.

note: (para)
en: In the repository, each commit is treated as an atomic transaction: either all the commits changes take place, or none of them take place. Subversion retains this atomicity in the face of program crashes, system crashes, network problems, and other users' actions.
target: U spremištu savako urezivanje se trtira kao atomik transakcija: ili se urežu sve promene ili nijedna. Subverzija čuva ovu atomičnost u slučaju pucanja programa ili sistema, mrežnih problema i drugih akcija korisnika.

note: (para)
en: Each time the repository accepts a commit, this creates a new state of the filesystem tree, called a <firstterm>revision</firstterm>. Each revision is assigned a unique natural number, one greater than the number of the previous revision. The initial revision of a freshly created repository is numbered zero, and consists of nothing but an empty root directory.
target: Svaki put kada spremište pristupi urezivanju to kreiira novo stanje stabla fajlsistema nazvanog <firstterm>revisija</firstterm>. Svaka revizija se označava jedinstvenim prirodnim brojem koji je za jedan veći od broja prethodne revizije.Početna revizija sveže kreiranog spremišta označena je nulom i ne sadrži ništa osim praznog korenog imenika.

note: (para)
en: A nice way to visualize the repository is as a series of trees. Imagine an array of revision numbers, starting at 0, stretching from left to right. Each revision number has a filesystem tree hanging below it, and each tree is a <quote>snapshot</quote> of the way the repository looked after each commit.
target: Lep način da se vizualizuje spremište je serija stabala. Zamislimo oblast revizionih brojeva, počevši od nule, razvučenih s leva u desno. Svaki revizioni broj ima fajlsistem stablo visi ispod njega i svako stablo je <quote>naznaka</quote> kako spremište izgleda posle urezivanja.

note: (title)
en: Global Revision Numbers
target: Globalni revizioni brojevi

note: (para)
en: Unlike those of many other version control systems, Subversion's revision numbers apply to <emphasis>entire trees</emphasis>, not individual files. Each revision number selects an entire tree, a particular state of the repository after some committed change. Another way to think about it is that revision N represents the state of the repository filesystem after the Nth commit. When a Subversion user talks about ``revision 5 of <filename>foo.c</filename>'', they really mean ``<filename>foo.c</filename> as it appears in revision 5.'' Notice that in general, revisions N and M of a file do <emphasis>not</emphasis> necessarily differ!
target: Drugačije nego kod većine drugih sistema kontrole verzija, Subverzioni revizioni brojevi se pojavljuju kao <emphasis>cela stabla</emphasis>, a ne individualni fajlovi. Svaki revizioni broj selektuje celo stablo, partikularno stanje spremišta posle nekog urezivanja izmena. Drugi način razmišljanja o tome je da revizija N pretstavlja stanje fajlsistema spremišta posle Ntog urezivanja. Kada korisnik Subverzije govori o ``revisija 5 od <filename>foo.c</filename>'', on stvarno misli ``<filename>foo.c</filename>  kako se javlja u reviziji 5." Primetimo da uopšte revizije N i M fajla <emphasis>nisu</emphasis> obavezno različite.

note: (para)
en: It's important to note that working copies do not always correspond to any single revision in the repository; they may contain files from several different revisions. For example, suppose you check out a working copy from a repository whose most recent revision is 4:
target: Važno je primetiti da radna kopija ne korespondira uvek bilo kojoj pojedinačnoj reviziji u spremištu; ona može sadržati fajlove iz više različitih revizija. Na primer, pretpostavimo da preuzimate radnu kopiju iz spremišta čija je najskorija revizija 4:

note: (screen)
en: 
    calc/Makefile:4
         integer.c:4
         button.c:4
target: 
    kalk/Makefile:4
         integer.c:4
         button.c:4

note: (para)
en: At the moment, this working directory corresponds exactly to revision 4 in the repository. However, suppose you make a change to <filename>button.c</filename>, and commit that change. Assuming no other commits have taken place, your commit will create revision 5 of the repository, and your working copy will now look like this:
target: Trenutno ovaj radni imenik odgovara tačno reviziji 4 u spremištu. Međutim, pretpostavimo da izmenite <filename>button.c</filename>, i urežete izmene. Uzmimo da nije bilo drugih urezivanja, vaše urezivanje kreira reviziju 5 spremišta i vaša radna kopija sada izgleda ovako:

note: (screen)
en: 
    calc/Makefile:4
         integer.c:4
         button.c:5
target: 
    kalk/Makefile:4
         integer.c:4
         button.c:5

note: (para)
en: Suppose that, at this point, Sally commits a change to <filename>integer.c</filename>, creating revision 6. If you use <command>svn update</command> to bring your working copy up to date, then it will look like this:
target: Pretpostavimo to, u tom trenutku, Saki urezuje izmene <filename>integer.c</filename>, kreirajući reviziju 6. Ako koristite <command>svn ažuriraj</command> da dovedete vašu radnu kopiju u ažurno stanje to će izgledati ovako:

note: (screen)
en: 
    calc/Makefile:6
         integer.c:6
         button.c:6
target: 
    kalk/Makefile:6
         integer.c:6
         button.c:6

note: (para)
en: Sally's changes to <filename>integer.c</filename> will appear in your working copy, and your change will still be present in <filename>button.c</filename>. In this example, the text of <filename>Makefile</filename> is identical in revisions 4, 5, and 6, but Subversion will mark your working copy of <filename>Makefile</filename> with revision 6 to indicate that it is still current. So, after you do a clean update at the top of your working copy, it will generally correspond to exactly one revision in the repository.
target: Saine izmene <filename>integer.c</filename> se pojavljuju u vašoj radnoj kopiji i vaše izmene su još prisutne u <filename>button.c</filename>. U ovom primeru, tekst u <filename>Makefile</filename> je identičan u revizijama 4,5 i 6, ali Subverzija će označiti vašu radnu kopiju <filename>Makefile</filename> revizijom 6 da indicira da je još tekuća. Tako, posle urađenog čistog ažuriranja na vrh vaše radne kopije ona će generalno korespondirati tačno jednoj reviziji u spremištu.

note: (title)
en: How Working Copies Track the Repository
target: Kako radna kopija prati spremište

note: (para)
en: For each file in a working directory, Subversion records two essential pieces of information in the <filename>.svn/</filename> administrative area:
target: Za svaki fajl u radnom imeniku Subverzija upisuje dva važna komada informacija u <filename>.svn/</filename> administarativnu oblast:

note: (para)
en: what revision your working file is based on (this is called the file's <firstterm>working revision</firstterm>), and
target: na koju reviziju je vaša radna kopija zasnovana )to se zove fajlova <firstterm>radna revizija</firstterm>), i

note: (para)
en: a timestamp recording when the local copy was last updated by the repository.
target: vremenski marker zapisan kada se lokalna kopija zadnji put ažurira u spremištu.

note: (para)
en: Given this information, by talking to the repository, Subversion can tell which of the following four states a working file is in:
target: Dajući ove informacije, govoreći spremištu, Subverzija može reći koje od sledećih četiri statusa ima radni fajl:

note: (term)
en: Unchanged, and current
target: Neizmenjen i tekući

note: (para)
en: The file is unchanged in the working directory, and no changes to that file have been committed to the repository since its working revision. A <command>commit</command> of the file will do nothing, and an <command>update</command> of the file will do nothing.
target: Fajl je neizmenjen u radnom imeniku, i nema izmena tog fajla pri urezivanju u spremište od njegove radne revizije. <command>Urezivanje</command> fajla ne radi ništa, i <command>ažuriranje</command>  fajla ne radi ništa.

note: (term)
en: Locally changed, and current
target: Lokalno izmenjen i tekući

note: (para)
en: The file has been changed in the working directory, and no changes to that file have been committed to the repository since its base revision. There are local changes that have not been committed to the repository, thus a <command>commit</command> of the file will succeed in publishing your changes, and an <command>update</command> of the file will do nothing.
target: Fajl je izmenjen u radnom imeniku i izmene nisu urezane u spremište od osnovne rebžvizije. Postoje lokalne izmene koje još nisu urezane u spremište, tako <command>urezivanje</command> fajla će pratiti publikovanje vaših izmena u spremište, a  <command>ažuriranje</command> fajla neće uraditi ništa.

note: (term)
en: Unchanged, and out-of-date
target: Nepromenjen i zastareo

note: (para)
en: The file has not been changed in the working directory, but it has been changed in the repository. The file should eventually be updated, to make it current with the public revision. A <command>commit</command> of the file will do nothing, and an <command>update</command> of the file will fold the latest changes into your working copy.
target: Fajl nije izmenjen u radnom imeniku ali je izmenjen u spremištu. Fajl bi trebalo da bude ažuriran da se učini savremen sa javnom revizijom. <command>Urezivanje</command> fajla ne radi ništa, a <command>ažuriranje</command> fajla uvodi zadnje izmene u vašu radnu kopiju.

note: (term)
en: Locally changed, and out-of-date
target: Lokalno izmenjen i zastareo

note: (para)
en: The file has been changed both in the working directory, and in the repository. A <command>commit</command> of the file will fail with an <emphasis>out-of-date</emphasis> error. The file should be updated first; an <command>update</command> command will attempt to merge the public changes with the local changes. If Subversion can't complete the merge in a plausible way automatically, it leaves it to the user to resolve the conflict.
target: Fajl je izmenjen u oba slučaja i u radnom imeniku i u spremištu. <command>Urezivanje</command> fajla biće neuspešno sa  greškom <emphasis>zastareo</emphasis>. Fajl se mora najpre ažurirai; sa <command>ažuriraj</command> komandom pokušaće se spajanje javnih izmena sa lokalnim izmenama. Ako Subverzija ne može potpuno da spoji na razuman način automatski, ona ostavlja korisniku da razreši konflikt.

note: (title)
en: Summary
target: Zaključak

note: (para)
en: We've covered a number of fundamental Subversion concepts in this chapter:
target: Mi smo ovde pokrili određeni broj osnovnih Subverzionih koncepata:

note: (para)
en: We've introduced the notions of the central repository, the client working copy, and the array of repository revision trees.
target: Uveli smo označavanje centralnog spremišta, klijentove radne kopije, i oblast revizionog stabla spremišta.

note: (para)
en: We've seen some simple examples of how two collaborators can use Subversion to publish and receive changes from one another, using the 'copy-modify-merge' model.
target: Vidli smo neke proste primere kako saradnici mogu da koriste Subverziju da publikuju  i prime izmene od drugih, koristeći 'kopiraj-menjaj-spoji' model.

note: (para)
en: We've talked a bit about the way Subversion tracks and manages information in a working copy.
target: Govorili smo o načinu kako Subverzija prati i upravlja informacijama u radnoj kopiji.

note: (title)
en: Setting Up A Server
target: Podešavanje servera

note: (para)
en: To use TortoiseSVN (or any other Subversion client), you need a place where your repositories are located. You can either store your repositories locally and access them using the <literal>file://</literal> protocol or you can place them on a server and access them with the <literal>http://</literal> or <literal>svn://</literal> protocols. The two server protocols can also be encrypted. You use <literal>https://</literal> or <literal>svn+ssh://</literal>. This chapter shows you step by step on how you can set up such a server on a Windows machine.
target: Da koristite TortozSVN (ili bilo koji drugi Subverzioni klijent), potrebno vam je mesto gde je locirano vaše spremište. Možete uskladištiti vaše spremište lokalno i pristupati mu koristeći  <literal>file://</literal> protokol ili ga smestiti na serveu i pristupati mu sa <literal>http://</literal> ili <literal>svn://</literal> protokolima. Dva server protokola mogu, takođe, biti šifrovana. Koristite  <literal>https://</literal> ili <literal>svn+ssh://</literal>. Ovo poglavlje prikazuje korak po korak kako podešavate takav server na Vindouz mašini.

note: (para)
en: More detailed information on the Subversion server options, and how to choose the best architecture for your situation, can be found in the Subversion book under <ulink url="http://svnbook.red-bean.com/en/1.4/svn.serverconfig.html"><citetitle>Server Configuration</citetitle></ulink>.
target: Detaljnije informacije o opcijama Subverzionog servera i kako izabrati najbolju arhitekturu za vašu situaciju, može se naći u knjizi  Subverzije pod  <ulink url="http://svnbook.red-bean.com/en/1.4/svn.serverconfig.html"><citetitle>Server Configuration</citetitle></ulink>.

note: (para)
en: If you don't have a server and you work alone then local repositories are probably your best choice. You can skip this chapter and go directly to <xref linkend="tsvn-repository"/>.
target: Ako nemate server i radite sami tada lokalno spremište je vaš najbolji izbor. Možete preskočiti ovo poglavlje i ići pravo na  <xref linkend="tsvn-repository"/>.

note: (para)
en: If you were thinking about setting up a multi-user repository on a network share, think again. Read <xref linkend="tsvn-repository-local-share"/> to find out why we think this is a bad idea.
target: Ako razmišljate da podesite višekorisničko spremište na mrežnom deljenom prostoru, razmislite još jednom. Pročitajte <xref linkend="tsvn-repository-local-share"/> da nađete zašto mi mislimo da je to loša ideja.

note: (title)
en: Apache Based Server
target: Apaš zasnovan server

note: (primary)
en: Apache
target: Apaš

note: (para)
en: The most flexible of all possible server setups for Subversion is the Apache based one. Although a bit more complicated to set up, it offers benefits that other servers cannot:
target: Najfleksibilniji od svih mogućih server podešavanja za Subverziju je Apaš zasnovani server. Mada je malo komplikovaniji za podešavanje on pruža pogodnosti koje drugi  serveri nemaju:

note: (primary) (term)
en: WebDAV
target: VebDAV

note: (para)
en: The Apache based Subversion server uses the WebDAV protocol which is supported by many other programs as well. You could e.g. mount such a repository as a <quote>Web folder</quote> in the Windows explorer and then access it like any other folder in the file system.
target: Apaš zasnovan Subverzioni server koristi VebDAV protokol koji je dobro podržan sa mnogo drugih programa. Mogli biste npr. postaviti spremište kao <quote>Veb imenik/quote> u Vindouz eksploreru i da mu pristupate kao svakom drugom imeniku fajl sistema.

note: (term)
en: Browsing The Repository
target: Pretraživanje spremišta

note: (para)
en: You can point your browser to the URL of your repository and browse the contents of it without having a Subversion client installed. This gives access to your data to a much wider circle of users.
target: Možete dovesti vaš pretraživač na URL spremišta i pretraživati njegov sadržaj bez instaliranog Subverzionog klijenta. Ovo daje pristup vašim podacima mnogo širem krugu korisnika.

note: (term) (title)
en: Authentication
target: Autentikacija

note: (para)
en: You can use any authentication mechanism Apache supports, including SSPI and LDAP.
target: Možete koristiti mehanizam autentikacije podrške Apašu, uključujući SSPI i LDAP.

note: (term)
en: Security
target: Sigurnost

note: (para)
en: Since Apache is very stable and secure, you automatically get the same security for your repository. This includes SSL encryption.
target: Kako je Apaš veoma stabilan i siguran, vi automatski dobijate istu sigurnost za spremište. Ovo obuhvata SSP šifrovanje.

note: (title)
en: Installing Apache
target: Instaliranje Apaša

note: (para)
en: Please note that Windows XP without the service pack 1 will lead to bogus network data and could therefore corrupt your repository!
target: Molim vas imajte u vidu da Vindous XP bez servis paketa 1 dovodi do veštačkih mrežnih podataka tako da će pokvariti spremište.

note: (para)
en: Download the latest version of the Apache web server from <ulink url="http://httpd.apache.org/download.cgi"><citetitle>http://httpd.apache.org/download.cgi</citetitle></ulink>. Make sure that you download the version 2.2.x - the version 1.3.xx won't work!
target: Skinite zadnju verziju Apaš veb servera sa <ulink url="http://httpd.apache.org/download.cgi"><citetitle>http://httpd.apache.org/download.cgi</citetitle></ulink>.Budite da skidate verziju 2.2.x - verzija 1.3.xx ne radi!

note: (para)
en: The msi installer for Apache can be found by clicking on <literal>other files</literal>, then browse to <filename>binaries/win32</filename>. You may want to choose the msi file <filename>apache-2.2.x-win32-x86-openssl-0.9.x.msi</filename> (the one that includes OpenSSL).
target: Msi instalacija za Apaš može se naći klikom na <literal>ostali fajlovi </literal>, zatim pretražite do  <filename>binaries/win32</filename>.Možda biste želeli da izaberete msi fajl <filename>apache-2.2.x-win32-x86-openssl-0.9.x.msi</filename> (onaj koji obuhvata OpenSSL).

note: (para)
en: Once you have the Apache2 installer you can double click on it and it will guide you through the installation process. Make sure that you enter the server-URL correctly (if you don't have a DNS name for your server just enter the IP-address). I recommend to install Apache <emphasis>for All Users, on Port 80, as a Service</emphasis>. Note: if you already have IIS or any other program running which listens on port 80 the installation might fail. If that happens, go to the programs directory, <filename>\Apache Group\Apache2\conf</filename> and locate the file <filename>httpd.conf</filename>. Edit that file so that <literal>Listen 80</literal> is changed to a free port, e.g. <literal>Listen 81</literal>. Then restart the installation - this time it should finish without problems.
target: Jednom kada imate Apaš2 instaliran možete dvostruko kliknuti na njega i on će vas voditi kroz instalacioni proces. Budite sigurni da unesete server-URL korektno (ako nemate DNS ime vašeg servera samo upišite IP-adresu). Preporučujem da instalirate Apaš <emphasis>za sve korisnike, na Portu 80,kao Servis </emphasis>. Pažnja: ako već imate IIS ili neki drugi program koji radi i čita na portu 80 instalacija može biti neuspešna. Ako se to desi idite na programski imenik <filename>\Apache Group\Apache2\conf</filename> i nađite fajl <filename>httpd.conf</filename>. Uredite taj fajl tako da <literal>Listen 80</literal> bude izmenjeno na slobodan port, npr. <literal>Listen 81</literal>. Zatim restartujte instalaciju - ovog puta će završiti bez problema.

note: (para)
en: Now test if the Apache web server is running correctly by pointing your web browser to <systemitem class="url">http://localhost/</systemitem> - a preconfigured Website should show up.
target: Sada testirajte da li Apaš veb server radi ispravno upravljajući veb pretraživač na <systemitem class="url">http://localhost/</systemitem> - prekonfigurisan vebsajt treba da bude prikazan.

note: (para)
en: If you decide to install Apache as a service, be warned that by default it will run as the local system account. It would be a more secure practice for you to create a separate account for Apache to run as.
target: Ako odlučite da instalirate Apaš kao servis, znajte da tada uobičajeno radi kao sistem lokalnog rčuna. Bila bi sigurnija praksa za vas da kreirate poseban račun za rad kao Apaš.

note: (para)
en: Make sure that the account on the server that Apache is running as has an explicit entry in the repository directory's access control list (right-click directory | properties | security), with full control. Otherwise, users will not be able to commit their changes.
target: Budite sigurni da taj račun na serveru gde radi Apaš ima eksplicitan ulaz pristupu imenika kontrolne liste spremišta (desni klik imenik | osobine | sigurnost), sa punom kontrolom. Drugim rečima, korisnik neće biti sposoban da ureže svoje izmene.

note: (para)
en: Even if Apache runs as local system, you still need such an entry (which will be the SYSTEM account in this case).
target: Čak i ako Apaš radi kao lokalni sistem, vi još imate potrebu za takvim ulazom (koja bi imala SISTEM račun u ovom slučaju).

note: (para)
en: If Apache does not have this permission set up, your users will get <quote>Access denied</quote> error messages, which show up in the Apache error log as error 500.
target: Ako Apaš nema podešenu ovu dozvolu, vaši korisnici će dobiti <quote>Pristup zabranjen</quote> poruku greške, koja je prikazana u Apaš dnevniku kao greška 500.

note: (para)
en: The first thing you need before installing Apache is a computer with Windows 2000, Windows XP+SP1, Windows 2003, Vista or Server 2008. <warning><placeholder-1/></warning><placeholder-2/><caution><placeholder-3/><placeholder-4/><placeholder-5/><placeholder-6/></caution>
target: Prva svar koja vam je potrebna pre instaliranja Apaša je kompjuter sa Vindouz 2000, Vindouz XP+SP1, Vindouz 2003, Vista ili Server 2008.<warning><placeholder-1/></warning><placeholder-2/><caution><placeholder-3/><placeholder-4/><placeholder-5/><placeholder-6/></caution>

note: (title)
en: Installing Subversion
target: Instaliranje Subverzije

note: (para)
en: Download the latest version of the Subversion Win32 binaries for Apache. Be sure to get the right version to integrate with your version of Apache, otherwise you will get an obscure error message when you try to restart. If you have Apache 2.2.x go to <ulink url="http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=8100"><citetitle>http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=8100</citetitle></ulink>.
target: Skinite zadnju verziju Subverzije Vin32 binarije za Apaš. Budite sigurni da ste dobili ispravnu verziju za integraciju sa vašom verzijom Apaša, u suprotnom će te dobiti čudne poruke greške kada probate sa restartom. Ako imate Apaš 2.2.x idite na <ulink url="http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=8100"><citetitle>http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=8100</citetitle></ulink>.

note: (para)
en: Run the Subversion installer and follow the instructions. If the Subversion installer recognized that you've installed Apache, then you're almost done. If it couldn't find an Apache server then you have to do some additional steps.
target: Pokrenite Subverzionu instalaciju i pratite instrukcije. Ako instalacija Subverzije prepozna da ste instalirali Apaš onda je u redu. Ako ne nađe Apaš server morate uraditi neke dodatne korake.

note: (para)
en: Using the windows explorer, go to the installation directory of Subversion (usually <filename>c:\program files\Subversion</filename>) and find the files <filename>/httpd/mod_dav_svn.so</filename> and <filename>mod_authz_svn.so</filename>. Copy these files to the Apache modules directory (usually <filename>c:\program files\apache group\apache2\modules </filename>).
target: Koristeći vindouz pretraživač idite na instalacioni imenik Subverzije (obično <filename>c:\program files\Subversion</filename>) i nađite fajlove <filename>/httpd/mod_dav_svn.so</filename> i <filename>mod_authz_svn.so</filename>. Kopirajte ove fajlove u Apaš imenik modula (obično <filename>c:\program files\apache group\apache2\modules </filename>).

note: (para)
en: Copy the file <filename>/bin/libdb*.dll</filename> and <filename>/bin/intl3_svn.dll</filename> from the Subversion installation directory to the Apache bin directory.
target: Kopirajte fajl <filename>/bin/libdb*.dll</filename> i <filename>/bin/intl3_svn.dll</filename> iz Subverzijinog instalacionog imenika u Apaš bin imenik.

note: (para)
en: Edit Apache's configuration file (usually <filename> C:\Program Files\Apache Group\Apache2\conf\httpd.conf</filename>) with a text editor such as Notepad and make the following changes:
target: Uredite Apaš konfiguracioni fajl (obično <filename> C:\Program Files\Apache Group\Apache2\conf\httpd.conf</filename>) pomoću tekst uređivača kao što je Notepad i uradite sledeće izmene:

note: (para)
en: Uncomment (remove the '<literal>#</literal>' mark) the following lines: <screen>
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule dav_module modules/mod_dav.so
    </screen> Add the following two lines to the end of the <literal>LoadModule</literal> section. <screen>
    LoadModule dav_svn_module modules/mod_dav_svn.so
    LoadModule authz_svn_module modules/mod_authz_svn.so
    </screen>
target: Otkomentirajte (uklonite '<literal>#</literal> znak) sledećim linijama:<screen>
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule dav_module modules/mod_dav.so
    </screen> Add the following two lines to the end of the <literal>LoadModule</literal> section. <screen>
    LoadModule dav_svn_module modules/mod_dav_svn.so
    LoadModule authz_svn_module modules/mod_authz_svn.so
    </screen>

note: (title) (term)
en: Configuration
target: Konfiguracija

note: (para)
en: At the end of the config file add the following lines: <screen>
    &lt;Location /svn&gt;
      DAV svn
      SVNListParentPath on
      SVNParentPath D:\SVN
      #SVNIndexXSLT "/svnindex.xsl"
      AuthType Basic
      AuthName "Subversion repositories"
      AuthUserFile passwd
      #AuthzSVNAccessFile svnaccessfile
      Require valid-user
    &lt;/Location&gt;
    </screen> This configures Apache so that all your Subversion repositories are physically located below <filename>D:\SVN</filename>. The repositories are served to the outside world from the URL: <systemitem class="url"> http://MyServer/svn/ </systemitem>. Access is restricted to known users/passwords listed in the <filename>passwd</filename> file.
target: Na kraj konfig fajla dodajte sledeće linije: <screen>
    &lt;Location /svn&gt;
      DAV svn
      SVNListParentPath on
      SVNParentPath D:\SVN
      #SVNIndexXSLT "/svnindex.xsl"
      AuthType Basic
      AuthName "Subversion repositories"
      AuthUserFile passwd
      #AuthzSVNAccessFile svnaccessfile
      Require valid-user
    &lt;/Location&gt;
    </screen> This configures Apache so that all your Subversion repositories are physically located below <filename>D:\SVN</filename>. The repositories are served to the outside world from the URL: <systemitem class="url"> http://MyServer/svn/ </systemitem>. Access is restricted to known users/passwords listed in the <filename>passwd</filename> file.

note: (para)
en: To create the <filename>passwd</filename> file, open the command prompt (DOS-Box) again, change to the <filename>apache2</filename> folder (usually <filename>c:\program files\apache group\apache2</filename>) and create the file by entering <screen>
    bin\htpasswd -c passwd &lt;username&gt;
    </screen> This will create a file with the name <filename>passwd</filename> which is used for authentication. Additional users can be added with <screen>
    bin\htpasswd passwd &lt;username&gt;
    </screen>
target: Da biste kreirali <filename>passwd</filename> fajl, otvorite komandnu liniju  (DOS-Boks) ponovo, izmenite u <filename>apache2</filename> imenik (obično <filename>c:\program files\apache group\apache2</filename>) i kreirajte fajl unošenjem <screen>
    bin\htpasswd -c passwd &lt;username&gt;
    </screen> Ovo će kreirati fajl sa imenom <filename>passwd</filename> koji se koristi za autentikaciju. Dodatni korisnici mogu biti dodati sa  <screen>
    bin\htpasswd passwd &lt;username&gt;
    </screen>

note: (para)
en: Restart the Apache service again.
target: Restrtujte Apaš server ponovo.

note: (para)
en: Point your browser to <systemitem class="url">http://MyServer/svn/MyNewRepository</systemitem> (where <filename>MyNewRepository</filename> is the name of the Subversion repository you created before). If all went well you should be prompted for a username and password, then you can see the contents of your repository.
target: Upravite vaš pretraživač na <systemitem class="url">http://MyServer/svn/MyNewRepository</systemitem> (gde je  <filename>MyNewRepository</filename> ime Subverzionog spremišta koje ste ranije kreirali). Ako je sve dobro prošlo bićete upitani za korisničko ime i lozinku, zatim možete videti sadržaj spremišta.

note: (para)
en: Now you have set up Apache and Subversion, but Apache doesn't know how to handle Subversion clients like TortoiseSVN yet. To get Apache to know which URL will be used for Subversion repositories you have to edit the Apache configuration file (usually located in <filename>c:\program files\apache group\apache2\conf\httpd.conf</filename>) with any text editor you like (e.g. Notepad): <placeholder-1/>
target: Sada možete podesiti Apaš i Subverziju, ali Apaš još ne zna kako da opsluži Subverzionog klijenta kao što je TortozSVN. Da bi Apaš znao koji URL treba koristiti za Subverziono spremište morate da uredite Apaš konfiguracioni fajl )obično na lokaciji <filename>c:\program files\apache group\apache2\conf\httpd.conf</filename>) bilo kojim uređivačem teksta koji volite (npr. Notepad): <placeholder-1/>

note: (primary)
en: SVNPath
target: SVNPutanja

note: (primary) (literal)
en: SVNParentPath
target: SVNPredakPutanja

note: (title)
en: Apache <filename>httpd.conf</filename> Settings
target: Apaš <filename>httpd.conf</filename> podešavanje

note: (entry)
en: Setting
target: Podešavanje

note: (entry)
en: Explanation
target: Objašnjenje

note: (entry)
en: means that the Subversion repositories are available from the URL <placeholder-1/>
target: znači da je Subverziono spremište dostupno sa URL <placeholder-1/>

note: (entry)
en: tells Apache which module will be responsible to serve that URL - in this case the Subversion module.
target: kaže Apašu koji modul je odgovoran da opsluži taj URL - u ovom slučaju Subverzioni modul.

note: (entry)
en: For Subversion version 1.3 and higher, this directive enables listing all the available repositories under <placeholder-1/>.
target: Za Subverziju 1.3 i više, ova direktiva omgućava listanje svih raspoloživih spremišta pod <placeholder-1/>.

note: (entry)
en: tells Subversion to look for repositories below <placeholder-1/>
target: kaže Subverziji da pogleda spremište ispod <placeholder-1/>

note: (entry)
en: Used to make the browsing with a web browser prettier.
target: Korišćen da fino pretražuje sa veb pretraživačem.

note: (entry)
en: is to activate basic authentication, i.e. Username/password
target: da aktivira osnovnu autentifikaciju, npr. korisničkoime/lozinka

note: (entry)
en: is used as an information whenever an authentication dialog pops up to tell the user what the authentication is for
target: korišćen kao informacija kadgod se pojavi autentifikacioni dijalog da kaže korisniku zašto je autentifikacija

note: (entry)
en: specifies which password file to use for authentication
target: određuje koji fajl lozinki koristiti za autentifikaciju

note: (entry)
en: Location of the Access file for paths inside a Subversion repository
target: Lokacija fajla računa za putanje unutar Subverzionog spremišta

note: (entry)
en: specifies that only users who entered a correct username/password are allowed to access the URL
target: određuje da samo korisnici koji unesu korektan ime/lozinka mogu da pristupe URL

note: (para)
en: If you want your repository to have read access for everyone but write access only for specific users you can change the line <screen>
    Require valid-user
    </screen> to <screen>
    &lt;LimitExcept GET PROPFIND OPTIONS REPORT&gt;
    Require valid-user
    &lt;/LimitExcept&gt;
    </screen>
target: Ako želite da vaše spremište ima pristup za čitanje za svakog ali pristup za upisivanje samo za određene korisnike morate izmeniti liniju <screen>
    Require valid-user
    </screen> u <screen>
    &lt;LimitExcept GET PROPFIND OPTIONS REPORT&gt;
    Require valid-user
    &lt;/LimitExcept&gt;
    </screen>

note: (para)
en: Using a <filename>passwd</filename> file limits and grants access to all of your repositories as a unit. If you want more control over which users have access to each folder inside a repository you can uncomment the line <screen>
    #AuthzSVNAccessFile svnaccessfile
    </screen> and create a Subversion access file. Apache will make sure that only valid users are able to access your <filename>/svn</filename> location, and will then pass the username to Subversion's <literal>AuthzSVNAccessFile</literal> module so that it can enforce more granular access based upon rules listed in the Subversion access file. Note that paths are specified either as <literal>repos:path</literal> or simply <literal>path</literal>. If you don't specify a particular repository, that access rule will apply to all repositories under <literal>SVNParentPath</literal>. The format of the authorization-policy file used by <literal>mod_authz_svn</literal> is described in <xref linkend="tsvn-serversetup-mod_authz_svn"/>
target: Korišćenje <filename>passwd</filename> fajla ograničava i garantuje pristup svim vašim spremištima kao jedinicama. Ako želite više kontrole na to koji korisnici imaju pristup svakom imeniku unutar spremišta možete otkomentirati liniju  screen>
    #AuthzSVNAccessFile svnaccessfile
    </screen> i kreirati Subverzioni fajl pristupa. Apaš će sigurno učiniti da samo valjani korisnici mogu da pristupe vašoj <filename>/svn</filename> lokaciji, i proslediće korisničko ime Subverzionom <literal>AuthzSVNAccessFile</literal> modulu tako da će se pojačati granularniji pristup zasnovan na pravilima izlistanim u Subverzionom fajlu pristupa. Primetite da su putanje specificirane ili kao<literal>repos:path</literal> ili jednostavno <literal>path</literal>. Ako ne specificirate posebno spremište, tada će se pristupna pravila primenjivati na sva spremišta pod <literal>SVNPredakPutanja</literal>. Format fajla autorizacione-polise korišćen od <literal>mod_authz_svn</literal> opisan je na <xref linkend="tsvn-serversetup-mod_authz_svn"/>

note: (para)
en: To make browsing the repository with a web browser 'prettier', uncomment the line <screen>
    #SVNIndexXSLT "/svnindex.xsl"
    </screen> and put the files <filename>svnindex.xsl</filename>, <filename>svnindex.css</filename> and <filename>menucheckout.ico</filename> in your document root directory (usually <filename>C:/Program Files/Apache Group/Apache2/htdocs</filename>). The directory is set with the <literal>DocumentRoot</literal> directive in your Apache config file.
target: Da učinite pretraživanje spremišta veb brozerom 'finije', otkomentirajte liniju <screen>
    #SVNIndexXSLT "/svnindex.xsl"
    </screen> i stavite fajlve <filename>svnindex.xsl</filename>, <filename>svnindex.css</filename> i <filename>menucheckout.ico</filename> u vaš koreni imenik dokumenata (obično <filename>C:/Program Files/Apache Group/Apache2/htdocs</filename>). Imenik je podešen sa <literal>DocumentRoot</literal> direktivom u Apaš konfiguracionom fajlu.

note: (para)
en: You can get those three files directly from our source repository at <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/other/svnindex"><citetitle>http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/other/svnindex</citetitle></ulink>. If you're asked for authentication for this link, enter <literal>guest</literal> as username and leave the password empty.
target: Možete uzeti ova stabla fajlova direktno sa našeg izvorno spremišta na  <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/other/svnindex"><citetitle>http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/other/svnindex</citetitle></ulink>. Ako vam traže autentifikaciju unesite <literal>guest</literal> ka o ime korisnika i ostavite lozinku praznom.

note: (para)
en: The XSL file from the TortoiseSVN repository has a nice gimmick: if you browse the repository with your web browser, then every folder in your repository has an icon on the right shown. If you click on that icon, the TortoiseSVN checkout dialog is started for this URL.
target: XSL fajl iz TortzSVN spremišta ima fin trik; ako pretražujete spremište vašim veb pretraživačem svaki imenik u vašem spremištu ima ikonu prikazanu s desna. Ako kliknete na tu ikonu TortozSVN  pokreće dijalog preuzimanja za taj URL.

note: (para)
en: A short explanation of what you just entered: <placeholder-1/> But that's just an example. There are many, many more possibilities of what you can do with the Apache web server. <placeholder-2/>
target: Kratko objašnjenje šta ste upravo uneli: <placeholder-1/> Ali to je samo jedan primer. Ima mnogo, mnogo više mogućnosti šta sve možete učiniti sa Apaš veb serverom. <placeholder-2/>

note: (title)
en: Multiple Repositories
target: Višestruka spremišta

note: (primary)
en: Index of projects
target: Indeks projekta

note: (para)
en: If you used the <literal>SVNParentPath</literal> directive then you don't have to change the Apache config file every time you add a new Subversion repository. Simply create the new repository under the same location as the first repository and you're done! In my company I have direct access to that specific folder on the server via SMB (normal windows file access). So I just create a new folder there, run the TortoiseSVN command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Create repository here...</guimenuitem></menuchoice> and a new project has a home...
target: Ako ste koristili <literal>SVNPredakPutanja</literal> direktivu zatim vi niste menjali Apaš kofig fajl svaki put kada ste dodavali novo Subverziono spremište. Jednostavno kreirajte novo spremište pod istom lkacijom kao prvo spremište i vi ste završili! U mojoj kompaniji ja imam direktan pristup specifičnom imeniku na serveru preko SMB (normalan vindouz pristup fajlovima). Tako sam samo kreirao novi imenik tamo, pokrenuo TortozSVN komandu <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Create repository here...</guimenuitem></menuchoice>  i novi projekat je dobio dom...

note: (para)
en: If you are using Subversion 1.3 or later, you can use the <literal>SVNListParentPath on</literal> directive to allow Apache to produce a listing of all available projects if you point your browser at the parent path rather than at a specific repository.
target: Ako koristite Subverziju 1.3 ili kasniju, morate koristiti <literal>SVNListajPredakPutanju na</literal> direktivu da omogućite Apašu da da listing svih dostupnih projekata ako upravite vaš pretraživač na predačku putanju pre nego na posebno spremište.

note: (title)
en: Path-Based Authorization
target: Autorizacija zavisna od putanje

note: (primary)
en: Authorization
target: Autorizacija

note: (para)
en: The <literal>mod_authz_svn</literal> module permits fine-grained control of access permissions based on user names and repository paths. This is available with the Apache server, and as of Subversion 1.3 it is available with svnserve as well.
target: Modul <literal>mod_authz_svn</literal> omogućava fino-zrnastu kontrolu na dozvolama zasnovanog pristupa korisničkih imena i putanja spremišta. Ovo je omogućeno Apaš serverom i od Subverzije 1.3 moguće je sa svnserv.

note: (para)
en: An example file would look like this: <screen>
    [groups]
    admin = john, kate
    devteam1 = john, rachel, sally
    devteam2 = kate, peter, mark
    docs = bob, jane, mike
    training = zak
    # Default access rule for ALL repositories
    # Everyone can read, admins can write, Dan German is excluded.
    [/]
    * = r
    @admin = rw
    dangerman =
    # Allow developers complete access to their project repos
    [proj1:/]
    @devteam1 = rw
    [proj2:/]
    @devteam2 = rw
    [bigproj:/]
    @devteam1 = rw
    @devteam2 = rw
    trevor = rw
    # Give the doc people write access to all the docs folders
    [/trunk/doc]
    @docs = rw
    # Give trainees write access in the training repository only
    [TrainingRepos:/]
    @training = rw
    </screen>
target: Primer bi izgledao ovakos: <screen>
    [groups]
    admin = john, kate
    devteam1 = john, rachel, sally
    devteam2 = kate, peter, mark
    docs = bob, jane, mike
    training = zak
    # Default access rule for ALL repositories
    # Everyone can read, admins can write, Dan German is excluded.
    [/]
    * = r
    @admin = rw
    dangerman =
    # Allow developers complete access to their project repos
    [proj1:/]
    @devteam1 = rw
    [proj2:/]
    @devteam2 = rw
    [bigproj:/]
    @devteam1 = rw
    @devteam2 = rw
    trevor = rw
    # Give the doc people write access to all the docs folders
    [/trunk/doc]
    @docs = rw
    # Give trainees write access in the training repository only
    [TrainingRepos:/]
    @training = rw
    </screen>

note: (para)
en: Note that checking every path can be an expensive operation, particularly in the case of the revision log. The server checks every changed path in each revision and checks it for readability, which can be time-consuming on revisions which affect large numbers of files.
target: Primetimo da provera svake putanje može biti skupa operacija, posebno u slučaju dnevnika revizija. Server proverava svaku promenjenu putanju u svakoj reviziji i proverava da li je čitljiva, što može biti vremenski opterećujuće na revizijama koje obuhvataju veliki broj fajlova.

note: (para)
en: Authentication and authorization are separate processes. If a user wants to gain access to a repository path, she has to meet <emphasis>both</emphasis>, the usual authentication requirements and the authorization requirements of the access file.
target: Autentifikacija i autorizacija su zasebni procesi. Ako korisnik želi da otvori pristup u putanju spremišta, mora se sresti sa <emphasis>oba</emphasis>, zahtevima obične autentifikacije i zahtevima autorizacije pristupa fajlu.

note: (title)
en: Authentication With a Windows Domain
target: Autentifikacija sa Vindouz domenom

note: (primary)
en: Windows domain
target: Vindouz domen

note: (primary)
en: domaincontroller
target: domenkontrolor

note: (para)
en: As you might have noticed you need to make a username/password entry in the <filename>passwd</filename> file for each user separately. And if (for security reasons) you want your users to periodically change their passwords you have to make the change manually.
target: Kao što možete primetiti vama je potrebno da napravite korisnik/lozinka ulaz u <filename>passwd</filename> fajl za svakog korisnika posebno. I ako (zbog sigurnosti) želite da vaši korisnici povremeno menjaju lozinke imate da uradite izmene ručno.

note: (para)
en: But there's a solution for that problem - at least if you're accessing the repository from inside a LAN with a windows domain controller: <literal>mod_auth_sspi</literal>!
target: Ali ima rešenja za taj problem - ako pristupate spremištu unutar LAN sa Vindouz domejn kontrolerom: <literal>mod_auth_sspi</literal>!

note: (para)
en: The original SSPI module was offered by Syneapps including source code. But the development for it has been stopped. But don't despair, the community has picked it up and improved it. It has a new home on <ulink url="http://sourceforge.net/projects/mod-auth-sspi/"><citetitle>SourceForge</citetitle></ulink>.
target: Originalni SSPI modul je ponuđen od Sinepsa uključujući i izvorni kod. Ali razvoj je zaustavljen. Ali ne očajavajte, zajednica će ga podići i poboljšati. On ima novi dom ulink url="http://sourceforge.net/projects/mod-auth-sspi/"><citetitle>SourceForge</citetitle></ulink>.

note: (para)
en: Download the module which matches your apache version, then copy the file <filename>mod_auth_sspi.so</filename> into the Apache modules folder.
target: Skinite modul koji hvata vašu apaš verziju, zatim kopirajte fajl <filename>mod_auth_sspi.so</filename> u Apaš modul imenik.

note: (para)
en: Edit the Apache config file: add the line <screen>
    LoadModule sspi_auth_module modules/mod_auth_sspi.so
    </screen> to the <literal>LoadModule</literal> section. Make sure you insert this line <emphasis>before</emphasis> the line <screen>
    LoadModule auth_module modules/mod_auth.so
    </screen>
target: Uredite Apaš konfig fajl: dodajte liniju <screen>
    LoadModule sspi_auth_module modules/mod_auth_sspi.so
    </screen> u <literal>LoadModule</literal> delu. Budite sigurni da ste ubacili ovu liniju <emphasis>pre</emphasis> linije <screen>
    LoadModule auth_module modules/mod_auth.so
    </screen>

note: (para)
en: To make the Subversion location use this type of authentication you have to change the line <screen>
    AuthType Basic
    </screen> to <screen>
    AuthType SSPI
    </screen> also you need to add <screen>
    SSPIAuth On
    SSPIAuthoritative On
    SSPIDomain &lt;domaincontroller&gt;
    SSPIOmitDomain on
    SSPIUsernameCase lower
    SSPIPerRequestAuth on
    SSPIOfferBasic On
    </screen> within the <literal>&lt;Location /svn&gt;</literal> block. If you don't have a domain controller, leave the name of the domain control as <literal>&lt;domaincontroller&gt;</literal>.
target: Da napravite Sbverzionu lokaciju koristite ovaj tip autentikacije koju imate da izmenite liniju <screen>
    AuthType Basic
    </screen> to <screen>
    AuthType SSPI
    </screen> takođe treba da dodate <screen>
    SSPIAuth On
    SSPIAuthoritative On
    SSPIDomain &lt;domaincontroller&gt;
    SSPIOmitDomain on
    SSPIUsernameCase lower
    SSPIPerRequestAuth on
    SSPIOfferBasic On
    </screen> within the <literal>&lt;Location /svn&gt;</literal> block. If you don't have a domain controller, leave the name of the domain control as <literal>&lt;domaincontroller&gt;</literal>.

note: (para)
en: Note that if you are authenticating using SSPI, then you don't need the <literal>AuthUserFile</literal> line to define a password file any more. Apache authenticates your username and password against your windows domain instead. You will need to update the users list in your <filename>svnaccessfile</filename> to reference <literal>DOMAIN\username</literal> as well.
target: Primetite da ako ste autentikovani korišćenjem SSPI, tada vam više uopšte nije potrebna <literal>AuthUserFile</literal> linija da definiše fajl lozinke. Apaš umesto toga  autentfiikuje vaše korisničko ime i lozinku preko vindouz domena. Potrebno vam je da ažurirate listu korisnika u vašem <filename>svnaccessfile</filename> ka referenci <literal>DOMAIN\imekorisnika</literal>.

note: (para)
en: The SSPI authentication is only enabled for SSL secured connections (https). If you're only using normal http connections to your server, it won't work.
target: SPI autentifikacija je omogućena samo za SSL sigurne konekcije (https). Ako koristite normalnu http konekciju ka vašem serveru, to neće raditi.

note: (para)
en: To enable SSL on your server, see the chapter: <xref linkend="tsvn-serversetup-apache-7"/>
target: Da omogućite SSL na vašem serveru, vidite poglavlje: <xref linkend="tsvn-serversetup-apache-7"/>

note: (para)
en: Subversion <filename>AuthzSVNAccessFile</filename> files are case sensitive in regard to user names (<literal>JUser</literal> is different from <literal>juser</literal>).
target: Subverzioni <filename>AuthzSVNAccessFile</filename> fajlovi su osetljivi na veličinu slova u imenima korisnika (<literal>JUser</literal> je različito od<literal>juser</literal>).

note: (para)
en: In Microsoft's world, Windows domains and user names are not case sensitive. Even so, some network administrators like to create user accounts in CamelCase (e.g. <literal>JUser</literal>).
target: U Mikrosoftovom svetu, Vindouz domeni i korisnička imena nisu osetljivi na veličinu slova. Čak su i neki mrežni administratori voleli da kreiraju korisničke naloge u CamelCase (npr. <literal>JUser</literal>).

note: (para)
en: This difference can bite you when using SSPI authentication as the windows domain and user names are passed to Subversion in the same case as the user types them in at the prompt. Internet Explorer often passes the username to Apache automatically using whatever case the account was created with.
target: Ova razlika vas može ugristi kada koristite SSPI autentifikaciju kao vindouz domen i korisničko ime prođe u Subverziju u istom obliku kako ga je korisnik otkucao u promptu. Internet Eksplorer često propušta korisničko ime ka Apašu automatski koristeći bilo koju veičinu slova bez obzira kako je račun ispisan.

note: (para)
en: The end result is that you may need at least two entries in your <literal>AuthzSVNAccessFile</literal> for each user -- a lowercase entry and an entry in the same case that Internet Explorer passes to Apache. You will also need to train your users to also type in their credentials using lower case when accessing repositories via TortoiseSVN.
target: Krajnji rezultat je da vam možda treba najmanje dva ulaza u vaš <literal>AuthzSVNAccessFile</literal> za svakog korisnika -- ulaz sa malim slovima i ulaz isti onom kako Internet Eksplorer prosleđuje ka Apašu. Vama će takođe trebati da izvežbate sebe da kucate njihove kredibilitete koristeći mala slova kada pristupate spremištu preko TortoseSVN.

note: (para)
en: Apache's Error and Access logs are your best friend in deciphering problems such as these as they will help you determine the username string passed onto Subversion's <literal>AuthzSVNAccessFile</literal> module. You may need to experiment with the exact format of the user string in the <literal>svnaccessfile</literal> (e.g. <literal>DOMAIN\user</literal> vs. <literal>DOMAIN//user</literal>) in order to get everything working.
target: Apašev dnevnik grešaka i pristupa je vaš najbolji prijatelj pri dešifrovanju problema kao što su oni koji vam pomažu da otkrijete string korisničkog imena u <literal>svnaccessfile</literal> (npr. <literal>DOMAIN\user</literal> prema <literal>DOMAIN//user</literal>)  da bi dobili da sve radi.

note: (title)
en: Multiple Authentication Sources
target: Višestruki autentifikacioni izvori

note: (primary)
en: Multiple authentication
target: Višestruke autentifikacije

note: (para)
en: It is also possible to have more than one authentication source for your Subversion repository. To do this, you need to make each authentication type non-authoritative, so that Apache will check multiple sources for a matching username/password.
target: Moguće je imati više od jednog autentifikacionog izvora za Subverziono spremište. Da se to uradi potrebno je napraviti svaki autentifikacioni tip neautoritativan tako da Apaš proverava višestruke izvore da bi dohvatio korisnik/lozinka.

note: (para)
en: A common scenario is to use both Windows domain authentication and a <literal>passwd</literal> file, so that you can provide SVN access to users who don't have a Windows domain login.
target: Zajednički scenario je da se koristi oboje, Vindouz domen autentikacija i <literal>passwd</literal> fajl, tako možete omogućiti SVN pristup ka korisnicima koji nemaju pristup Vindouz domenu.

note: (para)
en: To enable both Windows domain and <filename>passwd</filename> file authentication, add the following entries within the <literal>&lt;Location&gt;</literal> block of your Apache config file: <screen>
    AuthBasicAuthoritative Off
    SSPIAuthoritative Off
    </screen>
target: Da se omogući oba, Vindouz domen i <filename>passwd</filename> fajl autentifikacija, dodajte sledeće ulaze u okviru <literal>&lt;Location&gt;</literal> bloka vašrg Apaš konfig fajla: <screen>
    AuthBasicAuthoritative Off
    SSPIAuthoritative Off
    </screen>

note: (para)
en: Here is an example of the full Apache configuration for combined Windows domain and <literal>passwd</literal> file authentication: <screen>
    &lt;Location /svn&gt;
      DAV svn
      SVNListParentPath on
      SVNParentPath D:\SVN
    
      AuthName "Subversion repositories"
      AuthzSVNAccessFile svnaccessfile.txt
    
    # NT Domain Logins.
      AuthType SSPI
      SSPIAuth On
      SSPIAuthoritative Off
      SSPIDomain &lt;domaincontroller&gt;
      SSPIOfferBasic On
    
    # Htpasswd Logins.
      AuthType Basic
      AuthBasicAuthoritative Off
      AuthUserFile passwd
    
      Require valid-user
    &lt;/Location&gt;
    </screen>
target: Ovde je jedan primer pune Apaš konfiguracije za kombinovane Vindouz domene i <literal>passwd</literal> fajl autentifikaciju:  <screen>
    &lt;Location /svn&gt;
      DAV svn
      SVNListParentPath on
      SVNParentPath D:\SVN
    
      AuthName "Subversion repositories"
      AuthzSVNAccessFile svnaccessfile.txt
    
    # NT Domain Logins.
      AuthType SSPI
      SSPIAuth On
      SSPIAuthoritative Off
      SSPIDomain &lt;domaincontroller&gt;
      SSPIOfferBasic On
    
    # Htpasswd Logins.
      AuthType Basic
      AuthBasicAuthoritative Off
      AuthUserFile passwd
    
      Require valid-user
    &lt;/Location&gt;
    </screen>

note: (title)
en: Securing the server with SSL
target: Osiguranje servera sa SSL

note: (para)
en: Even though Apache 2.2.x has OpenSSL support, it is not activated by default. You need to activate this manually.
target: Bez obzira ako Apaš 2.2.x ima OpenSSL podršku, to nije obično aktivirano. Treba da to aktivirate ručno.

note: (para)
en: In the apache config file, uncomment the lines: <screen>
    #LoadModule ssl_module modules/mod_ssl.so
    </screen> and at the bottom <screen>
    #Include conf/extra/httpd-ssl.conf
    </screen> then change the line (on one line) <screen>
    SSLMutex "file:C:/Program Files/Apache Software Foundation/\
    Apache2.2/logs/ssl_mutex"
    </screen> to <screen>
    SSLMutex default
    </screen>
target: U apaš konfig fajlu, otkomentiraj linije: <screen>
    #LoadModule ssl_module modules/mod_ssl.so
    </screen> and at the bottom <screen>
    #Include conf/extra/httpd-ssl.conf
    </screen> then change the line (on one line) <screen>
    SSLMutex "file:C:/Program Files/Apache Software Foundation/\
    Apache2.2/logs/ssl_mutex"
    </screen> to <screen>
    SSLMutex default
    </screen>

note: (para)
en: Next you need to create an SSL certificate. To do that open a command prompt (DOS-Box) and change to the Apache folder (e.g. <filename>C:\program files\apache group\apache2</filename>) and type the following command: <screen>
    bin\openssl req -config conf\openssl.cnf -new -out my-server.csr
    </screen> You will be asked for a passphrase. Please don't use simple words but whole sentences, e.g. a part of a poem. The longer the phrase the better. Also you have to enter the URL of your server. All other questions are optional but we recommend you fill those in too.
target: Sledeći put treba da kreirati SSL sertifikat. Da to uradite otvorite komandnu liniju (DOS-Boks) i pređite u Apaš imenik (npr. <filename>C:\program files\apache group\apache2</filename>) i ukucajte sledeću komandu: <screen>
    bin\openssl req -config conf\openssl.cnf -new -out my-server.csr
    </screen>  Bićete upitani za pasfrazu. Molim vas nemojte koristiti jednostavne reči već celu rečenicu, npr. deo poeme. Duža fraza je bolja. Takođe imate da uđete u URL vašeg servera. Sva ostala pitanja su neobavezna ali mi preporučujemo da ih sve popunite.

note: (para)
en: Normally the <filename>privkey.pem</filename> file is created automatically, but if it isn't you need to type this command to generate it: <screen>
    bin\openssl genrsa -out conf\privkey.pem 2048
    </screen>
target: Normalno <filename>privkey.pem</filename> fajl je kreiran automatski, ali ako nije treba da otkucate ovu komandu da ga generišete: <screen>
    bin\openssl genrsa -out conf\privkey.pem 2048
    </screen>

note: (para)
en: Next type the commands <screen>
    bin\openssl rsa -in conf\privkey.pem -out conf\server.key
    </screen> and (on one line) <screen>
    bin\openssl req -new -key conf\server.key -out conf\server.csr \
    -config conf\openssl.cnf
    </screen> and then (on one line) <screen>
    bin\openssl x509 -in conf\server.csr -out conf\server.crt
                     -req -signkey conf\server.key -days 4000
    </screen> This will create a certificate which will expire in 4000 days. And finally enter (on one line): <screen>
    bin\openssl x509 -in conf\server.cert -out conf\server.der.crt
                     -outform DER
    </screen> These commands created some files in the Apache <filename>conf</filename> folder (<filename>server.der.crt</filename>, <filename>server.csr</filename>, <filename>server.key</filename>, <filename>.rnd</filename>, <filename>privkey.pem</filename>, <filename>server.cert</filename>).
target: Zatim otkucajte komande <screen>
    bin\openssl rsa -in conf\privkey.pem -out conf\server.key
    </screen> and (on one line) <screen>
    bin\openssl req -new -key conf\server.key -out conf\server.csr \
    -config conf\openssl.cnf
    </screen> and then (on one line) <screen>
    bin\openssl x509 -in conf\server.csr -out conf\server.crt
                     -req -signkey conf\server.key -days 4000
    </screen> This will create a certificate which will expire in 4000 days. And finally enter (on one line): <screen>
    bin\openssl x509 -in conf\server.cert -out conf\server.der.crt
                     -outform DER
    </screen> These commands created some files in the Apache <filename>conf</filename> folder (<filename>server.der.crt</filename>, <filename>server.csr</filename>, <filename>server.key</filename>, <filename>.rnd</filename>, <filename>privkey.pem</filename>, <filename>server.cert</filename>).

note: (para)
en: Restart the Apache service.
target: Restartujte Apaš servis.

note: (para)
en: Point your browser to <systemitem class="url">https://servername/svn/project</systemitem> ...
target: Upravite pretraživač ka <systemitem class="url">https://servername/svn/project</systemitem> ...

note: (title)
en: SSL and Internet Explorer
target: SSL i Internet Eksplorer

note: (para)
en: If you're securing your server with SSL and use authentication against a windows domain you will encounter that browsing the repository with the Internet Explorer doesn't work anymore. Don't worry - this is only the Internet Explorer not able to authenticate. Other browsers don't have that problem and TortoiseSVN and any other Subversion client are still able to authenticate.
target: Ako osigurate vaš server sa SSL i koristite autentifikaciju prema Vindouz domenu vi ćete naći da pretraživanje spremišta Internet Eksplorerom uopšte ne radi. Ne brinite - to samo Internet Eksplorer nije sposoban da autentifikuje. Drugi pretraživači nemaju taj problem i TortozSVN i bilo koji drugi Subverzioni klijent još može da autentifikuje.

note: (para)
en: define a separate <literal>&lt;Location /path&gt;</literal> directive in the Apache config file, and add the <literal>SSPIBasicPreferred On</literal>. This will allow IE to authenticate again, but other browsers and Subversion won't be able to authenticate against that location.
target: definišite odvojenu <literal>&lt;Location /path&gt;</literal> direktivu u Apaš konfig fajlu, i dodajte <literal>SSPIBasicPreferred On</literal>. Ovo će omogućiti IE da autentifikuje opet, ali drugi pretraživači i Subverzija nisu sposobni da autentifikuju prema lokaciji.

note: (para)
en: Offer browsing with unencrypted authentication (without SSL) too. Strangely IE doesn't have any problems with authenticating if the connection is not secured with SSL.
target: Ponudite pretraživanje sa nešifriranom autentifikacijom (bez SSL) takođe. IE nema bilo koje probleme sa autentifikacijom ako veza nije osigurana sa SSL.

note: (para)
en: In the SSL "standard" setup there's often the following statement in Apache's virtual SSL host: <screen>
    SetEnvIf User-Agent ".*MSIE.*" \
                 nokeepalive ssl-unclean-shutdown \
                 downgrade-1.0 force-response-1.0
    </screen> There are (were?) good reasons for this configuration, see <ulink url="http://www.modssl.org/docs/2.8/ssl_faq.html#ToC49"><citetitle>http://www.modssl.org/docs/2.8/ssl_faq.html#ToC49</citetitle></ulink> But if you want NTLM authentication you have to use <literal>keepalive</literal>. If You uncomment the whole <literal>SetEnvIf</literal> you should be able to authenticate IE with windows authentication over SSL against the Apache on Win32 with included <literal>mod_auth_sspi</literal>.
target: U SSL "standardno"  podešavanje ima često sledeću naredbu na Apaš virtualnom SSL domaćinu: <screen>
    SetEnvIf User-Agent ".*MSIE.*" \
                 nokeepalive ssl-unclean-shutdown \
                 downgrade-1.0 force-response-1.0
    </screen> Ima (gde?)dobrih razloga za ovu konfiguraciju, vidite <ulink url="http://www.modssl.org/docs/2.8/ssl_faq.html#ToC49"><citetitle>http://www.modssl.org/docs/2.8/ssl_faq.html#ToC49</citetitle></ulink> Ali ako  želite NTLM autentifikaciju imate da koristite<literal>keepalive</literal>. Ako Vi otkomentirate celu <literal>SetEnvIf</literal> trebalo bi da možete da autentifikujete IE sa vindouz autentifikacijom preko SSL prema Apašu na Vin32 uključivši  <literal>mod_auth_sspi</literal>.

note: (para)
en: If you still want to use IE to browse the repository you can either: <placeholder-1/>
target: Ako još uvek želite da koristite IE za pretraživanje spremišta možete ili: <placeholder-1/>

note: (title)
en: Forcing SSL access
target: Forsiranje SSL pristupa

note: (para)
en: When you've set up SSL to make your repository more secure, you might want to disable the normal access via non-SSL (http) and only allow https access. To do this, you have to add another directive to the Subversion <literal>&lt;Location&gt;</literal> block: <literal>SSLRequireSSL</literal>.
target: Kada se podesi SSP da učini spremište sigurnim, možete želeti da onemogućiti normalni pristup preko non-SSL (http) i dozvoljava samo https pristup. Da se to uradi, treba dodati još jednu direktivu u Subverziju <literal>&lt;Location&gt;</literal> block: <literal>SSLRequireSSL</literal>.

note: (para)
en: An example <literal>&lt;Location&gt;</literal> block would look like this: <screen>
    &lt;Location /svn&gt;
      DAV svn
      SVNParentPath D:\SVN
      SSLRequireSSL
      AuthType Basic
      AuthName "Subversion repositories"
      AuthUserFile passwd
      #AuthzSVNAccessFile svnaccessfile
      Require valid-user
    &lt;/Location&gt;
    </screen>
target: Primer <literal>&lt;Location&gt;</literal> blok će izgledati kao ovo: <screen>
    &lt;Location /svn&gt;
      DAV svn
      SVNParentPath D:\SVN
      SSLRequireSSL
      AuthType Basic
      AuthName "Subversion repositories"
      AuthUserFile passwd
      #AuthzSVNAccessFile svnaccessfile
      Require valid-user
    &lt;/Location&gt;
    </screen>

note: (title)
en: Using client certificates with virtual SSL hosts
target: Korišćenje klijent sertifikata sa virtualnim SSL domaćinima.

note: (para)
en: Sent to the TortoiseSVN mailing list by Nigel Green. Thanks!
target: Poslato TortozSVN poštanskoj listi od Nigel Grina. Hvala!

note: (para)
en: In some server configurations you may need to setup a single server containing 2 virtual SSL hosts: The first one for public web access, with no requirement for a client certificate. The second one to be secure with a required client certificate, running a Subversion server.
target: U nekim serverskim konfiguracijama treba da podesite pojednačni server koji sadrži 2 virtualna SSL domaćina: Prvi za publik veb pristup, bez zahteva za klijentske sertifikate. Drugi da bude siguran sa traženjem sertifikata klijenta, izvršavajući Subverzioni server.

note: (para)
en: Adding an <literal>SSLVerifyClient Optional</literal> directive to the <emphasis>per-server</emphasis> section of the Apache configuration (i.e. outside of any <literal>VirtualHost</literal> and <literal>Directory</literal> blocks) forces Apache to request a client Certificate in the initial SSL handshake. Due to a bug in <literal>mod_ssl</literal> it is essential that the certificate is requested at this point as it does not work if the SSL connection is re-negotiated.
target: Dodavanje <literal>SSLPriveraKlijenta Opciono</literal> direktivu u <emphasis>per-server</emphasis> deo Apaš konfiguraciju (tj. izvan <literal>VirtualniDomaćin</literal>  i <literal>Imenik</literal> blokovi) forsira Apaš da zahteva klijentov Sertifikat u početnom SSL rukovanju. U toku baga u <literal>mod_ssl</literal> važno je da zahtev za sertifikatom u toj tački ne radi ako se SSL konekcija ponovo pregovara.

note: (para)
en: The solution is to add the following directive to the virtual host directory that you want to lock down for Subversion: <screen>
    SSLRequire %{SSL_CLIENT_VERIFY} eq "SUCCESS"
    </screen> This directive grants access to the directory only if a client certificate was received and verified successfully.
target: Rešenje je da se doda sledeća direktiva virtuelnom imeniku domaćina koji žwželite da zaključate za Subverziju: <screen>
    SSLRequire %{SSL_CLIENT_VERIFY} eq "SUCCESS"
    </screen> Ova direktiva garantuje pristup imeniku samo ako je primljen klijentov sertifikat i zadovoljavajuće verikovan.

note: (para)
en: To summarise, the relevant lines of the Apache configuration are: <screen>
    SSLVerifyClient Optional
    
    ### Virtual host configuration for the PUBLIC host 
    ### (not requiring a certificate)
    
    &lt;VirtualHost 127.0.0.1:443&gt;
      &lt;Directory "pathtopublicfileroot"&gt;
      &lt;/Directory&gt;
    &lt;/VirtualHost&gt;
    
    ### Virtual host configuration for SUBVERSION 
    ### (requiring a client certificate)
    &lt;VirtualHost 127.0.0.1:443&gt;
      &lt;Directory "subversion host root path"&gt;
        SSLRequire %{SSL_CLIENT_VERIFY} eq "SUCCESS"
      &lt;/Directory&gt;
    
      &lt;Location /svn&gt;
        DAV svn
        SVNParentPath /pathtorepository
      &lt;/Location&gt;
    &lt;/VirtualHost&gt;
    </screen>
target: Da sumiramo, relevantne linije Apaš konfiguracij e su: <screen>
    SSLVerifyClient Optional
    
    ### Virtual host configuration for the PUBLIC host 
    ### (not requiring a certificate)
    
    &lt;VirtualHost 127.0.0.1:443&gt;
      &lt;Directory "pathtopublicfileroot"&gt;
      &lt;/Directory&gt;
    &lt;/VirtualHost&gt;
    
    ### Virtual host configuration for SUBVERSION 
    ### (requiring a client certificate)
    &lt;VirtualHost 127.0.0.1:443&gt;
      &lt;Directory "subversion host root path"&gt;
        SSLRequire %{SSL_CLIENT_VERIFY} eq "SUCCESS"
      &lt;/Directory&gt;
    
      &lt;Location /svn&gt;
        DAV svn
        SVNParentPath /pathtorepository
      &lt;/Location&gt;
    &lt;/VirtualHost&gt;
    </screen>

note: (title)
en: Svnserve Based Server
target: Svnserv zasnovan server

note: (para)
en: There may be situations where it's not possible to use Apache as your server. Fortunately, Subversion includes Svnserve - a lightweight stand-alone server which uses a custom protocol over an ordinary TCP/IP connection.
target: Mogu se javiti situacije gde nije mogućw da se koristi Apaš kao server. Srećom, Subverzija uključuje Svnserv - jednostavan samostalan server koji koristi običan protokol preko redovne TCP/IP veze.

note: (para)
en: In most cases svnserve is easier to setup and runs faster than the Apache based server. And now that SASL support is included it is easy to secure as well.
target: U većini slučajeva svnserv je lakše podesiti i radi brže od Apaš zasnovanom serveru. I sada ta SASL podrška je dobro uključena da lako zaštiti.

note: (title)
en: Installing svnserve
target: Istaliranje svnserva

note: (para)
en: Get the latest version of Subversion from <ulink url="http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91"><citetitle>http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91</citetitle></ulink>. Alternatively get a pre-packaged installer from CollabNet at <ulink url="http://www.collab.net/downloads/subversion"><citetitle>http://www.collab.net/downloads/subversion</citetitle></ulink>. This installer will setup svnserve as a Windows service, and also includes some of the tools you need if you are going to use SASL for security.
target: Uzmite zadnju verziju Subverije sa <ulink url="http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91"><citetitle>http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91</citetitle></ulink>. Alternativno uzmite upakovanu instalaciju od KolabNeta sa <ulink url="http://www.collab.net/downloads/subversion"><citetitle>http://www.collab.net/downloads/subversion</citetitle></ulink>. Ova instalacija će podesiti svnserv kao Vindouz servis, takđe uključuje neke alate koji su vam potrebni ako nameravate da koristite SASL za sigurnost.

note: (para)
en: If you already have a version of Subversion installed, and svnserve is running, you will need to stop it before continuing.
target: Ako već imate verziju Subverzije i pokrenut je svnserv, trebaće da ga zaustavite pre nego nastavite.

note: (para)
en: Run the Subversion installer. If you run the installer on your server (recommended) you can skip step 4.
target: Pokrenite Subverzionu instalaciju. Ako radite instalaciju na vašem serveru (preporučljivo) preskočite korak 4.

note: (para)
en: Open the windows-explorer, go to the installation directory of Subversion (usually <filename>C:\Program Files\Subversion</filename>) and in the <filename>bin</filename> directory, find the files <filename>svnserve.exe</filename>, <filename>intl3_svn.dll</filename>, <filename>libapr.dll</filename>, <filename>libapriconv.dll</filename>, <filename>libapriutil.dll</filename>, <filename>libdb*.dll</filename>, <filename>libeay32.dll</filename> and <filename>ssleay32.dll</filename> - copy these files, or just copy all of the <filename>bin</filename> directory, into a directory on your server e.g. <filename>c:\svnserve</filename>
target: Otvorite vindouz-eksplorer, idite na instalacioni direktorijum Subverzije (obično <filename>C:\Program Files\Subversion</filename>) i na < filename>bin</filename> imenik, nađite fajlove <filename>svnserve.exe</filename>, <filename>intl3_svn.dll</filename>, <filename>libapr.dll</filename>, <filename>libapriconv.dll</filename>, <filename>libapriutil.dll</filename>, <filename>libdb*.dll</filename>, <filename>libeay32.dll</filename> and <filename>ssleay32.dll</filename> - copy these files, or just copy all of the <filename>bin</filename> directory, into a directory on your server e.g. <filename>c:\svnserve</filename>

note: (title)
en: Running svnserve
target: Pokretanje svnserva

note: (para)
en: Now that svnserve is installed, you need it running on your server. The simplest approach is to run the following from a DOS shell or create a windows shortcut: <screen>
    svnserve.exe --daemon
    </screen> svnserve will now start waiting for incoming requests on port 3690. The --daemon switch tells svnserve to run as a daemon process, so it will always exist until it is manually terminated.
target: Sada je svnserv instaliran, treba da ga pokrenete na vašem serveru. Jednostavan pristup je da pokrenete sedeće iz DOS školjke ili kreirate vindouz prečicu: <screen>
    svnserve.exe --daemon
    </screen>svnserv će sada krenuti čekajući na dolazni zahtev na portu 3690. Prekidač --daemon kaže svnservu da radi kao daemon proces, tako da će uvek postojati sve dok se ručno ne zaustavi.

note: (para)
en: If you have not yet created a repository, follow the instructions given with the Apache server setup <xref linkend="tsvn-serversetup-apache-4"/>.
target: Ako koš niste kreirali spremište, pratite instrukcije koje vam daje Apaš server podešavanje <xref linkend="tsvn-serversetup-apache-4"/>.

note: (para)
en: To test that svnserve is working, use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Repo-Browser</guimenuitem></menuchoice> to view a repository.
target: Da bi testirali da li svnserv radi koristite <menuchoice><guimenu>TortozSVN</guimenu><guimenuitem>Repo-Pretraživač</guimenuitem></menuchoice> da vidite spremište.

note: (para)
en: Assuming your repository is located in <filename>c:\repos\TestRepo</filename>, and your server is called <filename>localhost</filename>, enter: <screen>
    svn://localhost/repos/TestRepo
    </screen> when prompted by the repo browser.
target: Pretpostavljajući da je vaše spremište smešteno na <filename>c:\repos\TestRepo</filename>, i da se vaš server zove <filename>localhost</filename>, unesite:: <screen>
    svn://localhost/repos/TestRepo
    </screen> kada vas upita repo pretraživač.

note: (para)
en: You can also increase security and save time entering URLs with svnserve by using the --root switch to set the root location and restrict access to a specified directory on the server: <screen>
    svnserve.exe --daemon --root drive:\path\to\repository\root
    </screen> Using the previous test as a guide, svnserve would now run as: <screen>
    svnserve.exe --daemon --root c:\repos
    </screen> And in TortoiseSVN our repo-browser URL is now shortened to: <screen>
    svn://localhost/TestRepo
    </screen> Note that the --root switch is also needed if your repository is located on a different partition or drive than the location of svnserve on your server.
target: Takođe možete povećati sigurnost i uštedeti vreme unoseći URL sa svnservom koristeći --root prekidač da podesite lokaciju korena i ograničite pristup specificiranim imenicima na serveru: <screen>
    svnserve.exe --daemon --root drive:\path\to\repository\root
    </screen> Koristeći prethodni test kao vodič, svnsrv će sada raditi kao:  <screen>
    svnserve.exe --daemon --root c:\repos
    </screen> I TortozSVN URL našeg repo-pretraživača je skraćen kao: <screen>
    svn://localhost/TestRepo
    </screen> Primetimo da --root prekidač je takođe potreban ako je spremište locirano na različitoj particiji drajva u odnosu na lokaciju svnserva na vašem serveru.

note: (para)
en: Svnserve will service any number of repositories. Just locate them somewhere below the root folder you just defined, and access them using a URL relative to that root.
target: Sbnserv će opsluživati bilo koji broj spremišta. Samo ih locirajte negde ispod korenog imenika koji ste upravo definisali, i pristupite im koristeći URL relativan na taj koren.

note: (title)
en: Run svnserve as a Service
target: Pokretanje svnserva kao Servis

note: (para)
en: Running svnserve as a user is usually not the best way. It means always having a user logged in on your server, and remembering to restart it after a reboot. A better way is to run svnserve as a windows service. Starting with Subversion 1.4, svnserve can be installed as a native windows service.
target: Pokretanje svnserva kao korisnik nije najbolji način. To znači da ima korisnik koji je uvek upisan na vašem serveru i pamti se da se restartuje posle ponovnog pokretanja. Bolji način je da pokrenete svnserv kao vindouz servis. Počevši od Subverzije 1.4, svnserv se može instalirati kao prirodni vindouz servis.

note: (para)
en: To install svnserve as a native windows service, execute the following command all on one line to create a service which is automatically started when windows starts. <screen>
    sc create svnserve binpath= "c:\svnserve\svnserve.exe --service 
        --root c:\repos" displayname= "Subversion" depend= tcpip 
        start= auto
    </screen> If any of the paths include spaces, you have to use (escaped) quotes around the path, like this: <screen>
    sc create svnserve binpath= "
        \"C:\Program Files\Subversion\bin\svnserve.exe\"
        --service --root c:\repos" displayname= "Subversion" 
        depend= tcpip start= auto
    </screen> You can also add a description after creating the service. This will show up in the Windows Services Manager. <screen>
    sc description svnserve "Subversion server (svnserve)"
    </screen>
target: Da bi se instalirao svnserv kao prirodni vindouz servis izvršite sledeću komandu, celu na jednoj liniji, da kreirate servis koji automatski kreće kad vindouz krene. <screen>
    sc create svnserve binpath= "c:\svnserve\svnserve.exe --service 
        --root c:\repos" displayname= "Subversion" depend= tcpip 
        start= auto
    </screen> Ako neka putanja ima razmak treba da koristite (izbegavajuće) navodnike oko putanje, kao: <screen>
    sc create svnserve binpath= "
        \"C:\Program Files\Subversion\bin\svnserve.exe\"
        --service --root c:\repos" displayname= "Subversion" 
        depend= tcpip start= auto
    </screen> Takođe možete dodati opis posle kreiranja servisa. Ovo će se prikazati u Vindouz servis menadžeru. <screen>
    sc opis svnserv "Subverzio server (svnserve)"
    </screen>

note: (para)
en: Note the rather unusual command line format used by <literal>sc</literal>. In the <literal>key= value</literal> pairs there must be no space between the key and the <literal>=</literal> but there must be a space before the value.
target: Primetimo nepoželjan format komandne linije koji koristi <literal>sc</literal>. U  <literal>ključ= vrednost</literal> parovima nesme biti razmak između ključa i <literal>=</literal> ali mora biti razmaka pre vrednosti.

note: (para)
en: Microsoft now recommend services to be run as under either the Local Service or Network Service account. Refer to <ulink url="http://www.microsoft.com/technet/security/topics/serversecurity/serviceaccount/default.mspx"><citetitle>The Services and Service Accounts Security Planning Guide</citetitle></ulink>. To create the service under the Local Service account, append the following to the example above. <screen>
    obj= "NT AUTHORITY\LocalService"
    </screen> Note that you would have to give the Local Service account appropriate rights to both Subversion and your repositories, as well as any applications which are used by hook scripts. The built-in group for this is called "LOCAL SERVICE".
target: Mikrosoft sada preporučuje servise da rade pod ili LokalServis ili MrežniServis nalog. Uporedite sa <ulink url="http://www.microsoft.com/technet/security/topics/serversecurity/serviceaccount/default.mspx"><citetitle> Servisi i Servis nalog sigurnost vodič planiranja </citetitle></ulink>.  Da bi se kreirao servis pod Lokal Servis nalogom, dodajte sledeće gornjem primeru. <screen>
    obj= "NT AUTHORITY\LocalService"
    </screen> Primetimo da imate dati Lokal Servis nalogu odgovarajuća prava za Subverziju i spremišta, isto kao svim aplikacijama koje se koriste kao zakačive skripte. Grupa za ovu izradu zove se "LOCAL SERVICE".

note: (para)
en: Once you have installed the service, you need to go to the services manager to start it (this time only; it will start automatically when the server reboots).
target: Jednom kada instalirate servise treba da odete na servis menadžer da ga pokrenete (samo tada, on će se pokrenuti automatski kada se servis ponovo pokreće).

note: (para)
en: For more detailed information, refer to <ulink url="http://svn.collab.net/repos/svn/trunk/notes/windows-service.txt"><citetitle>Windows Service Support for Svnserve</citetitle></ulink>.
target: Za informacije sa više detalja konsultujte <ulink url="http://svn.collab.net/repos/svn/trunk/notes/windows-service.txt"><citetitle> Vindouz servis podršku za Svnserv</citetitle></ulink>.

note: (para)
en: If you installed an earlier version of svnserve using the <literal>SVNService</literal> wrapper, and you now want to use the native support instead, you will need to unregister the wrapper as a service (remember to stop the service first!). Simply use the command <screen>
    svnservice -remove
    </screen> to remove the service registry entry.
target: Ako ste instalirali raniju verziju svnserva koristeći <literal>SVNServis</literal> omotač i sada želite da koristite prirdnu podršku umesto njega, potrebno je da odregistrujete omotač kao servis (setite se da prvo zaustavite servis!). Jednostavno koristite komandu <screen>
    svnservice -remove
    </screen> da uklonite ulaz u servis registar.

note: (title)
en: Basic Authentication with svnserve
target: Osnovna autentifikacija sa svnserv

note: (para)
en: The default svnserve setup provides anonymous read-only access. This means that you can use an <literal>svn://</literal> URL to checkout and update, or use the repo-browser in TortoiseSVN to view the repository, but you won't be able to commit any changes.
target: Uobičajeno podešavanje svnserva omogućava anonimni pristup samo čitanje. Ovo znači da možete koristiti <literal>svn://</literal> URL da preuzmete i ažurirate ili koristite repo-pretraživač u TortozSVN da vidite spremište, ali ne možete urezivati bilo kakve izmene.

note: (para)
en: To enable write access to a repository, you need to edit the <filename>conf/svnserve.conf</filename> file in your repository directory. This file controls the configuration of the svnserve daemon, and also contains useful documentation.
target: Da bi omogućili pristup upisivanju u spremište, potrebno je da uredite <filename>conf/svnserve.conf</filename> fajl u imeniku spremišta. Ovaj fajl kontroliše konfiguraciju svnserv domena, takođe sadrži korisnu dokumentaciju.

note: (para)
en: You can enable anonymous write access by simply setting: <screen>
    [general]
    anon-access = write
    </screen> However, you will not know who has made changes to a repository, as the <literal>svn:author</literal> property will be empty. You will also be unable to control who makes changes to a repository. This is a somewhat risky setup!
target: Možete omogućiti anonimni pristup upisivanju jednostavnim podešavanjem: <screen>
    [general]
    anon-access = write
    </screen> Ipak, nećete znati ko je napravio promene u spremištu kako je <literal>svn:author</literal> deo prazan. Vi ćete, takođe, biti nesposobni da kontrolišete ko je napravio izmene u spremištu. Ovo je ipak rizično podešavanje!

note: (para)
en: One way to overcome this is to create a password database: <screen>
    [general]
    anon-access = none
    auth-access = write
    password-db = userfile
    </screen> Where <filename>userfile</filename> is a file which exists in the same directory as <filename>svnserve.conf</filename>. This file can live elsewhere in your file system (useful for when you have multiple repositories which require the same access rights) and may be referenced using an absolute path, or a path relative to the <filename>conf</filename> directory. If you include a path, it must be written <filename>/the/unix/way</filename>. Using \ or drive letters will not work. The <filename>userfile</filename> should have a structure of: <screen>
    [users]
    username = password
    ...
    </screen> This example would deny all access for unauthenticated (anonymous) users, and give read-write access to users listed in <filename>userfile</filename>.
target: Jedan način da se prevaziđe ovo je kreiranje baza lozinki: <screen>
    [general]
    anon-access = none
    auth-access = write
    password-db = userfile
    </screen> Gde <filename>userfile</filename> je fajl koji postoji u istom imeniku kao  <filename>svnserve.conf</filename>. Ovaj fajl može biti bilo gde u vašem fajl sistemu (korisno kada imate više spremišta koja zahtevaju ista pristupna prava) i može se pozivati koristeći apsolutnu putanju, ili putanju relativnu na  <filename>conf</filename> imenik. Ako uključite putanju, mora biti napisana  <filename>/the/unix/way</filename>. Koristeći \ ili slovo drajva neće funkcionisati.  <filename>Userfile</filename> treba da ima strukturu: <screen>
    [users]
    username = password
    ...
    </screen> Ovaj primertreba da zabrani sve neautentifikovane (anonimne) korisnike i da ćitanje-upis pristup korisnicima izlistanim u  <filename>userfile</filename>.

note: (para)
en: If you maintain multiple repositories using the same password database, the use of an authentication realm will make life easier for users, as TortoiseSVN can cache your credentials so that you only have to enter them once. More information can be found in the Subversion book, specifically in the sections <ulink url="http://svnbook.red-bean.com/en/1.4/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.auth.users"><citetitle>Create a 'users' file and realm</citetitle></ulink> and <ulink url="http://svnbook.red-bean.com/en/1.4/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache"><citetitle>Client Credentials Caching</citetitle></ulink>
target: Ako održavate više spremišta koristeći istu bazu lozinki, korišćenje autentifikacione oblasti olakšće život korisnicima, kako TortozSVN kešira vašu akreditaciju vi ćete je uraditi samo jedanput. Više informacija se može naći u Subverzionoj knjizi, specijalno u delu <ulink url="http://svnbook.red-bean.com/en/1.4/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.auth.users"><citetitle>Kreirajte 'users' fajl i oblast </citetitle></ulink> i <ulink url="http://svnbook.red-bean.com/en/1.4/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache"><citetitle>Client Credentials Caching</citetitle></ulink>

note: (title)
en: Better Security with SASL
target: Bolja sigurnost sa SASL

note: (title)
en: What is SASL?
target: Šta je SASL?

note: (para)
en: The Cyrus Simple Authentication and Security Layer is open source software written by Carnegie Mellon University. It adds generic authentication and encryption capabilities to any network protocol, and as of Subversion 1.5 and later, both the svnserve server and TortoiseSVN client know how to make use of this library.
target: Cirus jednostavna autentifikacija i sigurnosni sloj je softver otvorenog koda napisan na Karnegi Melon univerzitetu. On dodaje srodnu autentifikaciju i mogućnosti šifriranja svakom mrežnom protokolu i od Subverzije 1.5 i dalje, oba, svnserv i TortozSVN klijenti znaju kako da koriste ovu biblioteku.

note: (para)
en: For a more complete discussion of the options available, you should look at the Subversion book in the section <ulink url="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl"><citetitle>Using svnserve with SASL</citetitle></ulink>. If you are just looking for a simple way to set up secure authentication and encryption on a Windows server, so that your repository can be accessed safely over the big bad Internet, read on.
target: Za kompletniju diskusiju dostupnih opcija treba pogledati Subverzionu knjigu u delu  <ulink url="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl"><citetitle>Koristeći svnserv sa SASL </citetitle></ulink>. Ako ste samo potražili lak način da podesite sigurnu autentifikaciju i šifriranje na Vindouz serveru vašem  spremištu će se pristupati preko velikog lošeg Internet čitanja.

note: (title)
en: SASL Authentication
target: SASL autentifikacija

note: (para)
en: To activate specific SASL mechanisms on the server, you'll need to do three things. First, create a <literal>[sasl]</literal> section in your repository's <filename>svnserve.conf</filename> file, with this key-value pair: <screen>
    use-sasl = true
    </screen>
target: Da aktivirate specifične SASL mehanizme na serveru potrebne su vam tri stvari. Najpre kreirajte <literal>[sasl]</literal> sekciju u fajlu spremišta  <filename>svnserve.conf</filename>, sa ovim ključ-vrednost parovima: <screen>
    use-sasl = true
    </screen>

note: (para)
en: Second, create a file called <filename>svn.conf</filename> in a convenient location - typically in the directory where subversion is installed.
target: Drugo, kreirajte fajl koji se zove <filename>svn.conf</filename> na konvencionalnu lokaciju - tipično u imeniku gde je subverzija instalirana.

note: (para)
en: Thirdly, create two new registry entries to tell SASL where to find things. Create a registry key named <literal>[HKEY_LOCAL_MACHINE\SOFTWARE\Carnegie Mellon\Project Cyrus\SASL Library]</literal> and place two new string values inside it: <literal>SearchPath</literal> set to the directory path containing the <filename>sasl*.dll</filename> plug-ins (normally in the Subversion install directory), and <literal>ConfFile</literal> set to the directory containing the <filename>svn.conf</filename> file. If you used the CollabNet installer, these registry keys will already have been created for you.
target: Treće, kreirajte dva nova registar ulaza da kažete SASL gde da nađe potrebne stvarčice. Kreirajte registar ključ pod imenom <literal>[HKEY_LOCAL_MACHINE\SOFTWARE\Carnegie Mellon\Project Cyrus\SASL Library]</literal> i stavite dva nova stringa unutar njega: <literal>SearchPath</literal> podesite na putanju imenika koji sadrži <filename>sasl*.dll</filename> plagin (normalno u Subverzioni instalacioni imenik), i <literal>ConfFile</literal> podešen na imenik koji sadži <filename>svn.conf</filename> fajl. Ako koristite KolabNet instalator, ovi registar ključevi će biti već kreirani za vas.

note: (para)
en: Edit the <filename>svn.conf</filename> file to contain the following: <screen>
    pwcheck_method: auxprop
    auxprop_plugin: sasldb
    mech_list: DIGEST-MD5
    sasldb_path: C:\TortoiseSVN\sasldb
    </screen> The last line shows the location of the authentication database, which is a file called <filename>sasldb</filename>. This could go anywhere, but a convenient choice is the repository parent path. Make sure that the svnserve service has read access to this file.
target: Uredite <filename>svn.conf</filename> fajl da sadrži sledeće: <screen>
    pwcheck_method: auxprop
    auxprop_plugin: sasldb
    mech_list: DIGEST-MD5
    sasldb_path: C:\TortoiseSVN\sasldb
    </screen> Poslednja linija prikazuje lokaciju autentifikacione baze podataka, koja je fajl pod imenom <filename>sasldb</filename>. To može biti bilo gde, ali uobičajen izbor je predačka putanja spremišta. Osigurajte da svnser servis ima čitajući pristup ovom fajlu.

note: (para)
en: If svnserve was already running, you will need to restart it to ensure it reads the updated configuration.
target: Ako snserv već radi potrebno je da ga restartujete da se osigura da pročita ažuriranu konfihuraciju.

note: (para)
en: Now that everything is set up, all you need to do is create some users and passwords. To do this you need the <literal>saslpasswd2</literal> program. If you used the CollabNet installer, that program will be in the install directory. Use a command something like this: <screen>
    saslpasswd2 -c -f C:\TortoiseSVN\sasldb -u realm username
    </screen> The <literal>-f</literal> switch gives the database location, <literal>realm</literal> must be the same as the value you defined in your repository's <filename>svnserve.conf</filename> file, and username is exactly what you expect it to be. Note that the realm is not allowed to contain space characters.
target: Sada je sve podešeno, sve što vam je potrebno je da kreirate korisnike i lozinke. Da biste to uradili potreban vam je <literal>saslpasswd2</literal> progran. Ako koristite KolabNet instalaciju taj program će biti u instalacionom imeniku. Koristite komandu nešto kao ovo: <screen>
    saslpasswd2 -c -f C:\TortoiseSVN\sasldb -u realm username
    </screen> Prekidač <literal>-f</literal> daje lokaciju baze podataka, <literal>oblast</literal> mora da bude ista kao vrednost koju ste definisali u <filename>svnserve.conf</filename> fajlu spremišta, a korisnikovo ime je tačno ono koje očekujete da bude. Primetimo da oblast ne dozvoljava da sadrži karakter razmak.

note: (para)
en: You can list the usernames stored in the database using the <literal>sasldblistusers2</literal> program.
target: Možete listati imena korisnika stavljene u bazu podataka koristeći <literal>sasldblistusers2</literal> program.

note: (title)
en: SASL Encryption
target: SASL šifrovanje

note: (para)
en: To enable or disable different levels of encryption, you can set two values in your repository's <filename>svnserve.conf</filename> file: <screen>
    [sasl]
    use-sasl = true
    min-encryption = 128
    max-encryption = 256
    </screen>
target: Da se omoguće ili onemoguće različiti nivoi šifrovanja možete podesiti dve vrednosti u <filename>svnserve.conf</filename> fajlu spremišta: screen>
    [sasl]
    use-sasl = true
    min-encryption = 128
    max-encryption = 256
    </screen>

note: (para)
en: The <literal>min-encryption</literal> and <literal>max-encryption</literal> variables control the level of encryption demanded by the server. To disable encryption completely, set both values to 0. To enable simple checksumming of data (i.e., prevent tampering and guarantee data integrity without encryption), set both values to 1. If you wish to allow (but not require) encryption, set the minimum value to 0, and the maximum value to some bit-length. To require encryption unconditionally, set both values to numbers greater than 1. In our previous example, we require clients to do at least 128-bit encryption, but no more than 256-bit encryption.
target: <literal>Min-encryption</literal> i <literal>max-encryption</literal> promenljive kontrolišu nivo šifrovanja koje zahteva server. Da se potpuno onemogući šifrovanje postavite obe vrednosti na 0. Da se omogući sumaprovere podataka (npr. predupredi mešanje i garantovati integritet podataka bez šifrovanja), postavite obe vrednosti na 1. Ako želite da dopustite (ali ne zahtevate) šifrovanje, postavite minimalnu vrednost na 0, i maksimalnu vrednost na neku dužinu bitova. Za bezuslovno zahtevanje šifrovanja postavite be vrednosti na vrednost veću od 1. U našem prethodnom primeru zahtevamo da klijenti rade 128-bitno šifrovanje, ali ne više od 256-bitnog šifrovanja.

note: (title)
en: Authentication with svn+ssh
target: Autentifikacija sa svn+ssh

note: (para)
en: Another way to authenticate users with a svnserve based server is to use a secure shell (SSH) to tunnel requests through. It is not as simple to set up as SASL, but it may be useful is some cases.
target: Drugi način autentifikacije korisnika pomoću svnserva zasnovanog servera je korišćenje sigurnosnu ljusku (SSH) da se provuče zahtev. To nije jednostavno da se podesi kao SASL, ali može biti korisno u nekim slučajevima.

note: (para)
en: With this approach, svnserve is not run as a daemon process, rather, the secure shell starts svnserve for you, running it as the SSH authenticated user. To enable this, you need a secure shell daemon on your server.
target: Evo to g pristupa, svnserv ne radi kao skriveni proces, radije, sigurnosna ljuska pokreće svnserv za vas, pokrećući ga kao SSH autentifikovanog korisnika. Da se to omogući potreban je skrivena sigurnosna ljuska na serveru.

note: (para)
en: A basic method for setting up your server is given in <xref linkend="tsvn-ssh-howto"/>. You can find other SSH topics within the FAQ by searching for <quote>SSH</quote>.
target: Osnovni metod podešavanja vašeg servera dat je u <xref linkend="tsvn-ssh-howto"/>. Možete naći druge SSH teme u okviru FAK tražeći <quote>SSH</quote>.

note: (para)
en: Further information about svnserve can be found in the <ulink url="http://svnbook.red-bean.com"><citetitle>Version Control with Subversion</citetitle></ulink>.
target: Dalje informacije o svnservu mogu se naći na <ulink url="http://svnbook.red-bean.com"><citetitle>Version Control with Subversion</citetitle></ulink>.

note: (title)
en: Path-based Authorization with svnserve
target: Putanjom-zasnovana autorizacija sa svnservom.

note: (para)
en: Starting with Subversion 1.3, svnserve supports the same <literal>mod_authz_svn</literal> path-based authorization scheme that is available with the Apache server. You need to edit the <filename>conf/svnserve.conf</filename> file in your repository directory and add a line referring to your authorization file. <screen>
    [general]
    authz-db = authz
    </screen> Here, <filename>authz</filename> is a file you create to define the access permissions. You can use a separate file for each repository, or you can use the same file for several repositories. Read <xref linkend="tsvn-serversetup-mod_authz_svn"/> for a description of the file format.
target: Počevši od Subverzije 1.3, svnserv podržava isti <literal>mod_authz_svn</literal> putanjom-zasnovanu autorizacionu šemu koja je omogućena Apaš serverom. Potrebno je da uredite <filename>conf/svnserve.conf</filename> fajl u imeniku spremišta i dodate liniju koja se poziva na autorizacioni fajl.<screen>
    [general]
    authz-db = authz
    </screen> Ovde, <filename>authz</filename> je fajl koji ste kreirali da definišete pristupne dozvole. Možete koristiti poseban fajl za svako spremište, ili možete koristiti isti fajl za više spremišta. Pročitajte xref linkend="tsvn-serversetup-mod_authz_svn"/> za opis formata fajla.

note: (para)
en: No matter which protocol you use to access your repositories, you always need to create at least one repository. This can either be done with the Subversion command line client or with TortoiseSVN.
target: Nije bitno koji protokol koristite da pristupite spremištu, uvek vam je potrebno da kreirate bar jedno spremište. Ovo može biti urađeno Subverzionom komandnom linijom ili klijentom sa TortozSVN.

note: (para)
en: If you haven't created a Subversion repository yet, it's time to do that now.
target: Ako još niste kreirali Subverziono spremište, vreme je da to uradite sada.

note: (title)
en: Repository Creation
target: Kreiranje spremišta

note: (primary)
en: create repository
target: kreiraj spremište

note: (para)
en: You can create a repository with the FSFS backend or with the older Berkeley Database (BDB) format. The FSFS format is generally faster and easier to administer, and it works on network shares and Windows 98 without problems. The BDB format was once considered more stable simply because it has been in use for longer, but since FSFS has now been in use in the field for several years, that argument is now rather weak. Read <ulink url="http://svnbook.red-bean.com/en/1.4/svn.reposadmin.planning.html#svn.reposadmin.basics.backends"><citetitle>Choosing a Data Store</citetitle></ulink> in the Subversion book for more information.
target: Možete kreirati spremište sa FSFS kraj ili stari Berkli baza podataka (BDB) format. FSFS format je  generalno brži i lakši za administraciju, radi na mrežnom deljenom prostoru i Vindouz 98 bez problema. BDB format je zamišljen mnogo stabilnijim jednostavno zato što se duže koristi, ali od kako je FSFS  u upotrebi nekoliko godina taj argument je sve slabiji. Pročitajte <ulink url="http://svnbook.red-bean.com/en/1.4/svn.reposadmin.planning.html#svn.reposadmin.basics.backends"><citetitle>Choosing a Data Store</citetitle></ulink> u Subverzionoj knjizi za više informacija.

note: (title)
en: Creating a Repository with the Command Line Client
target: Kreiranje spremišta klijentom komandne linije

note: (primary)
en: Create
target: Kreiranje

note: (secondary)
en: Command Line Client
target: Klijent komandne linije

note: (para)
en: Create an empty folder with the name SVN (e.g. <filename>D:\SVN\</filename>), which is used as root for all your repositories.
target: Kreirajte prazan imenik sa imenom SVN (npr.   <filename>D:\SVN\</filename>), koji se koristi kao koren za sva spremišta.

note: (para)
en: Create another folder <filename>MyNewRepository</filename> inside <filename>D:\SVN\</filename>.
target: Kreirajte drugi imenik <filename>MyNewRepository</filename> unutar <filename>D:\SVN\</filename>.

note: (para)
en: Open the command prompt (or DOS-Box), change into <filename>D:\SVN\</filename> and type <screen>
    svnadmin create --fs-type bdb MyNewRepository
    </screen> or <screen>
    svnadmin create --fs-type fsfs MyNewRepository
    </screen>
target: Otvorite komandni prompt (ili DOS -boks), pređite u <filename>D:\SVN\</filename> i otkucajte <screen>
    svnadmin create --fs-type bdb MyNewRepository
    </screen> or <screen>
    svnadmin create --fs-type fsfs MyNewRepository
    </screen>

note: (para)
en: Now you've got a new repository located at <filename>D:\SVN\MyNewRepository</filename>.
target: Sada imate spremište u <filename>D:\SVN\MyNewRepository</filename>.

note: (title)
en: Creating The Repository With TortoiseSVN
target: Kreiranje spremišta sa TortozSVN

note: (title)
en: The TortoiseSVN menu for unversioned folders
target: TortozSVN meni za neverzionisani imenik

note: (para)
en: Open the windows explorer
target: Otvorite vindouz pretraživač

note: (para)
en: Create a new folder and name it e.g. <filename>SVNRepository</filename>
target: Kreirajte novi imenik i nazovite ga npr. <filename>SVNRepository</filename>

note: (para)
en: <action>Right-click</action> on the newly created folder and select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Create Repository here...</guimenuitem></menuchoice>.
target: <action>Desni-klik</action> na novo kreirani imenik i izaberite <menuchoice><guimenu>TortozSVN</guimenu><guimenuitem>Kreirajte spremište ovde...</guimenuitem></menuchoice>.

note: (para)
en: A repository is then created inside the new folder. <emphasis>Don't edit those files yourself!!!</emphasis>. If you get any errors make sure that the folder is empty and not write protected.
target: Spremište će biti kreirano unutar novog imenika. <emphasis>Nemojte uređivati te fajlove sami!!!</emphasis>. Ako dobijete bilo kakvu grešku osigurajte da imenik bude prazan i nije zaštićen od upisivanja.

note: (para)
en: TortoiseSVN no longer offers the option to create BDB repositories, although you can still use the command line client to create them. FSFS repositories are generally easier for you to maintain, and also makes it easier for us to maintain TortoiseSVN due to compatibility issues between the different BDB versions.
target: TortozSVN više ne nudi opciju da se kreira BDB spremište, ali još možete koristiti klijenta komandne linije da ga kreirate. FSFS spremišta su generalno jednostavnija za rukovanje i nama lakša da održavamo TortozSVN preko kompatibilnih problema između raznih BDB verzja.

note: (para)
en: Future versions of TortoiseSVN will not support <literal>file://</literal> access to BDB repositories due to these compatibility issues, although it will of course always support this repository format when accessed via a server through the <literal>svn://</literal>, <literal>http://</literal> or <literal>https://</literal> protocols. For this reason, we strongly recommend that any new repository which must be accessed using <literal>file://</literal> protocol is created as FSFS.
target: Buduće verzije TortozSVN neće podržati <literal>file://</literal> pristup BDB spremištima zbog kompatibilnih problema, ali će svakako uvek podržavati taj format spremišta kada se pristupa preko servera kroz <literal>svn://</literal>, <literal>http://</literal> ili <literal>https://</literal> protokole. Iz tog razloga čvrsto preporučujemo da svako novo spremište kojem se mora pristupati koristeći <literal>file://</literal> protokol bude kreirano kao FSFS.

note: (para)
en: Of course we also recommend that you don't use <literal>file://</literal> access at all, apart from local testing purposes. Using a server is more secure and more reliable for all but single-developer use.
target: Svakako takođe preporuujemo da ne koristite <literal>file://</literal> pristuo uopšte, čak ni iz lokalnih potreba testiranja. Korišćenje servera je mnogo sigurnije i mnogo pouzdanije za sve osim u korišćenju pojedinca.

note: (title)
en: Local Access to the Repository
target: Lokalni pristup spremištu

note: (primary)
en: Access
target: Pristup

note: (primary)
en: UNC paths
target: UNC putanja

note: (para)
en: To access your local repository you need the path to that folder. Just remember that Subversion expects all repository paths in the form <systemitem class="url">file:///C:/SVNRepository/</systemitem>. Note the use of forward slashes throughout.
target: Da se pristupi lokalnom spremištu potrbna je putanja do tog imenika. Setimo se da Subverzija očekuje sve putanje spremišta u obliku <systemitem class="url">file:///C:/SVNRepository/</systemitem>. Zapazimo korišćenje  pravih kosih crta u celoj putanji.

note: (para)
en: To access a repository located on a network share you can either use drive mapping, or you can use the UNC path. For UNC paths, the form is <systemitem class="url">file://ServerName/path/to/repos/</systemitem>. Note that there are only 2 leading slashes here.
target: Da bi se pristupilo spremištu na mrežnom deljenju i možete koristiti ili mapiranje drajva, ili koristiti UNC putanju. Za UNC putanje oblik je <systemitem class="url">file://ServerName/path/to/repos/</systemitem>. Primetimo da ovde imamo 2 vodeće kose crte.

note: (para)
en: Prior to SVN 1.2, UNC paths had to be given in the more obscure form <systemitem class="url">file:///\ServerName/path/to/repos</systemitem>. This form is still supported, but not recommended.
target: Pre SVN 1.2, UNC putanje su bile date u čudnijem obliku systemitem class="url">file:///\ServerName/path/to/repos</systemitem>. Ovaj oblik se još podržava, ali se ne preporučuje.

note: (para)
en: Do not create or access a Berkeley DB repository on a network share. It <emphasis>cannot</emphasis> exist on a remote file system. Not even if you have the network drive mapped to a drive letter. If you attempt to use Berkeley DB on a network share, the results are unpredictable - you may see mysterious errors right away, or it may be months before you discover that your repository database is subtly corrupted.
target: Ne treba kreirati ili pristupati Berkli DB spremištu na mrežni deljeni prostor. To <emphasis>ne može</emphasis> postojati na udaljenom fajl sistemu. Niti čak ako imate mrežni drajv mapiran slovom drajva. Ako pokušate da koristite Berkli DB na mrežnoj izmeni, rezultat je nepredvidljiv - možete videti misteriozne greške trenutno, ili mogu proći meseci pre nego otkrijete da je vaša baza podataka spremišta neznatno pokvarena.

note: (title)
en: Accessing a Repository on a Network Share
target: Pristupanje spremištu na mrežnom deljenom prostoru

note: (primary)
en: Network share
target: Mrežni deljeni prostor

note: (para)
en: Although in theory it is possible to put a FSFS repository on a network share and have multiple users access it using <literal>file://</literal> protocol, this is most definitely <emphasis>not</emphasis> recommended. In fact we would <emphasis>strongly</emphasis> discourage it, and do not support such use.
target: Takođe je poznato u teoriji da je moguće staviti FSFS spremište na mrežnom deljenom prostoru i imati višestruki korisnički pristup koristeći <literal>file://</literal> protokol, ovo se definitivno <emphasis>ne</emphasis> preporučuje. U stvari možemo <emphasis>čvrsto</emphasis> obeshrabriti to, i ne podržati takvo korišćenje.

note: (para)
en: Firstly you are giving every user direct write access to the repository, so any user could accidentally delete the entire repository or make it unusable in some other way.
target: Najpre dajete svakom korisniku direktno pravo upisa u spremište, tako da bilo koji korisnik može slučajno obrisati celo spremište ili ga učiniti nekorisnim na neki drugi način.

note: (para)
en: Secondly not all network file sharing protocols support the locking that Subversion requires, so you may find your repository gets corrupted. It may not happen straight away, but one day two users will try to access the repository at the same time.
target: Drugo, neće svi protokoli za mrežni deljeni prostor podržavatizaključavanje koje zahteva Subverzija, tako da možete naći vaše spremište pokvareno. To se ne mora desiti odmah, ali jednog dana dva korisnika mogu pokušati da pristupe spremištu u isto vreme.

note: (para)
en: Thirdly the file permissions have to be set just so. You may just about get away with it on a native Windows share, but SAMBA is particularly difficult.
target: Treće, fajl dozvole mogu biti tako podešene. Možete otići na prirodni Vindouz deljeni prostor, ali SAMBA je posebno teška.

note: (para)
en: <literal>file://</literal> access is intended for local, single-user access only, particularly testing and debugging. When you want to share the repository you <emphasis>really</emphasis> need to set up a proper server, and it is not nearly as difficult as you might think. Read <xref linkend="tsvn-serversetup"/> for guidelines on choosing and setting up a server.
target: <literal>file://</literal> pristup je planiran za lokalni, samo jedan-korisnik pristup, partikularno testiranje i debagovanje. Kada želite deljenje spremišta vi <emphasis>stvarno</emphasis> treba da podesite odgovarajući server, i to nije skoro tako teško kako se može pomisliti. Pročitajte  <xref linkend="tsvn-serversetup"/> za vodič kako izabrati i podesiti server.

note: (title)
en: Repository Layout
target: Izgled spremišta

note: (para)
en: Before you import your data into the repository you should first think about how you want to organize your data. If you use one of the recommended layouts you will later have it much easier.
target: Pre nego uvezete vaše podatke u spremište morate najpre razmisliti kako želite da organizujete podatke. Ako koristite neki od preporučenih iugleda kasnije će vam biti lakše.

note: (para)
en: There are some standard, recommended ways to organize a repository. Most people create a <filename>trunk</filename> directory to hold the <quote>main line</quote> of development, a <filename>branches</filename> directory to contain branch copies, and a <filename>tags</filename> directory to contain tag copies. If a repository holds only one project, then often people create these top-level directories:
target: Postoje neki standardni, preporučljivi načini organizovanja spremišta. Većina ljudi kreira <filename>deblo</filename> imenik da čuva <quote>glavnu liniju</quote> razvoja, <filename>grane</filename> imenik da čuva kopije grana, i <filename>znake</filename> imenik da drži kopije oznaka. Ako spremište sadrži samo jedan projekat, tada ljudi često kreiraju vršni imenik:

note: (para)
en: If a repository contains multiple projects, people often index their layout by branch:
target: Ako spremište sadrži više projekata, ljudi čest indeksiraju njhov izgled granama:

note: (para)
en: ...or by project:
target: ...ili projektom:

note: (para)
en: Indexing by project makes sense if the projects are not closely related and each one is checked out individually. For related projects where you may want to check out all projects in one go, or where the projects are all tied together in a single distribution package, it is often better to index by branch. This way you have only one trunk to checkout, and the relationships between the sub-projects is more easily visible.
target: Indeksiranje pomoću projekata je osetljiv na to da li su projekti blisko uporedivi i da li se svaki može individualno preuzeti. Za uporedive projekte gde možete preuzetii sve projekte odjednom, ili gde su svi projekti vezani zajedno u jedan distribucioni paket, često je bolje indeksiranje grana. U ovom slučaju vam je potrebno jedno deblo za preuzimanje i povezanost između sub-projekata je mnogo lakše vidljiva.

note: (para)
en: If you adopt a top level <filename>/trunk /tags /branches</filename> approach, there is nothing to say that you have to copy the entire trunk for every branch and tag, and in some ways this structure offers the most flexibility.
target: Ako usvojimo vršni nivo <filename>/trunk /tags /branches</filename> pristup, nije ništa reći da imate kopirati celo deblo za svaku granu i znak, i u neki put ova struktura nudi najveću flksibilnost.

note: (para)
en: For unrelated projects you may prefer to use separate repositories. When you commit changes, it is the revision number of the whole repository which changes, not the revision number of the project. Having 2 unrelated projects share a repository can mean large gaps in the revision numbers. The Subversion and TortoiseSVN projects appear at the same host address, but are completely separate repositories allowing independent development, and no confusion over build numbers.
target: Za projekte koji nisu povezani možete više voleti da koristite odvojena spremišta. Kada urezujete izmene, revizioni broj celog spremišta se menja, ne revizioni broj projekta. Ako imate 2 nezavisna projekta deljenje spremišta može značiti velike praznine u revizionim brojevima. Subverzija i TortozSVN projekti se pojavljuju na istim adresama domaćina, ali su sasvim nezavisna spremišta omogućavajući nezavisan razvoj i nema kofuzije oko razvojnih brojeva.

note: (para)
en: Of course, you're free to ignore these common layouts. You can create any sort of variation, whatever works best for you or your team. Remember that whatever you choose, it's not a permanent commitment. You can reorganize your repository at any time. Because branches and tags are ordinary directories, TortoiseSVN can move or rename them however you wish.
target: Svakako, slobodni ste da zanemarite ovaj zajednički izgled. Možete kreirati bilo koju vrstu varijacija, što god radi bolje za vaš tim. Setite se da što god izaberete to nije stalno urezivanje. Vi možete reorganizovati vaše spremište bilo kada. Pošto su grane i oznake pravi imenici TortozSVN ih može pomerati i preimenovati kad god želite.

note: (para)
en: Switching from one layout to another is just a matter of issuing a series of server-side moves; If you don't like the way things are organized in the repository, just juggle the directories around.
target: Prebacivanje sa jednog izgleda na drugi je tek stvar emitovanja serije pomeranja sa serverske strane; Ako ne volite način na koji su stvari organizovane u spremištu, malo žonglirajte okolnim imenicima.

note: (para)
en: create a new empty folder on your hard drive
target: kreirajte prazan imenik na vašem čvrstom disku

note: (para)
en: create your desired top-level folder structure inside that folder - don't put any files in it yet!
target: kreirajte željeni vršni-nivo imenik strukturu unutar tog imenika - nemojte stavljati nijedan fajl još!

note: (para)
en: import this structure into the repository via a <action>right click</action> on the folder and selecting <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Import...</guimenuitem></menuchoice> This will import your temp folder into the repository root to create the basic repository layout.
target: uveite ovu strukturu u spremište preko <action>desni klik</action> na imenik i izborom <menuchoice><guimenu>TortozSVN</guimenu><guimenuitem>Uvezi...</guimenuitem></menuchoice> Ovo će uvesti vaš privremeni imenik u koren spremišta da kreira osnovni izgled spremišta.

note: (para)
en: So if you haven't already created a basic folder structure inside your repository you should do that now. There are two ways to achieve this. If you simply want to create a <filename>/trunk /tags /branches</filename> structure, you can use the repository browser to create the three folders (in three separate commits). If you want to create a deeper hierarchy then it is simpler to create a folder structure on disk first and import it in a single commit, like this: <placeholder-1/>
target: Tako, ako niste već kreirali strukturu osnovnog imenika unutar vašeg spremišta treba to da uradite sada. Postoje dva načina da se to postigne. Ako jednostavno želite da kreirate <filename>/trunk /tags /branches</filename> strukturu možete koristiti pretraživač spremišta da kreirate ta tri imenika (u tri posebna urezivanja). Ako želite da kreirate dublju hijerarhiju tada je to slično najpre kreiranju strukture imenika na disku i njen uvoz pri jedinstvenom urezivanju kao ovo: <placeholder-1/>

note: (para)
en: Note that the name of the folder you are importing does not appear in the repository, only its contents. For example, create the following folder structure: <screen>
    C:\Temp\New\trunk
    C:\Temp\New\branches
    C:\Temp\New\tags
    </screen> Import <filename>C:\Temp\New</filename> into the repository root, which will then look like this: <screen>
    /trunk
    /branches
    /tags
    </screen>
target: Primetimo da ime imenika koji uvozite ne pojavljuje se u spremištu, samo sadržaj. Na primer, kreirajte sledeće strukture imenika:<screen>
    C:\Temp\New\trunk
    C:\Temp\New\branches
    C:\Temp\New\tags
    </screen> Uvezite <filename>C:\Temp\New</filename> u koren spremišts, koje će sada izgledati kao:<screen>
    /trunk
    /branches
    /tags
    </screen>

note: (title)
en: Repository Backup
target: Osiguranje spremišta

note: (primary)
en: backup
target: osiguranje

note: (para)
en: Whichever type of repository you use, it is vitally important that you maintain regular backups, and that you verify the backup. If the server fails, you may be able to access a recent version of your files, but without the repository all your history is lost forever.
target: Koji god tip spremišta da koristite, izuzetno je važno da održavate regularno osiguranje, i da proverite osiguranje. Ako server padne vi ste možda  sposobni da pristupite zadnjoj verziji vaših fajlova, ali bez spremišta sva istorja je izgubljena zauvek.

note: (para)
en: The simplest (but not recommended) way is just to copy the repository folder onto the backup medium. However, you have to be absolutely sure that no process is accessing the data. In this context, access means <emphasis>any</emphasis> access at all. A BDB repository is written to even when the operation only appears to require reading, such as getting status. If your repository is accessed at all during the copy, (web browser left open, WebSVN, etc.) the backup will be worthless.
target: Jednostavan (ali nepreporučljiv) način je da se samo kopira imenik spremišta na medijum osiguranja. Međutim, potrebno je da budete apsolutno sigurni da ni jedan proces ne pristupa podacima. U ovom kontekstu, pristup znači <emphasis>svaki</emphasis> pristup uopšte. BDB spremište je upisano čak i kad se operacija pojavi da zahteva čitanje kao uzimanje statusa. Ako je vašem spremištu pristupljeno u toku kopiranja, (veb pretraživač ostaje otvoren, VepSVN, itd.) osiguranje će biti bezvredno.

note: (para)
en: The recommended method is to run <screen>
    svnadmin hotcopy path/to/repository path/to/backup --clean-logs
    </screen> to create a copy of your repository in a safe manner. Then backup the copy. The <literal>--clean-logs</literal> option is not required, but removes any redundant log files when you backup a BDB repository, which may save some space.
target: Preporučljiv metod je da se pokrene <screen>
    svnadmin hotcopy path/to/repository path/to/backup --clean-logs
    </screen> da se kreira kopija vašeg spremišta na bezbedan način. Zatim se pravi kopija osiguranja. Opcija <literal>--clean-logs</literal> nije potrebna, ali uklanja redundantne fajlove dnevnika kada osiguravate BDB spremišta, što štedi nešto prostora.

note: (para)
en: The <literal>svnadmin</literal> tool is installed automatically when you install the Subversion command line client. If you are installing the command line tools on a Windows PC, the best way is to download the Windows installer version. It is compressed more efficiently than the <filename>.zip</filename> version, so the download is smaller, and it takes care of setting the paths for you. You can download the latest version of the Subversion command line client from <ulink url="http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91"><citetitle>http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91</citetitle></ulink>.
target: Alat <literal>svnadmin</literal> je instaliran automatski kada instalirate Subverzionog klijenta komandne linije. Ako instalirate alat komandne linije na Vindouz PC, najbolji način je da skinete Vindouz instoler verziju. Ona je efikasnije komprimovana nego <filename>.zip</filename> verzija, tako da je skidanje manje, i ono vodi brigu da podesi putanju za vas. Možete skibuti zadnju verziju Subverzionog klijenta komandne linije sa <ulink url="http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91"><citetitle>http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91</citetitle></ulink>.

note: (title)
en: Hook Scripts
target: Zakačive Skripte

note: (primary)
en: hooks
target: zakačaljke

note: (primary)
en: hook scripts
target: zakačive skripte

note: (primary)
en: server side hook scripts
target: zakačive skripte sa serverske strane

note: (para)
en: A hook script is a program triggered by some repository event, such as the creation of a new revision or the modification of an unversioned property. Each hook is handed enough information to tell what that event is, what target(s) it's operating on, and the username of the person who triggered the event. Depending on the hook's output or return status, the hook program may continue the action, stop it, or suspend it in some way. Please refer to the chapter on <ulink url="http://svnbook.red-bean.com/en/1.4/svn.reposadmin.create.html#svn.reposadmin.create.hooks"><citetitle>Hook Scripts</citetitle></ulink> in the Subversion Book for full details about the hooks which are implemented.
target: Zakačive skripte su programi okidane nekim događajem iz spremišta, kao što je kreiranje nove revizije ili izmena neverzionirane osobine. Svaka zakačaljka je rukovođena sa dovoljno informacija da kže koji događaj se desio, koji okidač(i) je pokrenuo i korisničko ime osobe koja je okinula događaj. U zavisnosti od izlaza zakačaljke ili povratnog statusa, zakačiv program može nastaviti akciju, zaistaviti je, ili suspendovati na neki način. Molim vas da pogledate poglavlje <ulink url="http://svnbook.red-bean.com/en/1.4/svn.reposadmin.create.html#svn.reposadmin.create.hooks"><citetitle>Hook Scripts</citetitle></ulink> u Subverzionoj knjizi za pune detalje o zakačaljkama koje su implementirane.

note: (para)
en: These hook scripts are executed by the server that hosts the repository. TortoiseSVN also allows you to configure client side hook scripts that are executed locally upon certain events. See <xref linkend="tsvn-dug-settings-hooks"/> for more information.
target: Ovi zakačivi skriptovi su izvršeni na serveru koji ugošćava spremište. TortozSVN takođe omogućava da konfigurišete klijent stranu zakačivih skripti gde se očekuju lokalno pod nekim događajima. Vidite xref linkend="tsvn-dug-settings-hooks"/> za više informacija.

note: (para)
en: Sample hook scripts can be found in the <filename>hooks</filename> directory of the repository. These sample scripts are suitable for Unix/Linux servers but need to be modified if your server is Windows based. The hook can be a batch file or an executable. The sample below shows a batch file which might be used to implement a pre-revprop-change hook. <screen>
    rem Only allow log messages to be changed.
    if "%4" == "svn:log" exit 0
    echo Property '%4' cannot be changed &gt;&amp;2
    exit 1
    </screen> Note that anything sent to stdout is discarded. if you want a message to appear in the Commit Reject dialog you must send it to stderr. In a batch file this is achieved using <filename>&gt;&amp;2</filename>
target: Jednostavne zakačive skripte mogu se naći u <filename>zakačaljke> imeniku spremišta. Ove jednostavne skripte su pogodne za Uniks/Linuks servere ali traže izmene ako je server zasnovan na Vindouzu. Zakačke mogu biti grupni fajl ili izvršilac. Uzorak ispod pokazuje grupni fajl koji se može koristiti da se primeni kao pre-revprop-izmena zakačaljka. screen>
    rem Only allow log messages to be changed.
    if "%4" == "svn:log" exit 0
    echo Property '%4' cannot be changed &gt;&amp;2
    exit 1
    </screen> Primetimo sve poslato na stdout se odbacuje ako želite poruku da se pojavi u Ureži Odbaci dijalogu morate je poslati na stderr. U grupnom fajlu to se postiže korišćenjem <filename>&gt;&amp;2</filename>

note: (title)
en: Checkout Links
target: Veze preuzimanja

note: (primary)
en: checkout link
target: veza preuzimanja

note: (primary)
en: TortoiseSVN link
target: TortozSVN veza

note: (primary)
en: link
target: veza

note: (primary)
en: website
target: vebsajt

note: (para)
en: If you want to make your Subversion repository available to others you may want to include a link to it from your website. One way to make this more accessible is to include a <firstterm>checkout link</firstterm> for other TortoiseSVN users.
target: Ako želite učiniti vaše Subverziono spremište dostupno drugima morate uključiti vezu ka njemu od vašeg vebsajta. Jedan način da se to uradi mnogo pristupčnije je da se uključi <firstterm>veza preuzimanja</firstterm> za druge TortozSVN korisnike.

note: (para)
en: When you install TortoiseSVN, it registers a new <literal>tsvn:</literal> protocol. When a TortoiseSVN user clicks on such a link, the checkout dialog will open automatically with the repository URL already filled in.
target: Kada instalirate TortozSVN on registruje novi <literal>tsvn:</literal> protokol. Kada TortozSVN korisnik klikne na takvu vezu, dijalog preuzimanja se automatski otvara sa URLom spremišta već upisanim.

note: (para)
en: To include such a link in your own html page, you need to add code which looks something like this: <placeholder-1/>
target: Da unesete takvu vezu u vašu html stranicu potrebno vam je da dodate kod koji izgleda nešto kao ovo: <placeholder-1/>

note: (para)
en: Of course it would look even better if you included a suitable picture. You can use the <ulink url="http://tortoisesvn.tigris.org/images/TortoiseCheckout.png"><citetitle>TortoiseSVN logo</citetitle></ulink> or you can provide your own image. <placeholder-1/>
target: Svakako to će izgledati čak bolje ako uključite odgovarajuću sliku. Možete koristiti <ulink url="http://tortoisesvn.tigris.org/images/TortoiseCheckout.png"><citetitle>TortozSVN logo</citetitle></ulink> ili možete nabaviti svoju sopstvenu sliku. <placeholder-1/>

note: (title)
en: Daily Use Guide
target: Vodič dnevnog korišćenja

note: (para)
en: This document describes day to day usage of the TortoiseSVN client. It is <emphasis>not</emphasis> an introduction to version control systems, and <emphasis>not</emphasis> an introduction to Subversion (SVN). It is more like a place you may turn to when you know approximately what you want to do, but don't quite remember how to do it.
target: Ovaj dokument opisuje korišćenje dan za danom klijenta TortozSVN. To <emphasis>nije</emphasis> uvod u sistem kontrole verzija, i <emphasis>nije</emphasis>  uvod u Subverziju (SV). To je više kao mesto gde se možete vratiti tamo gde približno znate šta želite da uradite, ali ne razumete kako da to uradite.

note: (para)
en: If you need an introduction to version control with Subversion, then we recommend you read the fantastic book: <ulink url="http://svnbook.red-bean.com/"><citetitle>Version Control with Subversion</citetitle></ulink>.
target: Ako želite uvod u kontrolu verzija sa Subverzijom, preporučujemo vam da pročitate fantastičnu knjigu: <ulink url="http://svnbook.red-bean.com/"><citetitle>Kontrola verzija sa Subverzijom</citetitle></ulink>.

note: (para)
en: This document is also a work in progress, just as TortoiseSVN and Subversion are. If you find any mistakes, please report them to the mailing list so we can update the documentation. Some of the screenshots in the Daily Use Guide (DUG) might not reflect the current state of the software. Please forgive us. We're working on TortoiseSVN in our free time.
target: Ovaj dokument je takođe u radu, kao i TortozSVN to je i Subverzija. Ako nađete neku grešku, molim vas pošaljite je na poštansku listu da možemo ažurirati dokumentaciju. Neke slike ekrana u Vodiču dnevnog korišćenja (VDK) možda ne odražavaju tekuće stanje softvera. Molim vas da nam oprostite. Mi radimo na TortozSVN u svoje slobodno vreme.

note: (para)
en: You should have installed TortoiseSVN already.
target: Trebalo bi da već imate instaliran TortozSVN.

note: (para)
en: You should be familiar with version control systems.
target: Trebalo bi da ste familijarni sa sistemom kontrole verzija.

note: (para)
en: You should know the basics of Subversion.
target: Trebalo bi da znate osnove Subverzije.

note: (para)
en: You should have set up a server and/or have access to a Subversion repository.
target: Trebalo bi da imate podešen server i-ili da imate pristup Subverzionom spremištu.

note: (para)
en: In order to get the most out of the Daily Use Guide: <placeholder-1/>
target: Da bi dobili najviše od Vodiča dnevnog korišćenja: <placeholder-1/>

note: (title)
en: Getting Started
target: Krenimo od početka

note: (title)
en: Icon Overlays
target: Prekrivne ikone

note: (title)
en: Explorer showing icon overlays
target: Pretraživač prikazuje prekrivne ikone

note: (para)
en: <placeholder-1/> One of the most visible features of TortoiseSVN is the icon overlays which appear on files in your working copy. These show you at a glance which of your files have been modified. Refer to <xref linkend="tsvn-dug-wcstatus-1"/> to find out what the different overlays represent.
target: <placeholder-1/> Jedna od najvidljivijih osobina TortozSVN su prekrivne ikone koje se pojavljuju na fajlovima u vašoj radnoj kopiji. One vam pokazuju, savršeno, koji je od vaših fajlova izmenjen. Uporedite sa <xref linkend="tsvn-dug-wcstatus-1"/> da nađete šta različiti prekrivači pokazuju.

note: (title)
en: Context Menus
target: Kontekst meniji:

note: (primary)
en: context menu
target: kontekst meni

note: (primary)
en: right-click
target: desni-klik

note: (title)
en: Context menu for a directory under version control
target: Kontekst meni za imenik pod kontrolom verzija

note: (para)
en: <placeholder-1/> All TortoiseSVN commands are invoked from the context menu of the windows explorer. Most are directly visible, when you <action>right click</action> on a file or folder. The commands that are available depend on whether the file or folder or its parent folder is under version control or not. You can also see the TortoiseSVN menu as part of the Explorer file menu.
target: <placeholder-1/> Sve TortozSVN komande se pozivaju iz kontekst menija vindouz eksplorera. Većina je direktno vidljiva kada uradite <action>desni klik</action> na fajl ili imenik. Koje su komande dostupne zavisi od toga da li  je fajl ili imenik ili njihov predački imenik pod kontrolom verzija ili nije. Možete, takođe, videtu stablo TortozSVN menija kao deo Eksplorer fajl menija.

note: (para)
en: Some commands which are very rarely used are only available in the extended context menu. To bring up the extended context menu, hold down the <keycap>Shift</keycap> key when you <action>right-click</action>.
target: Neke komande koje se veoma retko koriste su dostupne samo u proširenom kontekst meniju. Da pozovete prošireni kontekst meni držite <keycap>Šift</keycap> taster kada uradite <action>desni-klik</action>.

note: (title)
en: Explorer file menu for a shortcut in a versioned folder
target: Eksplorer fajl meni za skraćenice u verzionisanom imeniku

note: (para)
en: In some cases you may see several TortoiseSVN entries. This is not a bug! <placeholder-1/> This example is for an unversioned shortcut within a versioned folder, and in the Explorer file menu there are <emphasis>three</emphasis> entries for TortoiseSVN. One is for the folder, one for the shortcut itself, and the third for the object the shortcut is pointing to. To help you distinguish between them, the icons have an indicator in the lower right corner to show whether the menu entry is for a file, a folder, a shortcut or for multiple selected items.
target: U nekim slučajevima možete videti više TortozSVN ulaza. To nije bag! <placeholder-1/> Ovaj primer je za neverzionisane skraćenice u okviru verzionisanog imenika, i u Eksplorer fajl meniju postoji <emphasis>stablo</emphasis> ulaz za TortozSVN. Jedno je za imenik, jedno za same skraćenice, i treće za objekte na koje pokazuju skraćenice. Da bismo vam pomogli da ih razlikujete, ikone imaju indikator u donjem desnom uglu koji pokazuje da li je meni ulaz za fajl, skraćenicu ili višestruko selektovane stavke.

note: (para)
en: If you are using Windows 2000 you will find that the context menus are shown as plain text, without the menu icons shown above. We are aware that this was working in previous versions, but Microsoft has changed the way its icon handlers work for Vista, requiring us to use a different display method which unfortunately does not work on Windows 2000.
target: Ako koristite Vindouz 2000 naćićete da je kontekst meni prikazan kao potpuni tekst, bez ikona menija prikazanih iznad. Mi smo upoznati da je tako radilo u prethodnoj verziji, ali Mikrosoft je izmenio način rukovanja ikonama za Vistu, što od nas zahteva da koristimo različit način prikazivanja koji, na nesreću, ne radi na Vindouzu 2000.

note: (title)
en: Drag and Drop
target: Vuci baci

note: (primary)
en: drag handler
target: vuvi rukovalac

note: (primary)
en: drag-n-drop
target: vuci-i-baci

note: (primary)
en: right drag
target: desni vuci

note: (title)
en: Right drag menu for a directory under version control
target: Desni vuci meni za imenike pod kontrolom verzija

note: (para)
en: <placeholder-1/> Other commands are available as drag handlers, when you <action>right drag</action> files or folders to a new location inside working copies or when you <action>right drag</action> a non-versioned file or folder into a directory which is under version control.
target: <placeholder-1/> Druge komande su dostupne kao vučni rukovaoci, kada  <action>desni vuci</action> fajlova i imenika na novu lokaciju unutar radne kopije ili kada action>desni vuci</action> neverzionisan fajl ili imenik u imenik koji je pod kontrolom verzija.

note: (title)
en: Common Shortcuts
target: Zajedničke skraćenice

note: (para)
en: Help, of course.
target: Po,oć, svakako.

note: (para)
en: Refresh the current view. This is perhaps the single most useful one-key command. For example ... In Explorer this will refresh the icon overlays on your working copy. In the commit dialog it will re-scan the working copy to see what may need to be committed. In the Revision Log dialog it will contact the repository again to check for more recent changes.
target: Osvežite tekući izgled. Ovo je možda jedna najkorisnija jedan-taster komanda. Na primer... U Eksploreru ovo će osvežiti prekrivačke ikone u vašoj radnoj kopiji. U dijalogu narezivanja to će re-skenirati radnu kopiju da vidi šta treba da bude urezano. U dijalogu Dnevnika revizija kontaktiraće još jednom spremište da proveri najskorije izmene.

note: (para)
en: Select all. This can be used if you get an error message and want to copy and paste into an email. Use Ctrl-A to select the error message and then ...
target: Izaberite sve. Ovo može biti korisno ako dobijete poruku greške i želite da kopirate i nalepite u e-poštu. Koristite Ctrl-A da izaberete poruku greške i onda ...

note: (para)
en: ... Copy the selected text.
target: ... Kopira izabrani tekst.

note: (para)
en: Some common operations have well-known Windows shortcuts, but do not appear on buttons or in menus. If you can't work out how to do something obvious, like refreshing a view, check here. <placeholder-1/>
target: Neke zajedničke operacije imaju dobro poznate Vindouz skraćenice, ali se ne pojavljuju na digmićima ili u menijima. Ako ne možete pronaći kako da uradite nešto  očigledno, kao što je osvežavanje izgleda, proverite ovde. <placeholder-1/>

note: (primary)
en: authentication
target: autentikacija

note: (title)
en: Authentication Dialog
target: Autentifikacioni dijalog

note: (para)
en: <filename>svn.simple</filename> contains credentials for basic authentication (username/password).
target: <filename>svn.simple</filename> sadrži akreditaciju osnove autentifikacije (korisnik/lozinka).

note: (para)
en: <filename>svn.ssl.server</filename> contains SSL server certificates.
target: <filename>svn.ssl.server</filename> sadrži SSL sertifikate servera.

note: (para)
en: <filename>svn.username</filename> contains credentials for username-only authentication (no password needed).
target: <filename>svn.username</filename> sadrži akreditaciju autentifikacje samo za korsničko ime (lozinka nije potrebna).

note: (para)
en: If the repository that you are trying to access is password protected, an authentication Dialog will show up. <placeholder-1/> Enter your username and password. The checkbox will make TortoiseSVN store the credentials in Subversion's default directory: <filename>%APPDATA%\Subversion\auth</filename> in three subdirectories: <placeholder-2/>
target: Ako je spremište kome pokušavate da pristupite zaštićeno lozinkom, autentifikacioni dijalog će vam biti prikazan. <placeholder-1/> Unesite korisničko ime i lozinku. Boks prove će učiniti da TortozSVN smesti akreditaciju u Subverzionom uobičajenom imeniku: <filename>%APPDATA%\Subversion\auth</filename> u stablu subimenika: <placeholder-2/>

note: (para)
en: If you want to clear the authentication cache for all servers, you can do so from the <guilabel>Saved Data</guilabel> page of TortoiseSVN's settings dialog. That button will clear all cached authentication data from the Subversion <filename>auth</filename> directories, as well as any authentication data stored in the registry by earlier versions of TortoiseSVN. Refer to <xref linkend="tsvn-dug-settings-saved-data"/>.
target: Ako želite da obrišete autentifikacioni keš za sve servere, možete to uraditi od <guilabel>Zapamćeni podaci</guilabel>  strane TortozSVN dijaloga podešavanja.To dugme će očistiti sve autentifikacione keširane podatke iz Subverzionog <filename>auth</filename>  imenika, kao i bilo koji autentifikacioni podatak smešten u registru od ranijih verzija TortozSVN. Uporedite sa <xref linkend="tsvn-dug-settings-saved-data"/>.

note: (para)
en: For more information on how to set up your server for authentication and access control, refer to <xref linkend="tsvn-serversetup"/>
target: Za više informacija kako da se podesi vaš server za autentifikaciju i kontrolu pristupa, pogledaj u <xref linkend="tsvn-serversetup"/>

note: (title)
en: Maximizing Windows
target: Maksimiranje Vindouza

note: (primary)
en: maximize
target: maksimiziranje

note: (para)
en: Many of TortoiseSVN's dialogs have a lot of information to display, but it is often useful to maximize only the height, or only the width, rather than maximizing to fill the screen. As a convenience, there are shortcuts for this on the <guilabel>Maximize</guilabel> button. Use the <action>middle mouse</action> button to maximize vertically, and <action>right mouse</action> to maximize horizontally.
target: Mnogi od TortozSVN dijaloga imaju puno informacija da prikažu, ali je često korisno da se maksimizira samo visina, ili samo širina, radije nego da se maksimizira na ceo ekran. Konvencionalno, postoje skraćenice za ovo na <guilabel>Maksimiziraj</guilabel> dugme. Koristi <action>srednj dugme miša</action> da se maksimizira vertikalno, i <action>desni miš</action> da se maksimizira horizontalno.

note: (title)
en: Importing Data Into A Repository
target: Uvoz podataka u spremište

note: (primary)
en: import
target: uvezi

note: (primary)
en: add files to repository
target: dodavanje fajlova u spremište

note: (title) (entry) (glossterm)
en: Import
target: Uvezi

note: (primary)
en: temporary files
target: privremeni fajlovi

note: (para)
en: If you are importing into an existing repository which already contains some projects, then the repository structure will already have been decided. If are importing data into a new repository then it is worth taking the time to think about how it will be organised. Read <xref linkend="tsvn-repository-layout"/> for further advice.
target: Ako uvozite u postojeće spremište koje već sadrži neke projekte, tada bi trebalo da su strukture spremišta već određene. Ako uvozite podatke u novo spremište vredi potrošiti vreme na razmišljanju o tome kako bi ga trebalo organizovati. Pročitajte  <xref linkend="tsvn-repository-layout"/> za dalje savete.

note: (para)
en: There is no way to select files and folders to include, aside from using the global ignore settings.
target: Nema načina da se izaberu fajlovi i imenici za uključivanje pored korišćenja globalnog podešavanja zanemarivanja.

note: (para)
en: The folder imported does not become a working copy. You have to do a checkout to copy the files back from the server.
target: Uvezeni folder ne postaje radna kopija. Imate da uradite preuzimanje da kopirate fajlove nazad sa servera.

note: (para)
en: It is easy to import to the wrong folder level in the repository.
target: Lako je uvesti u loš nivo imenika u spremištu.

note: (para)
en: This section describes the Subversion import command, which was designed for importing a directory hierarchy into the repository in one shot. Although it does the job, it has several shortcomings: <placeholder-1/> For these reasons we recommend that you do not use the import command at all but rather follow the two-step method described in <xref linkend="tsvn-dug-import-in-place"/>. But since you are here, this is how the basic import works ...
target: Ovaj deo opisuje Subverzionu komandu uvoza, koja je dizajnirana za uvoz hijerarhiju imenika u spremište u jednom opaljenju. Bez obzira što to  završava posao to ima više grešaka: <placeholder-1/>  Iz ovih razloga preporučujemo da ne koristite komandu uvoza uopšte već radije pratite dvostepen metod opisan u <xref linkend="tsvn-dug-import-in-place"/>. Ali pošto ste ovda, evo kako osnovni uvoz radi ...

note: (para)
en: Remove all files which are not needed to build the project (temporary files, files which are generated by a compiler e.g. *.obj, compiled binaries, ...)
target: Izbacite sve fajlove koji nisu potrebni za gradnju projekta (privremeni fajlovi, koje generiše kompajler npr. *.obj, kompajlirane binarije, ...)

note: (para)
en: Organize the files in folders and sub-folders. Although it is possible to rename/move files later it is highly recommended to get your project's structure straight before importing!
target: Organizujte fajlove u imenike i podimenike. Takođe je moguće preimenovanje/pomeranje fajlova kasnije jako je preporučljivo da dobijete pravu strukturu projekta pre uvoza!

note: (para)
en: Before you import your project into a repository you should: <placeholder-1/>
target: Pre nego što uvezete vaš projekat u spremište potrebno je da: <placeholder-1/>

note: (title)
en: The Import dialog
target: Uvozni dijalog

note: (para)
en: Now select the top-level folder of your project directory structure in the windows explorer and <action>right click</action> to open the context menu. Select the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Import...</guimenuitem></menuchoice> which brings up a dialog box: <placeholder-1/>
target: Sada izaberite imenik vršnog nivoa vaše strukture imenika projekta u vindouz eksploreru i <action>desni klik</action> da se otvori kontekstni meni. Izabeite komandu <menuchoice><guimenu>TortozSVN</guimenu><guimenuitem>Uvoz...</guimenuitem></menuchoice> koja  donosi dijalog boks:

note: (para)
en: In this dialog you have to enter the URL of the repository location where you want to import your project. It is very important to realise that the local folder you are importing does not itself appear in the repository, only its content. For example if you have a structure: <screen>
    C:\Projects\Widget\source
    C:\Projects\Widget\doc
    C:\Projects\Widget\images
    </screen> and you import <filename>C:\Projects\Widget</filename> into <systemitem class="url">http://mydomain.com/svn/trunk</systemitem> then you may be surprised to find that your subdirectories go straight into <literal>trunk</literal> rather than being in a <literal>Widget</literal> subdirectory. You need to specify the subdirectory as part of the URL, <systemitem class="url">http://mydomain.com/svn/trunk/Widget-X</systemitem>. Note that the import command will automatically create subdirectories within the repository if they do not exist.
target: U ovom dijalogu imate da unesete URL lokacije spremišta gde želite da uvezete vaš projekat. Veoma je važno da vodite računa da lokalni imenik koji uvozite se ne pojavljuje sam u spremištu, samo njegov sadržaj. Na primer ako imate strukturu: <screen>
    C:\Projects\Widget\source
    C:\Projects\Widget\doc
    C:\Projects\Widget\images
    </screen> i unesete <filename>C:\Projects\Widget</filename> u <systemitem class="url">http://mydomain.com/svn/trunk</systemitem> bićete iznenađeni kad uvidite da vaši podimenici idu u<literal>trunk</literal> radije nego da budu u <literal>Widget</literal> podimenik. Potrebno je da secificirate podimenik kao deo URL, <systemitem class="url">http://mydomain.com/svn/trunk/Widget-X</systemitem>. Primetimo uvozna komanda će automatski kreirati podimenik unutar spremišta ako on ne postoji..

note: (para)
en: The import message is used as a log message.
target: Uvozna poruka se koristi kao poruka dnevnika.

note: (para)
en: By default, files and folders which match the global-ignore patterns are <emphasis>not</emphasis> imported. To override this behaviour you can use the <guilabel>Include ignored files</guilabel> checkbox. Refer to <xref linkend="tsvn-dug-settings-main"/> for more information on setting a global ignore pattern.
target: Uobičajeno, fajlovi i imenici koji hvataju globalno-zanemariv model <emphasis>nisu</emphasis> uvezeni. Da se premosti ovakvo ponašanje možete koristiti <guilabel>Uključiti zanemarene fajlove</guilabel> čekboks. Konsultujte <xref linkend="tsvn-dug-settings-main"/> za više informacija o podešavanju globalnog modela izbegavanja.

note: (para)
en: As soon as you press <guibutton>OK</guibutton> TortoiseSVN imports the complete directory tree including all files into the repository. The project is now stored in the repository under version control. Please note that the folder you imported is <emphasis>NOT</emphasis> under version control! To get a version-controlled <firstterm>working copy</firstterm> you need to do a Checkout of the version you just imported. Or read on to find out how to import a folder in place.
target: Ćim pritisnete <guibutton>OK</guibutton> TortozSVN uvozi kompletno stablo imenika uključujući sve fajlove u spremište. Projekat je sada smeten u spremište pod kontrolom verzija. Molim vas primetite to da imenik koji ste uvezli <emphasis>NIJE</emphasis> pod kontrolom verzija! Da dobijete verzijom kontrolisanu <firstterm>radnu kopiju</firstterm> potrebno je da uradite Preuzimanje verzije koju ste upravo uvezli. Ili da pročitate  kako uvesti imenik na mesto.

note: (title)
en: Import in Place
target: Uvoz na mesto

note: (primary)
en: import in place
target: uvoz na mesto

note: (para)
en: Use the repository browser to create a new project folder directly in the repository.
target: Koristite pretraživač spremišta da kreirate novi imenik projekta direktno u spremištu.

note: (para)
en: Checkout the new folder over the top of the folder you want to import. You will get a warning that the local folder is not empty. Now you have a versioned top level folder with unversioned content.
target: Preuzmite novi imenik preko vrha imenika koji želite da uvezete. Dobićete upozorenje da lokalni imenik nije prazan. Sada imate verzionisani imenik vršnog nivoa sa neverzionisanim sadržajem.

note: (para)
en: Use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Add...</guimenuitem></menuchoice> on this versioned folder to add some or all of the content. You can add and remove files, set <literal>svn:ignore</literal> properties on folders and make any other changes you need to.
target: Koristite <menuchoice><guimenu>TortozSVN</guimenu><guimenuitem>Dodaj...</guimenuitem></menuchoice> na ovaj verzionisani imenik da dodate deo ili ceo sadržaj. Možete dodati i izbaciti fajlove, postaviti <literal>svn:zanemari</literal> osobine imenika i uraditi druge izmene koje su vam potrebne.

note: (para)
en: Commit the top level folder, and you have a new versioned tree, and a local working copy, created from your existing folder.
target: Urežite imenik vršnog nivoa, i imate novo verzionisano stablo i lokalnu radnu kopiju, kreiranu od postojećeg imenika.

note: (para)
en: Assuming you already have a repository, and you want to add a new folder structure to it, just follow these steps: <placeholder-1/>
target: Uzmimo da već imate spremište i želite da dodate novu strukturu imenika u njega, samo pratite ove korake: <placeholder-1/>

note: (title)
en: Special Files
target: Specijalni fajlovi

note: (primary)
en: special files
target: specijalni fajlovi

note: (para)
en: Sometimes you need to have a file under version control which contains user specific data. That means you have a file which every developer/user needs to modify to suit his/her local setup. But versioning such a file is difficult because every user would commit his/her changes every time to the repository.
target: Ponekad vam je potrebno da imate fajl pod kontrolom verzija koji sadrži podatke specifične za korisnika. To znači da imate fajl koji svaki kreator/korisnik želi da menja da prati njegovo/njeno lokalno podešavanje. Ali verzionisanjem takvog fajla je teško jed svski korisnik želi da ureže njegove/njene izmene svaki put u spremište.

note: (para)
en: In such cases we suggest to use <emphasis>template</emphasis> files. You create a file which contains all the data your developers will need, add that file to version control and let the developers check this file out. Then, each developer has to <emphasis>make a copy</emphasis> of that file and rename that copy. After that, modifying the copy is not a problem anymore.
target: U takvim slučajevima sugeriramo da se koristi  <emphasis>templejt</emphasis> fajlovi. Kreirajte fajl koji sadrži sve podatke koji su potrebni razvojnom timu, dodajte taj fajl u kontrolu verzija i pustite da ljudi iz razvojnog tima provere ovaj fajl. Zatim, svaki čovek iz razvojnog tima je <emphasis>napravio kopiju</emphasis> tog fajla i preimenovao tu kopiju. Posle toga izmene kopija nisu više problem.

note: (para)
en: As an example, you can have a look at TortoiseSVN's build script. It calls a file named <filename>TortoiseVars.bat</filename> which doesn't exist in the repository. Only the file <filename>TortoiseVars.tmpl</filename>. <filename>TortoiseVars.tmpl</filename> is the template file which every developer has to create a copy from and rename that file to <filename>TortoiseVars.bat</filename>. Inside that file, we added comments so that the users will see which lines they have to edit and change according to their local setup to get it working.
target: Kao primer možete pogledati TortozSVN skript za izgradnju. On poziva fajl koji se zove filename>TortoiseVars.bat</filename> koji ne postoji u spremištu. Samo fajl <filename>TortoiseVars.tmpl</filename>. <filename>TortoiseVars.tmpl</filename> je šablon fajl koji svaki učesnik razvoja ima da kopira i preimenuje taj fajl u filename>TortoiseVars.bat</filename>. Unutar tog fajla dodajemo komentare tako da  korisnik može da vidi koje linije treba da uredi i izmeni prema svom lokalnom podešavanju da bi to radilo.

note: (para)
en: So as not to disturb the users, we also added the file <filename>TortoiseVars.bat</filename> to the ignore list of its parent folder, i.e. we've set the Subversion property <literal>svn:ignore</literal> to include that filename. That way it won't show up as unversioned on every commit.
target: Da ne bi uznemiravali korisnike takođe dodamo fajl <filename>TortoiseVars.bat</filename> listi  zanemarenih predačkog imenika, tj. mi smo podesili Subverzionu osobinu <literal>svn:zanemari</literal> da uključi to ime fajla. Na taj način on se neće pokazati neverzionisanim kod svakog urezivanja.

note: (title)
en: Referenced Projects
target: Referentni projekti

note: (primary)
en: external repositories
target: spoljašnje spremište

note: (primary)
en: externals
target: spoljašnji

note: (para)
en: Sometimes it is useful to construct a working copy that is made out of a number of different checkouts. For example, you may want different subdirectories to come from different locations in a repository, or perhaps from different repositories altogether. If you want every user to have the same layout, you can define the <literal>svn:externals</literal> properties.
target: Ponekad je korisno da se konsultuje radna kopija koja je napravljena od brojnih različitih preuzimanja. Na primer, možete želeti različite podimenike da dođu sa različitih lokacija u spremište, ili  možda kompletno iz različitih spremišta. Ako želite da svaki korisnik ima isti izgled možete definisati <literal>svn:spoljašne</literal> osobine.

note: (para)
en: Let's say you check out a working copy of <filename>/project1</filename> to <filename>D:\dev\project1</filename>. Select the folder <filename>D:\dev\project1</filename>, <action>right click</action> and choose <menuchoice><guimenu>Windows Menu</guimenu><guimenuitem>Properties</guimenuitem></menuchoice> from the context menu. The Properties Dialog comes up. Then go to the Subversion tab. There, you can set properties. Click <guibutton>Add...</guibutton>. Select the <literal>svn:externals</literal> property from the combobox and write in the edit box the repository URL in the format <literal>name url</literal> or if you want to specify a particular revision, <literal>name -rREV url</literal> You can add multiple external projects, 1 per line. Note that URLs must be properly escaped or they will not work. For example you must replace each space with <literal>%20</literal>. Note that it is not possible to use folder names with spaces in them. Suppose that you have set these properties on <filename>D:\dev\project1</filename>: <screen>
    sounds   http://sounds.red-bean.com/repos
    quick_graphs  http://graphics.red-bean.com/repos/fast%20graphics
    skins/toolkit -r21 http://svn.red-bean.com/repos/skin-maker
    </screen> Now click <guibutton>Set</guibutton> and commit your changes. When you (or any other user) update your working copy, Subversion will create a sub-folder <filename>D:\dev\project1\sounds</filename> and checkout the sounds project, another sub-folder <filename>D:\dev\project1\quick graphs</filename> containing the graphics project, and finally a nested sub-folder <filename>D:\dev\project1\skins\toolkit</filename> containing revision 21 of the skin-maker project.
target: Recimo da ste preuzeli radnu kopiju od <filename>/project1</filename> do <filename>D:\dev\project1</filename>. Izaberite imenik  <filename>D:\dev\project1</filename>, <action>desni klik</action> i izaberite <menuchoice><guimenu>Vindouz Meni</guimenu><guimenuitem>Osobine</guimenuitem></menuchoice> iz kontekst menija. Osobine dijalog dolazi. Zatim idite na tab Subverzija. Tamo možete podesiti osobine. Kliknite <guibutton>Dodaj...</guibutton>. Izaberite <literal>svn:spoljašnje</literal> osobine u komboboksu i napišite URL spremišta u formatu  <literal>ime url</literal> ili ako želite da specificirate partikularnu reviziju, <literal>ime -rREV url</literal> Mžete dodati višestruke spoljašnje projekte, 1 po liniji. Primetimo da taj URL mora biti odgovarajuće popunjen kosim crtama ili to neće raditi. Na primer morate zameniti svaki razmak sa <literal>%20</literal>. Primetimo da  nije moguće koristiti imena  imenika  sa razmacima u njima. Pretpostavimo da imate podešene ove osobine na <filename>D:\dev\project1</filename>: <screen>
    sounds   http://sounds.red-bean.com/repos
    quick_graphs  http://graphics.red-bean.com/repos/fast%20graphics
    skins/toolkit -r21 http://svn.red-bean.com/repos/skin-maker
    </screen> Sada klik na <guibutton>Podesi</guibutton> i urežite izmene. Kada vi (ili bilo koji drugi korisnik) ažurira vašu radnu kopiju, Subverzija će kreirati podimenik <filename>D:\dev\project1\sounds</filename> i proveriti sounds projekat, sledeći podimenik <filename>D:\dev\project1\quick graphs</filename> koji sadrži grafički projekat, i na kraju ugnježdeni podimenik <filename>D:\dev\project1\skins\toolkit</filename> koji sadrži reviziju 21 skin-maker projekta.

note: (para)
en: You should strongly consider using explicit revision numbers in all of your externals definitions, as described above. Doing so means that you get to decide when to pull down a different snapshot of external information, and exactly which snapshot to pull. Besides the common sense aspect of not being surprised by changes to third-party repositories that you might not have any control over, using explicit revision numbers also means that as you backdate your working copy to a previous revision, your externals definitions will also revert to the way they looked in that previous revision, which in turn means that the external working copies will be updated to match they way <emphasis>they</emphasis> looked back when your repository was at that previous revision. For software projects, this could be the difference between a successful and a failed build of an older snapshot of your complex code base.
target: Treba čvrsto osmisliti korišćenje spoljašnjih revizionih brojeva u svim vašim spoljašnjim definicijama, kako je opisano gore. Radeći tako znači da odlučujete da spustite različite slike spoljašnjih informacija, i tačno koju sliku izvući. Pored zajedničkog osećaja šta nas ne iznenađuje promenama u spremištima treće strane to je da može da nemate nikakakvu kontrolu na njima, koristeći eksplicitno revizione brojeve takođe znači da ste unazad datirali vašu radnu kopiju kao prethodnu reviziju, vaše spoljne definicije su takođe vraćene na način kako su izgledale u prethodnoj reviziji, koja znači to da će se spoljašnja radna kopija ažurirati da uhvati  način  kako <emphasis>one</emphasis> izgledaju nazad kada je spremište bili u prethodnoj reviziji. Za softverske projekte,  moglo bi biti razlika između uspešne i neuspešne gradnje stare slike složene kodne osnove.

note: (para)
en: If the external project is in the same repository, any changes you make there there will be included in the commit list when you commit your main project.
target: Ako je spoljašnji projekat u istom spremištu, bilo koja izmena koju napravite tamo biće uključena u listu za urezivanje kada urezujete glavni projekat.

note: (para)
en: If the external project is in a different repository, any changes you make to the external project will be notified when you commit the main project, but you have to commit those external changes separately.
target: Ako je spoljašnji projekat u različitom spremištu, bilo koje izmene koje napravite u spoljašnjem projektu biće označene kada urezujete glavni projekat, ali morate urezati te spoljašnje izmene izdvojeno.

note: (para)
en: If you use absolute URLs in <literal>svn:externals</literal> definitions and you have to relocate your working copy (i.e., if the URL of your repository changes), then your externals won't change and might not work anymore.
target: Ako koristite apsolutne URLove u <literal>svn:spoljašnje</literal> definicije i imate da relocirate vašu radnu kopiju (npr. ako je URL vašeg spremišta izmenjen), tada vaši eksternali se ne mogu izmeniti niti uopšte raditi.

note: (para)
en: To avoid such problems, Subversion clients version 1.5 and higher support relative external URLs. Four different methods of specifying a relative URL are supported. In the following examples, assume we have two repositories: one at <systemitem class="url">http://example.com/svn/repos-1</systemitem> and another at <systemitem class="url">http://example.com/svn/repos-2</systemitem>. We have a checkout of <systemitem class="url">http://example.com/svn/repos-1/project/trunk</systemitem> into <filename>C:\Working</filename> and the <literal>svn:externals</literal> property is set on trunk.
target: Da se izbegnu takvi problemi Subverzioni klijenti od verzije 1.5 podržavaju relativne spoljašnje URLove. Četiri različita metoda specificiranja relativnih URLova je podržano. U sledećem primerima uzmimo da imamo dva spremišta: jedno na systemitem class="url">http://example.com/svn/repos-1</systemitem> i drugo na <systemitem class="url">http://example.com/svn/repos-2</systemitem>.  Preuzeli  smo <systemitem class="url">http://example.com/svn/repos-1/project/trunk</systemitem>u <filename>C:\Working</filename> i <literal>svn:spoljašnje</literal> osobine su podešene na deblo.

note: (term)
en: Relative to parent directory
target: Relativno na predački imenik

note: (para)
en: These URLs always begin with the string <literal>../</literal> for example: <screen>
    ../../widgets/foo  common/foo-widget
    </screen> This will extract <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> into <filename>C:\Working\common\foo-widget</filename>.
target: Ovi URLovi uvek počinju stringom <literal>../</literal> na primer: <screen>
    ../../widgets/foo  common/foo-widget
    </screen> Ovo treba da ekstrahuje <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> u <filename>C:\Working\common\foo-widget</filename>.

note: (para)
en: Note that the URL is relative to the URL of the directory with the <literal>svn:externals</literal> property, not to the directory where the external is written to disk.
target: Primetimo da je URL relativno u odnosu na URL imenika sa  <literal>svn:spoljašnje </literal>osobine, nije ka imeniku gde su spoljšnje osobine upisane na disku.

note: (term)
en: Relative to repository root
target: Relativno na koren spremišta

note: (para)
en: These URLs always begin with the string <literal>^/</literal> for example: <screen>
    ^/widgets/foo  common/foo-widget
    </screen> This will extract <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> into <filename>C:\Working\common\foo-widget</filename>.
target: Ovi URLovi uvek počinju stringom <literal>^/</literal> na primer: <screen>
    ^/widgets/foo  common/foo-widget
    </screen> Ovo će izdvojiti <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> u <filename>C:\Working\common\foo-widget</filename>.

note: (para)
en: You can easily refer to other repositories with the same <literal>SVNParentPath</literal> (a common directory holding several repositories). For example: <screen>
    ^/../repos-2/hammers/claw  common/claw-hammer
    </screen> This will extract <systemitem class="url">http://example.com/svn/repos-2/hammers/claw</systemitem> into <filename>C:\Working\common\claw-hammer</filename>.
target: Možete se lako pozvati na drugo spremište sa istim  <literal>SVNPredakPutanja</literal> (zajednički imenik koji drži više spremišta). Na primer: <screen>
    ^/../repos-2/hammers/claw  common/claw-hammer
    </screen> Ovo će izdvojiti <systemitem class="url">http://example.com/svn/repos-2/hammers/claw</systemitem> u <filename>C:\Working\common\claw-hammer</filename>.

note: (term)
en: Relative to scheme
target: Relativno na šemu

note: (para)
en: URLs beginning with the string <literal>//</literal> copy only the scheme part of the URL. This is useful when the same hostname must the accessed with different schemes depending upon network location; e.g. clients in the intranet use <systemitem class="url">http://</systemitem> while external clients use <systemitem class="url">svn+ssh://</systemitem>. For example: <screen>
    //example.com/svn/repos-1/widgets/foo  common/foo-widget
    </screen> This will extract <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> or <systemitem class="url">svn+ssh://example.com/svn/repos-1/widgets/foo</systemitem> depending on which method was used to checkout <filename>C:\Working</filename>.
target: URL koji počinje stringom <literal>//</literal> kopira samo deo šeme URLa. Ovo je korisno kada se mora pristupiti  domćinu istog imena sa različitim šemama u zavisnosti od mrežne lokacije; npr. klijenti na intranetu koriste  <systemitem class="url">http://</systemitem> dok spoljšnji klijenti koriste <systemitem class="url">svn+ssh://</systemitem>. Na primer: <screen>
    //example.com/svn/repos-1/widgets/foo  common/foo-widget
    </screen> Ovo će izdvojiti <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> ili <systemitem class="url">svn+ssh://example.com/svn/repos-1/widgets/foo</systemitem> u zavisnosti koji metod je korišćen za preuzimanje <filename>C:\Working</filename>.

note: (term)
en: Relative to the server's hostname
target: Relativno do serverovog imena domaćina

note: (para)
en: URLs beginning with the string <literal>/</literal> copy the scheme and the hostname part of the URL, for example: <screen>
    /svn/repos-1/widgets/foo  common/foo-widget
    </screen> This will extract <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> into <filename>C:\Working\common\foo-widget</filename>. But if you checkout your working copy from another server at <systemitem class="url">svn+ssh://another.mirror.net/svn/repos-1/project1/trunk</systemitem> then the external reference will extract <systemitem class="url">svn+ssh://another.mirror.net/svn/repos-1/widgets/foo</systemitem>.
target: URL koji počinju stringom <literal>/</literal> kopiraju šemu i deo sa imenom domaćina URLa, na primer: <screen>
    /svn/repos-1/widgets/foo  common/foo-widget
    </screen> Ovo će izdvojiti <systemitem class="url">http://example.com/svn/repos-1/widgets/foo</systemitem> u <filename>C:\Working\common\foo-widget</filename>. Ali ako preuzmete vašu radni kopiju sa drugog servera na systemitem class="url">svn+ssh://another.mirror.net/svn/repos-1/project1/trunk</systemitem> tada će spoljašnje reference izdvojiti <systemitem class="url">svn+ssh://another.mirror.net/svn/repos-1/widgets/foo</systemitem>.

note: (para)
en: If you need more information how TortoiseSVN handles Properties read <xref linkend="tsvn-dug-propertypage"/>.
target: Ako vam treba više informacija kako TortozSVN rukuje sa Osobinama pročitajte <xref linkend="tsvn-dug-propertypage"/>.

note: (para)
en: To find out about different methods of accessing common sub-projects read <xref linkend="tsvn-howto-common-projects"/>.
target: Da biste našli više o raznim metodama pristupa zajedničkim podprojektima čitajte <xref linkend="tsvn-howto-common-projects"/>.

note: (title)
en: Checking Out A Working Copy
target: Provera radne kopije

note: (primary)
en: checkout
target: preuzmi

note: (primary)
en: create working copy
target: kreiranje radne kopije

note: (para)
en: To obtain a working copy you need to do a <firstterm>checkout</firstterm> from a repository.
target: Da biste dobili tadnu kopiju potrebno je da uradite <firstterm>preuzimanje</firstterm> iz spremišta.

note: (title)
en: The Checkout dialog
target: Preuzimanje dijalog

note: (para)
en: Select a directory in windows explorer where you want to place your working copy. <action>Right click</action> to pop up the context menu and select the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Checkout...</guimenuitem></menuchoice>, which brings up the following dialog box: <placeholder-1/> If you enter a folder name that does not yet exist, then a directory with that name is created.
target: Iyaberi imenik u vindouz eksploreru gde želite smestiti vašu radnu kopiju. <action>Desni klik</action> da se pojavi kontekst meni i izaberite komandu <menuchoice><guimenu>TortozSVN</guimenu><guimenuitem>Preuzmi...</guimenuitem></menuchoice>, koja daje sledeći dijalog boks: <placeholder-1/> Ako unesete ime imenika koje još ne postoji, tada će imenik tog imena biti kreiran.

note: (title)
en: Checkout Depth
target: Preuzimanje dubina

note: (term)
en: Fully recursive
target: Potpuno rekurzivan

note: (para)
en: Checkout the entire tree, including all child folders and sub-folders.
target: Preuzimanje celog stabla uključujući i potomačke imenike i podimenike.

note: (term)
en: Immediate children, including folders
target: Neposredni potomak,  uključujući imenike

note: (para)
en: Checkout the specified directory, including all files and child folders, but do not populate the child folders.
target: Preuzimanje specificiranog imenika, uključujući sve fajlove i potomačke imenike, ali ne naseljavati potomačke imenike.

note: (term)
en: Only file children
target: Samo fajlovi potomci

note: (para)
en: Checkout the specified directory, including all files but do not checkout any child folders.
target: Preuzimanje specificiranih imenika, uključujući sve fajlove ali ne preuzimati bilo koji potomački imenik.

note: (term)
en: Only this item
target: Samo ova stavka

note: (para)
en: Checkout the directory only. Do not populate it with files or child folders.
target: Preuzimanje samo imenika. Ne naseljavti ga fajlovima ili potomačkim imenicima.

note: (term) (listitem)
en: Working copy
target: Radna kopija

note: (para)
en: Retain the depth specified in the working copy. This option is not used in the checkout dialog, but it is the default in all other dialogs which have a depth setting.
target: Zadržati dubinu specificiranu u radnoj kopiji. Ova opcija se ne koristi u dijalogu preuzimanja, ali je uobičajena u svim ostalim dijalozima koji imahu podešavanje dubine.

note: (para)
en: You can choose the <firstterm>depth</firstterm> you want to checkout, which allows you to specify the depth of recursion into child folders. If you want just a few sections of a large tree, You can checkout the top level folder only, then update selected folders recursively. <placeholder-1/>
target: Možete izabrati <firstterm>dubinu</firstterm> koju želite pri pruzimanju, što vam omogućuje da specificirate dubinu rekurzije u potomačkim imenicima. Ako želite samo nekoliko delova velikog stabla, možete preuzeti samo imenik vršnog nivoa, zatim ažurirajte imenike rekurzivno. <placeholder-1/>

note: (title)
en: Exporting
target: Izvoz

note: (primary)
en: commit
target: ureži

note: (term)
en: Blue
target: Plavi

note: (primary)
en: update
target: ažuriraj

note: (term)
en: Green
target: Zelen

note: (primary)
en: resolve
target: reši

note: (title)
en: Check for Modifications
target: Provera izmena

note: (primary)
en: diffing
target: razlikovanje

note: (primary)
en: changelist
target: popis izmena

note: (primary)
en: log
target: dnevnik

note: (primary)
en: log messages
target: poruke dnevnika

note: (primary)
en: statistics
target: statistika

note: (primary)
en: diff
target: razl

note: (primary)
en: compare revisions
target: uporedi revizije

note: (primary)
en: TortoiseIDiff
target: TortozIDiff

note: (primary)
en: add
target: dodaj

note: (primary)
en: ignore
target: zanemari

note: (primary)
en: delete
target: briši

note: (primary)
en: remove
target: ukloni

note: (primary)
en: rename
target: preimenuj

note: (primary)
en: revert
target: vrati

note: (primary)
en: undo
target: poništi

note: (primary)
en: properties
target: osobine

note: (primary)
en: copy
target: kopiraj

note: (term) (listitem)
en: HEAD revision in the repository
target: GLAVNA revizija u spremištu

note: (term)
en: Specific revision in the repository
target: Određena revizija u spremištu

note: (primary)
en: switch
target: zamena

note: (title)
en: Merging
target: Spajanje

note: (primary)
en: merge
target: spoji

note: (term)
en: Merge a range of revisions
target: Spoji raspon revizija

note: (para)
en: This method covers the case when you have made one or more revisions to a branch (or to the trunk) and you want to port those changes across to a different branch.
target: Metoda se koristi u slučaju kad ste napravili jednu ili više revizija u grani (ili glavnoj grani) i želite preneti te izmene u neku drugu granu.

note: (term) (title)
en: Reintegrate a branch
target: Reintegriši granu

note: (term)
en: Merge two different trees
target: Spoji dva različita stabla

note: (secondary)
en: revision range
target: raspon revizija

note: (title)
en: Merge Options
target: Opcije spajanja

note: (primary)
en: merge reintegrate
target: spoji reintegriraj

note: (primary)
en: readonly
target: samo za čitanje

note: (primary)
en: unified diff
target: objedinjena razlika

note: (primary)
en: blame
target: okriviti

note: (title)
en: TortoiseBlame
target: TortozBlame

note: (term)
en: Blame Revisions
target: Krivac revizija

note: (term)
en: Blame Changes
target: Krivac promena

note: (term)
en: Compare and Blame with Working BASE
target: Uporedi sa radnom OSNOVOM i okrivi

note: (title)
en: The Repository Browser
target: Pretraživač spremišta

note: (primary)
en: repo-browser
target: repo-pretraživač

note: (primary)
en: revision graph
target: revizioni graf

note: (title)
en: A Revision Graph
target: Revizioni graf

note: (term)
en: Show HEAD revisions
target: Prikaži GLAVNE revizije

note: (term)
en: Fold tags
target: Skupi oznake

note: (term)
en: Reduce cross lines
target: Smanji presečne-linije

note: (primary)
en: export
target: izvoz

note: (primary)
en: unversion
target: neverzionisan

note: (primary)
en: relocate
target: premesti

note: (title)
en: TortoiseSVN's Settings
target: TortozSVN postavke

note: (primary)
en: settings
target: podešavanje

note: (term)
en: Language
target: Jezik

note: (term)
en: Automatically check for newer versions every week
target: Automatski proveri novije verzije jednom nedeljno

note: (term)
en: System sounds
target: Sistemski zvuci

note: (para)
en: Error
target: Greška

note: (para)
en: Notice
target: Beleška

note: (para)
en: Warning
target: Upozorenje

note: (term)
en: Global ignore pattern
target: Globalni uzorak izostavljanja

note: (term)
en: Subversion configuration file
target: Subverzijin konfiguracioni fajl

note: (term)
en: Default number of log messages
target: Uobičajen broj poruka dnevnika

note: (term)
en: Font for log messages
target: Pismo za poruke dnevnika

note: (term)
en: Short date / time format in log messages
target: Kratak oblik datum/vreme u dnevniku poruka

note: (term)
en: Recurse into unversioned folders
target: Rekurzija u neverzionisanim imenicima

note: (term)
en: Use auto-completion of file paths and keywords
target: Koristi autokompletiranje fajl putanja i ključnih reči

note: (term)
en: Timeout in seconds to stop the auto-completion parsing
target: Kašnjenje u skundama da se zaustavi analiziranje za autokompletiranje

note: (term)
en: Max. items to keep in the log message history
target: Maks. stavki za čuvanje u istoriji dnevnika poruka

note: (term)
en: Select items automatically
target: Odaberi stavke automatski

note: (term)
en: Contact the repository on startup
target: Kontaktiraj spremište pri pokretanja

note: (term)
en: Show Lock dialog before locking files
target: Prikaži dijalog zaključavanja pre zaključavanja fajlova

note: (term)
en: Possible or real conflict / obstructed
target: Moguć ili stvarni sukob / sprečen

note: (term)
en: Added files
target: Dodati fajlovi

note: (term)
en: Missing / deleted / replaced
target: Nedostaje / obrisano / zamenjeno

note: (term)
en: Merged
target: Spojeno

note: (term)
en: Modified / copied
target: Promenjeno / kopirano

note: (term)
en: Deleted node
target: Obrisani čvor

note: (term)
en: Added node
target: Dodat čvor

note: (term)
en: Renamed node
target: Preimenovani čvor

note: (term)
en: Replaced node
target: Zamenjen čvor

note: (term)
en: Default
target: Uobičajeno

note: (term)
en: Shell
target: Školjka

note: (term)
en: None
target: Ništa

note: (title)
en: Diff/Merge Advanced Settings
target: Razl/Spoji napredno podešavanje

note: (term)
en: URL history
target: URL istorija

note: (term)
en: Log messages (Input dialog)
target: Poruke dnevnika (Ulazni dijalog)

note: (term)
en: Log messages (Show log dialog)
target: Poruke dnevnika (Prikaži dijalog dnevnika)

note: (term)
en: Dialog sizes and positions
target: Dijalog veličina i pozicije

note: (term)
en: Authentication data
target: Autentifikacioni podatak

note: (term)
en: Action log
target: Dnevnik akcija

note: (title)
en: Log Caching
target: Keš dnevnika

note: (term)
en: Enable log caching
target: Omogući keš dnevnika

note: (title)
en: Log Cache Statistics
target: Statistika keša  dnevnika

note: (term)
en: Connection
target: Veza

note: (term)
en: Last update
target: Zadnje ažuriranje

note: (para)
en: The last time the cache content was changed.
target: Poslednji put kada je promenjen sadržaj keša

note: (term)
en: Last head update
target: Zadnje glavno ažuriranje

note: (term)
en: Authors
target: Autori

note: (term)
en: Paths
target: Putanje

note: (term)
en: Skip ranges
target: Preskoči raspone

note: (term)
en: Max revision
target: Maks. revizija

note: (term)
en: Revision count
target: Broj revizija

note: (term)
en: Colors
target: Boje

note: (term)
en: Font
target: Pismo

note: (entry) (title) (glossterm)
en: Switch
target: Zamena

note: (entry)
en: Description
target: Opis

note: (primary)
en: moving
target: premeštanje

note: (primary)
en: log message
target: poruka dnevnika

note: (primary)
en: version
target: verzija

note: (entry)
en: Value
target: Vrednost

note: (entry) (title) (glossterm)
en: Checkout
target: Preuzimanje

note: (entry) (title) (glossterm)
en: Update
target: Ažuriranje

note: (entry) (title) (glossterm)
en: Commit
target: Urezivanje

note: (entry) (title) (glossterm)
en: Add
target: Dodavanje

note: (entry) (title) (glossterm)
en: Revert
target: Vrati na staro

note: (entry) (glossterm)
en: Resolve
target: Reši

note: (entry) (title) (glossterm)
en: Export
target: Izvezi

note: (entry) (title)
en: Branch/Tag
target: Grana/znak

note: (entry) (title) (glossterm)
en: Merge
target: Spoji

note: (entry) (title) (glossterm)
en: Delete
target: Obriši

note: (entry) (title)
en: Rename
target: Preimenuj

note: (entry)
en: Update to revision
target: Ažuriraj prema reviziji

note: (entry) (title) (glossterm)
en: Diff
target: Razl

note: (entry) (title)
en: Show Log
target: Prikaži dnevnik

note: (entry) (title)
en: Edit Conflicts
target: Uredi sukob

note: (entry) (title) (glossterm)
en: Relocate
target: Premesti

note: (entry)
en: Check for modifications
target: Provera izmena

note: (entry)
en: Ignore
target: Zanemari

note: (entry)
en: Repository Browser
target: Pretraživač spremišta

note: (entry) (title) (glossterm)
en: Blame
target: Krivac

note: (entry) (title)
en: Create Patch
target: Izradi zakrpu

note: (entry) (title)
en: Apply Patch
target: Primena zakrpa

note: (entry)
en: Revision graph
target: Revizioni graf

note: (entry) (glossterm)
en: Lock
target: Zaključavanje

note: (entry)
en: Properties
target: Osobine

note: (entry)
en: Diff with URL
target: Razl sa  URL

note: (entry)
en: Delete unversioned items
target: Obriši neverzionisane stavke

note: (entry)
en: Settings
target: Postavke

note: (entry)
en: Help
target: Pomoć

note: (primary)
en: command line
target: komandna linija

note: (entry)
en: Command
target: Komanda

note: (option)
en: /path
target: /putanja

note: (option)
en: path
target: putanja

note: (option)
en: /blame
target: /krivac

note: (title)
en: Update to Revision
target: Ažuriraj prema reviziji...

note: (title)
en: Revision Graph
target: Revizioni graf

note: (title)
en: Repo Browser
target: Repo-pretraživač

note: (title)
en: Resolved
target: Rešeno

note: (listitem)
en: Specific revision in repository
target: Određena revizija u spremištu

note: (title)
en: Add to Ignore List
target: Dodaj u listu za zanemarivanje

note: (glossterm)
en: Copy
target: Kopiraj

note: (glossterm)
en: HEAD revision
target: GLAVNA Revizija

note: (glossterm)
en: Log
target: Dnevnik

note: (glossterm)
en: Property
target: Svojstvo

note: (glossterm)
en: Repository
target: Spremište

note: (glossterm)
en: Revision
target: Revizija

note: (glossterm)
en: Working Copy
target: Radna kopija
