TortoiseSVN Documentation - en to unknown language translation catalogue (2216 entries)

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: (title)
en: Preface
target: Predgovor

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 jedno od ovih  pitanja,TortoiseSVN je za vas! Nastavite sa čitanjem da bi ste našli kako vam TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN, š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 TortoiseSVN. 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN komandi i njihovih ekvivalenata u Subverzija klijenta komandne linije <literal>svn.exe</literal>.

note: (title)
en: TortoiseSVN is free!
target: TortoiseSVN 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: TortoiseSVN 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 read 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>. You will be prompted to enter username and password. The username is <literal>guest</literal>, and the password must be left blank. The most recent version (where we're currently working) is located under <filename>/trunk/</filename>, and the released versions are located under <filename>/tags/</filename>.
target: TortoiseSVN 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>. Bićete pitani da unesete korisnika i lozinku. Korisnik<literal>guest</literal>, a lozinka mora ostati prazna. 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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>TortoiseSVN</guimenu><guimenuitem>Dnevnik prikaza</guimenuitem></menuchoice> means: selekt <emphasis>Dnevniik prikaza</emphasis>iz <emphasis>TortoiseSVN</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 TortoiseSVN 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 TortoiseSVN?

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: TortoiseSVN je beplatan klijent otvorenog koda za <firstterm>Subverzioni</firstterm> sistem kontrole verzija. Dakle, TortoiseSVN 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: TortoiseSVN 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 TortoiseCVS.

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 TortoiseCVS i iskoristio ga kao osnovu za TortoiseSVN. 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 TortoiseSVN. Pošto TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN. On vodi brigu o vebsajtu i upravlja prevodima.

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

note: (para)
en: What makes TortoiseSVN such a good Subversion client? Here's a short list of features.
target: Šta čini TortoiseSVN 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: TortoiseSVN 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. TortoiseSVNov 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 TortoiseSVN 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. TortoiseSVN 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 TortoiseSVN 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 prati 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 TortoiseSVN

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: TortoiseSVN radi na  Windows 2000 SO2,  Windows XP  ili viši, Windows ME i Windows NT4 više nisu podržani od TortoiseSVN 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 TortoiseSVN 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: TortoiseSVN 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 TortoiseSVN.

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: TortoiseSVN 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: TortoiseSVN uključuje kontrolu pravopisa koja vam dozvoljava da kontrolišete vaše  dnevnik poruka 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 TortoiseSVN jezičkih paketa. To će instalirati odgovarajuće fajlove rečnika kao i TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN, 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. TortoiseSVN 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-Deljenja

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: Kako izbeći problem

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 uređuju 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-Stopi 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-stopi</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>stopi</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-Stopi 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 stopi 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 stopljen 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-stopi 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 stopive 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-stopi 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 nestopive 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 stopi 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-stopi' 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 TortoiseSVN (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.5/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.5/svn.serverconfig.html"><citetitle>Server konfiguracija</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>binarieš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> Ovo konfiguriše Apaš tako da Subverzijino spremište je fizički locirano pod  <filename>D:\SVN</filename>. Spremišta za ostali svet opslužuje  URL: <systemitem class="url"> http://MyServer/svn/</systemitem>. Pristup je ograničen na poznavanje korisnik /lozinka dato u  <filename>passwd</filename> fajlu.

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 TortoiseSVN. 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> to <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>SVNParentPath</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>. (<xref linkend="tsvn-preface-source"/> explains how to access the TortoiseSVN source repository).
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>. (<xref linkend="tsvn-preface-source"/> objašnjava kako pristupiti TortoiseSVN spremištu izvora).

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 TortoiseSVN 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 TortoiseSVN  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 TortoiseSVN 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> also you need to add <screen>
    SSPIAuth On
    SSPIAuthoritative On
    SSPIDomain &lt;domaincontroller&gt;
    SSPIOmitDomain on
    SSPIUsernameCase lower
    SSPIPerRequestAuth on
    SSPIOfferBasic On
    </screen> sa <literal>&lt;Location /svn&gt;</literal> blok.  Ako nemate kontrolor domena, ostavite ime kontrole domena kao<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> Ove komande su kreirale neke fajlove u Apaš <filename>konf</filename> imenik (<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 TortoiseSVN 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_ssp</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 TortoiseSVN 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> - kopirajte ove falove, ili samo kopirajte sve iz <filename>bin</filename> imenika, u imenik na vašem serveru npr. <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>TortoiseSVN</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> 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>  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> 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>

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 "LOKALNI SERVIS".

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 TortoiseSVN 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> 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> 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.5/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.5/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 TortoiseSVN 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.5/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.5/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache"><citetitle>Klient Kredencials Kešing</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 TortoiseSVN 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/en/1.5/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/en/1.5/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 TortoiseSVN.

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.5/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.5/svn.reposadmin.planning.html#svn.reposadmin.basics.backends"><citetitle>Izbor smeštanja podataka</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> and type <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 TortoiseSVN

note: (title)
en: The TortoiseSVN menu for unversioned folders
target: TortoiseSVN 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>TortoiseSVN</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: TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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/repoš</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: (screen)
en: 
    /trunk/paint
    /trunk/calc
    /branches/paint
    /branches/calc
    /tags/paint
    /tags/calc
target: 
    /trunk/paint
    /trunk/calc
    /branchešpaint
    /branchešcalc
    /tagšpaint
    /tagšcalc

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

note: (screen)
en: 
    /paint/trunk
    /paint/branches
    /paint/tags
    /calc/trunk
    /calc/branches
    /calc/tags
target: 
    /paint/trunk
    /paint/branches
    /paint/tags
    /calčtrunk
    /calčbranches
    /calčtags

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 ođednom, 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 TortoiseSVN 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 TortoiseSVN 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>TortoiseSVN</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: (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.5/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.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks"><citetitle>Zakačive skripte</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. TortoiseSVN 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 Unikš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: TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN on registruje novi <literal>tsvn:</literal> protokol. Kada TortoiseSVN 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>TortoiseSVN logo</citetitle></ulink> ili možete nabaviti svoju sopstvenu sliku. <placeholder-1/>

note: (para)
en: You can also make the link point to a specific revision, for example <placeholder-1/>
target: Takođe možete napraviti vezu ka specijalnoj reviziji, na primer <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 TortoiseSVN. 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 TortoiseSVN 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 TortoiseSVN u svoje slobodno vreme.

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

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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN. 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 TortoiseSVN 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 TortoiseSVN 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 TortoiseSVN. 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 TortoiseSVN 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>TortoiseSVN</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> TortoiseSVN 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>TortoiseSVN</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 TortoiseSVN 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 TortoiseSVN 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>TortoiseSVN</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: (para)
en: If you check out a sparse working copy (i.e., by choosing something other than <literal>fully recursive</literal> for the checkout depth), you can fetch additional sub-folders by using the repository browser (<xref linkend="tsvn-dug-repobrowser"/>) or the check for modifications dialog (<xref linkend="tsvn-dug-wcstatus-2"/>).
target: Ako preuzmete praznu radnu kopiju (tj. izborom nečeg drgog nego <literal>potpuno rekurzivno</literal> za dubinu preuzimanja), možete dostići dodatne subimenike koristeći pretraživač spremišta (<xref linkend="tsvn-dug-repobrowser"/> ili dijalog za proveru izmena (<xref linkend="tsvn-dug-wcstatus-2"/>).

note: (para)
en: In the repository browser, <action>Right click</action> on the checked out folder, then use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Repo-Browser</guimenuitem></menuchoice> to bring up the repository browser. Find the sub-folder you would like to add to your working copy, then use <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Update item to revision...</guimenuitem></menuchoice> That menu will only be visible if the selected item does not exist yet in your working copy, but the parent item does exist.
target: U pretraživaču spremišta, <action>Desni klik</action> na preuzeti imenik, zatim koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Repo-Pretrživač</guimenuitem></menuchoice> da pozovete pretraživač spremišta. Nađite subimenik koji želite da dodate vašoj radnoj kopiji, zatim koristite <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem> Ažuriraj stavku po reviziji...</guimenuitem></menuchoice>Taj meni biće vidljiv samo ako izabrana stavka još ne postoji u vašoj radnoj kopiji, ali predačka stavka postoji.

note: (para)
en: In the check for modifications dialog, first click on the button <guibutton>Check repository</guibutton>. The dialog will show all the files and folders which are in the repository but which you have not checked out as <literal>remotely added</literal>. <action>Right click</action> on the folder(s) you would like to add to your working copy, then use <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Update</guimenuitem></menuchoice>.
target: U dijalogu porovere modifikacija, najpre kliknite na dugme <guibutton>Proveri spremište</guibutton>. Dijalog će pokazati sve fajlove i imenike koji su u spremištu ali ih nisu preuzeti kao <literal>daljinski dodati</literal>. <action>Desni klik</action>na imenik(e) koje želite dodati vašoj radnoj kopiji, zatim koristite <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Ažuriraj</guimenuitem></menuchoice>.

note: (para)
en: This feature is very useful when you only want to checkout parts of a large tree, but you want the convenience of updating a single working copy. Suppose you have a large tree which has sub-folders <literal>Project01</literal> to <literal>Project99</literal>, and you only want to checkout <literal>Project03</literal>, <literal>Project25</literal> and <literal>Project76/SubProj</literal>. Use these steps:
target: Ova osobina je veoma korisna kada samo želite da preuzmete dao velikog stabla, ali želite konvenciju ažuriranja pojedinačne radne kopije. Pretpostavimo da imate veliko stablo koje ima sub-imenike <literal>Project01</literal> do <literal>Project99</literal>, i želite da preuzmete <literal>Project03</literal>, <literal>Project25</literal> i <literal>Project76/SubProj</literal>. Koristite ove korake:

note: (para)
en: Checkout the parent folder with depth <quote>Only this item</quote> You now have an empty top level folder.
target: Preuzmite predački imenik sa dubinom <quote>Samo ova stavka</quote> Sada imate prazan vršni imenik.

note: (para)
en: Select the new folder and use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Repo browser</guimenuitem></menuchoice> to display the repository content.
target: Izaberite novi imenik i koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Repo pretraživač</guimenuitem></menuchoice> da prikažete sadržaj spremišta.

note: (para)
en: Right click on <literal>Project03</literal> and <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Update item to revision...</guimenuitem></menuchoice>. Keep the default settings and click on <guibutton>OK</guibutton>. You now have that folder fully populated.
target: Desni klik na <literal>Project03</literal>i <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Ažuriraj stavku do revizije...</guimenuitem></menuchoice>.Čuvajte uobičajeno podešavanje i kliknite na <guibutton>OK</guibutton>. Vi sada imate imenik potpuno popunjen.

note: (para)
en: Repeat the same process for <literal>Project25</literal>.
target: Ponovite isti proces za <literal>Project25</literal>.

note: (para)
en: Navigate to <literal>Project76/SubProj</literal> and do the same. This time note that the <literal>Project76</literal> folder has no content except for <literal>SubProj</literal>, which itself is fully populated. Subversion has created the intermediate folders for you without populating them.
target: Upravite se ka <literal>Project76/SubProj</literal> i uradite isto. Ovog puta primetimo da <literal>Project76</literal> imenik nema sadržaj osim za <literal>SubProj</literal>, koji je sam potpuno poppunjen. Subverzija je kreirala prelazne imenike za vas ne popunjavajući ih.

note: (title)
en: Working copy depth cannot be reduced
target: Dubina radne kopije ne može da se umanji

note: (para)
en: Once you have checked out a working copy to a particular depth you can increase that depth later to get more content. However you cannot reduce the depth again to remove content. That feature may be added in a later version of Subversion.
target: Kada jednom preuzmete radnu kopiju do određene dubine možete povećati dubinu kasnije da dođete do više sadržaja.  međutim ne možete redukovati dubinu da izbacite sadržaj.  Ova osobina će biti dodata u kasnijim verzijama Subverzije.

note: (title)
en: Using an older server
target: Korišćenje starijeg servera

note: (para)
en: Pre-1.5 servers do not understand the working copy depth request, so they cannot always deal with requests efficiently. The command will still work, but an older server may send all the data, leaving the client to filter out what is not required, which may mean a lot of network traffic. If possible you should upgrade your server to 1.5.
target: Pre-1.5 serveri ne razumeju zahtev za dubinom radne kopije, tako da oni uopšte ne mogu da rade efikasno sa tim zahtevima. Komanda će još raditi ali stari server može slati sve podatekeostavljajući klojentu da filtrira ono što nije potrebno, što može biti veći deo mrežnog saobraćaja. Ako je moguće treba da dogradite server na 1.5.

note: (para)
en: If the project contains references to external projects which you do <emphasis>not</emphasis> want checked out at the same time, use the <guilabel>Omit externals</guilabel> checkbox.
target: Ako projekat sadrži reference ka eksternim projektima koje <emphasis>ne</emphasis> želite da preuzmete u isto vreme, koristite <guilabel>Izostaviti eksterne</guilabel> čekboks.

note: (para)
en: If <guilabel>Omit externals</guilabel> is checked, or if you wish to increase the depth value, you will have to perform updates to your working copy using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Update to Revision...</guimenuitem></menuchoice> instead of <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Update</guimenuitem></menuchoice>. The standard update will include all externals and keep the existing depth.
target: Ako <guilabel>Izostaviti eksterne</guilabel> je označeno, ili ako želite da povećate vrednost dubine, imaćete da uradite ažuriranje vaše radne kopije koristeći <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ažuriraj do Revizije...</guimenuitem></menuchoice> umesto <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ažuriraj</guimenuitem></menuchoice>.

note: (para)
en: It is recommended that you check out only the <literal>trunk</literal> part of the directory tree, or lower. If you specify the parent path of the directory tree in the URL then you might end up with a full hard disk since you will get a copy of the entire repository tree including every branch and tag of your project!
target: Preporučuje se da preuzmete samo samo <literal>trunk</literal>  deo stabla imenika, ili niže. Ako odredite predačku putanju stabla imenika u URL tada možete završiti sa punim hard diskom jer dobijate kopiju celog stabla spremišta uključujući svaku granu i znak vašeg projekta!

note: (title)
en: Exporting
target: Izvoz

note: (para)
en: Sometimes you may want to create a local copy without any of those <filename>.svn</filename> directories, e.g. to create a zipped tarball of your source. Read <xref linkend="tsvn-dug-export"/> to find out how to do that.
target: Ponekad možete želeti da napravite lokalnu kopiju bez bilo kakvog <filename>.svn</filename> imenika, tj. da napravite komprimovanu datoteku sorsa. Pročitajte <xref linkend="tsvn-dug-export"/> da nađete kako da to uradite.

note: (title)
en: Committing Your Changes To The Repository
target: Urezivanje vaših izmena u spremište

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

note: (primary)
en: send changes
target: slanje izmena

note: (primary)
en: check in
target: prijavljivanje

note: (para)
en: Sending the changes you made to your working copy is known as <firstterm>committing</firstterm> the changes. But before you commit you have to make sure that your working copy is up to date. You can either use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Update</guimenuitem></menuchoice> directly. Or you can use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Check for Modifications</guimenuitem></menuchoice> first, to see which files have changed locally or on the server.
target: Slanjem izmena koje ste uradili u vašu radnu kopiju poznato je kao <firstterm>urezivanje</firstterm> izmena. Ali pre nego što urezujete treba da budete sigurni da je radna kopija ažurirana. Možete ili koristiti <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ažuriraj</guimenuitem></menuchoice> direktno. Ili možete koristiti <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Provera Izmena</guimenuitem></menuchoice> najpre, da vidite koji su fajlovi izmenjeni lokalno ili na serveru.

note: (title)
en: The Commit Dialog
target: Urezivanje dijalog

note: (title)
en: The Commit dialog
target: rezivanje dijalog

note: (para)
en: If your working copy is up to date and there are no conflicts, you are ready to commit your changes. Select any file and/or folders you want to commit, then <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Commit...</guimenuitem></menuchoice>. <placeholder-1/>
target: Ako je vaša radna kopija ažurirana i nema konflikta, vi ste spremni da urežete vaše izmene. Izaberite bilo koji fajl/ili imenike koje želiti da urežete, tada <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ureži...</guimenuitem></menuchoice>. <placeholder-1/>

note: (para)
en: The commit dialog will show you every changed file, including added, deleted and unversioned files. If you don't want a changed file to be committed, just uncheck that file. If you want to include an unversioned file, just check that file to add it to the commit.
target: Dijalog urezivanja će vam pokazati svaki izmnjeni fajl, uključujući dodate, neverzionisane fajlove. Ako ne želite da izmenjeni fajlovi budu urezani, samo otčekirjte te fajlove. Ako želite da uključite neverzionisani fajl, samo čekirajte taj fajl da ga dodate u urezivanje.

note: (para)
en: Items which have been switched to a different repository path are also indicated using an <literal>(s)</literal> marker. You may have switched something while working on a branch and forgotten to switch back to trunk. This is your warning sign!
target: Stavke koje su prebačene u različite putanje spremišta takođe su označene korišćenjem <literal>(s)</literal> markera. Možete prebaciti nešto dok radite na grani i da to zaboravite da vratite u deblo. Ovo je vaš upozoravajući znak!

note: (title)
en: Commit files or folders?
target: Urezivanje fajlova ili imenika?

note: (para)
en: When you commit files, the commit dialog shows only the files you have selected. When you commit a folder the commit dialog will select the changed files automatically. If you forget about a new file you created, committing the folder will find it anyway. Committing a folder does <emphasis>not</emphasis> mean that every file gets marked as changed; It just makes your life easier by doing more work for you.
target: Kada urezujete fajlove, dijalog urezivanja prikazuje samo fajlove koje ste izabrali. kada urezujete imenik dijalog urezivanja će izabrati izmenjene fajlove automatski. Ako zaboravite novi fajl koji ste kreirali, urezivanje imenika će ga naći u svakom slučaju. Urezivanje imenika <emphasis>ne</emphasis> znači da je svaki fajl označen kao izabran; To samo čini vaš život lakšim radeći više posla za vas.

note: (para)
en: If you have modified files which have been included from a different repository using <literal>svn:externals</literal>, those changes cannot be included in the same atomic commit. A warning symbol below the file list tells you if this has happened, and the tooltip explains that those external files have to be committed separately.
target: Ako imate izmnjene fajlove koji su uključeni iz raznih spremišta korišćenjem <literal>svn:externals</literal>, ove izmene ne mogu biti uključene u istom atomik urezivanju. Simbol upozorenja ispod liste fajlova kaže vam ako se to desilo, i alatoznaka objašnjava da se ti eksterni fajlovi imaju urezati odvojeno.

note: (title)
en: Many unversioned files in the commit dialog
target: Mnogo neverzionisanih fahlova u dialogu urezivanja

note: (para)
en: add the file (or a wildcard extension) to the list of files to exclude on the settings page. This will affect every working copy you have.
target: dodajte fajl (ili vilkard proširenje) listi fajlova za isključenje na stranici podešavanja. Ovo će uticati na svaku radnu kopiju koju imate.

note: (para)
en: add the file to the <literal>svn:ignore</literal> list using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Add to ignore list</guimenuitem></menuchoice> This will only affect the directory on which you set the <literal>svn:ignore</literal> property. Using the SVN Property Dialog, you can alter the <literal>svn:ignore</literal> property for a directory.
target: dodajte fajl u <literal>svn:ignore</literal> listu koristeći <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Dodajte listi izbegavanja</guimenuitem></menuchoice> Ovo će uticati samo na imenik na koji ste podesili <literal>svn:ignore</literal>. Koristeći SVN Dijalog Osobina, možete zameniti <literal>svn:ignore</literal> osobine imenika.

note: (para)
en: If you think that the commit dialog shows you too many unversioned (e.g. compiler generated or editor backup) files, there are several ways to handle this. You can: <placeholder-1/> Read <xref linkend="tsvn-dug-ignore"/> for more information.
target: Ako mislite da dijalog urezivanja prikazuje suviše mnogo neverzionisanih (tj. koje generiše kompajler ili osiguanje uređivača) fajlova, postoji više načina da se to opsluži. Možete: <placeholder-1/>  Pročitajte <xref linkend="tsvn-dug-ignore"/> za više informacija.

note: (para)
en: <action>Double clicking</action> on any modified file in the commit dialog will launch the external diff tool to show your changes. The context menu will give you more options, as shown in the screenshot. You can also drag files from here into another application such as a text editor or an IDE.
target: <action>Dvostruku klik</action> na bilo koji izmenjen fajl u dijalogu urezivanja lansiraće spoljašnji diff alat da prikaže vaše izmene. Kontekst meni će vam dati više mogućnosti, kao što je prikazano na snimku. Takođe možete vući fajlove odavde u drugu aplikaciju kao što je uređivač teksta ili IDE .

note: (para)
en: You can select or deselect items by clicking on the checkbox to the left of the item. For directories you can use <keycap>Shift</keycap>-<action>select</action> to make the action recursive.
target: Možete poništiti izbor stavki klikom na čekbokslevo od stavke. Za imenike možete koristiti <keycap>Šift</keycap>-<action>select</action> da učinite akciju rekurzivno.

note: (para)
en: The columns displayed in the bottom pane are customizable. If you <action>right click</action> on any column header you will see a context menu allowing you to select which columns are displayed. You can also change column width by using the drag handle which appears when you move the mouse over a column boundary. These customizations are preserved, so you will see the same headings next time.
target: Kolone prikazane u donjem panelu su prilagodljive. Ako uradite <action>desni klik</action> na bilo koje zaglavlje kolone videćete kontekst meni koji vam dozvoljava da izaberete koja kolona će se prikazati. Možete i izmeniti širinu kolone koristeći vučnu traku koja se pojavljuje kada pomerate miša preko ivice kolone. Prilagođenja su sačuvana tako da možete videti ista zaglavlja sledeći put.

note: (para)
en: By default when you commit changes, any locks that you hold on files are released automatically after the commit succeeds. If you want to keep those locks, make sure the <guilabel>Keep locks</guilabel> checkbox is checked. The default state of this checkbox is taken from the <literal>no_unlock</literal> option in the Subversion configuration file. Read <xref linkend="tsvn-dug-settings-main"/> for information on how to edit the Subversion configuration file.
target: Uobičajeno je da kada se urezuju izmene, svako zaključavanje koje držite na fajlovima se automatski otključava posle zadovoljavajućeg urezivanja. Ako želite da zadržite zaključavanje budite sigurni da je <guilabel>Čuvaj zaključavanje</guilabel> čekboks je čekiran. Uobičajeno stanje ovog čekboksa uzet je iz <literal>no_unlock</literal> opcije u Subverzionom konfiguracionom fajlu. Pročitajte <xref linkend="tsvn-dug-settings-main"/> za informacije kako urediti Subverzioni konfiguracioni fajl.

note: (para)
en: You can drag files into the commit dialog from elsewhere, so long as the working copies are checked out from the same repository. For example, you may have a huge working copy with several explorer windows open to look at distant folders of the hierarchy. If you want to avoid committing from the top level folder (with a lengthy folder crawl to check for changes) you can open the commit dialog for one folder and drag in items from the other windows to include within the same atomic commit.
target: Možete dovući fajlove u dijalog urezivanja od bilo gde, sve dok vaša radna kopija je preuzeta iz istog spremišta. Na primer, možete imati ogromnu radnu kopiju sa više eksplorer prozora otvorenih na raznim imenicima hijerarhije. Ako želite da izbegnete urezivanje sa vršnog imenika (sa dužim puzačem imenika za proveru izmena) možete otvoriti dijalog urezivanja za jedan imenik i vući stavku iz drugog prozora da se uključi u okviru istog atomik urezivanja.

note: (para)
en: You can drag unversioned files which reside within a working copy into the commit dialog, and they will be SVN added automatically.
target: Možete vu-i neverzionisane fajlove obitavaju u okviru radne kopije u dijalogu urezivanja, i oni će biti SVN dodati automatski.

note: (title)
en: Repairing External Renames
target: Popravka spoljašnjih preimenovanja

note: (para)
en: Sometimes files get renamed outside of Subversion, and they show up in the file list as a missing file and an unversioned file. To avoid losing the history you need to notify Subversion about the connection. Simply select both the old name (missing) and the new name (unversioned) and use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Repair Move</guimenuitem></menuchoice> to pair the two files as a rename.
target: Ponekad se fajlovi preimenuju van Subverzije, i oni su prikazani u listi fajlova kao fajl koji nedostaje ili neverzionisani fajl. Da bi izbegli gubljenje istorije potrebno je  notirati Subverziji o vezi. Jednostavno izaberite obe stavri, staro ime (nedostajuće) i novo ime (neverzionisano)  koristi <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Popravi Pomeranje</guimenuitem></menuchoice> da se upare dva fajla kao preimenovanje.

note: (title)
en: Change Lists
target: Liste izmena

note: (para)
en: The commit dialog supports Subversion's changelist feature to help with grouping related files together. Find out about this feature in <xref linkend="tsvn-dug-changelists"/>.
target: Dijalog urezivanja podržava Subverzijinu listu izmena  osobine da pomogne grupisanjem odgovarjućih fajlova zajedno. Nađite o ovim osobinama na <xref linkend="tsvn-dug-changelists"/>.

note: (title)
en: Excluding Items from the Commit List
target: Isključivanje stavki iz liste za urezivanje

note: (para)
en: Sometimes you have versioned files that change frequently but that you really don't want to commit. Sometimes this indicates a flaw in your build process - why are those files versioned? should you be using template files? But occasionally it is inevitable. A classic reason is that your IDE changes a timestamp in the project file every time you build. The project file has to be versioned as it includes all the build settings, but it doesn't need to be committed just because the timestamp changed.
target: Ponekad imate verzionisane fajlove koji se često menjaju koji vi zaista ne želite urezati. Ponekad ovo ukazuje na protok u vašem procesu gradnje - zašto su ti fajlovi verzionisani? da li biste trebali koristiti model fajlove? Ali srećom to je neizbežno. Klasičan rezon je da vaš IDE menja vremenske markere u projekt fajlu svaki put kad gradite. Fajl projekta treba da bude verzionisan je uključuje sva podešavanja za gradnju, ali on ne treba da bude urezan baš zbog toga što su vremenski markeri promenjeni.

note: (para)
en: To help out in awkward cases like this, we have reserved a changelist called <literal>ignore-on-commit</literal>. Any file added to this changelist will automatically be unchecked in the commit dialog. You can still commit changes, but you have to select it manually in the commit dialog.
target: Da bi se pomoglo u uznemiravajućim situacijama kao što je ova, imamo rezervisanu listu izmena nazvanu <literal>ignore-on-commit</literal>. Bilo koji fajl dodat ovoj listi izmena biće automatski otčekiran u dijalogu urezivanja.Još uvek možete urezati izmene, ali imate da izaberete ručno u dijalogu urezivanja.

note: (title)
en: Commit Log Messages
target: Urezivanje dnevnika poruka

note: (para)
en: Be sure to enter a log message which describes the changes you are committing. This will help you to see what happened and when, as you browse through the project log messages at a later date. The message can be as long or as brief as you like; many projects have guidelines for what should be included, the language to use, and sometimes even a strict format.
target: Budite sigurni da unesete dnevnik poruka koji opisuje izmene koje urezujete. Ovo će vam pomoći da vidite šta se dešava  i kada, ako pretražite projektov dnevnik poruka kasnije. Poruka može biti toliko duga ili kratka koliko želite; mnogi projekti imaju uvodne linije o tome šta treba uključiti, jezik koji koristiti, ponekad i strogi format.

note: (para)
en: You can apply simple formatting to your log messages using a convention similar to that used within emails. To apply styling to <literal>text</literal>, use <literal>*text*</literal> for bold, <literal>_text_</literal> for underlining, and <literal>^text^</literal> for italics.
target: Možete primeniti jednostavno formatiranje dnevnika poruka koristeći konvenciju sličnu onoj koja se koristi u okviru elektronske pošte. Da bi se primenilo stilisanje <literal>teksta</literal>, koristite <literal>*tekst*</literal> za masna slova, <literal>_tekst_</literal> za podv učeno, i <literal>^tekst^</literal> za italik.

note: (title)
en: The Commit Dialog Spellchecker
target: Provera pravopisa dijaloga urezivanja

note: (para)
en: <placeholder-1/> TortoiseSVN includes a spellchecker to help you get your log messages right. This will highlight any mis-spelled words. Use the context menu to access the suggested corrections. Of course, it doesn't know <emphasis>every</emphasis> technical term that you do, so correctly spelt words will sometimes show up as errors. But don't worry. You can just add them to your personal dictionary using the context menu.
target: <placeholder-1/> TortoiseSVN uključuje proveru pravopisa da vam pomogne da dobijete ispravan dnevnik poruka. On će osvetliti sve loše-napisane reči. Koristite kontekst meni da pristupite sugerisanim korekcijama. Svakako, on ne zna <emphasis>svaki</emphasis> tehnički termin koji date, tako da  korektno napisane reči ponekad prikazuje kao sa greškom. Ali ne brinite. Treba samo da ih dodate u vaš lični rečnik koristeći kontekst meni.

note: (para)
en: The log message window also includes a filename and function auto-completion facility. This uses regular expressions to extract class and function names from the (text) files you are committing, as well as the filenames themselves. If a word you are typing matches anything in the list (after you have typed at least 3 characters, or pressed <keycap>Ctrl+Space</keycap>), a drop-down appears allowing you to select the full name. The regular expressions supplied with TortoiseSVN are held in the TortoiseSVN installation <filename>bin</filename> folder. You can also define your own regexes and store them in <filename>%APPDATA%\TortoiseSVN\autolist.txt</filename>. Of course your private autolist will not be overwritten when you update your installation of TortoiseSVN. If you are unfamiliar with regular expressions, take a look at the introduction at <ulink url="http://en.wikipedia.org/wiki/Regular_expression"><citetitle>http://en.wikipedia.org/wiki/Regular_expression</citetitle></ulink>, and the online documentation and tutorial at <ulink url="http://www.regular-expressions.info/"><citetitle>http://www.regular-expressions.info/</citetitle></ulink>.
target: Prozor dnevnika poruka takođe obuhvata fajlime i funkciju lakog autokompletiranja. To koristi regularne izraze da izdvoji klase i imena funkcija iz (tekst) fajlova koje urezujete, kao i sama fajlimena. Ako reč koju kucate hvata bil šta na listi (posle kucanja najmanje 3 karaktera, ili pritiskom na <keycap>Ctrl-Razmak</keycap>), javlja se padajući meni koji vam dozvoljava da izaberete puno ime. Regularni izrazi su obezbeđeni iz TortoiseSVN su sadržani u TortoiseSVN instalacionom <filename>bin</filename> imeniku. Možete takođe definisati regularne izraze i sačuvati ih u <filename>%APPDATA%\TortoiseSVN\autolist.txt</filename>.Svakako , vaša privatna autolista neće biti prepisana kada ažurirate vašu instalaciju TortoiseSVN. Ako niste familijarni sa regularnim izrazima, bacite pogled na uvod u <ulink url="http://en.wikipedia.org/wiki/Regular_expression"><citetitle>http://en.wikipedia.org/wiki/Regular_expression</citetitle></ulink>, i onlajn dokumentaciju i tutorijale na <ulink url="http://www.regular-expressions.info/"><citetitle>http://www.regular-expressions.info/</citetitle></ulink>.

note: (para)
en: You can re-use previously entered log messages. Just click on <guibutton>Recent messages</guibutton> to view a list of the last few messages you entered for this working copy. The number of stored messages can be customized in the TortoiseSVN settings dialog.
target: Možete ponovo koristiti prethodno unete poruke dnevnika. Samo kliknite na <guibutton>Skore poruke</guibutton> da vidite listu zadnjih nekoliko poruka koje ste uneli za ovu radnu kopiju. Broj sačuvanih poruka može biti podešen u TortoiseSVN dijalogu podešavanja.

note: (para)
en: You can clear all stored commit messages from the <guilabel>Saved data</guilabel> page of TortoiseSVN's settings, or you can clear individual messages from within the <guilabel>Recent messages</guilabel> dialog using the <keycap>Delete</keycap> key.
target: Možete obrisati sve sačuvane poruke od <guilabel>Sačuvani podaci</guilabel> strane TortoiseSVN podešavanja, ili možete obrisati pojedine poruke u okviru dijaloga <guilabel>Nedavne poruke</guilabel> koristeći <keycap>Briši</keycap> taster.

note: (title)
en: Special Folder Properties
target: Specijalni imenik osobina

note: (para)
en: There are several special folder properties which can be used to help give more control over the formatting of commit log messages and the language used by the spellchecker module. Read <xref linkend="tsvn-dug-propertypage"/> for further information.
target: Ima nekoliko specijalnih osobina imenika koje mogu biti korišćene da pomognu davanje više kontrole preko formatiranja dnevnika poruka i jezik korišćen modulom za proveru pravopisa. Čitajte <xref linkend="tsvn-dug-propertypage"/> za dalje informacije.

note: (title)
en: Integration with Bug Tracking Tools
target: Integracija sa alatom za praćenje bagova

note: (para)
en: If you have activated the bug tracking system, you can set one or more Issues in the <guilabel>Bug-ID / Issue-Nr:</guilabel> text box. Multiple issues should be comma separated. Alternatively, if you are using regex-based bug tracking support, just add your issue references as part of the log message. Learn more in <xref linkend="tsvn-dug-bugtracker"/>.
target: Ako ste aktivirali sistem praćenja bagova, možete podesiti jedan ili više Problema u <guilabel>Bug-ID / Issue-Nr:</guilabel> tekst boksu. Višestruki problemi treba da budu odvojeni zarezom.Alternativno, ako koristite regeks-zasnovana podrška tragača bagova, samo dodajte vaš problem reference kao deo dnevnika poruka. Pročitajte više u <xref linkend="tsvn-dug-bugtracker"/>.

note: (title)
en: Commit Progress
target: Napredovanje urezivanja

note: (title)
en: The Progress dialog showing a commit in progress
target: Progres dijalog koji prikazije napredovanje urezivanja

note: (para)
en: After pressing <guibutton>OK</guibutton>, a dialog appears displaying the progress of the commit. <placeholder-1/>
target: Posle pritiskanja <guibutton>OK</guibutton>, pojavljuje se dijalog koji prikazuje napredovanje urezivanja. <placeholder-1/>

note: (term)
en: Blue
target: Plavi

note: (para)
en: Committing a modification.
target: Urezivanje izmene.

note: (term)
en: Purple
target: Purpuran

note: (para)
en: Committing a new addition.
target: Urezivanje novih dodavanja

note: (term)
en: Dark red
target: Tamno crven

note: (para)
en: Committing a deletion or a replacement.
target: Urezivanje brisanja ili zamena

note: (term)
en: Black
target: Crn

note: (para)
en: All other items.
target: Sve druge stavke

note: (para)
en: The progress dialog uses colour coding to highlight different commit actions <placeholder-1/>
target: Progres dijalogkoristi kodiranje bojama da osvetli različite akcije urezivanja <placeholder-1/>

note: (para)
en: This is the default colour scheme, but you can customise those colours using the settings dialog. Read <xref linkend="tsvn-dug-settings-colours"/> for more information.
target: Ovo je uobičajena šema boja, ali možete prilagoditi ove boje koristeći dijalog podešavanja. Čitajte <xref linkend="tsvn-dug-settings-colours"/> za više informacije.

note: (title)
en: Update Your Working Copy With Changes From Others
target: Ađurirajte vašu radnu kopiju izmenama drugih

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

note: (primary)
en: fetch changes
target: naći izmene

note: (title)
en: Progress dialog showing finished update
target: Progres dijalog koji pokazuje završeno ažuriranje

note: (para)
en: <placeholder-1/> Periodically, you should ensure that changes done by others get incorporated in your local working copy. The process of getting changes from the server to your local copy is known as <emphasis>updating</emphasis>. Updating may be done on single files, a set of selected files, or recursively on entire directory hierarchies. To update, select the files and/or directories you want, <action>right click</action> and select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Update</guimenuitem></menuchoice> in the explorer context menu. A window will pop up displaying the progress of the update as it runs. Changes done by others will be merged into your files, keeping any changes you may have done to the same files. The repository is <emphasis>not</emphasis> affected by an update.
target: <placeholder-1/> Periodično, morate omogućiti da izmene koje su drugi uradili budu inkorporirane u vašu lokalnu radnu kopiju. Proces dobijanje izmena od servera u vašu lokalnu kopiju poznato kao <emphasis>ažuriranje</emphasis>. <ažuriranje može biti dato na pojedinačnim fajlovima, skup izabranih fajlova, ili rekurzivno na celoj hijerarhiji imenika. Da bi ažurirali, izaberite fajlove i/ili imenike koje želite,<action>desni klik</action> i izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ažuriraj</guimenuitem></menuchoice> u kontekst meniju pretraživača. Jedan prozor će iskočiti da prikaže napredovanje ažuriranja dok radi. <izmene koje su drugi uradili biće stopljene u vašim fajlovima, čuvajući bilo koje izmene koje možete imati u istim fajlovima. Spremište <emphasis>ne</emphasis> utiče na ažuriranje.

note: (para)
en: New item added to your WC.
target: Novq stavka dodata u vašu RK

note: (para)
en: Redundant item deleted from your WC, or missing item replaced in your WC.
target: Redundantne stavke obrisane iz vaše RK, ili nedostajuće stavke zamenjene u vašoj RK.

note: (term)
en: Green
target: Zelen

note: (para)
en: Changes from repository successfully merged with your local changes.
target: Izmene iz spremišta sukcesifno su stopljene sa vašim lokalnim izmenama.

note: (term)
en: Bright red
target: Svetlo crvena

note: (para)
en: Changes from repository merged with local changes, resulting in conflicts which you need to resolve.
target: Izmene iz spremišta stopljeni sa lokalnim imenama, rezultovane u konfliktima koje treba da  rešiti.

note: (para)
en: Unchanged item in your WC updated with newer version from the repository.
target: Neizmenjena stavka u vašoj RK ažuriran sa novom verzijom iz spremišta.

note: (para)
en: The progress dialog uses colour coding to highlight different update actions <placeholder-1/>
target: Progres dijalog koristi bpje kodirane da posvetli različite ažurirane akcije <placeholder-1/>

note: (para)
en: If you get any <emphasis>conflicts</emphasis> during an update (this can happen if others changed the same lines in the same file as you did and those changes don't match) then the dialog shows those conflicts in red. You can <action>double click</action> on these lines to start the external merge tool to resolve the conflicts.
target: Ako dobijete bilo koje <emphasis>konflikte</emphasis> u toku ažuriranja (to se može desiti ako su drugi izmenili iste linije u istom fajlu koje ste i vi izmenili i te izmene se ne mogu spariti) tada dijalog prikazuje ove konflikte crveno. Možete uraditi <action>dvostruki klik</action> na ove linije da pokrenete spoljašnji alat za stapanje da se razreše konflikti.

note: (para)
en: When the update is complete, the progress dialog shows a summary of the number of items updated, added, removed, conflicted, etc. below the file list. This summary information can be copied to the clipboard using <keycap>Ctrl+C</keycap>.
target: Kada je ažuriranje kompletno, progres dijalog prikazuje ukupnost brojnih  stavki ažuriranih, dodatih, uklonjenih, konfliktnih, itd. ispod fajl liste. Ukupna informacija se može kopirati u klipbord koristeći  <keycap>Ctrl+C</keycap>.

note: (para)
en: The standard Update command has no options and just updates your working copy to the HEAD revision of the repository, which is the most common use case. If you want more control over the update process, you should use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Update to Revision...</guimenuitem></menuchoice> instead. This allows you to update your working copy to a specific revision, not only to the most recent one. Suppose your working copy is at revision 100, but you want it to reflect the state which it had in revision 50 - then simply update to revision 50. In the same dialog you can also choose the <firstterm>depth</firstterm> at which to update the current folder. The terms used are described in <xref linkend="tsvn-dug-checkout-depth"/>. The default depth is <guilabel>Working copy</guilabel>, which preserves the existing depth setting. You can also choose whether to ignore any external projects in the update (i.e. projects referenced using <literal>svn:externals</literal>).
target: Standardna Ažuriraj komanda nema opcije i samo ažurira vašu radnu kopiju do GLAVNE revizije spremišta, što je najčešći slučaj korišćenja. Ako želite više kontrole procesa ažuriranja, potrebno je da koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ažuriraj u Reviziju...</guimenuitem></menuchoice> umesto. Ovo omogućava da se ažurira vaša radna kopija do specificirane revizije, ne samo do najskoriju. Pretpostavimo da vaša radna kopija je u reviziji 100, ali vi želite da reflektujete stanje koje je bilo u reviziji 50 - tada jednostavno ažurirajte u reviziju 50. U istom dijalogu možete takođe izabrati <firstterm>dubinu</firstterm> do koje ažurirati tekući imenik. Termini koji su korišćeni opisani su u <xref linkend="tsvn-dug-checkout-depth"/>. Uobičajena dubina je <guilabel>Radna kopija</guilabel>, koja čuva postojeće podešavanje dubine. Možete takođe izabrati da li zanemariti spoljašnje projekte pri ažuriranju (tj. projek se referira koristeći <literal>svn:externals</literal>).

note: (para)
en: If you update a file or folder to a specific revision, you should not make changes to those files. You will get <quote>out of date</quote> error messages when you try to commit them! If you want to undo changes to a file and start afresh from an earlier revision, you can rollback to a previous revision from the revision log dialog. Take a look at <xref linkend="tsvn-howto-rollback"/> for further instructions, and alternative methods.
target: Ako ažurirate fajl ili imenik sa specifičnom revizijom, ne treba da pravite izmene tih fajlova. Dobićete <quote>zastarelo</quote> poruku o grešci kada pokušate da ih urežete! Ako želite da vratite izmene fakla i ponovo počnete od ranije revizije, možete se vratiti na prethodnu reviziju iz dijaloga revizionog dnevnika. Bacite pogled na <xref linkend="tsvn-howto-rollback"/> za dalje instrukcije, i alternativne metode.

note: (para)
en: <menuchoice><guimenuitem>Update to Revision</guimenuitem></menuchoice> can occasionally be useful to see what your project looked like at some earlier point in its history. But in general, updating individual files to an earlier revision is not a good idea as it leaves your working copy in an inconsistent state. If the file you are updating has changed name, you may even find that the file just disappears from your working copy because no file of that name existed in the earlier revision. If you simply want a local copy of an old version of a file it is better to use the <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Save revision to...</guimenuitem></menuchoice> command from the log dialog for that file.
target: <menuchoice><guimenuitem>Ažuriraj sa Revizijom</guimenuitem></menuchoice> može srećom da bude korisno da vidite na šta je vaš projekat ličio  u nekom ranijem trenutku njegove istorije. Alu uopšteno, ažuriranjem pojedinih fajlova sa ranijom revizijom ije dobra ideja jer ostavlja vašu radnu kopiju u nekonzistentno stanje. Ako je fajl koji ažurirate promenio ime, možete čak naći da je fajl tek nestao iz vaše radne kopije jer nema fajla tog imena da postoji u ranijoj reviziji. Ako jednostavno želite lokalnu kopiju stare verzije fajla bolje je da koristite  <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Sačuvaj reviziju u...</guimenuitem></menuchoice> iz dijaloga dnevnika tog fajla.

note: (title)
en: Multiple Files/Folders
target: Višestruki fajlovi/imenici

note: (para)
en: If you select multiple files and folders in the explorer and then select <menuchoice><guimenuitem>Update</guimenuitem></menuchoice>, all of those files/folders are updated one by one. TortoiseSVN makes sure that all files/folders which are from the same repository are updated to the exact same revision! Even if between those updates another commit occurred.
target: Ako izaberete više fajlova i imenika u pretraživaču i tada izaberete <menuchoice><guimenuitem>Ažuriraj</guimenuitem></menuchoice>, svi ovi fajlovi/imenici se ažuriraju jedan po jedan. TortoiseSVN osigurava da ti svi fajlovi/imenici, koji su iz istog spremišta, su ažurirani sa upravo istom revizijom! Čak ako između ovih ažuriranja dođe do drugog urezivanja.

note: (title)
en: Local File Already Exists
target: Lokalni fajl već postoji

note: (para)
en: Sometimes when you try to update, the update fails with a message to say that there is already a local file of the same name. This typically happens when Subversion tries to checkout a newly versioned file, and finds that an unversioned file of the same name already exists in your working folder. Subversion will never overwrite an unversioned file - it might contain something you are working on, which coincidentally has the same filename as another developer has used for his newly committed file.
target: Ponekad dok pokušavate da ažurirate, ažuriranje ne uspe sa porukom koja kaže da već postoji fajl sa istim imenom u vašem radnom imeniku. Subverzija nikada neće preklopiti neverzionisani fajl - on može sadržati nešto na čemu radite, što slučajno ima isto ime koje je drugi čovek iz razvoja uzeo za svoj novo urezani fajl.

note: (para)
en: If you get this error message, the solution is simply to rename the local unversioned file. After completing the update, you can check whether the renamed file is still needed.
target: Ako dobijete ovu poruku ogrešci, rešenje je da jednostavno preimenujete lokalni neverzionisani fajl. Posle kompletiranja ažuriranja možete proveriti da li je preimenovan fajl još potreban.

note: (para)
en: If you keep getting error messages, use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Check for Modifications</guimenuitem></menuchoice> instead to list all the problem files. That way you can deal with them all at once.
target: Ako čuvate dobijene greške, koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Proveri Modifikacije</guimenuitem></menuchoice> umesto da listate problem fajlove. Na taj način radite sa svima njima odjednom.

note: (title)
en: Resolving Conflicts
target: Rešavanje konflikta

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

note: (para)
en: This is your file as it existed in your working copy before you updated your working copy - that is, without conflict markers. This file has your latest changes in it and nothing else.
target: Ovo je vaš fajl kako je postojao u vašoj radnoj kopiji pre nego ste ažurirali vašu radnu kopiju - to je, bez konfliktnih markera. Ovaj fajl ima vaše poslednje izmene u njemu i ništa više.

note: (para)
en: This is the file that was the BASE revision before you updated your working copy. That is, it the file that you checked out before you made your latest edits.
target: Ovo je fajl koji je bio u OSNOVNOJ reviziji pre nego ste ažurirali radnu kopiju. Dakle, taj fajl koji ste preuzeli pre nego ste uradili vaše zadnje uređenje.

note: (para)
en: This is the file that your Subversion client just received from the server when you updated your working copy. This file corresponds to the HEAD revision of the repository.
target: ovo je fajl koji je vaš Subverzioni klijent upravo primio sa servera kada ste ažurirali vašu radnu kopiju. Ovaj fajl odgovara GLAVNOJ reviziji spremišta.

note: (para)
en: Once in a while, you will get a <emphasis>conflict</emphasis> when you update your files from the repository. A conflict occurs when two or more developers have changed the same few lines of a file. As Subversion knows nothing of your project, it leaves resolving the conflicts to the developers. Whenever a conflict is reported, you should open the file in question, and search for lines starting with the string <literal>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</literal>. The conflicting area is marked like this: <screen>
    &lt;&lt;&lt;&lt;&lt;&lt;&lt; filename
        your changes
    =======
        code merged from repository
    &gt;&gt;&gt;&gt;&gt;&gt;&gt; revision
    </screen> Also, for every conflicted file Subversion places three additional files in your directory: <placeholder-1/>
target: Jednom  ćete  dobiti <emphasis>konflikt</emphasis> dok ažurirate vaše fajlove iz spremišta. Konflikt se javlja kada dva ili više ljudi izmene isto nekoliko linija fajla. Kako Subverzija nezna ništa o vašem projektu, ona ostavlja rešavanje konflikta ljudima. Kadgod se konflikt iznese treba da otvorite fajl u pitanju i potražite linije koje počinju stringom <literal>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</literal>. Konfliktna oblast je markirana kao ovo: <screen>
    &lt;&lt;&lt;&lt;&lt;&lt;&lt; filename
        your changes
    =======
        code merged from repository
    &gt;&gt;&gt;&gt;&gt;&gt;&gt; revision
    </screen> Takođe, za svaki konfliktni fajl Subverzija stavlja tri dodatna fajla u vaš imenik: <placeholder-1/>

note: (para)
en: You can either launch an external merge tool / conflict editor with <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Edit Conflicts</guimenuitem></menuchoice> or you can use any other editor to manually resolve the conflict. You should decide what the code should look like, do the necessary changes and save the file.
target: Možete ili lansirati spoljašnji alat za stapanje / konflikt uređivač sa <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Uredi Konflikte</guimenuitem></menuchoice> ili možete koristiti bilo koji uređivač da ručno rešite konflikt. Treba odlučiti kako kod treba da izgleda, uradite neophodne izmene i sačuvajte fajl.

note: (para)
en: Afterwards execute the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Resolved</guimenuitem></menuchoice> and commit your modifications to the repository. Please note that the Resolve command does not really resolve the conflict. It just removes the <filename>filename.ext.mine</filename> and <filename>filename.ext.r*</filename> files, to allow you to commit your changes.
target: Posle izvršenja komande <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Rešen</guimenuitem></menuchoice> i urežite vaše izmene u spremište. Molim primetite da komanda Reši ne rešava stvarno konflikte. Ona samo uklanja <filename>filename.ext.mine</filename> i <filename>filename.ext.r*</filename> fajlovi, da vam omogući da urežete vaše izmene.

note: (para)
en: If you have conflicts with binary files, Subversion does not attempt to merge the files itself. The local file remains unchanged (exactly as you last changed it) and you have <filename>filename.ext.r*</filename> files. If you want to discard your changes and keep the repository version, just use the Revert command. If you want to keep your version and overwrite the repository version, use the Resolved command, then commit your version.
target: Ako imate konflikt sa binarnim fajlovima, Subverzija ne pokušava da stopi same fajlove. Lokalni fajl ostaje neizmenjen (tačno kao što ste ga izmenili) i vi imate <filename>filename.ext.r*</filename> fajlove. Ako želite da odbacite svoje izmene i zadržite verziju iz spremišta, samo iskoristite komandu Vrati. Ako želite da zadržite vašu verziju i da prepišete verziju spremišta, koristite komandu Reši, i urežite svoju verziju.

note: (para)
en: You can use the Resolved command for multiple files if you right click on the parent folder and select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Resolved...</guimenuitem></menuchoice> This will bring up a dialog listing all conflicted files in that folder, and you can select which ones to mark as resolved.
target: Možete koristiti komandu Rešen za više fajlova sa desnim klikom na predački imenik i izborom <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Rešen...</guimenuitem></menuchoice> Ovo će dovesti dijalog listing svih konfliktnih fajlova u tom imeniku, i možete izabrati koji da markirate rešenim.

note: (title)
en: Getting Status Information
target: Dobijanje status informacija

note: (primary)
en: view changes
target: izmene izgleda

note: (primary)
en: working copy status
target: status radne kopije

note: (para)
en: While you are working on your working copy you often need to know which files you have changed/added/removed or renamed, or even which files got changed and committed by others.
target: Dok vi radite na svojoj radnoj kopiji često vam treba da znate koje fajlove ste izmenili/dodali/uklonili ili preimenovali, ili čak koji fajlovi su izmenjeni i urezani od drugih.

note: (primary)
en: overlays
target: prekrivači

note: (primary)
en: icons
target: ikone

note: (para)
en: Now that you have checked out a working copy from a Subversion repository you can see your files in the windows explorer with changed icons. This is one of the reasons why TortoiseSVN is so popular. TortoiseSVN adds a so called overlay icon to each file icon which overlaps the original file icon. Depending on the Subversion status of the file the overlay icon is different.
target: Sada imate da preuzmete radnu kopiju iz Subverzionog spremišta možete videti svoje fajlove u vindouz eksploreru sa izmenjenim ikonama. Ovo je rezon zašto TortoiseSVN tako popularan. TortoiseSVN dodaje takozvane prekrivne ikone za svaku fajl ikonu koja prekriva originalnu ikonu fajla. Zavisno o Subverzionom stanju fajl prekrivna ikona se razlikuje.

note: (para)
en: <graphic fileref="../images/InSubVersionIcon.png"/> A fresh checked out working copy has a green checkmark as overlay. That means the Subversion status is <emphasis>normal</emphasis>.
target: <graphic fileref="../images/InSubVersionIcon.png"/>  Sveže preuzeta radna kopija ima zelen čekmarku kao prekrivač. To znači da je Subverzioni status <emphasis>normalan</emphasis>.

note: (para)
en: <graphic fileref="../images/ModifiedIcon.png"/> As soon as you start editing a file, the status changes to <emphasis>modified</emphasis> and the icon overlay then changes to a red exclamation mark. That way you can easily see which files were changed since you last updated your working copy and need to be committed.
target: <graphic fileref="../images/ModifiedIcon.png"/> Čim počnete uređenje fajla, status se menja u <emphasis>modifikovan</emphasis> i prekrivač ikone se menja u crveni uzvičnik marker. Tada možete lako videti koji fajlovi su izmenjeni od zadnjeg ažuriranja vaše radne kopije i treba da bude urezana.

note: (para)
en: <graphic fileref="../images/ConflictIcon.png"/> If during an update a <emphasis>conflict</emphasis> occurs then the icon changes to a yellow exclamation mark.
target: <graphic fileref="../images/ConflictIcon.png"/> Ako se tokom ažuriranja <emphasis>konflikta</emphasis> javi da se ikona izmeni u žuti uzvičnik marku.

note: (para)
en: <graphic fileref="../images/ReadOnlyIcon.png"/> If you have set the <literal>svn:needs-lock</literal> property on a file, Subversion makes that file read-only until you get a lock on that file. Such files have this overlay to indicate that you have to get a lock first before you can edit that file.
target: <graphic fileref="../images/ReadOnlyIcon.png"/> Ako ste podesili <literal>svn:needs-lock</literal> osobine fajla, Subverzija čini fajl samo za čitanje dok zaključate fajl. Takvi fajlovi imaju ovaj prekrivač da označi da ste otključali najpre pre nego uređujete fajl.

note: (para)
en: <graphic fileref="../images/LockedIcon.png"/> If you hold a lock on a file, and the Subversion status is <emphasis>normal</emphasis>, this icon overlay reminds you that you should release the lock if you are not using it to allow others to commit their changes to the file.
target: <graphic fileref="../images/LockedIcon.png"/> Ako držite zakčan fajl i Subverzioni status je <emphasis>normalan</emphasis>, ovaj prekrivač ikona vas podseća da treba otključati fajl ako ga ne koristite da omogućite drugim korisnicima da urezuju svoje izmene u taj fajl.

note: (para)
en: <graphic fileref="../images/DeletedIcon.png"/> This icon shows you that some files or folders inside the current folder have been scheduled to be <emphasis>deleted</emphasis> from version control or a file under version control is missing in a folder.
target: <graphic fileref="../images/DeletedIcon.png"/>  Ova ikona pokazuje da su neki fajlovi i imenici unutar tekućeg imenika bili predviđeni da budu <emphasis>obrisani</emphasis> iz verzije kontrole ili fajl pod kontrolom verzija nedostaje u imeniku.

note: (para)
en: <graphic fileref="../images/AddedIcon.png"/> The plus sign tells you that a file or folder has been scheduled to be <emphasis>added</emphasis> to version control.
target: <graphic fileref="../images/AddedIcon.png"/> Znak plus vam kaže da taj fajl ili imenik je predviđen da bude <emphasis>dodat</emphasis> kontroli verzija.

note: (para)
en: <graphic fileref="../images/IgnoredIcon.png"/> The bar sign tells you that a file or folder is <emphasis>ignored</emphasis> for version control purposes. This overlay is optional.
target: <graphic fileref="../images/IgnoredIcon.png"/> Uspravna crta vam kaže da fajl i imnik je <emphasis>zanemaren</emphasis> u svrhu kontrole verzija. Ovaj prekrivač je opcionalni.

note: (para)
en: <graphic fileref="../images/UnversionedIcon.png"/> This icon shows files and folders which are not under version control, but have not been ignored. This overlay is optional.
target: <graphic fileref="../images/UnversionedIcon.png"/> Ova ikona prikazuje fajlove i imenike koji nisu pod kontrolom verzija, ali nisu zanemareni. Ovaj prekrivač je opcionalni.

note: (para)
en: In fact, you may find that not all of these icons are used on your system. This is because the number of overlays allowed by Windows is very limited and if you are also using an old version of TortoiseCVS, then there are not enough overlay slots available. TortoiseSVN tries to be a <quote>Good Citizen (TM)</quote> and limits its use of overlays to give other apps a chance too.
target: U stvari, možete naći da da nisu sve od ovih ikona korišćene u vašem sistemu. To je zato što broj prekrivača koje dozvoljava Windows je veoma ograničen i ako i koristite staru verziju TortoiseCVS, tada nema dovoljno mogućih prekrivajućih pozicija. TortoiseSVN pokušava da bude <quote>Dobar Građanin (TM)</quote> i ograničava njeno korišćenje prekrivača da takođe da drugim aplikacijama šansu.

note: (para)
en: Now that there are more Tortoise clients around (TortoiseCVS, TortoiseHG, ...) the icon limit becomes a real problem. To work around this, the TortoiseSVN project introduced a common shared icon set, loaded as a DLL, which can be used by all Tortoise clients. Check with your client provider to see if this has been integrated yet :-)
target: Sada ima više Tortoise klijenta okolo (TortoiseCVS, TortoiseHG, ...) granice ikona postaju pravi problem. Za rad na ovome TortoiseSVN projekat je uveo zajedničke deljiv skup ikona, unete kao DLL, koji se može koristiti sa svim Tortoise klijentima. Proverite sa dobavljačima klijenata da vidite da li su već integrisani :-)

note: (para)
en: For a description of how icon overlays correspond to Subversion status and other technical details, read <xref linkend="tsvn-app-internals-overlays"/>.
target: Za opis kako ikone prekrivači odgovaraju Subverzionom statusu i ostale tehničke detalje pročitaj <xref linkend="tsvn-app-internals-overlays"/>.

note: (title)
en: TortoiseSVN Columns In Windows Explorer
target: TortoiseSVN kolumne u vindouz eksploreru

note: (primary)
en: Explorer Columns
target: Eksplorer kolumne

note: (para)
en: The same information which is available from the icon overlays (and much more) can be displayed as additional columns in Windows Explorer's Details View.
target: Iste informacije su dostupne od ikona prekrivača (i mnogo više) može biti prikazano kao dodatna kolona u Windows Explorer-ovom Detaljnom Pogledu.

note: (para)
en: Simply right click on one of the headings of a column, choose <guimenuitem>More...</guimenuitem> from the context menu displayed. A dialog will appear where you can specify the columns and their order, which is displayed in the <quote>Detailed View</quote>. Scroll down until the entries starting with SVN come into view. Check the ones you would like to have displayed and close the dialog by pressing <guibutton>OK</guibutton>. The columns will be appended to the right of those currently displayed. You can reorder them by drag and drop, or resize them, so that they fit your needs.
target: Jednostavni desni klik na jedno od naslova kolona, izaberite <guimenuitem>Više...</guimenuitem> iz prikazanog kontekst menija. Dijalog će se pojaviti gde specificirate kolonu i njen red koji je prikazan u <quote>Detaljni Pogled</quote>. Premotaj do ulaza sa SVN  koje dođe pod oko. Proveri to što ste želeli prikazati i zatvorite dijalog pritiskom na <guibutton>OK</guibutton>.Kolone će se dodati desno od one koja je prikazana trenutno. Možete preurediti ih vučenjem i bacanjem, ili promenom njihove veličine, tako da to popunjava vaše potrebe.

note: (para)
en: The additional columns in the Windows Explorer are not available on Vista, since Microsoft decided to not allow such columns for <emphasis>all</emphasis> files anymore but only for specific file types.
target: Dodatne kolone u Windows Explorernisu dostupne u Vista, kako je Microsoft odlučio da ne dozvoli takve kolone za <emphasis>sve</emphasis> fajlove samo za specifične tipove fajlova.

note: (para)
en: If you want the current layout to be displayed in all your working copies, you may want to make this the default view.
target: Ako želite tekući izgled da bude prikazan u vašoj radnoj kopiji, možete učiniti to uobičajenim pogledom.

note: (title)
en: Local and Remote Status
target: Lokalni i daljinski status

note: (primary)
en: modifications
target: izmene

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

note: (para)
en: <placeholder-1/> It's often very useful to know which files you have changed and also which files got changed and committed by others. That's where the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Check For Modifications...</guimenuitem></menuchoice> comes in handy. This dialog will show you every file that has changed in any way in your working copy, as well as any unversioned files you may have.
target: <placeholder-1/> To je često jako korisno znati koje fajlove ste menjali i takođe koji fajlovi su izmenjeni i urezani od drugih. To je gde komanda <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Proveri Modifikacije...</guimenuitem></menuchoice> dolazi ručno. Ovaj dijalog će vam pokazati svaki fajl koji se izmenio na bilo koji način u vašoj radnoj kopiji, kao i bilo koje neverzionisane fajlove koje možete imati.

note: (para)
en: If you click on the <guibutton>Check Repository</guibutton> then you can also look for changes in the repository. That way you can check before an update if there's a possible conflict. You can also update selected files from the repository without updating the whole folder.
target: Ako kliknetet na <guibutton>Proveri Spremište</guibutton> tada možete pogledati izmene u spremištu. Na taj način možete proveriti pre ažuriranja ako ima mogučih konflikta. Takođe možete ažurirati izabrane fajlove iz spremišta bez ažuriranja celog imenika.

note: (para)
en: Locally modified items.
target: Lokalno imenjene stavke.

note: (para)
en: Added items. Items which have been added with history have a <literal>+</literal> sign in the <guilabel>Text status</guilabel> column, and a tooltip shows where the item was copied from.
target: Dodate stavke. Stavke koje su dodate sa istorijom ima jedan <literal>+</literal> znak u <guilabel>Tekst status</guilabel> koloni, i alattip prikazuje odakle su stavke kopirane.

note: (para)
en: Deleted or missing items.
target: Obrisane ili nedostajuće stavke.

note: (para)
en: Items modified locally and in the repository. The changes will be merged on update. These <emphasis>may</emphasis> produce conflicts on update.
target: Stavke izmenjene lokalno i u spremištu. Izmene će biti stopljeni pri ažuriranju. Ovi <emphasis>mogu</emphasis> proizvesti konflikte pri ažuriranju.

note: (para)
en: Items modified locally and deleted in repository, or modified in repository and deleted locally. These <emphasis>will</emphasis> produce conflicts on update.
target: Stavke izmenjene lokalno i izbrisane u spremištu, ili izmenjene u spremištu i obrisane lokalno. Ovo <emphasis>će</emphasis> proizvesti konflikte pri ažuriranju.

note: (para)
en: Unchanged and unversioned items.
target: Nepromenjen i neverzionisane stavke.

note: (para)
en: The dialog uses colour coding to highlight the status. <placeholder-1/>
target: Dijalog koristi kolor kodiranje da osvetli satus. <placeholder-1/>

note: (para)
en: From the context menu of the dialog you can show a diff of the changes. Check the local changes <emphasis>you</emphasis> made using <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Compare with Base</guimenuitem></menuchoice>. Check the changes in the repository made by others using <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Show Differences as Unified Diff</guimenuitem></menuchoice>.
target: Iz kontekst menija dijaloga možete prikazati razlike izmena. Provera lokalnih izmena <emphasis>vi</emphasis> uradite korišćenjem <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Uporedi sa Osnovom</guimenuitem></menuchoice>. Proverite izmene u spremištu koje su uradili drugi koristeći <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Prikaži Razlike kao Ujedinjene Razlike</guimenuitem></menuchoice>.

note: (para)
en: You can also revert changes in individual files. If you have deleted a file accidentally, it will show up as <emphasis>Missing</emphasis> and you can use <emphasis>Revert</emphasis> to recover it.
target: Takođe možete vratiti izmene u individualnim fajlovima. Ako slučajno obrišete fajl, to će biti prikazano kao <emphasis>Nedostaje</emphasis> i možete koristiti <emphasis>Vrati</emphasis> da se to pokrije.

note: (para)
en: Unversioned and ignored files can be sent to the recycle bin from here using <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Delete</guimenuitem></menuchoice>. If you want to delete files permanently (bypassing the recycle bin) hold the <keycap>Shift</keycap> key while clicking on <guilabel>Delete</guilabel>.
target: Neverzionisani i zanemareni fajlovi mogu biti poslati korpu za otpatke koristeći <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Obriši</guimenuitem></menuchoice>. Ako želiti da obrišete fajlove za stalno (premošćavanjem korpe za otpatke) držite <keycap>Šift</keycap>taster dok kliknete na <guilabel>Obriši</guilabel>.

note: (para)
en: If you want to examine a file in detail, you can drag it from here into another application such as a text editor or IDE.
target: Ako želite da pregledate detaljno fajl, možete ga povući odavde u drugu aplikaciju kao što je uređivač teksta ili IDE.

note: (para)
en: The columns are customizable. If you <action>right click</action> on any column header you will see a context menu allowing you to select which columns are displayed. You can also change column width by using the drag handle which appears when you move the mouse over a column boundary. These customizations are preserved, so you will see the same headings next time.
target: Kolone su podesive. Ako uradite <action>desni klik</action> na bilo koje zaglavlje kolone videćete kontekst meni koji vam omogućava da izaberete koje kolone će biti prikazane. Takođe možete izmeniti kolone koristeći vučnu ručicu koja se pojavljuje kada pomerate miša preko granica kolona. Ova podešavanja su sačuvana, tako da ćete videti ista zaglavlja sledeći put.

note: (para)
en: If you are working on several unrelated tasks at once, you can also group files together into changelists. Read <xref linkend="tsvn-dug-commit-changelists"/> for more information.
target: Ako radite na više nezavisnih zadataka odjednom, možete takođe grupirati fajlove zajedno u listu izmena. Pročitajte <xref linkend="tsvn-dug-commit-changelists"/> za više informacija.

note: (para)
en: At the bottom of the dialog you can see a summary of the range of repository revisions in use in your working copy. These are the <emphasis>commit</emphasis> revisions, not the <emphasis>update</emphasis> revisions; they represent the range of revisions where these files were last committed, not the revisions to which they have been updated. Note that the revision range shown applies only to the items displayed, not to the entire working copy. If you want to see that information for the whole working copy you must check the <guilabel>Show unmodified files</guilabel> checkbox.
target: Na dnu dijaloga možete videti zbir opsega revizija spremišta u vašoj radnoj kopiji. Ovo su <emphasis>urezane</emphasis> revizije, nisu <emphasis>ažurirane</emphasis> revizije; one predstavljaju opseg revizija gde su ovi fajlovi zadnji urezani, ne revizije koje su ažurirane. Primetimo da je prikazani opseg revizija primenjen samo na prikazanim stavkama, ne na celu radni kopiju. Ako želite da vidite te informacije za celu radnu kopiju morate proveriti  <guilabel>Prikaži nemodifikovane fajlove</guilabel> čekboks.

note: (para)
en: If you want a flat view of your working copy, i.e. showing all files and folders at every level of the folder hierarchy, then the <guilabel>Check for Modifications</guilabel> dialog is the easiest way to achieve that. Just check the <guilabel>Show unmodified files</guilabel> checkbox to show all files in your working copy.
target: Ako želite jasan pregled radne kopije, tj. prikazujući sve fajlove na svakom nivou hijerarhije imenika, onda <guilabel>Proveri Modifikacije</guilabel> dijalog je najlakši način da se to dostigne. Samo proverite <guilabel>Prikaži nemodifikovane fajlove</guilabel> čekboks da prikažetefajlove u vašoj radnoj kopiji.

note: (title)
en: Viewing Diffs
target: Pregled Razl

note: (primary)
en: diffing
target: razlikovanje

note: (para)
en: Often you want to look inside your files, to have a look at what you've changed. You can accomplish this by selecting a file which has changed, and selecting <guimenuitem>Diff</guimenuitem> from TortoiseSVN's context menu. This starts the external diff-viewer, which will then compare the current file with the pristine copy (<literal>BASE</literal> revision), which was stored after the last checkout or update.
target: Često želite da pogledate unutar vaših fajlova da vidite šta ste menjali. Možete izvršiti ovo izborom fajla koji je izmenjen i izborom <guimenuitem>Diff</guimenuitem> iz TortoiseSVN-ov kontekst meni. Ovo pokreće spoljašnji diff-pregledač, koji će uporediti tekući fajl sa neizmenjenom kopijom (<literal>OSNOVNA</literal> revizija), što je sačuvano posle zadnjeg preuzimanja ili ažuriranja.

note: (para)
en: Even when not inside a working copy or when you have multiple versions of the file lying around, you can still display diffs:
target: Čak i kad nij unutar radne kopije ili kada imate više verzija fajla koji leže okolo, možete još uvek prikazati razlike:

note: (para)
en: Select the two files you want to compare in explorer (e.g. using <keycap>Ctrl</keycap> and the mouse) and choose <guimenuitem>Diff</guimenuitem> from TortoiseSVN's context menu. The file clicked last (the one with the focus, i.e. the dotted rectangle) will be regarded as the later one.
target: Izaberite dva fajla koja želite da uporedite u eksploreru (npr. koristeći <keycap>Ctrl</keycap> i miš) i izaberite <guimenuitem>Diff</guimenuitem>  iz TortoiseSVN.ovog kontekstnog menija. Fajl na koji je poslednji put kliknuto (onaj koji je u fokusu, tj. tačkasti pravougaonik) biće pregledan kao kasniji.

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

note: (para)
en: In an ideal world, you only ever work on one thing at a time, and your working copy contains only one set of logical changes. OK, back to reality. It often happens that you have to work on several unrelated tasks at once, and when you look in the commit dialog, all the changes are mixed in together. The <firstterm>changelist</firstterm> feature helps you group files together, making it easier to see what you are doing. Of course this can only work if the changes do not overlap. If two different tasks affect the same file, there is no way to separate the changes.
target: U idealnom svetu, vi uvek  radite samo na jednoj stvari u vremenu, i vaša radna kopija sadrži samo jedan skup logičnih izmena. OK, vratimo se realnosti. To se često dešava da imate da radite na više nezavisnih zadataka odjednom, i kada pogledate u dijalog urezivanja, sve izmene su pomešane zajedno. Osobina <firstterm>lista izmena</firstterm> pomaže vam da grupišete fajlove zajedno, čineći to lakim da se vidi šta radite. Naravno ovo se može raditi samo ako izmene nisu preklopljene. Ako dva različita posla dotiču isti fajl, nema načina da izdvojite izmene.

note: (para)
en: The changelist feature in TortoiseSVN is only available in Windows XP and later, as it depends on a shell capability which is not present in Windows 2000. Sorry, but Win2K is really quite old now, so please don't complain.
target: Osobina liste izmena u TortoiseSVN su dostupne samo u  Windows XP i kasnije, kako to zavisi u mogućnostima školjke, koje nisu prisutne u Windows 2000. Izvinite, ali Win2K je zaista sasvim star sada, tako molimo ne žalite se.

note: (para)
en: You can see changelists in several places, but the most important ones are the commit dialog and the check-for-modifications dialog. Let's start in the check-for-modifications dialog after you have worked on several features and many files. When you first open the dialog, all the changed files are listed together. Suppose you now want to organise things and group those files according to feature.
target: Možete videti listu promena na više mesta, ali najvažnije je dijalog urezivanja i proveri-za-izmene dijalogu. Počnimo u proveri-za-izmene dijalogu posle vašeg rada na više osobina i više fajlova. Kada prvi put otvorite dijalog svi izmenjeni fajlovi su izlistani zajedno. Pretpostavimo da želite organizovati stvari i grupisati te fajlove saglano sa osobinama.

note: (para)
en: Select one or more files and use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Move to changelist</guimenuitem></menuchoice> to add an item to a changelist. Initially there will be no changelists, so the first time you do this you will create a new changelist. Give it name which describes what you are using it for, and click <guibutton>OK</guibutton>. The dialog will now change to show groups of items.
target: Izaberite jedan ili više fajlova i koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Pomeri u listu izmena</guimenuitem></menuchoice> da dodate stavku u listu izmena. Početno nema liste izmena tako da najpre treba  kreirati novu listu izmena. Dajte joj ime koje opisuje za šta ćete je koristiti i kliknite  <guibutton>OK</guibutton>.Dijalog se menja da pokaže grupe stavki.

note: (para)
en: Once you have created a changelist you can drag and drop items into it, either from another changelist, or from Windows Explorer. Dragging from Explorer can be useful as it allows you to add items to a changelist before the file is modified. You could do that from the check-for-modifications dialog, but only by displaying all unmodified files.
target: Kada jednom kreirate listu izmena možete vući i baciti stavke u nju, ili iz druge liste izmena, ili iz Windows Explorer. Vučenjem iz Eksplorera može biti korisno ako vam dozvoljava da dodate stavke u listu izmena u listu izmena pre nego je fajl izmenjen. Mogli ste to uraditi iz proveri-za-izmene dijaloga, ali samo prikazivanjem sve neizmenjene fajlove.

note: (title)
en: Commit dialog with Changelists
target: Dijalog urezivanja sa listom promena

note: (para)
en: <placeholder-1/> In the commit dialog you can see those same files, grouped by changelist. Apart from giving an immediate visual indication of groupings, you can also use the group headings to select which files to commit.
target: <placeholder-1/> U dijalogu urezivanja možete videti ove iste fajlove, grupisane listom izmena. Osim što daje trenutnu vizuelnu indikaciju grupisanja, možete koristiti grupna zaglavlja da izaberete koji fajl urezati.

note: (para)
en: On XP, there is a context menu when you right click on a group heading which gives you the choice to check or uncheck all group entries. On Vista however the context menu is not necessary. Click on the group header to select all entries, then check one of the selected entries to check all.
target: Na  XP, postoji kontekst meni kada uradite desni klik na grupno zaglavlje koje vam daje izbor da čekirate ili otčekirate sve grupne ulaze. Na Visti međutim, kontekst meni nije neophodan. Kliknite na grupno zaglavlje da izaberete ulaze, zatim čekirajte izabrane ulaze da čekirate sve.

note: (para)
en: TortoiseSVN reserves one changelist name for its own use, namely <literal>ignore-on-commit</literal>. This is used to mark versioned files which you almost never want to commit even though they have local changes. This feature is described in <xref linkend="tsvn-dug-commit-ignore"/>.
target: TortoiseSVN rezerviše jedno ime liste izmena za sopstveno korišćenje, imenom <literal>zanemari-pri-urezivanju</literal>. Ovo se koristi da se označe verzionisani fajlovi koji skoro nikad ne želite da urežete čak i kada imaju lokalne izmene. Osobina je opisana u <xref linkend="tsvn-dug-commit-ignore"/>.

note: (para)
en: When you commit files belonging to a changelist then normally you would expect that the changelist membership is no longer needed. So by default, files are removed from changelists automatically on commit. If you wish to retain the file in its changelist, use the <guilabel>Keep changelists</guilabel> checkbox at the bottom of the commit dialog.
target: Kada urezujete fajlove koji pripadaju listi izmena normalno je da očekujete da članovi liste izmena nisu više potrebni. Tako se uobičajeno fajlovi uklone iz liste izmena automatski pri urezivanju. Ako želite zadržati fajl u listi izmena, koristite <guilabel>Čuvaj liste izmena</guilabel> čekboks na dnu dijaloga urezivanja.

note: (para)
en: Changelists are purely a local client feature. Creating and removing changelists will not affect the repository, nor anyone else's working copy. They are simply a convenient way for you to organise your files.
target: Lista izmena je čista mogućnost lokalnog klijenta. kreiranjem i uklanjanjem lista izmena ne utiče na spremište, niti na bilo koju radnu kopiju. Ona je jednostavno uobičajeni način da organizujete vaše fajlove.

note: (title)
en: Revision Log Dialog
target: Revizioni dijalog dnevnika

note: (primary)
en: log
target: dnevnik

note: (primary)
en: history
target: istorija

note: (primary)
en: commit messages
target: poruke urezivanja

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

note: (para)
en: For every change you make and commit, you should provide a log message for that change. That way you can later find out what changes you made and why, and you have a detailed log for your development process.
target: Za svaku izmenu koju uradite i urežete, možete omogućiti dnevnik poruka za te izmene. Na taj način možete kasnije naći koje izmene ste uradili i zašto, i imate detaljan dnevnik za vaš razvojni proces.

note: (para)
en: The top pane shows a list of revisions where changes to the file/folder have been committed. This summary includes the date and time, the person who committed the revision and the start of the log message.
target: Gornji panel prikazuje listu revizija gde su izmene fajla/imenika urezane. Rezultat obuhvata datum i vreme, ličnost koja urezuje reviziju i počinje dnevnik poruka.

note: (para)
en: Lines shown in blue indicate that something has been copied to this development line (perhaps from a branch).
target: Linije prikazane plavo označavaju nešto što je kopirano u ovoj razvojnoj liniji (verovatno  iz grane).

note: (para)
en: The middle pane shows the full log message for the selected revision.
target: Srednji panel prikazuje pun dnevnik poruka za izabranu reviziju.

note: (para)
en: The bottom pane shows a list of all files and folders that were changed as part of the selected revision.
target: Donji panel prikazuje listu fajlova i imenika koji su izmenjeni kao deo izabrane revizije.

note: (para)
en: The Revision Log Dialog retrieves all those log messages and shows them to you. The display is divided into 3 panes. <placeholder-1/> But it does much more than that - it provides context menu commands which you can use to get even more information about the project history.
target: Dnevnik Revizija Dijalog obnavlja dnevnik poruka i prikazuje vam ga. Displej je podeljen u 3 panela, <placeholder-1/> Ali to je mnogo više od toga - to omogućava komandama kontekst menija koje možete koristiti da dobijete čak više informacija o istoriji projekta.

note: (title)
en: Invoking the Revision Log Dialog
target: Pozivanje na dijalog dnevnika revizija

note: (title)
en: The Revision Log Dialog
target: Dijalog dnevnika revizija

note: (para)
en: From the TortoiseSVN context submenu
target: Iz TortoiseSVN kontekst submeni

note: (para)
en: From the property page
target: Iz vlasničkih listova

note: (para)
en: From the Progress dialog after an update has finished. Then the Log dialog only shows those revisions which were changed since your last update
target: Iz Progresa dijaloga kada je ažuriranje završeno. Tada Dnevnik dijalog samo prikazuje te revizije koje su bile izmenjene od vašeg zadnjeg ažuriranja.

note: (para)
en: <placeholder-1/> There are several places from where you can show the Log dialog: <placeholder-2/>
target: <placeholder-1/> Ima više mesta odakle možete prikazati Dnevnik dijalog: <placeholder-2/>

note: (title)
en: Revision Log Actions
target: Akcije dnevnika revizija

note: (para)
en: The top pane has an <guilabel>Actions</guilabel> column containing icons that summarize what has been done in that revision. There are four different icons, each shown in its own column.
target: Gornji panel ima <guilabel>Akcije</guilabel> kolonu koja sadrži ikone koje sumiraju šta je dato u reviziji. Ima četiri različitih ikona svaka prikazana u njenoj sopstvenoj koloni.

note: (para)
en: <graphic fileref="../images/ActionModifiedIcon.png"/> If a revision modified a file or directory, the <emphasis>modified</emphasis> icon is shown in the first column.
target: <graphic fileref="../images/ActionModifiedIcon.png"/> Ako revizija menja fajl ili imenik, <emphasis>izmenjen</emphasis> ikona je prikazana u prvoj koloni.

note: (para)
en: <graphic fileref="../images/ActionAddedIcon.png"/> If a revision added a file or directory, the <emphasis>added</emphasis> icon is shown in the second column.
target: <graphic fileref="../images/ActionAddedIcon.png"/> Ako revizija doda fajl ili imenik,  <emphasis>dodat<mphasis> ikona je prikazana u drugoj koloni.

note: (para)
en: <graphic fileref="../images/ActionDeletedIcon.png"/> If a revision deleted a file or directory, the <emphasis>deleted</emphasis> icon is shown in the third column.
target: <graphic fileref="../images/ActionDeletedIcon.png"/> Ako revizija briše fajl ili imenik,  <emphasis>obrisan</emphasis> ikona je prikazana u trećoj koloni.

note: (para)
en: <graphic fileref="../images/ActionReplacedIcon.png"/> If a revision replaced a file or directory, the <emphasis>replaced</emphasis> icon is shown in the fourth column.
target: <graphic fileref="../images/ActionReplacedIcon.png"/>Ako je revizija  premestila fajl ili imenik, <emphasis>premešten</emphasis> ikona je prikazana u četvrtoj koloni.

note: (title)
en: Getting Additional Information
target: Dobijanje dodatnih informacija

note: (title)
en: The Revision Log Dialog Top Pane with Context Menu
target: Gornji panel kontekstnog menija dnevnika dijaloga revizija

note: (para)
en: Compare the selected revision with your working copy. The default Diff-Tool is TortoiseMerge which is supplied with TortoiseSVN. If the log dialog is for a folder, this will show you a list of changed files, and allow you to review the changes made to each file individually.
target: Uporedite izabranu reviziju sa vašom radnom kopijom. Uobičajeni Diff-alat je TortoiseMerge koji ide uz TortoiseSVN. Ako je dijalog dnevnika  za imenike, ovo će prikazati listu izmenjenih fajlova, i omogućavaju vam da pregledate izmene učinjene u svakom fajlu individualno.

note: (para)
en: View the changes made in the selected revision as a Unified-Diff file (GNU patch format). This shows only the differences with a few lines of context. It is harder to read than a visual file compare, but will show all file changes together in a compact format.
target: Pregled izmena urađenih u izabranoj reviziji kao Unified-Diff fajl (GNU format zakrpa9. Ovo prikazuje samo razlike između nekih linija sadržaja. To je teže za čitanje od vizuelnog poređenja fajlova, ali će prikazati sve izmene zajedno u kompaktnom obliku.

note: (para)
en: Compare the selected revision with the previous revision. This works in a similar manner to comparing with your working copy.
target: Upoređuje izabranu reviziju sa prethodnom revizijom. Ovo radi na sličan način pri poređenju vaše radne kopije.

note: (para)
en: Blame the selected revision, and the file in your working BASE and compare the blame reports using a visual diff tool. Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail. (files only).
target: Okrivljuje izabranu reviziju i fajl u vašoj radnoj OSNOVI i poredi izveštaj okrivljavanja koristeći vizualni diff alat. Pročitajte <xref linkend="tsvn-dug-blame-diffs"/> za više detalja. (samo fajlovi).

note: (para)
en: Blame the selected revision, and the previous revision, and compare the results using a visual diff tool. (folders only).
target: Okrivite izabranu reviziju i prethodnu reviziju i uporedite rezultat koristeći vizualni diff alat. (samo imenici).

note: (para)
en: Save the selected revision to a file so you have an older version of that file. (files only).
target: Sačuvajte izabranu reviziju u fajl tako da imate stariju verziju tog fajla. (samo fajlovi).

note: (para)
en: Open the selected file, either with the default viewer for that file type, or with a program you choose. (files only).
target: Otvora izabrani fajl, ili sa podrazumevanim prikazivačem tog tipa fajlova ili sa programom koji ste izabrali. (samo fajlovi).

note: (para)
en: Blame the file up to the selected revision. (files only).
target: Krivac za fajl do izabrane revizije. (samo fajlovi).

note: (para)
en: Open the repository browser to examine the selected file or folder in the repository as it was at the selected revision.
target: Otvara pretraživač spremišta da pregleda izabrane fajlove u spremištu kakvi su bili u izabranoj reviziji.

note: (para)
en: Create a branch/tag from a selected revision. This is useful e.g. if you forgot to create a tag and already committed some changes which weren't supposed to get into that release.
target: Kreira grana/znak iz izabrane revizije. Ovo je korisno npr. ako zaboravite da kreirate znak i  već ste urezali neke izmene koje nisu bile pretpostavljene da dođu u tu realizaciju.

note: (para)
en: Update your working copy to the selected revision. Useful if you want to have your working copy reflect a time in the past. It is best to update a whole directory in your working copy, not just one file, otherwise your working copy will be inconsistent and you will be unable to commit any changes.
target: Ažurirajte vašu radnu kopiju na izabranu reviziju. Korisno ako želite da vaša radna kopija odslikava prošlo vreme. Najbolje je ažurirati ceo imenik u vašoj radnoj kopiji, ne samo jedan fajl, inače će vaša radna kopija postati nekonzistentna i nećete biti sposobni da urežete bilo koju izmenu.

note: (para)
en: Revert changes from which were made in the selected revision. The changes are reverted in your working copy so this operation does <emphasis>not</emphasis> affect the repository at all! Note that this will undo the changes made in that revision only. It does not replace your working copy with the entire file at the earlier revision. This is very useful for undoing an earlier change when other unrelated changes have been made since. If you have made local changes, this command will merge these changes into your working copy.
target: Vraća izmene od kojih je urađena u izabranoj reviziji. Izmene su vraćene u vašu radnu kopiju tako da ta operacija <emphasis>ne</emphasis> menja spremište uopšte! Primetimo da će to poništiti izmene urađene samo u toj reviziji. To ne menja vašu radnu kopiju celim fajlom u ranijoj reviziji. Ovo je jako korisno poništavanje ranijih izmena kada druge su već urađene druge nezavisne izmene. Ako uradite lokalne izmene ova komanda će stopiti te izmene u vašoj radnoj kopiji.

note: (para)
en: Revert to an earlier revision. If you have made several changes, and then decide that you really want to go back to how things were in revision N, this is the command you need. Again, the changes are reverted in your working copy so this operation does <emphasis>not</emphasis> affect the repository until you commit the changes. Note that this will undo <emphasis>all</emphasis> changes made after the selected revision, replacing the file/folder with the earlier version. If you have made local changes, this command will merge these changes into your working copy.
target: Vraća u raniju reviziju. Ako ste uradili više izmena, i tada odlučili to da zaista želite da  vratite kako su stvari bile u reviziji N, ova komanda vam je potrebna. Ponovo, izmene su vraćene u vašu radnu kopiju tako da ova operacija <emphasis>ne</emphasis> menja spremište dok urezujete izmene. Primetite da će ovo poništiti <emphasis>sve</emphasis> izmene urađene posle izbora revizije, zamena fajl/imenik sa ranijom verzijom. Ako ste uradili lokalne izmene ova komanda će stopiti ove izmene u vašu radnu kopiju.

note: (para)
en: Merge the selected revision(s) into a different working copy. A folder selection dialog allows you to choose the working copy to merge into, but after that there is no confirmation dialog, nor any opportunity to try a dry run. It is a good idea to merge into an unmodified working copy so that you can revert the changes if it doesn't work out! This is a useful feature if you want to merge selected revisions from one branch to another.
target: Stapa izabranu reviziju(e) u različite radne kopije. Dijalog izbora imenika dozvoljava vam da izaberete radnu kopiju u koju stapate, ali posle toga nema dijaloga potvrde, niti bilo kakvo suprotstavljanje da počnete čist rad. Dobra je ideja stopiti u nemodifikovanu radnu kopiju tako da možete vratiti izmene ako to ne radi!Ovo je korisna osobina ako želite da stopite izabranu reviziju iz jedne grane u drugu.

note: (para)
en: Make a fresh checkout of the selected folder at the selected revision. This brings up a dialog for you to confirm the URL and revision, and select a location for the checkout.
target: Uradite sveže preuzimanje izabranog imenika u izabranoj reviziji. To izbacuje dijalog za vas da se potvrdi URL i revizija, i izabere lokacija za preuzimanje.

note: (para)
en: Export the selected file/folder at the selected revision. This brings up a dialog for you to confirm the URL and revision, and select a location for the export.
target: Izvoz izabranog fajla/imenika u izabranoj reviziji. To izbacuje dijalog za vas da potvrdite URL i reviziju, i izbor lokaciju za izvoz.

note: (para)
en: Edit the log message or author attached to a previous commit. Read <xref linkend="tsvn-dug-showlog-4"/> to find out how this works.
target: Uređuje dnevnik poruka ili autora spojenih prethodnim urezivanjem. Pročitajte <xref linkend="tsvn-dug-showlog-4"/> da nađete kako to radi.

note: (para)
en: Copy the log details of the selected revisions to the clipboard. This will copy the revision number, author, date, log message and the list of changed items for each revision.
target: Kopira detalje dnevnika o izabranim revizijama za klipbord. Ovo će kopirati revizioni broj, autora, datum, dnevnik poruka i listu izmenjenih stavki za svaku reviziju.

note: (para)
en: Search log messages for the text you enter. This searches the log messages that you entered and also the action summaries created by Subversion (shown in the bottom pane). The search is not case sensitive.
target: Pretražuje dnevnik poruka za tekst koji ste uneli. To pretražuje dnevnik poruka koje ste uneli i takođe zbirnu akciju kreiranu Subverzijom (prikazan u donjem panelu). Pretraživanje ne zavisi od veličine slova.

note: (para)
en: <placeholder-1/> The top pane of the Log dialog has a context menu that allows you to access much more information. Some of these menu entries appear only when the log is shown for a file, and some only when the log is shown for a folder. <placeholder-2/>
target: <placeholder-1/>  gornjem  panel dijaloga Dnevnika ima kontekst meni koji omogućava da pristupite ka mnogo više informacija. Neke od tih ulaza menija pojavljuju se samo kada je dnevnik prikazan za fajl, a neki samo kada je dnevnik prikazan za imenik. <placeholder-2/>

note: (title)
en: Top Pane Context Menu for 2 Selected Revisions
target: Gornji panel kontekstnog menija za 2 izabrane revizije

note: (para)
en: Compare the two selected revisions using a visual difference tool. The default Diff-Tool is TortoiseMerge which is supplied with TortoiseSVN.
target: Upoređuje dve izabrane revizije koristeći vizuelni alat razlike. Podrazumevan Diff-Alat je TortoiseMerge koji ide uz TortoiseSVN.

note: (para)
en: If you select this option for a folder, a further dialog pops up listing the changed files and offering you further diff options. Read more about the Compare Revisions dialog in <xref linkend="tsvn-dug-compare-revs"/>.
target: Ako izaberete opciju za imenik, sledeći dijalog izbaci listing izmenjenih fajlova i dozvoljava vam dalje diff opcije. Pročitajte više o Dijalogu Poređenja Revizija u <xref linkend="tsvn-dug-compare-revs"/>.

note: (para)
en: Blame the two revisions and compare the blame reports using a visual difference tool. Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
target: Okrivljuje dve revizije i poredi izveštaj okrivljavanja koristeći vizuelni alat razlika. Pročitajte <xref linkend="tsvn-dug-blame-diffs"/> za više detalja.

note: (para)
en: View the differences between the two selected revisions as a Unified-Diff file. This works for files and folders.
target: Pregleda razlike između dve izabrane revizije kao Ujedinjen-Diff fajl. To radi za fajlve i imenike.

note: (para)
en: Copy log messages to clipboard as described above.
target: Kopiranje dnevnika poruka u klipbord kako je opisano iznad.

note: (para)
en: Search log messages as described above.
target: Traženje poruka dnevnika kako je opisano iznad.

note: (para)
en: <placeholder-1/> If you select two revisions at once (using the usual <keycap>Ctrl</keycap>-modifier), the context menu changes and gives you fewer options: <placeholder-2/>
target: <placeholder-1/> Ako izaberete dve revizije odjednom (koristeći uobičajen <keycap>Ctrl</keycap>-modifikator), kontekst meni se menja i daje vam manje opcija: <placeholder-2/>

note: (para)
en: If you select two or more revisions (using the usual <keycap>Ctrl</keycap> or <keycap>Shift</keycap> modifiers), the context menu will include an entry to Revert all changes which were made in the selected revisions. This is the easiest way to rollback a group of revisions in one go.
target: Ako izaberete dve ili više revizija (koristeći obično <keycap>Ctrl</keycap>ili <keycap>Shift</keycap> modifikator), kontekst meni će uneti ulaz da Vrati sve izmene koje su urađene u izabranoj reviziji. Ovo je najlakši način za vraćanje grupe revizija u jednom potezu.

note: (para)
en: You can also choose to merge the selected revisions to another working copy, as described above.
target: Možete takođe izabrati da stopite izabrane revizije u drugu radnu kopiju, kako je gore opisano.

note: (title)
en: The Log Dialog Bottom Pane with Context Menu
target: Dijalog dnevnika donji panel sa kontekstnim menijem

note: (para)
en: Show changes made in the selected revision for the selected file. This context menu is only available for files shown as <emphasis>modified</emphasis>.
target: Prikazivanje izmena u izabranoj reviziji za izabrani fajl. ovaj kontekst meni je dostupan samo za fajlove prikazane kao <emphasis>izmenjeni</emphasis>.

note: (para)
en: Blame the selected revision and the previous revision for the selected file, and compare the blame reports using a visual diff tool. Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
target: Okrivljavanje izabrane revizije i prethodne revizije za izabrane fajlove, i poređenje izveštaja okrivljavanja koristeći vizualni alat razlike. Pročitajte <xref linkend="tsvn-dug-blame-diffs"/> za više detalja.

note: (para)
en: Open the selected file, either with the default viewer for that file type, or with a program you choose.
target: Otvara izabrani fajl, ili sa  podrazumevanim pregedačem tog tipa fajlova, ili sa programom koji izaberete.

note: (para)
en: Revert the changes made to the selected file in that revision.
target: Vratiti izmene učinjene izabranim fajlovima u toj reviziji.

note: (para)
en: View the Subversion properties for the selected item.
target: Vidi Subverzijine osobine za izabranu stavku.

note: (para)
en: Show the revision log for the selected single file.
target: Prikazuje revizioni dnevnik za izabrane pojedinačne fajlove.

note: (para)
en: Save the selected revision to a file so you have an older version of that file.
target: Sačuvati izabranu reviziju fajla tako da imate staru verziju tog fajla.

note: (para)
en: <placeholder-1/> The bottom pane of the Log dialog also has a context menu that allows you to <placeholder-2/>
target: <placeholder-1/> Donji panel Dnevnik dijalga takođe ima kontekst meni koji vam omogućava da <placeholder-2/>

note: (para)
en: You may notice that sometimes we refer to changes and other times to differences. What's the difference?
target: Možete zapaziti da ponekad govorimo o izmenama a drugi put o razlikama. U čemu je razlika?

note: (para)
en: Subversion uses revision numbers to mean 2 different things. A revision generally represents the state of the repository at a point in time, but it can also be used to represent the changeset which created that revision, eg. <quote>Done in r1234</quote> means that the changes committed in r1234 implement feature X. To make it clearer which sense is being used, we use two different terms.
target: Subverzija koristi revizione brojeve da označi 2 različite stvari. Revizija generalno predstavlja stanje spremišta u vremenskom trenutku, ali može takođe, biti korišćena da predstavi skup izmena koji je kreirala ta revizija, npr. quote>Dato u r1234</quote> znači da su izmene urezane u r1234 implementiraju osobinu  X. Da se to učini jasnim koji osećaj je korišćen, koristimo dva različita termina.

note: (para)
en: If you select two revisions N and M, the context menu will offer to show the <emphasis>difference</emphasis> between those two revisions. In Subversion terms this is <literal>diff -r M:N</literal>.
target: Ako izabrete dve revizije N i M, kontekst meni će ponuditi da prikaže <emphasis>razlike</emphasis> između te dve revizije. U Subverzijinim terminima to je <literal>diff -r M:N</literal>.

note: (para)
en: If you select a single revision N, the context menu will offer to show the <emphasis>changes</emphasis> made in that revision. In Subversion terms this is <literal>diff -r N-1:N</literal> or <literal>diff -c N</literal>.
target: Ako izaberete pojedinačnu reviziju N, kontekst meni će ponuditi da prikaže <emphasis>izmene</emphasis> napravljene u toj reviziji. U Subverzijinim terminima to je <literal>diff -r N-1:N</literal> ili  <literal>diff -c N</literal>.

note: (para)
en: The bottom pane shows the files changed in all selected revisions, so the context menu always offers to show <emphasis>changes</emphasis>.
target: Donji panel prikazuje fajlove izmenjene u svim izabranim revizijama, tako kontekst meni uvek dozvoljava prikazivanje <emphasis>izmen</emphasis>.

note: (title)
en: Getting more log messages
target: Dobijanje više poruka dnevnika

note: (para)
en: For a large repository there may be hundreds or even thousands of changes and fetching them all could take a long time. Normally you are only interested in the more recent changes. By default, the number of log messages fetched is limited to 100, but you can change this value in <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Settings</guimenuitem></menuchoice> (<xref linkend="tsvn-dug-settings-dialogs"/>),
target: Za ogromna spremišta može biti stotine ili čak hiljade izmena i sve ih pronaći može uzeti mnogo vremena. Normalno, vas interesuju samo najskorije izmene. Podrazmeva se da broj donetih poruka dnevnika ograničen je na 100, ali možete promeniti ovu vrednost u menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Podešavanja</guimenuitem></menuchoice> (<xref linkend="tsvn-dug-settings-dialogs"/>),

note: (para)
en: When the <guilabel>Stop on copy/rename</guilabel> box is checked, Show Log will stop at the point that the selected file or folder was copied from somewhere else within the repository. This can be useful when looking at branches (or tags) as it stops at the root of that branch, and gives a quick indication of changes made in that branch only.
target: Kada je <guilabel>Stani na kopiraj/preimenj</guilabel> boks čekiran, Prikaži Dnevnik će stati u tačku gde je izabrani fajl ili imenik kopiran od negde u okviru spremišta. Ovo može biti korisno kada tražimo grane (ili značke) kako su stale u korenu te grane, i daje brz pokazatelj izmena učinjenih samo u toj grani.

note: (para)
en: Normally you will want to leave this option unchecked. TortoiseSVN remembers the state of the checkbox, so it will respect your preference.
target: Normalno vi želite da ostavite opcije nečekirane. TortoiseSVN pamti stanje čekboksa, tako će on poštovati vaše preference.

note: (para)
en: When the Show Log dialog is invoked from within the Merge dialog, the box is always checked by default. This is because merging is most often looking at changes on branches, and going back beyond the root of the branch does not make sense in that instance.
target: Kada je Prikaži Dnevnik dijalog pozvan u okviru Stopi dijaloga, boks je uvek čekirana kao podrazumevano. To je zbog toga što stapanje najčešće gleda u izmene na granama, i vraćanje  ispod korena grane ne čini mišta u tom slučaju.

note: (para)
en: Note that Subversion currently implements renaming as a copy/delete pair, so renaming a file or folder will also cause the log display to stop if this option is checked.
target: Primetimo da Subverzija tekuće postavlja preimenovanje kao kopiraj/briši par, tako preimenovanje fajla ili imenika će takođe, uzrokovati zaustavljanje displeja dnevnika ako je ova opcija čekirana.

note: (para)
en: The Log dialog does not always show all changes ever made for a number of reasons: <placeholder-1/>
target: Dnevnik dijalog ne prikazuje uvek sve izmene ikad urađene iz brojnih razloga: <placeholder-1/>

note: (para)
en: If you want to see more log messages, click the <guibutton>Next 100</guibutton> to retrieve the next 100 log messages. You can repeat this as many times as needed.
target: Ako želite da vidite više poruka dnevnika, kliknite <guibutton>Sledećih 100</guibutton> da vratite sledećih 100 poruka dnevnika. Možete ponoviti ovo toliko puta koliko želite.

note: (para)
en: Next to this button there is a multi-function button which remembers the last option you used it for. Click on the arrow to see the other options offered.
target: Sledeće do ovog dugmeta je multi-funkciono dugme koje pamti zadnje opcije za koje ste ga koristili. Kliknite na strelicu da vidite druge opcije koje su ponuđene.

note: (para)
en: Use <guibutton>Show Range ...</guibutton> if you want to view a specific range of revisions. A dialog will then prompt you to enter the start and end revision.
target: Koristite <guibutton>Prikaži Opseg ...</guibutton> ako želite da vidite specifičan opseg revizija. Dijalog će vas onda pitati da unesete početnu i krajnju reviziju.

note: (para)
en: Use <guibutton>Show All</guibutton> if you want to see <emphasis>all</emphasis> log messages from HEAD right back to revision 1.
target: Koristite <guibutton>Prikaži sve</guibutton> ako želite da vidite <emphasis>ceo</emphasis> dnevnik poruka iz GLAVNE nazad do revizije 1.

note: (title)
en: Current Working Copy Revision
target: Tekuća Revizija Radne Kopije

note: (para)
en: Because the log dialog shows you the log from HEAD, not from the current working copy revision, it often happens that there are log messages shown for content which has not yet been updated in your working copy. To help make this clearer, the commit message which corresponds to the revision you have in your working copy is shown in bold.
target: Zato što dnevnik dijalog prikazuje dnevnik od GLAVNE, ne od tekuće revizije radne kopije, to se često dešava tamo gde je dnevnik poruka prikazan za sadržaj koji još nije ažuriran u vašoj radnoj kopiji. Pomoć to čini jasnijim, poruka urezivanja koja odgovara reviziji koju imate u vašoj radnoj kopiji prikazana je masnim slovima.

note: (para)
en: By default this only works for files. This is because the update revision for a folder may not correspond to the update revision of its content, and the only way to find the effective update revision for the folder is to crawl the working copy. This can be a slow operation for large working copies so if you want to enable this feature you must create a <literal>DWORD</literal> registry key with value 1 at <literal>HKCU\Software\TortoiseSVN\RecursiveLogRev</literal>.
target: Uobičajeno ovo samo radi za fajlove. To je zato što ažurirana revizija za imenike ne odgovara ažuriranoj reviziji njenog sadržaja, i jedini je način da se nađe efektivno ažurirana revizija za imenik je puzanje kroz radnu kopiju. Ovo može biti spora operacija za velike radne kopije tako da ako želite da omogućite ovu osobinu morate kreirati <literal>DWORD</literal>ključ registra sa vrednošću 1 u <literal>HKCU\Software\TortoiseSVN\RecursiveLogRev</literal>.

note: (title)
en: Merge Tracking Features
target: Spajanje osobina praćenja

note: (primary)
en: merge tracking log
target: dnevnik spajanja praćenja

note: (para)
en: Subversion 1.5 and later keeps a record of merges using properties. This allows us to get a more detailed history of merged changes. For example, if you develop a new feature on a branch and then merge that branch back to trunk, the feature development will show up on the trunk log as a single commit for the merge, even though there may have been 1000 commits during branch development.
target: Subverzija 1.5 i kasnije čuvaju svedočanstvo o stapanju koristeći osobine. Ovo nam omogućava da dobijemo detaljniju istoriju stopljenih izmena. Na primer, ako razvijate nove osobine na grani i zatim stopite tu granu nazad u deblo, dalji razvoj će pokazati u dnevniku debla pojednačno urezivanje za stapanje, čak i ako možda ima 1000 urezivanja u toku razvoja grane.

note: (title)
en: The Log Dialog Showing Merge Tracking Revisions
target: Dijalog dnevnika koji prikazuje spajanje praćenja revizija

note: (para)
en: If you want to see the detail of which revisions were merged as part of that commit, use the <guilabel>Include merged revisions</guilabel> checkbox. This will fetch the log messages again, but will also interleave the log messages from revisions which were merged. Merged revisions are shown in grey because they represent changes made on a different part of the tree.
target: Ako želite da vidite detalje koje revizije su stopljene kao deo tog urezivanja, koristite <guilabel>Uključene stopljene revizije</guilabel> čekboks. To će ponovo naći dnevnik poruka, ali će takođe ubaciti dnevnik poruka iz revizija koje su stopljene. Stopljene revizije su prikazane sivo jer prikazuju izmene učinjene na različitim delovima stabla.

note: (para)
en: Of course, merging is never simple! During feature development on the branch there will probably be occasional merges back from trunk to keep the branch in sync with the main line code. So the merge history of the branch will also include another layer of merge history. These different layers are shown in the log dialog using indentation levels.
target: Svakako, stapanje nikad nije jednostavno! U toku daljeg razvoja na grani verovatno će biti slučajnih stapanja nazad iz debla da se sačuva grana i sinkronizuje sa glavnom linijom koda. Tako da istorija stapanja grane takođe uključuje sledeći sloj istorije stapanja. Ovi različiti slojevi su prikazani u dijalogu dnevnika koristeći nivoe uvlačenja.

note: (title)
en: Changing the Log Message and Author
target: Izmena poruka dnevnika i autora

note: (primary)
en: edit log/author
target: uredi dnevnik/autor

note: (para)
en: Sometimes you might want to change a log message you once entered, maybe because there's a spelling error in it or you want to improve the message or change it for other reasons. Or you want to change the author of the commit because you forgot to set up authentication or...
target: Ponekad možete poželeti da izmenite dnevnik poruku koju ste nekad uneli, možda zato što je sintksna greška u njoj ili želite da poboljšate poruku ili je izmenite iz drugih razloga. Ili želite da izmenite autora urezivanja jer ste zaboravili da podesite autentifikaciju ili...

note: (para)
en: Subversion lets you change both the log message and the author of revisions any time you want. But since such changes can't be undone (those changes are not versioned) this feature is disabled by default. To make this work, you must set up a pre-revprop-change hook. Please refer to the chapter on <ulink url="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks"><citetitle>Hook Scripts</citetitle></ulink> in the Subversion Book for details about how to do that. Read <xref linkend="tsvn-repository-hooks"/> to find some further notes on implementing hooks on a Windows machine.
target: Subvezija vam dopušta da menjate dnevnik poruku i autora revizije kad god želite. Ali kako takve izmene ne mogu biti poništene (te izmene nisu verzionisane) ova osobina je podrazumevano onemogućena. Da se uradi ovaj posao, morate podesiti pre-revprop-izmene zakačaljku. Molim pogledajte poglavlje na  <ulink url="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks"><citetitle>Hook Scripts</citetitle></ulink> u Subverzionoj Knjizi za detalje kako da se to uradi. Pročitajte <xref linkend="tsvn-repository-hooks"/> da nađete neke dalje beleške o primeni zakačaljki na Windows mašini.

note: (para)
en: Once you've set up your server with the required hooks, you can change both author and log message of any revision, using the context menu from the top pane of the Log dialog. You can also edit a log message using the context menu for the middle pane.
target: Kada jedanput podesite svoj server sa željenim zakačaljkama, možete menjati autora i dnevnik poruku bilo koje revizije, koristeći kontekst meni iz gornjeg panela Dnevnik dijaloga. Možete takođe uređivati dnevnik poruku koristeći kontekst meni iz srednjeg panela.

note: (para)
en: Because Subversion's revision properties are not versioned, making modifications to such a property (for example, the <literal>svn:log</literal> commit message property) will overwrite the previous value of that property <emphasis>forever</emphasis>.
target: Pošto Subverzione revizione osobine nisu verzionisane, pravljenjem izmena u tim osobinama (na primer, <literal>svn:log</literal> poruka urezivanja osobina) će prekriti prethodnu vrednost osobine <emphasis>zauvek</emphasis>.

note: (title)
en: Filtering Log Messages
target: Filriranje dnevnika poruka

note: (para)
en: If you want to restrict the log messages to show only those you are interested in rather than scrolling through a list of hundreds, you can use the filter controls at the top of the Log Dialog. The start and end date controls allow you to restrict the output to a known date range. The search box allows you to show only messages which contain a particular phrase.
target: Ako želite da ograničite dnevnik poruke da prikazuju samo ono što vas interesuje pre nego da premotavate listu od stotinu, možete koristiti filter kontrolu na vrhu Dnevnik Dijaloga. Početak i kraj datum kontrolišu da vam dozvole da ograničite izlaz na poznat opseg datuma. Boks pretraživanja vam omogućava da prikažete samo poruke koje sadrže pojedine fraze.

note: (para)
en: Click on the search icon to select which information you want to search in, and to choose <emphasis>regex</emphasis> mode. Normally you will only need a simple text search, but if you need to more flexible search terms, you can use regular expressions. If you hover the mouse over the box, a tooltip will give hints on how to use the regex functions. You can also find online documentation and a tutorial at <ulink url="http://www.regular-expressions.info/"><citetitle>http://www.regular-expressions.info/</citetitle></ulink>.
target: Kliknite na ikonu pretraživanja da izaberete koje informacije želite da tražite, i izaberite <emphasis>regex</emphasis> mod. Normalno je da vam samo treba jednostavno pretraživanje teksta, ali ako vam treba fleksibilnije pretraživanje možete koristiti regularne izraze. Ako lebdite mišem preko boksa, alatsavet će vam dati napomenu kako da koristite regeks funkcije. Možete takođe naći onlajn dokumentaciju i tutorijal na <ulink url="http://www.regular-expressions.info/"><citetitle>http://www.regular-expressions.info/</citetitle></ulink>.

note: (para)
en: Note that these filters act on the messages already retrieved. They do not control downloading of messages from the repository.
target: Primetiom da ovi filtri deluju na poruke već obnovljene. Oni ne kontrolišu skidanje poruka iz spremišta.

note: (para)
en: You can also filter the path names in the bottom pane using the <guilabel>Hide unrelated changed paths</guilabel> checkbox. Related paths are those which contain the path used to display the log. If you fetch the log for a folder, that means anything in that folder or below it. For a file it means just that one file. The checkbox is tristate: you can show all paths, grey out the unrelated ones, or hide the unrelated paths completely.
target: Možete takođe filtrirati imena putanja u donjem panelu koristeći <guilabel>Sakri nepovezane izmenjene putanje</guilabel> čekboks. Povezane putanje su one koje sadrže putanju korišćenu da prikaže dnevnik. Ako nađete dnevnik za imenik, to znači da je bilo šta u tom imeniku ili ispod njega. Za fajl znači samo da je to jedan fajl. Čekboks je tristanje: možete prikazati sve putanje, osenčati nepovezane, ili potpuno sakriti nepovezane putanje.

note: (para)
en: Sometimes your working practices will require log messages to follow a particular format, which means that the text describing the changes is not visible in the abbreviated summary shown in the top pane. The property <literal>tsvn:logsummary</literal> can be used to extract a portion of the log message to be shown in the top pane. Read <xref linkend="tsvn-dug-propertypage-tsvn-props"/> to find out how to use this property.
target: Ponekad vaša radna praksa će zahtevati dnevnik poruke da prate poseban format, što znači da tekst koji opisuje izmene nije vidljiv u skraćenom sažetku prikazanom u gornjem panelu. Osobina <literal>tsvn:logsummary</literal> se može koristiti da izdvoji deo dnevnik poruke da bude prikazan na vršnom panelu. Pročitajte <xref linkend="tsvn-dug-propertypage-tsvn-props"/> da nađete kako da koristite ovu osobinu.

note: (title)
en: Statistical Information
target: Statističke informacije

note: (primary)
en: statistics
target: statistika

note: (para)
en: The <guibutton>Statistics</guibutton> button brings up a box showing some interesting information about the revisions shown in the Log dialog. This shows how many authors have been at work, how many commits they have made, progress by week, and much more. Now you can see at a glance who has been working hardest and who is slacking ;-)
target: <guibutton>Statistika</guibutton> dugme dovlači boks koji prikazuje neke interesantne informacije o revizijama prikazanaim u Dnevnik dijalogu. Ovo prikazuje koliko autora je radilo, koliko urezivanja je urađeno, nedeljni napredak, i još mnogo šta. Sada možete videti jasno ko radi naporno i ko zabušava ;-)

note: (title)
en: Statistics Page
target: Statističke stranice

note: (para)
en: This page gives you all the numbers you can think of, in particular the period and number of revisions covered, and some min/max/average values.
target: Ova strana vam daje sve brojeve o kojima možete razmišljati, posebno period i broj revizija koje su pokrivene i neke min/maks/srednje vrednosti.

note: (title)
en: Commits by Author Page
target: Urezivanje po autorskom listu

note: (title)
en: Commits-by-Author Histogram
target: Urezivanje-po-autorskom histogramu

note: (title)
en: Commits-by-Author Pie Chart
target: Ureuivanje-po-autorskom pita dijagramu

note: (para)
en: <placeholder-1/> This graph shows you which authors have been active on the project as a simple histogram, stacked histogram or pie chart. <placeholder-2/>
target: <placeholder-1/> Ovaj graf prikazuje koji autori su aktivni na projektu pomoću jednostavnog histograma, stek histograma ili pita dijagrama. <placeholder-2/>

note: (para)
en: Where there are a few major authors and many minor contributors, the number of tiny segments can make the graph more difficult to read. The slider at the bottom allows you to set a threshold (as a percentage of total commits) below which any activity is grouped into an <emphasis>Others</emphasis> category.
target: Tamo gde je malo glavnih autora i mnogo sporednih pomoćnika, broj tankih segmenata čini graf teškim za čitanje. Klizač na dnu omogućava vam da podesite prag (kao procenat ukupnog urezivanja) ispod koga je bilo koja aktivnost grupisana u kategoriju  <emphasis>Drugi</emphasis>.

note: (title)
en: Commits by date Page
target: Urezivanje po podacima lista

note: (title)
en: Commits-by-date Graph
target: Urezivanje-po-podacima grafa

note: (para)
en: <placeholder-1/> This page gives you a graphical representation of project activity in terms of number of commits <emphasis>and</emphasis> author. This gives some idea of when a project is being worked on, and who was working at which time.
target: <placeholder-1/> Ova strana vam daje grafički prikaz aktivnosti projekta u terminima broja urezivanja <emphasis>i</emphasis> autor. To daje neke ideje o tome kada je projekat rađen i ko je radio u koje vreme.

note: (para)
en: When there are several authors, you will get many lines on the graph. There are two views available here: <emphasis>normal</emphasis>, where each author's activity is relative to the base line, and <emphasis>stacked</emphasis>, where each author's activity is relative to the line underneath. The latter option avoids the lines crossing over, which can make the graph easier to read, but less easy to see one author's output.
target: Kada postoji više autora, dobićete mnogo linija na grafu. Postoji dva moguća pogleda ovde: <emphasis>normalan</emphasis>, gde svaka autorska aktivnost je relativna na osnovnu liniju, i <emphasis>stekovana</emphasis>, gde je svaka autorska aktivnost relativna na liniju ispod. Kasnije opcije izbegavaju linije koje se presecaju preko grafa što čini graf lakšim za čitanje ali manje lak da se vidi izlaz za jednog autora.

note: (para)
en: By default the analysis is case-sensitive, so users <literal>PeterEgan</literal> and <literal>PeteRegan</literal> are treated as different authors. However, in many cases user names are not case-sensitive, and are sometimes entered inconsistently, so you may want <literal>DavidMorgan</literal> and <literal>davidmorgan</literal> to be treated as the same person. Use the <guilabel>Authors case insensitive</guilabel> checkbox to control how this is handled.
target: Uobičajeno je da je analiza zavisna od veličine slova tako da korisnici <literal>PeterEgen</literal> i <literal>PeteRegen</literal> se tretiraju kao različiti autori. Međutim, u mnogim slučajevima imena korisnika nisu zavisna od veličine slova, i ponekad se unose nekonzistentno, tako da možete poželeti da <literal>DavidMorgan</literal> i <literal>davidmorgan</literal> budu tretirani kao ista osoba. Koristite <guilabel>Autori nezavisni od veličine slova</guilabel> čekboks da kontrolišete kako se ovim rukuje.

note: (para)
en: Note that the statistics cover the same period as the Log dialog. If that is only displaying one revision then the statistics will not tell you very much.
target: Primetimo da statistika pokriva isti period kao i Dnevnik dijalog. Ako on prikazuje samo jednu reviziju tada statistika vam neće reći mnogo.

note: (title)
en: Offline Mode
target: Isključen mod

note: (para)
en: If the server is not reachable, and you have log caching enabled you can use the log dialog and revision graph in offline mode. This uses data from the cache, which allows you to continue working although the information may not be up-to-date or even complete.
target: Ako server nije dostupan, i imate omogućeno keširanje dnevnika možete koristiti dnevnik dijalog i revizioni graf u isključenom modu. Ovo koristi podatke iz keša, koji dopuštaju da nastavite sa radom mada informacije nisu ažurne ili su nekompletne.

note: (title)
en: Refreshing the View
target: Osvežavanje izgleda

note: (para)
en: If you want to check the server again for newer log messages, you can simply refresh the view using <keycap>F5</keycap>. If you are using the log cache (enabled by default), this will check the repository for newer messages and fetch only the new ones. If the log cache was in offline mode, this will also attempt to go back online.
target: Ako želite da proverite server ponovo za nove dnevnik poruke, možete jednostavno da osvežite pregled koristeći <keycap>F5</keycap>. Ako koristite dnevnik keš (omogućen uobičajeno), to će proveriti spremište za nove poruke i naći će samo nove. Ako je dnevnik keš bio u isključenom modu, to će dovesti do njegovog uključenja.

note: (para)
en: If you are using the log cache and you think the message content or author may have changed, you can use <keycap>Shift-F5</keycap> or <keycap>Ctrl-F5</keycap> to re-fetch the displayed messages from the server and update the log cache. Note that this only affects messages currently shown and does not invalidate the entire cache for that repository.
target: Ako koristite dnevnik keš i smatrate da je sadržaj poruke ili autor možda izmenjen, možete koristiti <keycap>Shift-F5</keycap> or <keycap>Ctrl-F5</keycap> da ponovo nađete prikazane poruke sa servera i ažurirate dnevnik keš. Primetimo da to utiče samo na trenutno prikazane poruke i ne čini neispravnim ceo keš za to spremište.

note: (title)
en: Viewing Differences
target: Pregled razlika

note: (primary)
en: diff
target: razl

note: (primary)
en: compare
target: poređenje

note: (para)
en: One of the commonest requirements in project development is to see what has changed. You might want to look at the differences between two revisions of the same file, or the differences between two separate files. TortoiseSVN provides a built-in tool named <application>TortoiseMerge</application> for viewing differences of text files. For viewing differences of image files, TortoiseSVN also has a tool named <application>TortoiseIDiff</application>. Of course, you can use your own favourite diff program if you like.
target: Jedan od najčešćih zahteva u razvoju projekta je da se vidi šta je izmenjeno. Možete želeti da vidite razlike između dve revizije istog fajla, ili razlike između dva posbna fajla. TortoiseSVN ima ugrađen alat zvani <application>TortoiseMerge</application> za pregledanje razlika tekst fajlova. Da bi se pregledale razlike fajlova slika, TortoiseSVN takođe ima alat koji se zove <application>TortoiseIDiff</application>. svakako, možete koristiti vaš favorit diff program ako želite.

note: (title)
en: File Differences
target: Fajl razlike

note: (term)
en: Local changes
target: Lokalne izmene

note: (para)
en: If you want to see what changes <emphasis>you</emphasis> have made in your working copy, just use the explorer context menu and select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff</guimenuitem></menuchoice>.
target: Ako želite da vidite koje izmene ste <emphasis>vi</emphasis> uradili u vašoj radnoj kopiji, samo koristite eksplorerov kontekst meni i izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff</guimenuitem></menuchoice>.

note: (term)
en: Difference to another branch/tag
target: Razlike ka sledećoj grana-znak

note: (para)
en: If you want to see what has changed on trunk (if you are working on a branch) or on a specific branch (if you are working on trunk), you can use the explorer context menu. Just hold down the <keycap>Shift</keycap> key while you right click on the file. Then select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff with URL</guimenuitem></menuchoice>. In the following dialog, specify the URL in the repository with which you want to compare your local file to.
target: Ako želite da vidite šta je izmenjeno na deblu (ako radite na grani) ili na specifičnoj grani (ako radite na deblu), možete koristiti eksplorer kontekst meni. Samo držite <keycap>Shift</keycap> taster dok uradite desni klik na fajl. Tada izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff sa URL</guimenuitem></menuchoice>. U sledećem dijalogu specificirajte URL u spremištu sa kojim hoćete da poredite vaš lokalni fajl.

note: (para)
en: You can also use the repository browser and select two trees to diff, perhaps two tags, or a branch/tag and trunk. The context menu there allows you to compare them using <guimenuitem>Compare revisions</guimenuitem>. Read more in <xref linkend="tsvn-dug-compare-revs"/>.
target: Možete takođe koristiti pretraživač spremišta i izabrati dva stabla za diff, možda dve značke, ili granu/značku i deblo. Kontekst meni omogućava vam da ih poredite koristeći <guimenuitem>Poredi revizije</guimenuitem>. Pročitajte više u <xref linkend="tsvn-dug-compare-revs"/>.

note: (term)
en: Difference from a previous revision
target: Razlike od prethodne revizije

note: (para)
en: If you want to see the difference between a particular revision and your working copy, use the Revision Log dialog, select the revision of interest, then select <guimenuitem>Compare with working copy</guimenuitem> from the context menu.
target: Ako želite da vidite razlike između posebne revizije i vaše radne kopije, oristite Revizioni Dnevnik dijalog, izaberite reviziju koja vas interesuje, zatim izaberite <guimenuitem>Uporedite sa radnom kopijom</guimenuitem> iz kontekst menija.

note: (para)
en: If you want to see the difference between the last committed revision and your working copy, assuming that the working copy hasn't been modified, just right click on the file. Then select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff with previous version</guimenuitem></menuchoice>. This will perform a diff between the revision before the last-commit-date (as recorded in your working copy) and the working BASE. This shows you the last change made to that file to bring it to the state you now see in your working copy. It will not show changes newer than your working copy.
target: Ako želite da vidite razlike između zadnje urezane revizije i vaše radne kopije, uzimajući da radna kopija nije izmenjena, samo uradite desni klik na fajl. Zatim izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff sa prethodnom verzijom</guimenuitem></menuchoice>. Ovo će omogućiti diff između revizije pre zadnjeg -urezivanja-datuma (kako je zapisana u vašoj radnoj kopiji= i radne OSNOVE. Ovo vam prikazuje zadnje izmene tog fajla koje su dovele do stanja koje sada vidite u vašoj radnoj kopiji. To će prikazati izmene novije od vaše radne kopije.

note: (term)
en: Difference between two previous revisions
target: Razlike između dve prethodne revizije

note: (para)
en: If you want to see the difference between two revisions which are already committed, use the Revision Log dialog and select the two revisions you want to compare (using the usual <keycap>Ctrl</keycap>-modifier). Then select <guimenuitem>Compare revisions</guimenuitem> from the context menu.
target: Ako želite da vidite razlike između dve revizije koje su već urezane, koristite Revizioni Dnevnik i izaberite dve revizije koje želite da poredite koristeći uobičajen <keycap>Ctrl</keycap>-modifikator). Zatim izaberite <guimenuitem>Poredi revizije</guimenuitem> iz kontekst menija.

note: (para)
en: If you did this from the revision log for a folder, a Compare Revisions dialog appears, showing a list of changed files in that folder. Read more in <xref linkend="tsvn-dug-compare-revs"/>.
target: Ako ovo uradite iz revizionog dnevnika za imenike, Poređenje Revizija dijalog se pojavljuje, prikazujući listu izmenjenih fajlova u tom imeniku. Pročitajte više u <xref linkend="tsvn-dug-compare-revs"/>.

note: (term)
en: All changes made in a commit
target: Izmene učinjene pri urezivanju

note: (para)
en: If you want to see the changes made to all files in a particular revision in one view, you can use Unified-Diff output (GNU patch format). This shows only the differences with a few lines of context. It is harder to read than a visual file compare, but will show all the changes together. From the Revision Log dialog select the revision of interest, then select <guimenuitem>Show Differences as Unified-Diff</guimenuitem> from the context menu.
target: Ako želite da vidite izmene napravljene na svim fajlovima u pojedinoj reviziji u jednom pregledu, možete koristiti Ujedinjen-Diff izlaz (GNU format zakrpa). Ovo prikazuje samo razlike nekoliko linija u sadržaju. Teže je čitati nego vizuelno poređenje fajla, ali će prikazati sve izmene zajedno. Iz Revizioni Dnevnik dijaloga izaberite reviziju koja vas interesuje, zatim izaberite <guimenuitem>Prikaži Razlike kao Ujedinjeni-Diff</guimenuitem> iz kontekst menija.

note: (term)
en: Difference between files
target: Razlike između fajlova

note: (para)
en: If you want to see the differences between two different files, you can do that directly in explorer by selecting both files (using the usual <keycap>Ctrl</keycap>-modifier). Then from the explorer context menu select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff</guimenuitem></menuchoice>.
target: Ako želite da vidite razlike između dva različita fajla, možete to uraditi direktno u pretraživaču izboromoba fajla (koristeći običan <keycap>Ctrl</keycap>-modifikator). Zatim iz pretraživačevog kontekst menija izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff</guimenuitem></menuchoice>.

note: (term)
en: Difference between WC file/folder and a URL
target: Razlike između RK fajl/imenik i URL

note: (para)
en: If you want to see the differences between a file in your working copy, and a file in any Subversion repository, you can do that directly in explorer by selecting the file then holding down the <keycap>Shift</keycap> key whilst right clicking to obtain the context menu. Select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff with URL</guimenuitem></menuchoice>. You can do the same thing for a working copy folder. TortoiseMerge shows these differences in the same way as it shows a patch file - a list of changed files which you can view one at a time.
target: Ako želite da vidite razlike između fajla u vašoj radnoj kopiji, i fajl u bilo kojem Subverzionom spremištu, možete to uraditi direktno u pretraživaču izborom fajla zatim držeći <keycap>Shift</keycap> taster dok desnim klikom dobijete kontekst meni. Izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff sa URL</guimenuitem></menuchoice>. Možete uraditi istu stvar za imenik radne kopije. TortoiseMerge prikazuje ove razlike na isti način kao što je prikazano u fajlu zakrpe - lista izmenjenih fajlova koje možete pregledati jedan po jedan.

note: (term)
en: Difference with blame information
target: Razlike sa krivac informacijama

note: (para)
en: If you want to see not only the differences but also the author, revision and date that changes were made, you can combine the diff and blame reports from within the revision log dialog. Read <xref linkend="tsvn-dug-blame-diffs"/> for more detail.
target: Ako želite da vidite ne samo razlike već i autore, revizija i datum gde su izmene izvršene, možete kombinovati diff i okrivi izveštaje u okviru revizionog dnevnik dijaloga. Pročitajte <xref linkend="tsvn-dug-blame-diffs"/> za više detalja.

note: (term)
en: Difference between folders
target: Razlike između imenika

note: (para)
en: The built-in tools supplied with TortoiseSVN do not support viewing differences between directory hierarchies. But if you have an external tool which does support that feature, you can use that instead. In <xref linkend="tsvn-dug-diff-tools"/> we tell you about some tools which we have used.
target: Ugrađeni alat koji daje TortoiseSVN ne podržava viđene razlike između hijerarhije imenika. Alo ako imate spoljašnji alat koji podržava te osobine možete ga koristiti umesto toga. U <xref linkend="tsvn-dug-diff-tools"/> mi vam kažemo o nekim alatima koji su korišćeni.

note: (para)
en: If you have configured a third party diff tool, you can use <keycap>Shift</keycap> when selecting the Diff command to use the alternate tool. Read <xref linkend="tsvn-dug-settings-progs"/> to find out about configuring other diff tools.
target: Ako ste konfigurisali diff alat treće strane, možete koristiti  <keycap>Shift</keycap> kada izaberete Diff komandu da koristite alternativni alat. Pročitajte <xref linkend="tsvn-dug-settings-progs"/> da nađete o konfiguraciji drugih diff alata.

note: (title)
en: Line-end and Whitespace Options
target: Kraj-reda i razmak opcije

note: (para)
en: Sometimes in the life of a project you might change the line endings from <literal>CRLF</literal> to <literal>LF</literal>, or you may change the indentation of a section. Unfortunately this will mark a large number of lines as changed, even though there is no change to the meaning of the code. The options here will help to manage these changes when it comes to comparing and applying differences. You will see these settings in the <guilabel>Merge</guilabel> and <guilabel>Blame</guilabel> dialogs, as well as in the settings for TortoiseMerge.
target: Ponekad u životu projekta možete izmeniti završetak linija od <literal>CRLF</literal> u <literal>LF</literal>, ili možete izmeniti uvlačenje paragrafa. Na nesreću ovo će označiti veliki broj linija kao izmenjene, čak i kad nema izmena značajnog koda. Opcije će ovde pomoći da se upravlja ovim izmenama kada one dođu da se uporede i primene razlike. Možete videti ova podešavanja u  <guilabel>Stopi</guilabel> i <guilabel>Okrivi</guilabel> dijalozima, isto kao i u podešavanju TortoiseMerge.

note: (para)
en: <guilabel>Ignore line endings</guilabel> excludes changes which are due solely to difference in line-end style.
target: <guilabel>Zanemari završetak linija</guilabel> izbacuje izmene koje su samo zbog razlika u stilu završetka linija.

note: (para)
en: <guilabel>Compare whitespaces</guilabel> includes all changes in indentation and inline whitespace as added/removed lines.
target: <guilabel>Poređenje belihpolja </guilabel> uključuje sve izmene u uvlačenju i unutar linije belapolja kao dodate/uklonjene linije.

note: (para)
en: <guilabel>Ignore whitespace changes</guilabel> excludes changes which are due solely to a change in the amount or type of whitespace, eg. changing the indentation or changing tabs to spaces. Adding whitespace where there was none before, or removing a whitespace completely is still shown as a change.
target: <guilabel>Zanemari izmene belihpolja</guilabel> isključuje izmene koje su samo zbog izmena u iznosu ili tipu belihpolja, npr. izmenom uvlačenja ili izmenom tabova ili razmaka. Dodavanjem belih polja gde nisu bila ranije, ili uklanjanjem belihpolja potpuno je još uvek prikazano kao promena.

note: (para)
en: <guilabel>Ignore all whitespaces</guilabel> excludes all whitespace-only changes.
target: <guilabel>Zanemari sva belapolja</guilabel> isključuje sva samo-belapolja izmene.

note: (para)
en: Naturally, any line with changed content is always included in the diff.
target: Prirodno, svaka linija sa izmenjenim sadržajem uvek je uključena u diff.

note: (title)
en: Comparing Folders
target: Poređenje imenika

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

note: (primary)
en: export changes
target: izvoz izmena

note: (title)
en: The Compare Revisions Dialog
target: Poređenje revizionija dijalog

note: (para)
en: <placeholder-1/> When you select two trees within the repository browser, or when you select two revisions of a folder in the log dialog, you can <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Compare revisions</guimenuitem></menuchoice>.
target: <placeholder-1/> Kada izaberete dva stabla u okviru pretraživača spremišta, ili kada izaberete dve revizije imenika u dnevnik dijalogu, možete <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Poredi Revizije</guimenuitem></menuchoice>.

note: (para)
en: This dialog shows a list of all files which have changed and allows you to compare or blame them individually using context menu.
target: Ovaj dijalog prikazuje listu fajlova koji su izmenjeni i dozvoljava vam da uporedite ili okrivite njih pojedinačno koristeći kontekst meni.

note: (para)
en: You can also export the list of changed files to a text file, or you can export the changed files themselves to a folder. This operation works on the selected files only, so you need to select the files of interest - usually that means all of them.
target: Možete takođe izvesti listu izmenjenih fajlova u tekst fajl, ili možete izvesti izmenjene fajlove u imenik. Ova operacija radi samo na izabranim fajlovima, tako da vam treba da izaberete fajlove od interesa - obično to znači sve njih.

note: (para)
en: If you want to export the list of files <emphasis>and</emphasis> the actions (modified, added, deleted) as well, you can do that using the keyboard shortcuts <keycap>Ctrl-A</keycap> to select all entries and <keycap>Ctrl-C</keycap> to copy the detailed list to the clipboard.
target: Ako želite da izvezete listu fajlova <emphasis>i</emphasis> akciju (izmenjen,dodat,obrisan) takođe, možete to uraditi koristeći skraćenicu tastature <keycap>Ctrl-A</keycap> da izaberete sve ulaze i <keycap>Ctrl-C</keycap> da kopirate detaljnu listu u klipbord.

note: (para)
en: The button at the top allows you to change the direction of comparison. You can show the changes need to get from A to B, or if you prefer, from B to A.
target: Dugme na vrhu omogućava da izmenite pravac poređenja. Možete prikazati izmene potrebne da uzmete od A do B, ili ako više volite, od B do A.

note: (para)
en: The buttons with the revision numbers on can be used to change to a different revision range. When you change the range, the list of items which differ between the two revisions will be updated automatically.
target: Dugmići sa revizionim brojevima na sebi mogu se koristiti za izmene za različite revizione opsege. Kada izmenite opseg, lista stavki koja pravi razliku između dve revizije biće ažurirana automatski.

note: (para)
en: If the list of filenames is very long, you can use the search box to reduce the list to filenames containing specific text. Note that a simple text search is used, so if you want to restrict the list to C source files you should enter <filename>.c</filename> rather than <filename>*.c</filename>.
target: Ako je lista fajlimena veoma duga, možete koristiti traži boks da redukujete listu fajlimena koja sadrže specifičan tekst. Primetimo da se koristi jednostavno pretraživanje teksta, zako da ako želite da redukujete listu na C izvorne fajlove morate uneti <filename>.c</filename> pre nego <filename>*.c</filename>.

note: (title)
en: Diffing Images Using TortoiseIDiff
target: Razl slika koristeći TortozDif

note: (primary)
en: image diff
target: slika razl

note: (primary)
en: TortoiseIDiff
target: TortozIDiff

note: (para)
en: There are many tools available for diffing text files, including our own TortoiseMerge, but we often find ourselves wanting to see how an image file has changed too. That's why we created TortoiseIDiff.
target: Postoji mnogo alata dostupnih za razlikovanje tekst fajlova, uključujući naš TortoiseMerge, ali mi često nalazimo sebe da želimo takođe da vidimo kako kako se fajl slike izmenio. To je zašto smo kreirali TortoiseIDiff.

note: (title)
en: The image difference viewer
target: Pregledač razlika slika

note: (para)
en: <placeholder-1/><menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff</guimenuitem></menuchoice> for any of the common image file formats will start TortoiseIDiff to show image differences. By default the images are displayed side-by-side but you can use the View menu or toolbar to switch to a top-bottom view instead, or if you prefer, you can overlay the images and pretend you are using a lightbox.
target: <placeholder-1/><menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Diff</guimenuitem></menuchoice> za svaki od čestih fajl formata slike će startovati TortoiseIDiff da prikaže razlike u slici. Uobičajeno slike se prikazuju strana-po-stranu ali možete koristiti Pregled meni ili alatpult da pređete na vrh-dno pregled umesto toga, ili ako više volite, možete preklopiti slike i pretpostaviti da koristite lajtboks.

note: (para)
en: Naturally you can also zoom in and out and pan around the image. You can also pan the image simply by left-dragging it. If you select the <guilabel>Link images together</guilabel> option, then the pan controls (scrollbars, mousewheel) on both images are linked.
target: Prirodno je da možete povećati ili smanjiti ili kružiti oko slike. Možete prikazati sliku u panelu jednostavnim levim-vučenjem. Ako izaberete <guilabel>Veži slike zajedno</guilabel> opciju, zatim otvorite panel kontrolu (skrolpult, mištočkić) na obe vezane slike.

note: (para)
en: An image info box shows details about the image file, such as the size in pixels, resolution and colour depth. If this box gets in the way, use <menuchoice><guimenu>View</guimenu><guimenuitem>Image Info</guimenuitem></menuchoice> to hide it. You can get the same information in a tooltip if you hover the mouse over the image title bar.
target: Info boks slike prikazuje detalje fajla slike, kao što su veličina u pikselima, rezolucija i dubina boja. Ako se ovaj boks dobije koristite <menuchoice><guimenu>Pregled</guimenu><guimenuitem>Info Slike</guimenuitem></menuchoice>da ga sakrijete. Možete dobiti iste informacije u alatsavetu ako letite mišem preko pulta naslova slike.

note: (para)
en: When the images are overlaid, the relative intensity of the images (alpha blend) is controlled by a slider control at the left side. You can click anywhere in the slider to set the blend directly, or you can drag the slider to change the blend interactively. <keycap>Ctrl+Shift</keycap>-<action>Wheel</action> to change the blend.
target: Kada su slike prekrivene, relativni intezitet slike (alfa mešavina) se kontroliše klizačem sa leve strane. Možete kliknuti bilo gde na klizaču da se podesi mešavina direktno, ili možete vući klizač da promenite mešavinu interaktivno. <keycap>Ctrl+Shift</keycap>-<action>Wheel</action> da izmenite mešavinu.

note: (para)
en: The button above the slider toggles between two preset blends, indicated by the markers on either side of the blend slider. By default one is at the top and the other at the bottom, so the toggle button just switches between one image and the other. You can move the markers to choose the two blend values that the toggle button will use.
target: Dugme iznad klizača prebacuje između dve prepodešene mešavine, indicirane markerima na svakoj strani klizača mešavine. Uobičajeno je jedan na vrhu dok je drugi na dnu tako da dugme za prebacivanje samo preklapa između jedne i druge slike. Možete pomeriti markere da izaberete vrednosti dve smeše gde će se dugme za pribacivanje koristiti.

note: (para)
en: Sometimes you want to see a difference rather than a blend. You might have the image files for two revisions of a printed circuit board and want to see which tracks have changed. If you disable alpha blend mode, the difference will be shown as an <emphasis>XOR</emphasis> of the pixel colour values. Unchanged areas will be plain white and changes will be coloured.
target: Ponekad želite da vidite razlike pre nego smešu. Možete imati fajlove slike iz dve revizije ploče štampanog kola i želeti da vidite koje su trake promenjene. Ako onemogućite mod alfa smeše razlika će biti prikazana kao <emphasis>XOR</emphasis> vrednosto boje piksela. Nepromenjene površine biće potpuno bele a izmene će biti obojene.

note: (title)
en: External Diff/Merge Tools
target: Spoljašnji Razl/Stopi alat

note: (primary)
en: diff tools
target: razl alat

note: (primary)
en: merge tools
target: alat spajanja

note: (para)
en: If the tools we provide don't do what you need, try one of the many open-source or commercial programs available. Everyone has their own favourites, and this list is by no means complete, but here are a few that you might consider:
target: Ako alat kojim smo se snabdeli ne radi o što nam treb, treba probati jedan od mnogih programa otvorenog koda ili komercijalnih koji su dostupni. Svako ima svoje favorite i ta lista izgleda da nije kompletna, ali evo šta treba razmotriti:

note: (term)
en: WinMerge
target: VinMerdž

note: (para)
en: <ulink url="http://winmerge.sourceforge.net/"><citetitle>WinMerge</citetitle></ulink> is a great open-source diff tool which can also handle directories.
target: <ulink url="http://winmerge.sourceforge.net/"><citetitle>WinMerge</citetitle></ulink> je veliki diff alat otvorenog koda koji takođe opslužje imenike.

note: (term)
en: Perforce Merge
target: Nasilno spajanje

note: (para)
en: Perforce is a commercial RCS, but you can download the diff/merge tool for free. Get more information from <ulink url="http://www.perforce.com/perforce/products/merge.html"><citetitle>Perforce</citetitle></ulink>.
target: Perforce je komercijalni RCS, ali možete skinuti diff/stopi alat besplatno. Uzmite više informacija sa  <ulink url="http://www.perforce.com/perforce/products/merge.html"><citetitle>Perforce</citetitle></ulink>.

note: (para)
en: KDiff3 is a free diff tool which can also handle directories. You can download it from <ulink url="http://kdiff3.sf.net/"><citetitle>here</citetitle></ulink>.
target: KDiff3 je besplatan diff alat koji takođe može da opslužuje imenike. Možete ga skihuti sa <ulink url="http://kdiff3.sf.net/"><citetitle>here</citetitle></ulink>.

note: (term)
en: ExamDiff
target: EgzamDif

note: (para)
en: ExamDiff Standard is freeware. It can handle files but not directories. ExamDiff Pro is shareware and adds a number of goodies including directory diff and editing capability. In both flavours, version 3.2 and above can handle unicode. You can download them from <ulink url="http://www.prestosoft.com/"><citetitle>PrestoSoft</citetitle></ulink>.
target: EgzamDiff Standard je slobodan. Može raditi sa fajlovima ali ne sa imenicima. EgzamDiff Pro je šerver i dodaje brojne pogodnosti uključujući diff  imenika i mogćnosti uređenja. U oba slučaja, verzija 3.2 i iznad koriste junikod. Možete ih skinuti sa <ulink url="http://www.prestosoft.com/"><citetitle>PrestoSoft</citetitle></ulink>.

note: (term)
en: Beyond Compare
target: Posle upoređenja

note: (para)
en: Similar to ExamDiff Pro, this is an excellent shareware diff tool which can handle directory diffs and unicode. Download it from <ulink url="http://www.scootersoftware.com/"><citetitle>Scooter Software</citetitle></ulink>.
target: Sličan EgzamDiff Pro, ovo je je izvanredan šerver diff alat koji radi sa diff imenika i junikodom. Skinite ga sa  <ulink url="http://www.scootersoftware.com/"><citetitle>Scooter Software</citetitle></ulink>.

note: (term)
en: Araxis Merge
target: Araksovo spajanje

note: (para)
en: Araxis Merge is a useful commercial tool for diff and merging both files and folders. It does three-way comparison in merges and has synchronization links to use if you've changed the order of functions. Download it from <ulink url="http://www.araxis.com/merge/index.html"><citetitle>Araxis</citetitle></ulink>.
target: Araksis Merge je koristan komercijalni alat za diff i stapanje fajlova i imenika. On radi trostruko poređenje u stapanju i ima sinhronizacionu vezu za korišćenje ako ste izmenili red funkcija. Skinite ga sa <ulink url="http://www.araxis.com/merge/index.html"><citetitle>Araxis</citetitle></ulink>.

note: (para)
en: This text editor includes syntax colouring for unified diffs, making them much easier to read. Download it from <ulink url="http://www.scintilla.org/SciTEDownload.html"><citetitle>Scintilla</citetitle></ulink>.
target: Ovaj tekst uređivač uključuje bojenje sintakse za ujedinjennj diff, čineći ih mnogo lakšim za čitanje. Skinite ga sa <ulink url="http://www.scintilla.org/SciTEDownload.html"><citetitle>Scintilla</citetitle></ulink>.

note: (para)
en: Notepad2 is designed as a replacement for the standard Windows Notepad program, and is based on the Scintilla open-source edit control. As well as being good for viewing unified diffs, it is much better than the Windows notepad for most jobs. Download it for free <ulink url="http://www.flos-freeware.ch/notepad2.html"><citetitle>here</citetitle></ulink>.
target: Notepad2 je napravljen kao zamena standardnog Vindouz Notepad programa i ima za osnovu Scintila otvoren-kod kontrolu uređenja. Kako je dobar za pregled jedinsvenih diff, mnogo je bolji od Vindouz notepada za većinu posla. Skinite ga besplatno sa <ulink url="http://www.flos-freeware.ch/notepad2.html"><citetitle>here</citetitle></ulink>.

note: (para)
en: Read <xref linkend="tsvn-dug-settings-progs"/> for information on how to set up TortoiseSVN to use these tools.
target: Pročitajte  <xref linkend="tsvn-dug-settings-progs"/> za informacije kako da se podesi TortoiseSVN da koristi ove alate.

note: (title)
en: Adding New Files And Directories
target: Dodavanje novih fajlova i imenika

note: (primary)
en: add
target: dodaj

note: (primary)
en: version new files
target: verzionisati nove fajlove

note: (title)
en: Explorer context menu for unversioned files
target: Eksplorerov kontekst meni za neverzionisane fajlve

note: (para)
en: <placeholder-1/> If you created new files and/or directories during your development process then you need to add them to source control too. Select the file(s) and/or directory and use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Add</guimenuitem></menuchoice>.
target: <placeholder-1/> Ako ste kreirali nove fajlove i/ili imenike u toku procesa razvoja tada vam je potrebno da ih dodate u alat za kontrolu izvernog koda takođe. Izaberite fajl(ove) i/ili imenik i koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Dodaj</guimenuitem></menuchoice>.

note: (para)
en: After you added the files/directories to source control the file appears with a <literal>added</literal> icon overlay which means you first have to commit your working copy to make those files/directories available to other developers. Adding a file/directory does <emphasis>not</emphasis> affect the repository!
target: Posle dodavanja fajlova/imenika kontroli koda fajlovi se pojavljuju sa <literal>dodat</literal> prekrivnom ikonom koja znači da najpre treba da urežete vašu radnu kopiju da učinite ove fajlove/imenike dostupne drugim saradnicima. Dodavanjem fajla/imenika <emphasis>ne</emphasis> ne utiče na spremište.

note: (title)
en: Many Adds
target: Mnogo dodavanja

note: (para)
en: You can also use the Add command on already versioned folders. In that case, the add dialog will show you all unversioned files inside that versioned folder. This helps if you have many new files and need to add them all at once.
target: Takođe možete koristiti Dodaj komandu na već verzionisane imenike. U tom slučaju dodaj dijalog će prikazati sve neverzionisane fajlove unutar verzionisanog imenika. To vam pomaže da ako imate puno novih fajlova da ih dodate odjednom.

note: (para)
en: select the files you want to add
target: izaberite fajlove koje želite da dodate

note: (para)
en: <action>right-drag</action> them to the new location inside the working copy
target: <action>desno-povlačiti</action> njih u novu lokaciju unutar radne kopije.

note: (para)
en: release the right mouse button
target: otpustite desno dugme miša

note: (para)
en: select <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>SVN Add files to this WC</guimenuitem></menuchoice>. The files will then be copied to the working copy and added to version control.
target: izaberite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>SVN Dodaj fajlove u RK</guimenuitem></menuchoice>. Fajlovi će tada biti kopirani u radnu kopiju i dodati u kontrolu verzija.

note: (para)
en: To add files from outside your working copy you can use the drag-and-drop handler: <placeholder-1/>
target: Da bi se dodali falovi van vaše radne kopije možete koristiti uhvati-i-vuci ručicu: <placeholder-1/>

note: (para)
en: You can also add files within a working copy simply by left-dragging and dropping them onto the commit dialog.
target: Možete takođe dodati fajlove u okviru radne kopije jednostavno pomoću levog-vučenja i otpuštanja u dijalog urezivanja.

note: (para)
en: If you add a file or folder by mistake, you can undo the addition before you commit using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Undo add...</guimenuitem></menuchoice>.
target: Ako dodate fajl ili imenik greškom možete poništiti dodavanje pre nego urežete koristeći <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Poništi dodavanje...</guimenuitem></menuchoice>.

note: (title)
en: Copying/Moving/Renaming Files and Folders
target: Kopiranje/Pomeranje/Preimenovanje fajlova i imenika

note: (primary)
en: copy files
target: kopiraj fajlove

note: (primary)
en: rename files
target: preimenuj fajlove

note: (primary)
en: move files
target: pomeri fajlove

note: (primary)
en: branch
target: grana

note: (primary)
en: tag
target: znak

note: (para)
en: It often happens that you already have the files you need in another project in your repository, and you simply want to copy them across. You could simply copy the files and add them as described above, but that would not give you any history. And if you subsequently fix a bug in the original files, you can only merge the fix automatically if the new copy is related to the original in Subversion.
target: Često se dešava to da već imate fajlove koji su vam potrebni u drugom projektu u vašem spremištu i jednostavno želite da ih kopirate unutar. Možete jednostavno kopirati fajlove i dodati ih kako je opisano gore, ali to vam neće dati istoriju. Ako subsekventno fiksirate bagove u originalnim fajlovima možete samo stopiti fiksirano automatski ako se nova kopija odnosi na originalnu Subverziju.

note: (para)
en: The easiest way to copy files and folders from within a working copy is to use the right-drag menu. When you <action>right-drag</action> a file or folder from one working copy to another, or even within the same folder, a context menu appears when you release the mouse. <placeholder-1/> Now you can copy existing versioned content to a new location, possibly renaming it at the same time.
target: Najlakši način da se kopiraju fajlovi i imenici u okviru radne kopije je da se koristi meni desno-povlačenje. Kada <action>desno-vučete</action> fajl ili imenik iz jedne radne kopije u drugu, li čak u okviru istog imenika, kontekst meni se pojavljuje kada otpustite miš. <placeholder-1/> Sada možete kopirati postojeći verzionisani sadržaj u novu lokaciju, moguće preimeovanjem u isto vreme.

note: (para)
en: You can also copy or move versioned files within a working copy, or between two working copies, using the familiar cut-and-paste method. Use the standard Windows <action>Copy</action> or <action>Cut</action> to copy one or more versioned items to the clipboard. If the clipboard contains such versioned items, you can then use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Paste</guimenuitem></menuchoice> (note: not the standard Windows <action>Paste</action>) to copy or move those items to the new working copy location.
target: Možete kopirati ili pomerati verzionisane fajlove unutar radne kopije, ili između dve radne opije, koristeći familijarnu iseci-i-nalepi metod.Koristite standardnu Vindouz <action>Kopiraj</action> ili <action>Iseci</action> da kopirate jednu ili više verzionisanih stavki u klipbord. Ako klipbord sadrži te verzionisane stavke, mžete koristiti <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Nalepi</guimenuitem></menuchoice> (primedba: notirajte standard Vindouz <action>Paste</action>) da kopirate ili pomerite te stavke u novu lokaciju radne kopije.

note: (para)
en: You can copy files and folders from your working copy to another location in the repository using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Branch/Tag</guimenuitem></menuchoice>. Refer to <xref linkend="tsvn-dug-branch-1"/> to find out more.
target: Mžete kopirati fajlove i imenike iz svoje radne kopije na drugu lokaciju u spremištu koristeći <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Grana/Znak</guimenuitem></menuchoice>. Uporedite sa <xref linkend="tsvn-dug-branch-1"/> da nađete više o tome.

note: (para)
en: You can locate an older version of a file or folder in the log dialog and copy it to a new location in the repository directly from the log dialog using <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Create branch/tag from revision</guimenuitem></menuchoice>. Refer to <xref linkend="tsvn-dug-showlog-2"/> to find out more.
target: Možete locirati stariju verziju fajla ili imenika u dnevnik dijalogu i kopirati ih na novu lokaciju u imeniku spremišta direktno iz dnevnik dijaloga koristeći <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Kreiraj grana/znak iz revizije</guimenuitem></menuchoice>. Uporedi sa <xref linkend="tsvn-dug-showlog-2"/> za više detalja.

note: (para)
en: You can also use the repository browser to locate content you want, and copy it into your working copy directly from the repository, or copy between two locations within the repository. Refer to <xref linkend="tsvn-dug-repobrowser"/> to find out more.
target: Takođe možete koristiti  pretraživač spremišta da locirate sadržaj koji želite i da ga kopirate u svoju radnu kopiju direktno iz spremišta, ili da kopirate između dve lokacije unutar spremišta. Uporedite sa <xref linkend="tsvn-dug-repobrowser"/> za više detalja.

note: (title)
en: Cannot copy between repositories
target: Ne može da kopira između spremišta

note: (para)
en: Whilst you can copy and files and folders <emphasis>within</emphasis> a repository, you <emphasis>cannot</emphasis> copy or move from one repository to another while preserving history using TortoiseSVN. Not even if the repositories live on the same server. All you can do is copy the content in its current state and add it as new content to the second repository.
target: Mada možete kopirati fajlove i imenike  <emphasis>unutar</emphasis> spremišta, vi <emphasis>ne možete</emphasis> kopirati ili pomerati iz jednog spremišta u drugo dok čuvate istoriju koristeći TortoiseSVN. Čak ni ako spremište živi na istom serveru. Sve što mžete uraditi je kopiranje sadržaja u njegovom tekućem stanju i dodavanje kao novi sadržaj u drugo spremište.

note: (para)
en: If you are uncertain whether two URLs on the same server refer to the same or different repositories, use the repo browser to open one URL and find out where the repository root is. If you can see both locations in one repo browser window then they are in the same repository.
target: Ako ste nesigurni da li dva URL na istom serveru ukazuju na isti ili različita spremišta, koristite repo pretraživač da otvorite jedan URL i nađite gde je koren spremišta. Ako možete da vidite obe lokacije u jednom repo pretraživač prozoru onda su oni u istom spremištu.

note: (title)
en: Ignoring Files And Directories
target: Zanemarivanje fajlova i imenika

note: (primary)
en: ignore
target: zanemari

note: (primary)
en: unversioned files/folders
target: razverzionisanje fajlova/imenika

note: (para)
en: <placeholder-1/> In most projects you will have files and folders that should not be subject to version control. These might include files created by the compiler, <filename>*.obj, *.lst</filename>, maybe an output folder used to store the executable. Whenever you commit changes, TortoiseSVN shows your unversioned files, which fills up the file list in the commit dialog. Of course you can turn off this display, but then you might forget to add a new source file.
target: <placeholder-1/> U većini projekata vi imate fajlove i imenike koji nisu subjekat kontrole verzija. Oni mogu uključivati fajlove kreirane kompajlerom, <filename>*.obj, *.lst</filename>, možda izlazni imenik korišćen za smeštanje izvršnih fajlova. Kadagod urezujete izmene, TortoiseSVN prikazuje vaše neverzionisane fajlove koji popunjavaju listu u dijalogu urezivanja. Svakako da možete isključiti ovo prikazivanje, ali tada možete zaboraviti da dodate nove fajlove izvornog koda.

note: (para)
en: The best way to avoid these problems is to add the derived files to the project's ignore list. That way they will never show up in the commit dialog, but genuine unversioned source files will still be flagged up.
target: Najbolji način da se izbegnu ovi problemi je da se razvojni fajlovi dodaju listi zanemarenih u projektu. Na taj način oni se nikad ne prikazuju u dijalogu urezivanja, a pravi neverzionisani fajlovi izѕvornog koda su još uvek označeni.

note: (para)
en: If you <action>right click</action> on a single unversioned file, and select the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Add to Ignore List</guimenuitem></menuchoice> from the context menu, a submenu appears allowing you to select just that file, or all files with the same extension. If you select multiple files, there is no submenu and you can only add those specific files/folders.
target: Ako uradite <action>desni klik</action> na pojedini neverzionisani fajl, i izaberete komandu <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Dodaj Listi Zanemarenih</guimenuitem></menuchoice> iz kontekst menija, pojaviće se submeni koji vam omogućava da izaberete samo taj fajl, ili sve fajlove sa istom ekstenzijom. Ako izaberete više fajlova, nema submenija i možete samo da dodate te specifčne fajlove/imenike.

note: (para)
en: If you want to remove one or more items from the ignore list, <action>right click</action> on those items and select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Remove from Ignore List</guimenuitem></menuchoice> You can also access a folder's <literal>svn:ignore</literal> property directly. That allows you to specify more general patterns using filename globbing, described in the section below. Read <xref linkend="tsvn-dug-propertypage"/> for more information on setting properties directly. Please be aware that each ignore pattern has to be placed on a separate line. Separating them by spaces does not work.
target: Ako želite da uklonite jednu ili više stavki iz liste zanemarenih, <action>desni klik</action> na te stavke i izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ukloni sa Liste Zanemarenih</guimenuitem></menuchoice> Možete takođe pristupiti imeniku <literal>svn:ignore</literal> osobina direktno. To vam omogućava da specificirate mnogo opštiji model koristeći globiranje imena fajlova, opisano u sledećem paragrafu. Pročitajte <xref linkend="tsvn-dug-propertypage"/> za više informacija o podešavanju osobina direktno. Molim vas budite pažljivi jer svaki model zanemarivanja mora da bude smešten u posebnoj liniji. Odvajanje razmakom ne radi.

note: (title)
en: The Global Ignore List
target: Globalna lista zanemarivanja

note: (para)
en: Another way to ignore files is to add them to the <firstterm>global ignore list</firstterm>. The big difference here is that the global ignore list is a client property. It applies to <emphasis>all</emphasis> Subversion projects, but on the client PC only. In general it is better to use the <filename>svn:ignore</filename> property where possible, because it can be applied to specific project areas, and it works for everyone who checks out the project. Read <xref linkend="tsvn-dug-settings-main"/> for more information.
target: Drugi nčin da se zanemare fajlovi je da se dodaju u <firstterm>globalnu listu zanemarivanja</firstterm>. Velika razlika ovde je da je globalna lista zanemarivanja je klijentska osobina. Primenjuje se na  <emphasis>sve</emphasis> Subverzione projekte, ali na samo na klijentovom PC. Generalno je bolje da se koristi  <filename>svn:ignore</filename> osobina kada je moguće jer može biti primenjena na specifičnu oblast projekta, i to radi za svakog ko preuzme projekat. Pročitajte <xref linkend="tsvn-dug-settings-main"/> za više informacija.

note: (title)
en: Ignoring Versioned Items
target: Zanemarivanje verzionisanih stavki

note: (para)
en: Versioned files and folders can never be ignored - that's a feature of Subversion. If you versioned a file by mistake, read <xref linkend="tsvn-howto-unversion"/> for instructions on how to <quote>unversion</quote> it.
target: Verzionisani fajlovi i imenici ne mogu biti nikad zanemareni - to je osobina Subverzije. Ako verzionišete fajl greškom pročitajte <xref linkend="tsvn-howto-unversion"/> za instrukcije kako da ga <quote>odverzionišete</quote>.

note: (title)
en: Pattern Matching in Ignore Lists
target: Hvatanje modela u listi zanemarivanja

note: (primary)
en: pattern matching
target: hvatanje modela

note: (para)
en: Matches any string of characters, including the empty string (no characters).
target: Čini sličnim svaki string karaktera, uključujući prazan string (bez karaktera).

note: (para)
en: Matches any single character.
target: Hvatanje bilo kog pojedinog karaktera.

note: (para)
en: Matches any one of the characters enclosed in the square brackets. Within the brackets, a pair of characters separated by <quote>-</quote> matches any character lexically between the two. For example <literal>[AGm-p]</literal> matches any one of <literal>A</literal>, <literal>G</literal>, <literal>m</literal>, <literal>n</literal>, <literal>o</literal> or <literal>p</literal>.
target: Čini sličnim bilo koji karakter zatvoren u srednjoj zagradi. U okviru zagrada, par karaktera odvojenih sa <quote>-</quote> čine sličnim svaki karakter leksički između ta dva. Na primer <literal>[AGm-p]</literal> čini sličnim svaki od <literal>A</literal>, <literal>G</literal>, <literal>m</literal>, <literal>n</literal>, <literal>o</literal> or <literal>p</literal>.

note: (para)
en: Subversion's ignore patterns make use of filename globbing, a technique originally used in Unix to specify files using meta-characters as wildcards. The following characters have special meaning: <placeholder-1/>
target: Subverzioni model zanemarivanja  koristi globalisanje imena fajlova kao tehniku originalno korićenu u Uniksu da se specificiraju fajlovi koristeći meta-karaktere kao džokere. Sledeći karakteri imaju specijalna značenja:  <placeholder-1/>

note: (para)
en: Subversion uses the <literal>/</literal> as the path delimiter in all internal pathnames, and all pattern matching is done against this style of path names. If you want to use a path delimiter in your ignore pattern, be sure to use <literal>/</literal>, and not the Windows backslash.
target: Subverzija koristi <literal>/</literal> kao ograničavač putanje u svim internim imenima putanje, i svi modeli sparivanja su dati prema tom stilu imena fajlova. Ako želite da koristite ograničavač putanje u modelu zanemarivanja budite sigurni da koristite <literal>/</literal>, a ne Vindouz obratnu kosu crtu.

note: (para)
en: Pattern matching is case sensitive, which can cause problems on Windows. You can force case insensitivity the hard way by pairing characters, eg. to ignore <literal>*.tmp</literal> regardless of case, you could use a pattern like <literal>*.[Tt][Mm][Pp]</literal>.
target: Model sparivanja zavisi od veličine slova, što može uzrokovati problem na Vindouzu. Možete fosirati nezavisnost od veličine slova na teži način sparivanjem karaktera, tj. zanemarivanjem <literal>*.tmp</literal>  bezobzira od veličine slova, možete koristiti model <literal>*.[Tt][Mm][Pp]</literal>.

note: (para)
en: Subversion uses this pattern matching against every path presented to it for action. These paths are generally relative to the directory being acted upon for import, add, commit, etc. The matching pattern therefore has to take account of the fact that there may or may not be path components before the filename.
target: Subverzija koristi model sparivanja prema svakoj putanji koja joj se prikaže za akciju. Ove putanje su uopšteno relativne na imenik aktiviran za uvoz, dodavanje, urezivanje, itd. Model sparivanja tada ima da uzme u obzir činjenicu da može ili ne može biti komponenti putanje pre imena fajla.

note: (para)
en: If directory names are present in a path, the matching algorithm will not trim them off, so pattern <literal>Fred.*</literal> will match <literal>Fred.c</literal> but not <literal>subdir/Fred.c</literal>. This is significant if you add a folder which contains some files that you want to be ignored, because those filenames will be preceded with the folder name when Subversion compares them with the ignore pattern.
target: Ako je ime imenika prisutno u putanji algoritam sparivanja neće ga skresati tako da će model <literal>Fred.*</literal> spariti <literal>Fred.c</literal> ali ne <literal>subdir/Fred.c</literal>. Ovo je značajno ako dodate imenik koji sadrži neke fajlove koje želite da budu zanemareni, jer ta fajlimena su predvođena imenom imenika kada ih Subverzija poredi sa modelom zanemarivanja.

note: (para)
en: The <literal>/</literal> character is not treated in any special way for pattern matching purposes, so the pattern <literal>abc*xyz</literal> would match <literal>abcdxyz</literal> but also <literal>abcdir/subdir/anything/morexyz</literal>.
target: Karakte <literal>/</literal> se ne tretira na bilo koji specijalni način u svrhe modela sprivanja tako da model <literal>abc*xyz</literal> sparuje <literal>abcdxyz</literal> ali takođe <literal>abcdir/subdir/anything/morexyz</literal>.

note: (para)
en: To ignore all <literal>CVS</literal> folders you should either specify a pattern of <literal>*CVS</literal> or better, the pair <literal>CVS */CVS</literal>. The first option works, but would also exclude something called <literal>ThisIsNotCVS</literal>. Using <literal>*/CVS</literal> alone will not work on an immediate child <literal>CVS</literal> folder, and <literal>CVS</literal> alone will not work on sub-folders.
target: Da bi se zanemarili svi <literal>CVS</literal> imenici treba da specificirate model <literal>*CVS</literal> ili bolje, par <literal>CVS */CVS</literal>. Prva opcija radi, ali će takođe isključiti nešto kao  <literal>ThisIsNotCVS</literal>. Koristeći <literal>*/CVS</literal> samo neće raditi na direktni potomak <literal>CVS</literal> imenik, i <literal>CVS</literal> sam neće raditi na sub-imenicima.

note: (para)
en: If you want an official definition for globbing, you can find it in the IEEE specifications for the shell command language <ulink url="http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_13"><citetitle>Pattern Matching Notation</citetitle></ulink>.
target: Ako želite zvaničnu definiciju globalisanja naćićete je u IEEE specifikacijama za komandni jezik školjke  <ulink url="http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_13"><citetitle>Pattern Matching Notation</citetitle></ulink>.

note: (title)
en: Deleting, Moving and Renaming
target: Brisanje, pomeranje i preimenovanje

note: (title)
en: Explorer context menu for versioned files
target: Eksplorerov kontekst meni za verzionisane fajlove

note: (para)
en: Unlike CVS, Subversion allows renaming and moving of files and folders. So there are menu entries for delete and rename in the TortoiseSVN submenu. <placeholder-1/>
target: Suprotno CVS, Subverzija dozvoljava preimenovanje i pomeranje fajlova i imenika. Tako da ima meni ulaza za brisanje i preimenovanje u TortoiseSVN submeniju. <placeholder-1/>

note: (title)
en: Deleting files and folders
target: Brisanje fajlova i imenika

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

note: (primary)
en: remove
target: ukloni

note: (para)
en: Use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Delete</guimenuitem></menuchoice> to remove files or folders from subversion.
target: Koristi <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Briši</guimenuitem></menuchoice> da se uklone fajlovi i imenici iz subverzije.

note: (para)
en: When you <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Delete</guimenuitem></menuchoice> a file, it is removed from your working copy immediately as well as being marked for deletion in the repository on next commit. The file's parent folder shows a <quote>deleted</quote> icon overlay. Up until you commit the change, you can get the file back using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revert</guimenuitem></menuchoice> on the parent folder.
target: Kada uradite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Briši</guimenuitem></menuchoice> fajl, to ukloni iz vaše radne kopije trenutno kao što i markira za brisanje u spremištu pri sledećem urezivanju. Predački imenik fajla prikazuje <quote>obrisan</quote> prekrivnu ikonu. Sve dok ne urežete izmene možete vratiti fajlove nazad koristeći  <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Vrati</guimenuitem></menuchoice>  na predački imenik.

note: (para)
en: When you <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Delete</guimenuitem></menuchoice> a folder, it remains in your working copy, but the overlay changes to indicate that it is marked for deletion. Up until you commit the change, you can get the folder back using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revert</guimenuitem></menuchoice> on the folder itself. This difference in behaviour between files and folders is a part of Subversion, not TortoiseSVN.
target: Kada <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Briši</guimenuitem></menuchoice> imenik, ostaje u vašoj radnoj kopiji, ali se prekrivač menja da indicira da je markiran za brisanje. Sve dok ne urežete izmene možete vratiti imenik koristeći <menuchoice><guimenu>TortoiseSVna N</guimenu><guimenuitem>Vrati</guimenuitem></menuchoice>  na sam imenik. Ova razlika u ponašanju među fajlovima i imenicima je deo Subverzije, ne TortoiseSVN.

note: (para)
en: If you want to delete an item from the repository, but keep it locally as an unversioned file/folder, use <menuchoice><guimenu>Extended Context Menu</guimenu><guimenuitem>Delete (keep local)</guimenuitem></menuchoice>. You have to hold the <keycap>Shift</keycap> key while right clicking on the item in the explorer list pane (right pane) in order to see this in the extended context menu.
target: Ako želite da obrišete stavku iz spremišta, ali da je zadržite lokalno kaoneverzionisani fajl/imenik, koristite <menuchoice><guimenu>Prišireni Kontekst Meni</guimenu><guimenuitem>Briši (čuvaj lokalno)</guimenuitem></menuchoice>. Treba da držite <keycap>Shift</keycap> taster kada desno kliknete na stavku u pretraživačevom list panelu (desni panel) da bi ga videli  u proširenom kontekst meniju.

note: (para)
en: If a <emphasis>file</emphasis> is deleted via the explorer instead of using the TortoiseSVN context menu, the commit dialog shows those files and lets you remove them from version control too before the commit. However, if you update your working copy, Subversion will spot the missing file and replace it with the latest version from the repository. If you need to delete a version-controlled file, always use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Delete</guimenuitem></menuchoice> so that Subversion doesn't have to guess what you really want to do.
target: Ako je <emphasis>fajl</emphasis> obrisan preko pretraživača umesto korišćenjem TortoiseSVN kontekst menija, dijalog urezivanja prikazuje te fajlove i dozvoljava vam da ih uklonite iz kontrole verzija pre urezivanja takođe. Međutim, ako ažurirate vašu radnu kopiju, Subverzija će obeležiti fajl koji nedostaje i zameniti ga sa zadnjom verzijom iz spremišta. Ako vam treba da obrišete verzija-kontrolisan fajl, uvek koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Briši</guimenuitem></menuchoice> tako da Subverzija ne mora da pogađa šta vi stvarno želite da uradite.

note: (para)
en: If a <emphasis>folder</emphasis> is deleted via the explorer instead of using the TortoiseSVN context menu, your working copy will be broken and you will be unable to commit. If you update your working copy, Subversion will replace the missing folder with the latest version from the repository and you can then delete it the correct way using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Delete</guimenuitem></menuchoice>.
target: Ako je <emphasis>imenik</emphasis>  izbrisan preko pretraživača umesto koristići TortoiseSVN kontekst meni, vaša radna kopija će biti oštećena i vi nećeti moći da je urežete. Ako ažurirate vašu radnu kopiju Subverzija će zameniti nedostajući imenik sa zadnjom verzijom iz spremišta i možete ga tada obrisati na ispravan način koristeći <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Obriši</guimenuitem></menuchoice>.

note: (title)
en: Getting a deleted file or folder back
target: Vraćanje izbrisanih fajlova i imenika

note: (para)
en: If you have deleted a file or a folder and already committed that delete operation to the repository, then a normal <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revert</guimenuitem></menuchoice> can't bring it back anymore. But the file or folder is not lost at all. If you know the revision the file or folder got deleted (if you don't, use the log dialog to find out) open the repository browser and switch to that revision. Then select the file or folder you deleted, right-click and select <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Copy to...</guimenuitem></menuchoice> as the target for that copy operation select the path to your working copy.
target: Ako ste obrisali fajl ili imenik i već ste urezali tu operaciju brisanja onda normalno <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Vrati</guimenuitem></menuchoice> ne može da to vrati uopšte. Ali fajl ili imenik nije izgubljen potpuno. Ako znate reviziju fajla ili imenika uzmite obrisane (ako ne, koristite dnevnik dijalog da ih nađete) otvorite pretraživač spremišta i prebacite na tu reviziju. Zatim izaberite fajl ili imenik koje ste obrisali, desni klik i izaberite  <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Kopiraj u...</guimenuitem></menuchoice> kao cilj za tu operaciju kopiralja izaberite putanju u vašoj radnoj kopiji.

note: (title)
en: Moving files and folders
target: Pomeranje fajlova i imenika

note: (primary)
en: rename
target: preimenuj

note: (primary)
en: move
target: pomeri

note: (para)
en: If you want to do a simple in-place rename of a file or folder, use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Rename...</guimenuitem></menuchoice> Enter the new name for the item and you're done.
target: Ako želite da uradite jednostavno na-mestu preimenovanje fajla ili imenika, koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Preimenuj...</guimenuitem></menuchoice> Unesite novo ime za stavku i uradite.

note: (para)
en: select the files or directories you want to move
target: izbor fajlova ili imenika koje želite da pomerite

note: (para)
en: in the popup menu select <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>SVN Move versioned files here</guimenuitem></menuchoice>
target: u popap meniju izaberite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>SVN Pomeri verzionisani fajl ovde</guimenuitem></menuchoice>

note: (para)
en: If you want to move files around inside your working copy, perhaps to a different sub-folder, use the right-mouse drag-and-drop handler: <placeholder-1/>
target: Ako želite da pomerite fajlove okolo unutar vaše radne kopije, možda u različit sub-imenik, koristite desni-miš vuci-i-baci ručicu: <placeholder-1/>

note: (title)
en: Commit the parent folder
target: urezivanje predačkog imenika

note: (para)
en: Since renames and moves are done as a delete followed by an add you must commit the parent folder of the renamed/moved file so that the deleted part of the rename/move will show up in the commit dialog. If you don't commit the removed part of the rename/move, it will stay behind in the repository and when your co-workers update, the old file will not be removed. i.e. they will have <emphasis>both</emphasis> the old and the new copies.
target: Kako su preimenovanje i pomeranje dati kao brisanje praćeno dodavanjem morate urezati predački imenik preimenovanih/pomerenih fajlova tako da obrisani deo preimenovanja/pomeranja će se prikazati u dijalogu urezivanja. Ako ne urežete uklonjeni deo preimenuj/pomeri, on će ostati iza u spremištu i kada vaš saradnik ažurira stari fajl neće biti uklonjen. tj. on će imati <emphasis>obe</emphasis> staru i novu kopiju.

note: (para)
en: You <emphasis>must</emphasis> commit a folder rename before changing any of the files inside the folder, otherwise your working copy can get really messed up.
target: Vi <emphasis>morate</emphasis> urezati preimenovanje imenika pre izmena bilo kog fajla u imeniku, drugačije vaša radna kopija će stvarni biti zabrljana.

note: (para)
en: You can also use the repository browser to move items around. Read <xref linkend="tsvn-dug-repobrowser"/> to find out more.
target: Možete takođe koristiti pretraživač spremišta da pomerate stavke naokolo. Pročitajte <xref linkend="tsvn-dug-repobrowser"/> da nađete više detalja.

note: (title)
en: Do Not SVN Move Externals
target: Nemojte da SVN pomera eksternale

note: (para)
en: You should <emphasis>not</emphasis> use the TortoiseSVN <guilabel>Move</guilabel> or <guilabel>Rename</guilabel> commands on a folder which has been created using <literal>svn:externals</literal>. This action would cause the external item to be deleted from its parent repository, probably upsetting many other people. If you need to move an externals folder you should use an ordinary shell move, then adjust the <literal>svn:externals</literal> properties of the source and destination parent folders.
target: Vi <emphasis>ne</emphasis> treba da koristite TortoiseSVN <guilabel>Pomeri</guilabel> ili <guilabel>Preimenuj</guilabel> komande na imenicima koji su kreirani korišćenjem <literal>svn:externals</literal>. Ova akcija će prouzrokovati da se spoljašnja stavka obriše iz svog predačkog spremišta, verovatno unesretivši mnogo drugih ljudi. Ako treba da pomerite spoljašnji imenik treba koristiti obično pomeranje iz školjke, zatim podesite  <literal>svn:externals</literal> osobine predačkog imenika izvora i odredišta.

note: (title)
en: Changing case in a filename
target: Izmena velikih i malih slova u imenima fajla

note: (primary)
en: case change
target: izmena velikih i malih slova

note: (para)
en: Making case-only changes to a filename is tricky with Subversion on Windows, because for a short time during a rename, both filenames have to exist. As Windows has a case-insensitive file system, this does not work using the usual Rename command.
target: Praveći izmene u veličini slova u fajlimenu je trik sa Subverzijom u Vindouzu, jer u kratkom periodu u toku preimenovanja, oba fajlimena postoje. Kako Vindouz ima fajl sistem nezavisan od veličine slova ovo ne radi korišćenjem obične Preimenuj komande.

note: (para)
en: Fortunately there are (at least) two possible methods to rename a file without losing its log history. It is important to rename it within subversion. Just renaming in the explorer will corrupt your working copy!
target: Srećom postoji (najmanje) dva moguća metoda za preimenovanje fajla bez gubtka njegove istorije. Važno je da se on preimenuje u okviru subverzije. Samo preimenovanje u pretraživaču pokvariće vašu radnu kopiju!

note: (para)
en: Commit the changes in your working copy.
target: Urezivanje izmena u vašoj radnoj kopiji.

note: (para)
en: Rename the file from UPPERcase to upperCASE directly in the repository using the repository browser.
target: Preimenujte fajl iz  UPPERcase u upperCASE direktno u spremištu koristeći pretraživač spremišta.

note: (para)
en: Update your working copy.
target: Ažuriranje vaše radne kopije.

note: (para)
en: Solution A) (recommended) <placeholder-1/>
target: Rešenje A) (preporučeno) <placeholder-1/>

note: (para)
en: Rename from UPPERcase to UPPERcase_ with the rename command in the TortoiseSVN submenu.
target: Preimenujte UPPERcase u UPPERcase_ sa komandom preimenovanja u TortoiseSVN submeniju.

note: (para)
en: Commit the changes.
target: Urezivanje promena.

note: (para)
en: Rename from UPPERcase_ to upperCASE.
target: Preimenuj iz UPPERcase_ u upperCASE.

note: (para)
en: Solution B) <placeholder-1/>
target: Rešenje B) <placeholder-1/>

note: (title)
en: Dealing with filename case conflicts
target: Rad sa konfliktom veličine slova u imenu fajla

note: (para)
en: If the repository already contains two files with the same name but differing only in case (e.g. <filename>TEST.TXT</filename> and <filename>test.txt</filename>), you will not be able to update or checkout the parent directory on a Windows client. Whilst Subversion supports case-sensitive filenames, Windows does not.
target: Ako spremište već sadrži dva fajla sa istim imenom koji se razlikuju samo u veličini slova (npr. <filename>TEST.TXT</filename> i <filename>test.txt</filename>), vi nećete moći da ažurirate ili preuzmete predački imenik na Vindouz klijentu. Pošto Subverzija podržava fajlimena zavisna od veličine slova, Vindouz to ne radi.

note: (para)
en: This sometimes happens when two people commit, from separate working copies, files which happen to have the same name, but with a case difference. It can also happen when files are committed from a system with a case-sensitive file system, like Linux.
target: Ovo se ponekad dešava kada dva čoveka urezuju, iz posebnih radnih kopija, fajlove za koje se desi da imaju ista imena, ali sa razlikom u veličini slova. To se takođe dešava kada su fajlovi urezani iz sistema sa fajlsistemom koji razlikuje veličinu slova kao Linuks.

note: (para)
en: In that case, you have to decide which one of them you want to keep and delete (or rename) the other one from the repository.
target: U tom slučaju morate odlučiti koji od njih želite da zadržite i obrišete (ili preimenujete) drugi iz spremišta.

note: (title)
en: Preventing two files with the same name
target: Preduprediti dva fajla sa istim imeno

note: (para)
en: There is a server hook script available at: <ulink url="http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/"><citetitle>http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/</citetitle></ulink> that will prevent checkins which result in case conflicts.
target: Postoji server zakačiva skripta dostupna na:  <ulink url="http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/"><citetitle>http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/</citetitle></ulink> koja će preduprediti proveru koja rezultira konfliktom usled veličine slova.

note: (title)
en: Repairing File Renames
target: Ispravka preimenovanja fajlova

note: (para)
en: Sometimes your friendly IDE will rename files for you as part of a refactoring exercise, and of course it doesn't tell Subversion. If you try to commit your changes, Subversion will see the old filename as missing and the new one as an unversioned file. You could just check the new filename to get it added in, but you would then lose the history tracing, as Subversion does not know the files are related.
target: Ponekad vaš prijateljski IDE će preimenovati fajlove za vas kao deo pravljenja primera, i svakako to ne kaže Subverziji. Ako pokušate da urežete svoje izmene Subverzija će videti stara fajlimena kao nedostajuća i nova kao neverzionisane fajlove. Možete samo proveriti novo fajlime da dodate ali tada gubite sliku istorije pošto Subverzija nezna fajlove na koje se odnosi.

note: (para)
en: A better way is to notify Subversion that this change is actually a rename, and you can do this within the <guilabel>Commit</guilabel> and <guilabel>Check for Modifications</guilabel> dialogs. Simply select both the old name (missing) and the new name (unversioned) and use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Repair Move</guimenuitem></menuchoice> to pair the two files as a rename.
target: Bolji način je da se notira Subverzija da su ove izmene u stvari preimenovanja i možete to uraditi u okviru  <guilabel>Ureži</guilabel> i <guilabel>Proveri Modifikaciju</guilabel> dijalog. Jednostavno izaberite staro ime (nedostaje) i novo ime (neverzionisano) i koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Popravi Pomeri</guimenuitem></menuchoice> da uparite dva fajla kao preimenovanje.

note: (title)
en: Deleting Unversioned Files
target: Brisanje neverzionisanih fajlova

note: (para)
en: Usually you set your ignore list such that all generated files are ignored in Subversion. But what if you want to clear all those ignored items to produce a clean build? Usually you would set that in your makefile, but if you are debugging the makefile, or changing the build system it is useful to have a way of clearing the decks.
target: Obično podešavate listu zanemarivanja tako da su svi generisani fajlvi zanemareni u Subverziji. Ali šta ako želite da očistite sve zanemarene stavke da bi izradili čistu gradnju? Obično to podešavate u mejkfajlu ali ako debagujete mejkfajl ili menjanjem sistema izgradnje korisno je da se ima način čišćenja platforme.

note: (para)
en: TortoiseSVN provides just such an option using <menuchoice><guimenu>Extended Context Menu</guimenu><guimenuitem>Delete unversioned items...</guimenuitem></menuchoice>. You have to hold the <keycap>Shift</keycap> while right clicking on a folder in the explorer list pane (right pane) in order to see this in the extended context menu. This will produce a dialog which lists all unversioned files anywhere in your working copy. You can then select or deselect items to be removed.
target: TortoiseSVN omogućava upravo takvu opciju korišćenjem <menuchoice><guimenu>Prošireni Kontekst Meni</guimenu><guimenuitem>Briši neverzionisane stavke...</guimenuitem></menuchoice>. Držite <keycap>Shift</keycap> dok desno kliknete na imenik u panelu liste pretraživača (desni panel) da bi videli ovo u proširenom kontekst meniju. Ovo će proizvesti dijalog koji lista sve neverzionisane fajlove bilo gde u vašoj radnoj kopiji. Možete zatim izabrati stavke za uklanjanje.

note: (para)
en: When such items are deleted, the recycle bin is used, so if you make a mistake here and delete a file that should have been versioned, you can still recover it.
target: Kada se te stavke obrišu korpa za otpatke se koristi tako da ako napravite grešku i obrišete fajl koji treba da bude verzionisan još uvek ga možete povratiti.

note: (title)
en: Undo Changes
target: Poništi izmene

note: (primary)
en: revert
target: vrati

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

note: (title)
en: Revert dialog
target: Vrati dijalog

note: (para)
en: If you want to undo all changes you made in a file since the last update you need to select the file, <action>right click</action> to pop up the context menu and then select the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revert</guimenuitem></menuchoice> A dialog will pop up showing you the files that you've changed and can revert. Select those you want to revert and click on <guibutton>OK</guibutton>. <placeholder-1/>
target: Ako želite poništiti sve izmene koje ste uradili u fajlu od zadnjeg ažuriranja potrebno je da izaberete fajl, <action>desni klik</action> da iskoči kontekst meni i zatim izaberite komandu <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Vrati</guimenuitem></menuchoice> Dijalog će iskočiti prikazijući vam fajlove koje ste izmenili i vratili. Izaberite one koje želite da vratite i kliknite na <guibutton>OK</guibutton>. <placeholder-1/>

note: (para)
en: If you want to undo a deletion or a rename, you need to use Revert on the parent folder as the deleted item does not exist for you to right-click on.
target: Ako želite da poništite brisanje ili preimenovanje, potrebno je da koristite Vrati na predački imenik jer obrisani ne postoje da kliknete na njih.

note: (para)
en: If you want to undo the addition of an item, this appears in the context menu as <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Undo add...</guimenuitem></menuchoice>. This is really a revert as well, but the name has been changed to make it more obvious.
target: Ako želite poništiti dodavanje stavke to se pojavljuje u kontekst meniju kao <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Poništi Dodaj...</guimenuitem></menuchoice>. Ovo zaista vraća ali ime je promenjeno da ga učini mnogo uočljivijim.

note: (para)
en: The columns in this dialog can be customized in the same way as the columns in the <guilabel>Check for modifications</guilabel> dialog. Read <xref linkend="tsvn-dug-wcstatus-2"/> for further details.
target: Kolone u ovom dijalogu mogu se podesiti na isti način kao kolone u <guilabel>Proveri za modifikaciju</guilabel> dijalogu. Pročitajte <xref linkend="tsvn-dug-wcstatus-2"/> za više detalja.

note: (title)
en: Undoing Changes which have been Committed
target: Poništavanje izmena koje su urezane

note: (para)
en: <menuchoice><guimenuitem>Revert</guimenuitem></menuchoice> will only undo your local changes. It does <emphasis>not</emphasis> undo any changes which have already been committed. If you want to undo all the changes which were committed in a particular revision, read <xref linkend="tsvn-dug-showlog"/> for further information.
target: <menuchoice><guimenuitem>Vrati</guimenuitem></menuchoice> samo poništava vaše lokalne izmene. To <emphasis>ne</emphasis> poništava bilo koju izmenu koja je već urezana. Ako želite da poništite sve izmene koje su urezane u posebnoj reviziji pročitajte <xref linkend="tsvn-dug-showlog"/> za dodatne informacije.

note: (title)
en: Revert is Slow
target: Vraćanje je sporo

note: (para)
en: When you revert changes you may find that the operation takes a lot longer than you expect. This is because the modified version of the file is sent to the recycle bin, so you can retrieve your changes if you reverted by mistake. However, if your recycle bin is full, Windows takes a long time to find a place to put the file. The solution is simple: either empty the recycle bin or deactivate the <guilabel>Use recycle bin when reverting</guilabel> box in TortoiseSVN's settings.
target: Kada vratite izmene možete naći da ta operacija traje duže nego ste očekivali. To je zato što se izmenjena verzija fajla šalje u korpu tako da možete vratiti izmene ako ste pogrešili. Međutim, ako je korpa puna Vindouz uzima puno vremena da nađe mesto da stavi fajl. Rešenje je jednostavno: ili ispraznite korpu ili deaktivirajte <guilabel>Koristite korpu pri vraćanju</guilabel> boks u TortoiseSVN podešavanju.

note: (title) (entry) (glossterm)
en: Cleanup
target: Čišćenje

note: (primary)
en: cleanup
target: čišćenje

note: (para)
en: If a Subversion command cannot complete successfully, perhaps due to server problems, your working copy can be left in an inconsistent state. In that case you need to use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Cleanup</guimenuitem></menuchoice> on the folder. It is a good idea to do this at the top level of the working copy.
target: Ako Subverziona komanda ne može da se završi uspešno, moguće zbog problema na serveru, vaša radna kopija biće ostavljena u nekonzistentnom stanju. U tom slučaju treba da koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Čišćenje</guimenuitem></menuchoice> na imeniku. To je dobra ideja da se uradi na vršnom nivou radne kopije.

note: (para)
en: Cleanup has another useful side effect. If a file date changes but its content doesn't, Subversion cannot tell whether it has really changed except by doing a byte-by-byte comparison with the pristine copy. If you have a lot of files in this state it makes acquiring status very slow, which will make many dialogs slow to respond. Executing a Cleanup on your working copy will repair these <quote>broken</quote> timestamps and restore status checks to full speed.
target: Čišćenje ima i drugi propratni efekat. Ako je datum fajla promenjen a sadržaj nije, Subverzija ne može reći da li je zaista izmenjen osim proverom bajt-po-bajt sa čistom kopijom. Ako imate puno fajlova u ovom stanju provera statusa je vrlo spora što će uraditi puno dijaloga sporo odgovaranje. Izvršavanjem Čišćenja na radnoj kopiji popraviće <quote>poremećene</quote> vremenske markere i povratiti status provere punom brzinom.

note: (title)
en: Use Commit Timestamps
target: Koristi vremenske markere urezivanja

note: (para)
en: Some earlier releases of Subversion were affected by a bug which caused timestamp mismatch when you check out with the <guilabel>Use commit timestamps</guilabel> option checked. Use the Cleanup command to speed up these working copies.
target: Neke ranije realizacije Subverzije su imale bag koji je uzrokovao onflikt vremenskih markera kada ih proveravate sa  <guilabel>Koristi urezivanje vremenskih markera</guilabel> proverom opcija. Koristite Čišćenje komandu da ubrzate ove radne kopije.

note: (title)
en: Project Settings
target: Podešavanje projekta

note: (primary)
en: properties
target: osobine

note: (title)
en: Explorer property page, Subversion tab
target: Vlasnički list eksplorera, Subverzioni tab

note: (para)
en: <placeholder-1/> Sometimes you want to have more detailed information about a file/directory than just the icon overlay. You can get all the information Subversion provides in the explorer properties dialog. Just select the file or directory and select <menuchoice><guimenu>Windows Menu</guimenu><guimenuitem>properties</guimenuitem></menuchoice> in the context menu (note: this is the normal properties menu entry the explorer provides, not the one in the TortoiseSVN submenu!). In the properties dialog box TortoiseSVN has added a new property page for files/folders under Subversion control, where you can see all relevant information about the selected file/directory.
target: <placeholder-1/> Ponekad želite da imate detaljnije informacije o fajl/imenik nego što je prekrivna ikona. Možete dobiti sve informacije koje Subverzija daje u dijalogu osobina pretraživača. Samo izaberite fajl ili imenik i izaberite <menuchoice><guimenu>Vindouz Meni</guimenu><guimenuitem>Osobine</guimenuitem></menuchoice> u kontekst meniju (primedba: to je normalan meni osobina ulaz koji daje pretraživač, nije deo TortoiseSVN submenija!). U dijalogu osobina TortoiseSVN dodaje novu stranu osobina za fajlove/imenike pod Subverzijinom kontrolom, gde možete videti relevantne informacije o izabranom fajlu/imeniku.

note: (title)
en: Subversion Properties
target: Subverzione osobine

note: (primary)
en: Subversion properties
target: Subverzione osobine

note: (title)
en: Subversion property page
target: Subverzioni vlasnički list

note: (para)
en: <placeholder-1/> You can read and set the Subversion properties from the Windows properties dialog, but also from <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>properties</guimenuitem></menuchoice> and within TortoiseSVN's status lists, from <menuchoice><guimenu>Context menu</guimenu><guimenuitem>properties</guimenuitem></menuchoice>.
target: <placeholder-1/> Možete čitati i podesiti Subverzione osobine iz Vindouz osobine dijaloga, ali takođe iz <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>osobine</guimenuitem></menuchoice> i u okviru TortoiseSVN statusne liste iz <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>osobine</guimenuitem></menuchoice>.

note: (para)
en: You can add your own properties, or some properties with a special meaning in Subversion. These begin with <literal>svn:</literal>. <literal>svn:externals</literal> is such a property; see how to handle externals in <xref linkend="tsvn-dug-import-4"/>.
target: Možete dodatu vaše lične osobine, ili neke osobine sa specifičnim značenjem u Subverziji. To što počinje sa <literal>svn:</literal>. <literal>svn:externals</literal> je takva osobinač vidite kako se rukuje eksternalima u xref linkend="tsvn-dug-import-4"/>.

note: (title)
en: svn:keywords
target: svn:ključnereči

note: (primary)
en: keywords
target: ključne reči

note: (primary)
en: expand keywords
target: proširenje ključnih reči

note: (para)
en: Date of last known commit. This is based on information obtained when you update your working copy. It does <emphasis>not</emphasis> check the repository to find more recent changes.
target: Datum zadnjeg poznatog urezivanja. Ovo je zasnovano na informaciju dobijenu kada ste ažurirali vašu radnu kopiju. To <emphasis>ne</emphasis>  proverava spremište da nađe najskorije izmene.

note: (para)
en: Revision of last known commit.
target: Revizija zadnje poznatog urezvanja.

note: (para)
en: Author who made the last known commit.
target: Autor koji je uradio zadnje poznato urezivanje.

note: (para)
en: The full URL of this file in the repository.
target: Pun URL ovog fajla u spremištu.

note: (para)
en: A compressed combination of the previous four keywords.
target: Komprimovana kombinacija prethodne četiri ključne reči.

note: (para)
en: Subversion supports CVS-like keyword expansion which can be used to embed filename and revision information within the file itself. Keywords currently supported are: <placeholder-1/>
target: Subverzija podržava CVS-slične proširenje ključnih reči koje se mogu koristiti da uglave fajlime i revizionu informaciju u sam fajl. Ključne reči trenutno podržane su: <placeholder-1/>

note: (para)
en: To find out how to use these keywords, look at the <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.props.special.keywords.html"><citetitle>svn:keywords section</citetitle></ulink> in the Subversion book, which gives a full description of these keywords and how to enable and use them.
target: Da biste našli kako da koristite ključne reči pogledajte na <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.props.special.keywords.html"><citetitle>svn:keywords section</citetitle></ulink> u Subverzionoj knjizi, koja vam daje pun opis ovih ključnih reči i kako ih omogućiti i koristiti.

note: (para)
en: For more information about properties in Subversion see the <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html"><citetitle>Special Properties</citetitle></ulink>.
target: Dalje informacije o svnservu mogu se naći na <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html"><citetitle>Specijalne osobine</citetitle></ulink>.

note: (title)
en: Adding and Editing Properties
target: Dodavanje i uređenje osobina.

note: (title)
en: Adding properties
target: Dodavanje osobina

note: (para)
en: <placeholder-1/> To add a new property, first click on <guilabel>Add...</guilabel>. Select the required property name from the combo box, or type in a name of your own choice, then enter a value in the box below. Properties which take multiple values, such as an ignore list, can be entered on multiple lines. Click on <guibutton>OK</guibutton> to add that property to the list.
target: <placeholder-1/> Da biste dodali nove osobine najpre kliknite na <guilabel>Dodaj...</guilabel>. Izaberite ime željene osobine iz kombo boksa, ili ukucajte ime po vašem izboru, zatim unesite vrednost u boks ispod. Osobine koje imaju višestruke vrednosti, kao što je lista zanemarivanja, mogu se uneti u više linija. Kliknite na <guibutton>OK</guibutton> i dodajte tu osobinu u listu.

note: (para)
en: If you want to apply a property to many items at once, select the files/folders in explorer, then select <menuchoice><guimenu>Context menu</guimenu><guimenuitem>properties</guimenuitem></menuchoice>
target: Ako želite da primenite osobinu na više stavki odjednom, izaberite fajlove/imenike u pretraživaču, zatim izaberite <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>osobine</guimenuitem></menuchoice>

note: (para)
en: If you want to apply the property to <emphasis>every</emphasis> file and folder in the hierarchy below the current folder, check the <guilabel>Recursive</guilabel> checkbox.
target: Ako želite da primenite osobine na <emphasis>svaki</emphasis> fajl i imenik u hijerarhiji ispod tekućeg imenika, čekirajte <guilabel>Rekurziv</guilabel> čekboks.

note: (para)
en: Some properties, for example <literal>svn:needs-lock</literal>, can only be applied to files, so the property name doesn't appear in the drop down list for folders. You can still apply such a property recursively to all files in a hierarchy, but you have to type in the property name yourself.
target: Neke osobine, na primer <literal>svn:needs-lock</literal>, mogu se samo primeniti na fajlove, tako ime osobine se ne pojavljuje u padajućoj listi za imenike. Možete tek primeniti takve osobine rekurzivno na sve fajlove u hijerarhiji, ali morate da otkucate ime osobine sami.

note: (para)
en: If you wish to edit an existing property, select that property from the list of existing properties, then click on <guibutton>Edit...</guibutton>.
target: Ako želite da uredite postojeću osobinu, izaberite tu osobinu iz liste postojećih osobina, zatim kliknite na <guibutton>Uredi...</guibutton>.

note: (para)
en: If you wish to remove an existing property, select that property from the list of existing properties, then click on <guibutton>Remove</guibutton>.
target: Ako želite da uklonite postojeću osobinu, izaberite osobinu iz liste postojećih osobina, zatim kliknite na <guibutton>Ukloni</guibutton>.

note: (para)
en: The <literal>svn:externals</literal> property can be used to pull in other projects from the same repository or a completely different repository. For more information, read <xref linkend="tsvn-dug-import-4"/>.
target: Osobina <literal>svn:externals</literal> može se koristiti da se privuče u druge projekte iz istog spremišta ili sasvim različitog spremišta. Za više informacija, pročitajte <xref linkend="tsvn-dug-import-4"/>.

note: (title)
en: Exporting and Importing Properties
target: Izvoz i uvoz osobina

note: (para)
en: Often you will find yourself applying the same set of properties many times, for example <literal>bugtraq:logregex</literal>. To simplify the process of copying properties from one project to another, you can use the Export/Import feature.
target: Često ćete zateći sebe da primenjujete isti skup osobina više puta, na primer <literal>bugtraq:logregex</literal>. Da pojednostavite proces kopiranja osobina iz jednog projekta u drugi, možete koristiti Izvezi/Uvezi mogućnost.

note: (para)
en: From the file or folder where the properties are already set, use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>properties</guimenuitem></menuchoice>, select the properties you wish to export and click on <guibutton>Export...</guibutton>. You will be prompted for a filename where the property names and values will be saved.
target: Od fajla ili imenika gde je osobina već podešena koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>osobine</guimenuitem></menuchoice>, izaberite osobine koje želite da izvezete i kliknite na guibutton>Izvezi...</guibutton>. Bićete pitani za fajlime gde će se imena osobina i vrednosti sačuvati.

note: (para)
en: From the folder(s) where you wish to apply these properties, use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>properties</guimenuitem></menuchoice> and click on <guibutton>Import...</guibutton>. You will be prompted for a filename to import from, so navigate to the place you saved the export file previously and select it. The properties will be added to the folders non-recursively.
target: Iz imenika gde želite da primenite ove osobine, koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>osobine</guimenuitem></menuchoice> kliknite na <guibutton>Uvoz...</guibutton>. Bićete pitani za fajlime za uvoz pa odite do mesta gde ste sačuvali ranije izvezen fajl i izaberite ga. Osobine će biti dodate imeniku ne-rekurzivno.

note: (para)
en: If you want to add properties to a tree recursively, follow the steps above, then in the property dialog select each property in turn, click on <guibutton>Edit...</guibutton>, check the <guilabel>Apply property recursively</guilabel> box and click on <guibutton>OK</guibutton>.
target: Ako želite da dodate osobine stablu rekurzivno pratite gornje korake, zatim u dijalogu osobina izaberite svaku osobinu jednu za drugom, <guibutton>Uredi...</guibutton>, čekirajte <guilabel>Primeni osobinu rekurzivno</guilabel>boks i kliknite na  <guibutton>OK</guibutton>.

note: (para)
en: The Import file format is binary and proprietary to TortoiseSVN. Its only purpose is to transfer properties using Import and Export, so there is no need to edit these files.
target: Uvozni fajl format je binarni i vlasništvo TortoiseSVN. NJegova je jedina svrha da prenese osobine koristeći Uvoz i Izvoz, tako da nije potrebno uređenje ovih fajlova.

note: (title)
en: Binary Properties
target: Binarne Osobine

note: (para)
en: TortoiseSVN can handle binary property values using files. To read a binary property value, <guibutton>Save...</guibutton> to a file. To set a binary value, use a hex editor or other appropriate tool to create a file with the content you require, then <guibutton>Load...</guibutton> from that file.
target: TortoiseSVN može rukovati binarnim vrednostima osobina koristeći fajlove. Da bi se pročitala binarna vrednost osobine <guibutton>Sačuvaj...</guibutton> u fajl. Da se podesi binarna vrednost koristite heksa uređivač ili drugi odgovarajući alat da creirate fajl sa sadržajem koji vam je potreban, zatim  <guibutton>Unesi...</guibutton> iz tog fajla.

note: (para)
en: Although binary properties are not often used, they can be useful in some applications. For example if you are storing huge graphics files, or if the application used to load the file is huge, you might want to store a thumbnail as a property so you can obtain a preview quickly.
target: Mada se binarne osobine ne koriste često one mogu biti korisne u nekim aplikacijama. Na primer ako smeštate ogromne grafičke fajlove, ili ako aplikacija korišćena da unese fajl je ogromna, možete želeti da sačuvate pregledne sličice kao oobinu da biste mogli da brzo dobijete pregled.

note: (title)
en: Automatic property setting
target: Automatsko podešavanje osobina

note: (primary)
en: auto-props
target: auto-osob

note: (para)
en: You can configure Subversion and TortoiseSVN to set properties automatically on files and folders when they are added to the repository. There are two ways of doing this.
target: Možete konfigurisati Subverziju i TortoiseSVN da podesite osobine automatski na fajlovima i imenicima kada se oni dodaju u spremište. Postoji dva načina da se to uradi.

note: (para)
en: You can edit the subversion configuration file to enable this feature on your client. The <guilabel>General</guilabel> page of TortoiseSVN's settings dialog has an edit button to take you there directly. The config file is a simple text file which controls some of subversion's workings. You need to change two things: firstly in the section headed <literal>miscellany</literal> uncomment the line <literal>enable-auto-props = yes</literal>. Secondly you need to edit the section below to define which properties you want added to which file types. This method is a standard subversion feature and works with any subversion client. However it has to be defined on each client individually - there is no way to propagate these settings from the repository.
target: Možete urediti subverzioni konfiguracioni fajl da omogućite ovu osobinu na klijentu. <guilabel>Generalna</guilabel> strana TortoiseSVN podešavanja dijalog ima dugme za uređenje da ga pokrenete direktno. Konfig fajl je jednostavan tekst fajl koji kontroliše neke od subverzionih delovanja. Potrebno je da izmenite dve stvari: najpre u zaglavlju paragrafa <literal>asortiman</literal> otkomentirajte liniju <literal>enable-auto-props = yes</literal>. Drugo, potrebno je da uredite paragraf ispod da definiše koje osobine želite da dodate na koji tip fajla. Ovaj metod je standardna subverziona osobina i radi sa bilo kojim subverzionim klijentom. Međutim to je definisano kod svakog klijenta individualno - nema načina da se prenese ovo podešavanje iz spremišta.

note: (para)
en: An alternative method is to set the <literal>tsvn:autoprops</literal> property on folders, as described in the next section. This method only works for TortoiseSVN clients, but it does get propagated to all working copies on update.
target: Alternativni metod je da se podesi <literal>tsvn:autoprops</literal> osobina na imeniku, kako je opisano u sledećem paragrafu. Ovaj metod radi samo za TortoiseSVN klijente, ali to se dobija za sve radne kopije pri ažuriranju.

note: (para)
en: Whichever method you choose, you should note that auto-props are only applied to files at the time they are added to the repository. Auto-props will never change the properties of files which are already versioned.
target: Kojigod metod da se izabere morate primetiti  da auto-osobine su primenjene samo na fajlove u vreme kada su dodati spremištu. Auto-osobine neće nikada izmeniti osobine fajlova koji su već verzionisani.

note: (para)
en: If you want to be absolutely sure that new files have the correct properties applied, you should set up a repository pre-commit hook to reject commits where the required properties are not set.
target: Ako želiti da budete apsolutno sigurni u to da novi fajlovi imaju ispravne osobine primenjene, vi treba da podesite u spremištu pre-urezivanja zakačaljku da odbaci urezivanje tamo gde nisu podešene odgovarajuće osobine.

note: (title)
en: Commit properties
target: Urezivanje osobina

note: (para)
en: Subversion properties are versioned. After you change or add a property you have to commit your changes.
target: Subverzione osobine su verzionisane. Posle izmena ili dodavanja osobina treba da urežete vaše izmene.

note: (title)
en: Conflicts on properties
target: Konflikt u osobinama

note: (para)
en: If there's a conflict on committing the changes, because another user has changed the same property, Subversion generates a <filename>.prej</filename> file. Delete this file after you have resolved the conflict.
target: Ako postoji konflikt pri urezivanju izmena, zato što drugi korisnik ima izmenjene iste osobine, Subverzija generiše <filename>.prej</filename> fajl. Obrišite ovaj fajl posle razrešenja konflikta.

note: (title)
en: TortoiseSVN Project Properties
target: Osobine TortoiseSVN projekata

note: (primary)
en: project properties
target: osobine projekta

note: (primary)
en: TortoiseSVN properties
target: TortoiseSVN osobine

note: (para)
en: <literal>tsvn:logminsize</literal> sets the minimum length of a log message for a commit. If you enter a shorter message than specified here, the commit is disabled. This feature is very useful for reminding you to supply a proper descriptive message for every commit. If this property is not set, or the value is zero, empty log messages are allowed.
target: <literal>tsvn:logminsize</literal> podešava minimalnu dužinu dnevnik poruke za urezivanje. Ako unesete kraću poruku nego što je specificirano ovde, urezivanje je onemogućeno. Ova osobina je veoma korisna da vas podseti da snabdete odgovarajuću opisnu poruku za svako urezivanje. Ako ova osobina nije podešena, ili ima vrednost nula, prazan dnevnik poruka je dozvoljen.

note: (para)
en: <literal>tsvn:lockmsgminsize</literal> sets the minimum length of a lock message. If you enter a shorter message than specified here, the lock is disabled. This feature is very useful for reminding you to supply a proper descriptive message for every lock you get. If this property is not set, or the value is zero, empty lock messages are allowed.
target: <literal>tsvn:lockmsgminsize</literal> podešava minimalnu dužinu poruke zaključavanja. Ako unesete kraću poruku od specificirane ovde, zaključavanje je onemogućeno. Ova osobina je veoma korisna da vas podseti da snabdete odgovarajuću opisnu poruku za svako zaključavanje koje uzmete. Ako ova osobina nije podešena, ili je vrednost nula, prazna poruka zaključavanja se dozvoljava.

note: (para)
en: <literal>tsvn:logwidthmarker</literal> is used with projects which require log messages to be formatted with some maximum width (typically 80 characters) before a line break. Setting this property to a non-zero will do 2 things in the log message entry dialog: it places a marker to indicate the maximum width, and it disables word wrap in the display, so that you can see whether the text you entered is too long. Note: this feature will only work correctly if you have a fixed-width font selected for log messages.
target: <literal>tsvn:logwidthmarker</literal> se koristi sa projektima koji zahtevaju dnevnik poruku formatiranu na maksimalnu širinu (tipično 80 karaktera) pre savijanja linije. Podešavanje ove osobine na ne-nula uradiće 2 stvari u dnevnik poruka dijalogu: smešta marker da indicira maksimalnu širinu i onemogućava savijanje reči na displeju, tako možete videti da li je tekst koji ste uneli suviše dugačak. Primetimo: ova osobina radi korektno samo ako imate pismo fiksne-širine izabran za dnevnik poruka.

note: (para)
en: <literal>tsvn:logtemplate</literal> is used with projects which have rules about log message formatting. The property holds a multi-line text string which will be inserted in the commit message box when you start a commit. You can then edit it to include the required information. Note: if you are also using <literal>tsvn:logminsize</literal>, be sure to set the length longer than the template or you will lose the protection mechanism.
target: <literal>tsvn:logtemplate</literal>  se koristi sa projektima koji imaju pravila o formatiranju dnevnik poruka. osobine drže multi-linijski tekst string koji će biti ubačen u boks poruka urezivanja kada počnete urezivanje. Zatim možete urediti da uključite željene informacije. Primetio: ako takođe koristite <literal>tsvn:logminsize</literal>, budite sigurni da podesite dužinu veću od modela ili ćete izgubiti zaštitni mehanizam.

note: (para)
en: Subversion allows you to set <quote>autoprops</quote> which will be applied to newly added or imported files, based on the file extension. This depends on every client having set appropriate autoprops in their subversion configuration file. <literal>tsvn:autoprops</literal> can be set on folders and these will be merged with the user's local autoprops when importing or adding files. The format is the same as for subversion autoprops, e.g. <literal>*.sh = svn:eol-style=native;svn:executable</literal> sets two properties on files with the <literal>.sh</literal> extension.
target: Subverzija vam omogućava da podesite <quote>autoprops</quote> koji će biti primenjen na novo dodate ili uvezene fajlove, zasnovane na ekstenziji fajla. Ovo zavisi na svakom klijentu koji ima podešen odgovarajuči autoprops u svom subverzionom konfiguracionom fajlu. <literal>tsvn:autoprops</literal> može biti podešen na imeniku i to će biti stopljeno sa korisničkim lokalnim autoprops kada se uvezu ili dodaju fajlovi. Format je isti kao i za subverzioni autoprops, npr. <literal>*.sh = svn:eol-style=native;svn:executable</literal> podešava dve osobine na fajlovima sa <literal>.sh</literal> ekstenzijom.

note: (para)
en: If there is a conflict between the local autoprops and <literal>tsvn:autoprops</literal>, the project settings take precedence because they are specific to that project.
target: Ako postoji konflikt između lokalnih autoprops i <literal>tsvn:autoprops</literal>,  podešavanje projekta uzima primat jer je specifično za projekt.

note: (para)
en: In the Commit dialog you have the option to paste in the list of changed files, including the status of each file (added, modified, etc). <literal>tsvn:logfilelistenglish</literal> defines whether the file status is inserted in English or in the localized language. If the property is not set, the default is <literal>true</literal>.
target: U Ureži dijalogu imate opcije da nalepite na listu izmenjenih fajlova, uključujući status svakog fajla (dodat,izmenjen,itd). <literal>tsvn:logfilelistenglish</literal> definiše da li je status fajla ubačen na engleskom ili na lokalnom jeziku. Ako osobina nije podešena uobičajeno stanje je <literal>true</literal>.

note: (para)
en: TortoiseSVN can use spell checker modules which are also used by OpenOffice and Mozilla. If you have those installed this property will determine which spell checker to use, i.e. in which language the log messages for your project should be written. <literal>tsvn:projectlanguage</literal> sets the language module the spell checking engine should use when you enter a log message. You can find the values for your language on this page: <ulink url="http://msdn2.microsoft.com/en-us/library/ms776260.aspx"><citetitle>MSDN: Language Identifiers</citetitle></ulink>.
target: TortoiseSVN može koristiti proveru pravopisa modul koji se takođe koristi u OpenOffice i Mozilla. Ako ih imate instalirane ove osobine će odrediti koji proveravač pravopisa koristiti, tj. u kom jeziku dnevnik poruka za vaš projekat treba biti napisan. <literal>tsvn:projectlanguage</literal> podešava jezik model provere pravopisa mašine treba koristiti kada unesete dnevnik poruku. Možete naći vrednost za vaš jezik na strani: <ulink url="http://msdn2.microsoft.com/en-us/library/ms776260.aspx"><citetitle>MSDN: Language Identifiers</citetitle></ulink>.

note: (para)
en: You can enter this value in decimal, or in hexadecimal if prefixed with <literal>0x</literal>. For example English (US) can be entered as <literal>0x0409</literal> or <literal>1033</literal>.
target: Možete uneti ovu vrednost u decimalnoj ili heksadecimalnoj formi ako se prefiksuje sa <literal>0x</literal>. Na primer Engleski (US) može se uneti kao <literal>0x0409</literal> ili <literal>1033</literal>.

note: (para)
en: The property <literal>tsvn:logsummary</literal> is used to extract a portion of the log message which is then shown in the log dialog as the log message summary.
target: Osobina <literal>tsvn:logsummary</literal> se koristi izdvoji deo dnevnik poruke koji će biti prikazan u dnevnik poruka rezultata.

note: (para)
en: The value of the <literal>tsvn:logsummary</literal> property must be set to a one line regex string which contains one regex group. Whatever matches that group is used as the summary.
target: Vrednost <literal>tsvn:logsummary</literal> osobine mora biti podešena na jednu liniju regeks stringa koji sadrži jednu regeks grupu. Štogod spari tu grupu koristi se kao rezultat.

note: (para)
en: An example: <literal>\[SUMMARY\]:\s+(.*)</literal> Will catch everything after <quote>[SUMMARY]</quote> in the log message and use that as the summary.
target: Jedan primer: <literal>\[SUMMARY\]:\s+(.*)</literal> Će uhvatiti sve posle <quote>[SUMMARY]</quote> u dnevnik poruka i koristi ga kao rezultat.

note: (para)
en: When you want to add a new property, you can either pick one from the list in the combo box, or you can enter any property name you like. If your project uses some custom properties, and you want those properties to appear in the list in the combo box (to avoid typos when you enter a property name), you can create a list of your custom properties using <literal>tsvn:userfileproperties</literal> and <literal>tsvn:userdirproperties</literal>. Apply these properties to a folder. When you go to edit the properties of any child item, your custom properties will appear in the list of pre-defined property names.
target: Kada želite da dodate novu osobinu vi možete ili uzeti jedan iz liste u kombo boksu ili možete uneti bilo koje ime osobine koje želite. Ako vaš projekat koristi neke uobičajene osobine i želite te osobine da se pojave na listi u kombo boksu ( da izbegnete greške kada unosite ime osobine), možete kreirati listu vaših uobičajenih osobina koristeći <literal>tsvn:userfileproperties</literal> i <literal>tsvn:userdirproperties</literal>. Primenite ove osobine na imenik. Kada uredite osobine bilo koje potomačke stavke, vaše uobičajene osobine će se pojaviti u listi pre-definisanih imena osobina.

note: (para)
en: TortoiseSVN has a few special properties of its own, and these begin with <literal>tsvn:</literal>. <placeholder-1/>
target: TortoiseSVN ima neke svoje specijalne osobine, i one počinju sa <literal>tsvn:</literal>. <placeholder-1/>

note: (para)
en: Some <literal>tsvn:</literal> properties require a <literal>true/false</literal> value. TortoiseSVN also understands <literal>yes</literal> as a synonym for <literal>true</literal> and <literal>no</literal> as a synonym for <literal>false</literal>.
target: Neke <literal>tsvn:</literal> osobine zahtevaju <literal>true/false</literal> vrednosti. TortoiseSVN takođe razume <literal>yes</literal> kao sinonim za <literal>true</literal> i <literal>no</literal> kao sinonim za <literal>false</literal>.

note: (para)
en: TortoiseSVN can integrate with some bug tracking tools. This uses project properties that start with <literal>bugtraq:</literal>. Read <xref linkend="tsvn-dug-bugtracker"/> for further information.
target: TortoiseSVN može se integrisati sa nekim alatima za bag praćenje. Ovo koristi osobine projekata koja počinje sa <literal>bugtraq:</literal>. Pročitajte <xref linkend="tsvn-dug-bugtracker"/> za dodatne informacije.

note: (para)
en: It can also integrate with some web-based repository browsers, using project properties that start with <literal>webviewer:</literal>. Read <xref linkend="tsvn-dug-repoviewer"/> for further information.
target: Može se takođe integrisati sa nekim veb-zasnovanim pretraživačem spremišta, koristeći osobine projekta koje počinju sa <literal>webviewer:</literal>. Pročitajte <xref linkend="tsvn-dug-repoviewer"/> za dalje informacije.

note: (title)
en: Set the project properties on folders
target: Podešavanje osobina projekta o imeniku

note: (para)
en: These special project properties must be set on <emphasis>folders</emphasis> for the system to work. When you commit a file or folder the properties are read from that folder. If the properties are not found there, TortoiseSVN will search upwards through the folder tree to find them until it comes to an unversioned folder, or the tree root (eg. <literal>C:\</literal>) is found. If you can be sure that each user checks out only from e.g <filename>trunk/</filename> and not some sub-folder, then it is sufficient to set the properties on <filename>trunk/</filename>. If you can't be sure, you should set the properties recursively on each sub-folder. A property setting deeper in the project hierarchy overrides settings on higher levels (closer to <filename>trunk/</filename>).
target: Ove specijalne osobine projekta moraju biti podešene na <emphasis>imenike</emphasis> za sistem da rade. kada urezujete fajl ili imenik osobine se čitaju iz tog imenika. Ako se osobine ne nađu ovde TortoiseSVN će potražiti nagore kroz stblo imenika da ih nađe sve dok ne dođe do neverzionisanog imenika, ili koren stabla (npr. <literal>C:\</literal>) se nađe. Ako možete biti sigurni da svaki korisnik preuzima samo iz npr. <filename>trunk/</filename> i ne isti sub-imenik, zatim je dovoljno da se podese osobine na <filename>trunk/</filename>. Ako niste sigurni, morate podesiti osobine rekurzivno na svakom sub-imeniku. Podešavanje osobine dublje u hijerarhiji projekta prebaci podešavanje na viši nivo (bliže <filename>trunk/</filename>).

note: (para)
en: For project properties <emphasis>only</emphasis> you can use the <guilabel>Recursive</guilabel> checkbox to set the property to all sub-folders in the hierarchy, without also setting it on all files.
target: Za osobine projekta <emphasis>samo</emphasis> možete koristiti <guilabel>Rekurziv</guilabel> čekboks da podesite osobine svih sub-imenika u hijerarhiji, takođe bez podešavanja na sve fajlove.

note: (para)
en: When you add new sub-folders using TortoiseSVN, any project properties present in the parent folder will automatically be added to the new child folder too.
target: Kada dodate novi sub-imenik koristeći TortoiseSVN, osobine bilo kog projekta prisutne u predačkom imeniku će automatski biti dodate novom potomačkom imeniki takođe.

note: (para)
en: Although TortoiseSVN's project properties are extremely useful, they only work with TortoiseSVN, and some will only work in newer versions of TortoiseSVN. If people working on your project use a variety of Subversion clients, or possibly have old versions of TortoiseSVN, you may want to use repository hooks to enforce project policies. project properties can only help to implement a policy, they cannot enforce it.
target: Takođe TortoiseSVN osobine projekta su izuzetno korisne, one samo rade sa TortoiseSVN, i neki će samo raditi  u novoj verziji TortoiseSVN. Ako ljudi rade na vašem projektu koristite mnoštvo Subverzionih klijenata, ili moguće ako imate staru verziju TortoiseSVN, možete da koristite zakačaljke spremišta da forsirate politiku projekta. Osobine projekta mogu pomoći da se primeni politika, ona se ne može forsirati.

note: (title)
en: Branching / Tagging
target: Grananje/označavanje

note: (primary)
en: copy
target: kopiraj

note: (primary)
en: mark release
target: markiranje oslobađanja

note: (para)
en: One of the features of version control systems is the ability to isolate changes onto a separate line of development. This line is known as a <firstterm>branch</firstterm>. Branches are often used to try out new features without disturbing the main line of development with compiler errors and bugs. As soon as the new feature is stable enough then the development branch is <firstterm>merged</firstterm> back into the main branch (trunk).
target: Jedna od osobina sistema kontrole verzija je mogućnost da se izoluju izmene na odvojenoj liniji razvoja. Ova linija je poznata kao <firstterm>grana</firstterm>. Grane se često koriste da se isprobaju nove osobine bez narušavanja glavne linije razvoja sa greškama kompajlera i bagovima. Uskoro kada nove osobine postanu stabilne  razvojna grana je <firstterm>stopljena</firstterm> nazad u glavnu granu (deblo).

note: (para)
en: Another feature of version control systems is the ability to mark particular revisions (e.g. a release version), so you can at any time recreate a certain build or environment. This process is known as <firstterm>tagging</firstterm>.
target: Druga osobina sistema kontrole verzija je mogućnost da se markira posbna revizija (npr. realizovana verzija), tako da možete u bilo koje vreme ponovo kreirate određenu izradu ili okolinu. Ovaj proces je poznat kao <firstterm>označavanje</firstterm>.

note: (para)
en: Subversion does not have special commands for branching or tagging, but uses so-called <quote>cheap copies</quote> instead. Cheap copies are similar to hard links in Unix, which means that instead of making a complete copy in the repository, an internal link is created, pointing to a specific tree/revision. As a result branches and tags are very quick to create, and take up almost no extra space in the repository.
target: Subverzija nema specijalne komande za grananje i označavanje, ali koristi takozvane <quote>jeftine kopije</quote> umesto. Jeftine kopije su slične čvrstim vezama na Juniksu, koje znače to da se umesto pravljenja kompletnih kopija u spremištu, interna veza se kreira, ukazujući na specifično stablo/reviziju. Kao rezultat grane i značke se vrlo brzo kreiraju, i skoro da ne uzimaju dodatni prostor u spremištu.

note: (title)
en: Creating a Branch or Tag
target: Kreiranje Grane ili znaka

note: (title)
en: The Branch/Tag Dialog
target: Grana/Znak dijalog

note: (para)
en: If you have imported your project with the recommended directory structure, creating a branch or tag version is very simple: <placeholder-1/> Select the folder in your working copy which you want to copy to a branch or tag, then select the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Branch/Tag...</guimenuitem></menuchoice>.
target: Ako ste uvezli vaš projekat sa preporučenom strukturom imenika, kreiranjem grana ili znački verzija je veoma jednostavno: <placeholder-1/> Izaberite imenik u vašoj radnoj kopiji koji želite da kopirate u granu ili znak, zatim izaberite komandu <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Grana/Znak...</guimenuitem></menuchoice>.

note: (para)
en: The default destination URL for the new branch will be the source URL on which your working copy is based. You will need to edit that URL to the new path for your branch/tag. So instead of <screen>
        http://svn.collab.net/repos/ProjectName/trunk
    </screen> you might now use something like <screen>
        http://svn.collab.net/repos/ProjectName/tags/Release_1.10
    </screen> If you can't remember the naming convention you used last time, click the button on the right to open the repository browser so you can view the existing repository structure.
target: Uobičajeni destinacioni URL za novu granu bio bi izvorni URL na kome je radna kopija zasnovana. Potrebno vam je da uredite URL ka novoj putanji za granu/znak. Tako umesto <screen>
        http://svn.collab.net/repos/ProjectName/trunk
    </screen> možete sada koristiti nešto kao <screen>
        http://svn.collab.net/repos/ProjectName/tags/Release_1.10
    </screen> Ako ne možete zapamtiti konvenciju imenovanja koju ste koristili u poslednje vreme, kliknite na dugme desno da otvorite pretraživač spremišta tako možete videti postojeću strukturu spremišta.

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

note: (para)
en: The new branch is copied directly in the repository from the HEAD revision. No data needs to be transferred from your working copy, and the branch is created very quickly.
target: Nova grana se kopira direktno u spremište  iz GLAVNE revizije. Nikakve podatke ne treba preneti iz vaše radne kopije, i grana se kreira brzo.

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

note: (para)
en: The new branch is copied directly in the repository but you can choose an older revision. This is useful if you forgot to make a tag when you released your project last week. If you can't remember the revision number, click the button on the right to show the revision log, and select the revision number from there. Again no data is transferred from your working copy, and the branch is created very quickly.
target: Nova grana je kopirana direktno u spremište ali možete izabrati stariju reviziju. Ovo je korisno ako ste zaboravili da uradite znak kada ste realizovali vaš projekat prošle nedelje. Ako ne možete zapamtiti revizioni broj kliknite dugme s desne strane da prikažete revizioni dnevnik i izaberite revizioni broj odatle. Ponovo nema podataka koji se prenose iz vaše radne kopije i grana se kreira brzo.

note: (para)
en: The new branch is an identical copy of your local working copy. If you have updated some files to an older revision in your WC, or if you have made local changes, that is exactly what goes into the copy. Naturally this sort of complex tag may involve transferring data from your WC back to the repository if it does not exist there already.
target: Nova grana je idntična kopija vaše lokalne radne kopije. Ako ste ažurirali neke fajlove sa starijom revizijom u vašoj RK, ili ako ste napravili lokalne izmene, to je tačno ono što ide u kopiju. Prirodno ova vrsta kompleksnih znački može obuhvatiti podatke iz vaše RK nazad u spremište ako ona već ne postoji tamo.

note: (para)
en: Now you have to select the source of the copy. Here you have three options: <placeholder-1/>
target: Sada imate da izaberete izvor za kopiranje. Ovde imate tri mogućnosti: <placeholder-1/>

note: (para)
en: If you want your working copy to be switched to the newly created branch automatically, use the <guilabel>Switch working copy to new branch/tag</guilabel> checkbox. But if you do that, first make sure that your working copy does not contain modifications. If it does, those changes will be merged into the branch WC when you switch.
target: Ako želite vašu radnu kopiju da prebacite na novo kreiranu granu automatski, koristite  <guilabel>prebaci radnu kopiju na novu granu/znak</guilabel> čekboks. Ali ako to uradite, najpre budite sigurni da vaša radna kopija ne sadrži izmene. Ako sadrži, ove promene će biti stopljene u granu RK kada prebacite.

note: (para)
en: Press <guibutton>OK</guibutton> to commit the new copy to the repository. Don't forget to supply a log message. Note that the copy is created <emphasis>inside the repository</emphasis>.
target: Pritisnite <guibutton>OK</guibutton>  da urežete novu kopiju u spremište. Ne zaboravite da obezbedite dnevnik poruku. Primetimo da je kopija kreirana <emphasis>unutar spremišta</emphasis>.

note: (para)
en: Note that unless you opted to switch your working copy to the newly created branch, creating a Branch or Tag does <emphasis>not</emphasis> affect your working copy. Even if you create the branch from your WC, those changes are committed to the new branch, not to the trunk, so your WC may still be marked as modified with respect to the trunk.
target: Primetimo da osim što ste odlučili da prebacite vašu radnu kopiju na novokreiranu granu, kreiranje Grane ili Znaka <emphasis>ne</emphasis> utiče na vašu radnu kopiju. Čak i ako kreirate granu iz vaše RK, ove izmene su urezane u novu granu, ne u deblo, tako da vaša RK može još uvek biti markirana kao izmenjena sa respektom na deblo.

note: (title)
en: To Checkout or to Switch...
target: Preuzeti ili prebaciti...

note: (primary)
en: switch
target: zamena

note: (para)
en: ...that is (not really) the question. While a checkout downloads everything from the desired branch in the repository to your working directory, <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Switch...</guimenuitem></menuchoice> only transfers the changed data to your working copy. Good for the network load, good for your patience. :-)
target: ... to nije (ne realno) pitanje. Dok preuzimanje skida sve iz željene grane u spremištu ka imeniku vaše radne kopije, <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Prebaci...</guimenuitem></menuchoice> samo prenosi izmenjene podatke u vašu radnu kopiju. Dobro za mrežno unošenje, dobro za vaše strpljenje. :-)

note: (para)
en: <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Checkout</guimenuitem></menuchoice> to make a fresh checkout in an empty folder. You can check out to any location on your local disk and you can create as many working copies from your repository as you like.
target: <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Preuzimanje</guimenuitem></menuchoice> da se uradi sveže preuzimanje u prazan imenik. Možete preuzeti bilo koju lokaciju na vašem lokalnom disku i možete kreirati onoliko radnih kopija iz vašeg spremišta koliko želite.

note: (para)
en: Switch your current working copy to the newly created copy in the repository. Again select the top level folder of your project and use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Switch...</guimenuitem></menuchoice> from the context menu.
target: Prebacite vašu radnu kopiju u novo kreiranu kopiju spremištu. Opet izaberite vršni nivo imenik vašeg projekta i koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Prebaci...</guimenuitem></menuchoice> iz kontekst menija.

note: (para)
en: In the next dialog enter the URL of the branch you just created. Select the <guilabel>Head Revision</guilabel> radio button and click on <guibutton>OK</guibutton>. Your working copy is switched to the new branch/tag.
target: U sledećem dijalogu unesite URL grane koju ste kreirali. Izaberite <guilabel>Glavna Revizija</guilabel> radio dugme i kliknite na <guibutton>OK</guibutton>. Vaša radna kopija je prebačena na novu granu/znak.

note: (para)
en: Switch works just like Update in that it never discards your local changes. Any changes you have made to your working copy which have not yet been committed will be merged when you do the Switch. If you do not want this to happen then you must either commit the changes before switching, or revert your working copy to an already-committed revision (typically HEAD).
target: Prebacite rad tek kao Ažuriranje i nikad ne odbaciti vaše lokalne izmene. Bilo koje izmene koje ste uradili u vašoj radnoj kopiji koje još nisu urezane biće stopljene kada uradite Prebacivanje. Ako ne želite da se to desi morate ili urezati  izmene pre prebacivanje, ili vratiti vašu radnu kopiju u već-urezanu reviziju (tipčno GLAVNA).

note: (para)
en: If you want to work on trunk and branch, but don't want the expense of a fresh checkout, you can use Windows Explorer to make a copy of your trunk checkout in another folder, then <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Switch...</guimenuitem></menuchoice> that copy to your new branch.
target: Ako želite da radite na deblu i grani, ali ne želite skupo sveže preuzimanje, možete koristiti Vindouz Eksplorer da napravite kopiju vašeg debla u sledći imenik, zatim  <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Prebaci...</guimenuitem></menuchoice>  zatim kopirajte u novu granu.

note: (title)
en: The Switch Dialog
target: Prebaci dijalog

note: (para)
en: To be able to work with your freshly generated branch or tag you have several ways to handle it. You can: <placeholder-1/><placeholder-2/>
target: Da bi bili sposobni da radite sa sveže generisanom granom ili znakom imate više načina da rukujete time. Možete: <placeholder-1/><placeholder-2/>

note: (para)
en: Tags are typically used to create a static snapshot of the project at a particular stage. As such they not normally used for development - that's what branches are for, which is the reason we recommended the <filename>/trunk /branches /tags</filename> repository structure in the first place. Working on a tag revision is <emphasis>not a good idea</emphasis>, but because your local files are not write protected there is nothing to stop you doing this by mistake. However, if you try to commit to a path in the repository which contains <filename>/tags/</filename>, TortoiseSVN will warn you.
target: Značke se obično koriste da se kreira statička slika projekta u pojedinom stanju. Kao takvi se ne koriste normalno pri razvoju - to je zašto postoje grane, koji rezon mi preporučujemo <filename>/trunk /branches /tags</filename> strukturu spremišta na prvom mestu. Rad na znak revizijama <emphasis>nije dobra ideja</emphasis>, ali vaši lokalni fajlovi nisu zaštićeni od upisivanja pa nema ništa da vas zaustavi da to uradite greškom. Međutim, ako pokušate da urežete putanju u spremište koja sadrži <filename>/tags/</filename>, TortoiseSVN će vas upozoriti.

note: (para)
en: It may be that you need to make further changes to a release which you have already tagged. The correct way to handle this is to create a new branch from the tag first and commit the branch. Do your Changes on this branch and then create a new tag from this new branch, e.g. <filename>Version_1.0.1</filename>.
target: To može biti da je potrebno uaditi dalje izmene za realizaciju koju već označavate. Korektan način rukovanja ovim je kreiranje nove grane od znaka najpre i urezati granu. Uradite vaše Izmene na ovoj grani i zatim kreirajte novi znak od ove nove grane, npr. <filename>Version_1.0.1</filename>.

note: (para)
en: If you modify a working copy created from a branch and commit, then all changes go to the new branch and <emphasis>not</emphasis> the trunk. Only the modifications are stored. The rest remains a cheap copy.
target: Ako izmenite radnu kopiju kreiranu od grane i urežete, zatim sve izmene idu u novu granu i <emphasis>ne</emphasis> u deblo. Samo modifikacije su uskladištene. Ostatak ostaje jeftina kopija.

note: (para)
en: Although Subversion itself makes no distinction between tags and branches, the way they are typically used differs a bit. <placeholder-1/>
target: Takođe, sama Subverzija ne pravi razliku između znački i grana, način kako se tipično koriste razlikuje se u malom. <placeholder-1/>

note: (title)
en: Merging
target: Spajanje

note: (primary)
en: merge
target: stopi

note: (para)
en: Where branches are used to maintain separate lines of development, at some stage you will want to merge the changes made on one branch back into the trunk, or vice versa.
target: Tamo gde se grane koriste da održavaju odvojene linije razvoja, u nekim stanjima vi ćete želeti da stopite izmene napravljene na grani nazad u deblo, ili obratno.

note: (para)
en: It is important to understand how branching and merging works in Subversion before you start using it, as it can become quite complex. It is highly recommended that you read the chapter <ulink url="http://svnbook.red-bean.com/en/1.5/svn.branchmerge.html"><citetitle>Branching and Merging</citetitle></ulink> in the Subversion book, which gives a full description and many examples of how it is used.
target: Važno je razumeti kako grane i stapanje rade na Subverziji pre početka njihovog korišćenja, jer može biti sasvim kompleksno. Jako se preporučuje da pročitate poglavlje <ulink url="http://svnbook.red-bean.com/en/1.5/svn.branchmerge.html"><citetitle>Branching and Merging</citetitle></ulink> u Subverzionoj knjizi, koja daje pun opis i mnogo primera kak se korist.

note: (para)
en: The next point to note is that merging <emphasis>always</emphasis> takes place within a working copy. If you want to merge changes <emphasis>into</emphasis> a branch, you have to have a working copy for that branch checked out, and invoke the merge wizard from that working copy using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Merge...</guimenuitem></menuchoice>.
target: Sledeća tačka za notiranje je tda to stapanje <emphasis>uvek</emphasis> nalazi mesto u okviru radne kopije. Ako želite da stopite izmene <emphasis>u</emphasis> granu, imate da uzmete radnu kopiju za preuzimanje grane, i pozovete čarobnjak stapanja iz radne kopije koristeći <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Stopi...</guimenuitem></menuchoice>.

note: (para)
en: In general it is a good idea to perform a merge into an unmodified working copy. If you have made other changes in your WC, commit those first. If the merge does not go as you expect, you may want to revert the changes, and the <guilabel>Revert</guilabel> command will discard <emphasis>all</emphasis> changes including any you made before the merge.
target: Generalno je to dobra ideja da se izvrši stapanje u neizmenjenu radnu kopiju. Ako ste uradili druge izmene u vašoj RK, urežite ih najpre. Ako stapanje ne ide kako ste očekivali, morate vratiti izmene i <guilabel>Vrati</guilabel> komanda će poništiti <emphasis>sve</emphasis> izmene uključujući bilo koje urađene pre stapanja.

note: (para)
en: There are three common use cases for merging which are handled in slightly different ways, as described below. The first page of the merge wizard asks you to select the method you need.
target: Postoje tri često korišćena slučaja za stapanje koji su podržani u blago različitom načinu, kako je opisano dole. Prva strana čarobnjaka stapanja vas pita da izaberete metod koji vam treba.

note: (term)
en: Merge a range of revisions
target: Stopi opseg 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: (para)
en: What you are asking Subversion to do is this: <quote>Calculate the changes necessary to get [FROM] revision 1 of branch A [TO] revision 7 of branch A, and apply those changes to my working copy (of trunk or branch B).</quote>
target: Kako pitate Subverziju da to uradi: <quote>Izračunati izmene neophodne da uzmete [OD] revizije 1 grane A [DO] revizije 7 grane A, primenite ove izmene u mojoj radnoj kopiji (deblo ili grana B).</quote>

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

note: (para)
en: This method covers the case when you have made a feature branch as discussed in the Subversion book. All trunk changes have been ported to the feature branch, week by week, and now the feature is complete you want to merge it back into the trunk. Because you have kept the feature branch synchronized with the trunk, the latest versions of branch and trunk will be absolutely identical except for your branch changes.
target: Ovaj metod pokriva slučaj kada ste uradili  posebnu granu što je razmatrano u Subverzionoj knjizi. Sve izmene debla su provedena u posebnoj grani, nedelja po nedelju, i sada je posebnost kompletno ono što želite da stopite nazad u deblo. Pošto hoćete da zadržite posebnu granu sinhroniziranu sa deblom, zadnja verzija grane i debla će biti apsolutno identične osim za vaše izmene grane.

note: (para)
en: This is a special case of the tree merge described below, and it requires only the URL to merge from (normally) your development branch. It uses the merge-tracking features of Subversion to calculate the correct revision ranges to use, and perform additional checks which ensure that the branch has been fully updated with trunk changes. This ensures that you don't accidentally undo work that others have committed to trunk since you last synchronized changes.
target: Ovo je specijalni slučaj stapanja stabla opisan dole, i on zahteva samo URL da stopi (normalno) vašu granu razvoja. Koristi praćenje stapanja osobinu Subverzije da izračuna ispravni revizioni opseg za korišćenje, i omogućava dodatnu proveru koja omogućava da je ta grana potpuno ažurirana izmenom debla. Ovo omogućava  da vi ne poništite grškom rad koji su drugi urezali u deblo od vaše zadnje sihronizovane izmene.

note: (para)
en: After the merge, all branch development has been completely merged back into the main development line. The branch is now redundant and can be deleted.
target: Posle stapanja, cela grana razvoja je kompletno stopljena nazad u glavnu razvojnu liniju. Grana je sada nekorisna i može biti obrisana.

note: (para)
en: Once you have performed a reintegrate merge you should not continue to use it for development. The reason for this is that if you try to resynchronize your existing branch from trunk later on, merge tracking will see your reintegration as a trunk change that has not yet been merged into the branch, and will try to merge the branch-to-trunk merge back into the branch! The solution to this is simply to create a new branch from trunk to continue the next phase of your development.
target: Kada jednom izvršite reintegraciju stapanja nećete nastaviti da ga koristite za razvoj. Rezon za ovo je to da ako pokušate da resinhronizujete vašu postojeću granu iz debla kasnije, praćenje stapanja će pogledati vašu reintegraciju kao izmenu debla koje još nije stopljeno u granu, i pokušaće da stopi granu-u-deblo stapanje nazad u granu! Rešenje ovome je jednostavno da se kreira nova grana iz debla da se nastavi sledeća faza vašeg razvoja.

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

note: (para)
en: This is a more general case of the reintegrate method. What you are asking Subversion to do is: <quote>Calculate the changes necessary to get [FROM] the head revision of the trunk [TO] the head revision of the branch, and apply those changes to my working copy (of the trunk).</quote> The net result is that trunk now looks exactly like the branch.
target: Ovo je mnogo opštiji slučaj reintegracionog metoda. Ono što pitate Subverziju da to uradi je: <quote>Izračunajte izmene neophodne da dobijete [OD] glavne revizije debla [DO]glavne revizije grane,i primeniti te izmen na moju radnu kopiju (debla).</quote> čist rezultat je to deblo sada izgleda tačno kao grana.

note: (para)
en: If your server/repository does not support merge-tracking then this is the only way to merge a branch back to trunk. Another use case occurs when you are using vendor branches and you need to merge the changes following a new vendor drop into your trunk code. For more information read the chapter on <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html"><citetitle>vendor branches</citetitle></ulink> in the Subversion Book.
target: Ako vaš server/spremište ne podržava stapanje-praćenje onda je ovo jedini način da se stopi grana nazad u deblo. Sledeći slučaj korišćenja se javlja kada koristite prodajne grane i potrebno vam je da stopite izmene koje prate novi prodajni pad u vaš kod debla.Za više informacija pročitajte  poglavlje <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html"><citetitle>vendor branches</citetitle></ulink> u Subverzionoj kljizi.

note: (title)
en: Merging a Range of Revisions
target: Spajanje opsega revizija

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

note: (title)
en: The Merge Wizard - Select Revision Range
target: Čarobnjak soajanja - Izbor opsega revizija

note: (para)
en: <placeholder-1/> In the <guilabel>From:</guilabel> field enter the full folder URL of the branch or tag containing the changes you want to port into your working copy. You may also click <guibutton>...</guibutton> to browse the repository and find the desired branch. If you have merged from this branch before, then just use the drop down list which shows a history of previously used URLs.
target: <placeholder-1/> U <guilabel>Od:</guilabel> polju unesite pun imenik URL grane ili znaka koji sadrži izmene koje želite da prenesete u radnu kopiju. Možete kliknuti <guibutton>...</guibutton> da pretražite spremište i nađete željenu granu. Ako ste stopili iz ove grane ranije, sada samo koristite padajuću listu koja prikazuje istoriju prethodno korišćenih URLova.

note: (para)
en: In the <guilabel>Revision range to merge</guilabel> field enter the list of revisions you want to merge. This can be a single revision, a list of specific revisions separated by commas, or a range of revisions separated by a dash, or any combination of these.
target: U <guilabel>Revizioni opseg za stapanje</guilabel> polju unesite listu revizija koje želite da stopite. Ovo može biti pojedinačna revizija, lista specifičnih revizija odvojenih zapetama, ili opseg revizija odvojenih crticom, ili kombinacija svega.

note: (para)
en: There is an important difference in the way a revision range is specified with TortoiseSVN compared to the command line client. The easiest way to visualise it is to think of a fence with posts and fence panels.
target: Postoji važna razlika u načinu kako je specificiran opseg revizija sa TortoiseSVN poređena sa klijentom komandne linije. Najlakši način da se vizualizuje to je da se misli  o ogradi sa zidom i ogradi panelom.

note: (para)
en: With the command line client you specify the changes to merge using two <quote>fence post</quote> revisions which specify the <emphasis>before</emphasis> and <emphasis>after</emphasis> points.
target: Sa klijentom komandne linije vi specificirate izmene za stapanje koristeći dva <quote>ograda sa zidom</quote> revizija koja specificira <emphasis>pre</emphasis> i <emphasis>posle</emphasis> tačaka.

note: (para)
en: With TortoiseSVN you specify the changeset to merge using <quote>fence panels</quote>. The reason for this becomes clear when you use the log dialog to specify revisions to merge, where each revision appears as a changeset.
target: Sa TortoiseSVN vi specificirate izmenljivskup da se stopi koristeći <quote>ograda panelima</quote>. Razlog za ovo postaje čista kada koristite dnevnik dijalog da specificirate revizije za stapanje, gde se svaka revizija pojavljuje kao izmenljivskup.

note: (para)
en: If you are merging revisions in chunks, the method shown in the subversion book will have you merge 100-200 this time and 200-300 next time. With TortoiseSVN you would merge 100-200 this time and 201-300 next time.
target: Ako stapate revizije u kriškama, prikazan metod u subverzionoj knjizi će stopiti 100-200 sada i 200-300 posle. Sa TortoiseSVN stopićete 100-200 sada i 201-300 posle.

note: (para)
en: This difference has generated a lot of heat on the mailing lists. We acknowledge that there is a difference from the command line client, but we believe that for the majority of GUI users it is easier to understand the method we have implemented.
target: Ove razlike su generisale mnogo udara na mejling liste. Mi saznajemo to da ima razlike sa klijentom komandne linije, ali verujemo da većina GUI korisnika lakše razume metodu koju smo  implementirali.

note: (para)
en: The easiest way to select the range of revisions you need is to click on <guibutton>Show Log</guibutton>, as this will list recent changes with their log comments. If you want to merge the changes from a single revision, just select that revision. If you want to merge changes from several revisions, then select that range (using the usual <keycap>Shift</keycap>-modifier). Click on <guibutton>OK</guibutton> and the list of revision numbers to merge will be filled in for you.
target: Najlakši način da se izabere opseg revizija koje su vam potrebne je da se klikne na <guibutton>Prikaži Dnevnik</guibutton>, koji će izlistati skore promene sa njihovim komentarima dnevnika. AAko želite da stopite izmene iz pojedinačne revizije samo kliknite na tu reviziju. Ako želite da stopite izmene iz više revizija, onda izaberite taj opseg (koristeći uobičajeni <keycap>Shift</keycap>-modifikator). Kliknite na <guibutton>OK</guibutton> i lista revizionih brojeva za stapanje će biti napunjena za vas.

note: (para)
en: If you want to merge changes back <emphasis>out</emphasis> of your working copy, to revert a change which has already been committed, select the revisions to revert and make sure the <guilabel>Reverse merge</guilabel> box is checked.
target: Ako želite da stopite izmene nazad <emphasis>van</emphasis> vaše radne kopije, da vratite izmene koje su već urezane, izaberite reviziju za vraćanje i budite sigurni da je <guilabel>Inverzno stapanje</guilabel> boks čekiran.

note: (para)
en: If you are using the merge tracking features of Subversion, you do not need to remember which revisions have already been merged - Subversion will record that for you. If you leave the revision range blank, all revisions which have not yet been merged will be included. Read <xref linkend="tsvn-dug-merge-tracking"/> to find out more.
target: Ako koristite praćenje stapanja osobinu Subverzije, ne treba vam da pamtite koje revizije su već stopljene - Subverzija beleži to za vas. Ako ostavite revizioni opseg praznim, sve revizije koje još niste stopili biće uključene. Pročitajte <xref linkend="tsvn-dug-merge-tracking"/>  da nađete više o tome.

note: (para)
en: If other people may be committing changes then be careful about using the HEAD revision. It may not refer to the revision you think it does if someone else made a commit after your last update.
target: Ako drugi ljudi možda urezuju izmene budite pažljivi pri korišćenju GLAVNE revizije. Ona možda ne ukazuje na reviziju na koju vi mislite ako još neko urezuje posle vašeg zadnjeg ažuriranja.

note: (para)
en: Click <guibutton>Next</guibutton> and go to <xref linkend="tsvn-dug-merge-options"/>
target: Kliknite <guibutton>Sledeći</guibutton> i idite na  <xref linkend="tsvn-dug-merge-options"/>

note: (secondary)
en: reintegrate
target: reintegracija

note: (title)
en: The Merge Wizard - Reintegrate Merge
target: Čarobnjak spajanja - Reintegracija spajanja

note: (para)
en: <placeholder-1/> To merge a feature branch back into the trunk you must start the merge wizard from within a working copy of the trunk.
target: <placeholder-1/> Da stopite posebnu granu nazad u deblo morate početi čarobnjak stapanja unutar radne kopije debla.

note: (para)
en: In the <guilabel>From URL:</guilabel> field enter the full folder URL of the branch that you want to merge back. You may also click <guibutton>...</guibutton> to browse the repository.
target: U <guilabel>Iz URL:</guilabel> polja unesite pun imenik URL grane koju želite da stopite nazad. Možete takođe kliknuti <guibutton>...</guibutton> da pretražite spremište.

note: (para)
en: There are some conditions which apply to a reintegrate merge. Firstly, the server must support merge tracking. The working copy must be of depth infinite (no sparse checkouts), and it must not have any local modifications, switched items or items that have been updated to revisions other than HEAD. All changes to trunk made during branch development must have been merged across to the branch (or marked as having been merged). The range of revisions to merge will be calculated automatically.
target: Postoje neki uslovi koji dovode do reintegrisanja stapanja. Najpre, server mora da podržava stapanja praćenje. Radna kopija mora biti eskonačne dubine (bez praznog preuzimanja), i ne sme imati bilo kakvu lokalnu izmenu, prebačene stavke ili stavke koje su ažurirane na reviziju različitu od GLAVNE. Sve izmene debla urađene u toku razvoja grane moraju biti stopljene kroz granu (ili označene da su stopljene). Opseg revizija za stapanje biće izračunat automatski.

note: (title)
en: Merging Two Different Trees
target: Spajanje dva različita stabla

note: (secondary)
en: two trees
target: dva stabla

note: (title)
en: The Merge Wizard - Tree Merge
target: Čarobnjak spajanja - Spajanje stabla

note: (para)
en: <placeholder-1/> If you are using this method to merge a feature branch back to trunk, you need to start the merge wizard from within a working copy of trunk.
target: <placeholder-1/> Ako koristite ovaj metod da stopite posebnu granu nazad u deblo. ptreno vam je da počnete čarobnjak stapanja unutar radne kopije debla.

note: (para)
en: In the <guilabel>From:</guilabel> field enter the full folder URL of the <emphasis>trunk</emphasis>. This may sound wrong, but remember that the trunk is the start point to which you want to add the branch changes. You may also click <guibutton>...</guibutton> to browse the repository.
target: U <guilabel>Iz:</guilabel> polju unesite pun imenik URL  <emphasis>debla</emphasis>. Ovo možda zvuči loše, ali zapamtite da deblo je početna tačka kojoj želite da dodate izmene grane. Možete takođe kliknuti <guibutton>...</guibutton> da pretražite spremište.

note: (para)
en: In the <guilabel>To:</guilabel> field enter the full folder URL of the feature branch.
target: U <guilabel>Do:</guilabel> polju unesite pun imenik URL posebne grane.

note: (para)
en: In both the <guilabel>From Revision</guilabel> field and the <guilabel>To Revision</guilabel> field, enter the last revision number at which the two trees were synchronized. If you are sure no-one else is making commits you can use the HEAD revision in both cases. If there is a chance that someone else may have made a commit since that synchronization, use the specific revision number to avoid losing more recent commits.
target: U oba <guilabel>Od Revizije</guilabel> polju i  <guilabel>Do Revizije</guilabel> polju, unesite zadnji revizioni broj u kom dva stabla treba sinhronizovati. Ako ste sigurni da niko još ne urezuje možete koristiti GLAVNU reviziju u oba slučaja. Ako nema šanse da još neko urezuje od te sinhronizacije, koristite specifičan revizioni broj da izbegnete gubljenje skorih urezivanja.

note: (para)
en: You can also use <guibutton>Show Log</guibutton> to select the revision.
target: Možete takođe koristiti <guibutton>Prikaži Dnevnik</guibutton> da izaberete reviziju.

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

note: (para)
en: This page of the wizard lets you specify advanced options, before starting the merge process. Most of the time you can just use the default settings.
target: Ova strana čarobnjaka vam dopušta da odredite dodatne opcije, pre početka procesa stapanja. Većinu vrmena vi ste koristili uobičajeno podešavanje.

note: (para)
en: You can specify the depth to use for the merge, i.e. how far down into your working copy the merge should go. The depth terms used are described in <xref linkend="tsvn-dug-checkout-depth"/>. The default depth is <guilabel>Working copy</guilabel>, which uses the existing depth setting, and is almost always what you want.
target: Morate odrediti dubinu koju ćete koristiti za stapanje, npr. koliko daleko u radnu kopiju stapanje ide. Korišćenje termina dubina opisano je u <xref linkend="tsvn-dug-checkout-depth"/>. Uobičajena dubina je  <guilabel>Radna kopija</guilabel>, koja koristi postojeće podešavanje dubine, i skoro uvek je ono što želite.

note: (para)
en: Most of the time you want merge to take account of the file's history, so that changes relative to a common ancestor are merged. Sometimes you may need to merge files which are perhaps related, but not in your repository. For example you may have imported versions 1 and 2 of a third party library into two separate directories. Although they are logically related, Subversion has no knowledge of this because it only sees the tarballs you imported. If you attempt to merge the difference between these two trees you would see a complete removal followed by a complete add. To make Subversion use only path-based differences rather than history-based differences, check the <guilabel>Ignore ancestry</guilabel> box. Read more about this topic in the Subversion book, <ulink url="http://svnbook.red-bean.com/en/1.5/svn.branchmerge.advanced.html#svn.branchmerge.advanced.ancestry"><citetitle>Noticing or Ignoring Ancestry</citetitle></ulink>
target: Najviše vremena vi želite da stapanje uzme u obzir istoriju fajla, tako da izmene relativne zajedničkom prethodniku su stopljene. Ponekad vam je potrebno da stopite fajlove koji možda zavise, ali nisu u vašem spremištu. Na primer možda ste uvezli verzije 1 i 2 biblioteke trećeg lica u dva odvojena imenika.Takođe, oni su logički zavisni, Subverzija nema znanja o tome jer samo vidi loptu koju unesete. Ako pokušate da stopite razlike ta dva stabla videćete kompletno uklanjanje kome sledi kompletno dodavanje. Da učinite da Subverzija koristi samo zasnovane na putanji razlike pre nego istorijski-zasnovane razlike, čekirajte guilabel>Zanemari poreklo</guilabel>  boks. Pročitajte više o ovome u Subverzionoj knjizi, <ulink url="http://svnbook.red-bean.com/en/1.5/svn.branchmerge.advanced.html#svn.branchmerge.advanced.ancestry"><citetitle>Noticing or Ignoring Ancestry</citetitle></ulink>

note: (para)
en: You can specify the way that line ending and whitespace changes are handled. These options are described in <xref linkend="tsvn-dug-diff-eol-whitespace"/>. The default behaviour is to treat all whitespace and line-end differences as real changes to be merged.
target: Možete odrediti način rukovanja sa završetkom linija i izmenama belihpolja. Ove opcije su opisane u <xref linkend="tsvn-dug-diff-eol-whitespace"/>.  Uobičajeno ponašanje je da se tretiraju sva bela polja i kraj-linije razlike kao stvarne izmen koje se stapaju.

note: (para)
en: If you are using merge tracking and you want to mark a revision as having been merged, without actually doing the merge here, check the <guilabel>Only record the merge</guilabel> checkbox. There are two possible reasons you might want to do this. It may be that the merge is too complicated for the merge algorithms, so you code the changes by hand, then mark the change as merged so that the merge tracking algorithm is aware of it. Or you might want to prevent a particular revision from being merged. Marking it as already merged will prevent the merge occurring with merge-tracking-aware clients.
target: Ako koristite stapanja praćenje i želite da označite reviziju da je stopljena, bez stvarnog stapanja ovde, čekirajte <guilabel>Samo obeležite stapanje</guilabel> čekboks. Postoje dva moguća razloga koja možete želeti da ovo uradite. Može biti da je stapanje jako komplikovano za algoritam stapanja, onda ćete uraditi izmene ručno, zatim markirate izmene kao stopljene da bi stapanja praćenje algoritam bio upoznat sa tim. Ili možete želeti da predupredite posebne revizije da budu stopljene. Označavajuči ih već stopljenim predupređujete pojavu stapanja pomoću stopi-tragač-upoznat klijentima.

note: (para)
en: Now everything is set up, all you have to do is click on the <guibutton>Merge</guibutton> button. If you want to preview the results <guibutton>Test Merge</guibutton> performs the merge operation, but does <emphasis>not</emphasis> modify the working copy at all. It shows you a list of the files that will be changed by a real merge, and notes those areas where conflicts will occur.
target: Sada je sve podešeno, sve što imate da uradite je da kliknete na <guibutton>Stopi</guibutton> dugme. Ako želite da pregledate rezultat <guibuttone>Testiraj Stapanje</guibutton> omogućava operaciju stapanja, ali <emphasis>ne</emphasis> modifikuje radnu kopiju uopšte. To prikazuje listu fajlova koji će biti izmenjeni stvarnim stapanjem, i notira te površine gde se konflikti javljaku.

note: (para)
en: The merge progress dialog shows each stage of the merge, with the revision ranges involved. This may indicate one more revision than you were expecting. For example if you asked to merge revision 123 the progress dialog will report <quote>Merging revisions 122 through 123</quote>. To understand this you need to remember that Merge is closely related to Diff. The merge process works by generating a list of differences between two points in the repository, and applying those differences to your working copy. The progress dialog is simply showing the start and end points for the diff.
target: Stapanje progres dijalog prikazuje svako stanje stapanja, sa revizionim opsezima uključenim. To može indicirati jednu više reviziju nego što ste očekivali. Na primer, ako tražite da stopite reviziju 123 dijalog napredovanja pokazuje <quote>Stapanje revizija122 do 123</quote>. Da shvatite ovo potrebno je da se setite da je Stapanje blisko zavisno sa Diff. Proces stapanja radi generišući listu razlika između dve tačke u spremištu, i primenjuje te razlike na radnu kopiju. Dijalog napredovanja jednostavno prikazuje početnu i krajnju tačku za diff.

note: (title)
en: Reviewing the Merge Results
target: Pregled rezultata spajanja

note: (para)
en: The merge is now complete. It's a good idea to have a look at the merge and see if it's as expected. Merging is usually quite complicated. Conflicts often arise if the branch has drifted far from the trunk.
target: Stapanje je sada kompletno. Dobra je ideja da se pogleda na stapanje i vidi da li je kako se očekivalo. Stapanje je obično sasvim kompletno. Konflikti često nastaju ako je grana pomerena daleko od debla.

note: (para)
en: For Subversion clients and servers prior to 1.5, no merge information is stored and merged revisions have to be tracked manually. When you have tested the changes and come to commit this revision, your commit log message should <emphasis>always</emphasis> include the revision numbers which have been ported in the merge. If you want to apply another merge at a later time you will need to know what you have already merged, as you do not want to port a change more than once. For more information about this, refer to <ulink url="http://svnbook.red-bean.com/en/1.4/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac"><citetitle>Best Practices for Merging</citetitle></ulink> in the Subversion book.
target: Za Subverzione klijente i servere pre 1.5, nisu stopi informacije uskladištene i stopljene revizije su praćene ručno. Kada ste testirali izmene i došli do urezivanja ove revizije, vaš dnevnik poruka urezivanja treba <emphasis>uvek</emphasis> da obuhvati revizione brojeve koji su preneti u stapanju. Ako želite da primenite sledeće stapanje kasnije potrebno vam je da znate šta ste već stopili, jer ne želite da prenesete izmene više nego jednom. Za više informacija o tome pogledajte <ulink url="http://svnbook.red-bean.com/en/1.4/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac"><citetitle>Best Practices for Merging</citetitle></ulink> u Subverzijinoj knjizi.

note: (para)
en: If your server and all clients are running Subversion 1.5 or higher, the merge tracking facility will record the revisions merged and avoid a revision being merged more than once. This makes your life much simpler as you can simply merge the entire revision range each time and know that only new revisions will actually be merged.
target: Ako vaš server i svi klijenti rade Subverziju 1.5 ili višu, praćenje stapanja mogućnost će zabeležiti revizije stoljene i izostaviti revizije koje su stopljene više od jedanput. Ovo čini vaš život mnogo jednostavnijim kao kad jednostavno stopite celi revizioni opseg svaki put i znate da samo nova revizija će stvarno biti stopljena.

note: (para)
en: Branch management is important. If you want to keep this branch up to date with the trunk, you should be sure to merge often so that the branch and trunk do not drift too far apart. Of course, you should still avoid repeated merging of changes, as explained above.
target: Upravljanje granama je važno. Ako želite da držite ovu granu ažurnom sa deblom, treba da budete sigurni da stapate često tako da grana i deblo ne odu suviše daleko. Naravno, potrebno je još uvek izbegavati ponavljanje stapanja izmena, kako je objašnjeno gore.

note: (para)
en: If you have just merged a feature branch back into the trunk, the trunk now contains all the new feature code, and the branch is obsolete. You can now delete it from the repository if required.
target: Ako ste upravo stopili posebnu granu nazad u deblo, deblo sada sadrži sve nove posebne kodove, i grana je nepotrebna. Možete je sada obrisati iz spremišta ako je potrebno.

note: (para)
en: Subversion can't merge a file with a folder and vice versa - only folders to folders and files to files. If you click on a file and open up the merge dialog, then you have to give a path to a file in that dialog. If you select a folder and bring up the dialog, then you must specify a folder URL for the merge.
target: Subverzija ne može stopiti fajl sa imenikom i obratno - samo imenici sa imenicima i fajlovi sa fajlovima. Ako kliknete na fajl i otvorite dijalog stapanja, zatim možete zadati putanju do fajla u dijalogu. Ako izaberete i pokrenete dijalog morate specificirati imenik URL za stapanje.

note: (title)
en: Merge Tracking
target: Praćenje Spajanja

note: (primary)
en: merge tracking
target: praćenje spajanja

note: (para)
en: You can avoid the danger of merging the same revision twice (repeated merge problem). Once a revision is marked as having been merged, future merges which include that revision in the range will skip over it.
target: Možete izbeći opasnost od stapanja iste revizije dvaput (problem ponavljanja stapanja). Kada je jednom revizija označena da je stopljena, buduća stapanja koja uključuju tu reviziju u svom opsegu preskočiće je.

note: (para)
en: When you merge a branch back into trunk, the log dialog can show you the branch commits as part of the trunk log, giving better traceability of changes.
target: Kada stopite granu nazad u deblo, dnevnik dijalog može prikazati urezivanje grane kao deo deblovog dnevnika, dajući bolju preglednost izmena.

note: (para)
en: When you show the log dialog from within the merge dialog, revisions already merged are shown in grey.
target: Kada prikažete dnevnik dijalog u okviru stapanja dijaloga, revizije već stopljene su prikazane sivo.

note: (para)
en: When showing blame information for a file, you can choose to show the original author of merged revisions, rather than the person who did the merge.
target: Kada se prikazuju invormacije okrivljavanja za fajl, možete izabrati da prikažete originalnog autora stopljene revizije, pre nego osobu koja je uradila stapanje.

note: (para)
en: You can mark revisions as <emphasis>do not merge</emphasis> by including them in the list of merged revisions without actually doing the merge.
target: Možete obeležiti reviziju kao <emphasis>ne stapaj</emphasis> uključujući je u listu stopljenih revizija bez stvarnog stapanja.

note: (para)
en: Subversion 1.5 introduced facilities for merge tracking. When you merge changes from one tree into another, the revision numbers merged are stored and this information can be used for several different purposes. <placeholder-1/>
target: Subverzija 1.5 uvodi mogućnost za praćenje stapanja. Kada se vaše stapanje menja sa jednog stabla na drugo, revizioni brojevi stopljeni su uskladišteni i ta informacija može biti korišćena za više različitih svrha. <placeholder-1/>

note: (para)
en: Merge tracking information is stored in the <literal>svn:mergeinfo</literal> property by the client when it performs a merge. When the merge is committed the server stores that information in a database, and when you request merge, log or blame information, the server can respond appropriately. For the system to work properly you must ensure that the server, the repository and all clients are upgraded. Earlier clients will not store the <literal>svn:mergeinfo</literal> property and earlier servers will not provide the information requested by new clients.
target: Praćenje stapanja informacija je uskladištena u <literal>svn:mergeinfo</literal> osobini klijenta kada on izvrši stapanje. Kada je stapanje urezano server uskladišti tu informaciju u bazi podataka, i kada zahtevate stapanje, dnevnik ili okrivljavanje informacije, server može odgovoriti odgovarajuće. Za sistem koji radi ispravno morate omogućiti takav server, spremište i svi klijenti su dograđeni. Raniji klijenti neće uskladištiti <literal>svn:mergeinfo</literal> osobinu i raniji serveri neće obezbediti informacije koje traže novi klijenti.

note: (para)
en: Find out more about merge tracking from Subversion's <ulink url="http://subversion.tigris.org/merge-tracking/index.html"><citetitle>Merge tracking documentation</citetitle></ulink>.
target: Nađite više o praćenju stapanja iz Subverzione <ulink url="http://subversion.tigris.org/merge-tracking/index.html"><citetitle>Merge tracking documentation</citetitle></ulink>.

note: (title)
en: Handling Conflicts during Merge
target: Rukovanje konfliktima u toku spajanja

note: (primary)
en: merge conflicts
target: konflikti spajanja

note: (title)
en: The Merge Conflict Callback Dialog
target: Konflikti spajanja dijalog odgovora

note: (para)
en: Merging does not always go smoothly. Sometimes there is a conflict, and if you are merging multiple ranges, you generally want to resolve the conflict before merging of the next range starts. TortoiseSVN helps you through this process by showing the <emphasis>merge conflict callback</emphasis> dialog. <placeholder-1/>
target: Stapanje uvek ne ide ravno. Ponekad ima konflikta, i ako stapate više opsega vi generalno želite da rešite konflikt pre početka stapanja sledećeg opsega. TortoiseSVN vam pomaže kroz ovaj proces prikazivanjem  <emphasis>povratni konflikt stapanja </emphasis>dijalog. <placeholder-1/>

note: (para)
en: You may decide that your local changes are much more important, so you want to discard the version from the repository and keep your local version. Or you might discard your local changes in favour of the repository version. Either way, no attempt is made to merge the changes - you choose one or the other.
target: Možete odlučiti da su vaše lokalne izmene mnogo važne, tako vi želite da izbacite verziju iz spremišta i sačuvate lokalnu verziju. Ili želite da odbacite lokalne izmene kao uslugu verziji spremišta. U svakom slučaju nema pokušaja  da se uradi stapanje izmena . izaberite jedno ili drugo.

note: (para)
en: Normally you will want to look at the conflicts and resolve them. In that case, choose the <guibutton>Edit Conflict</guibutton> which will start up your merge tool. When you are satisfied with the result, click <guibutton>Resolved</guibutton>.
target: Normalno vi ćete želeti da pogledate konflikt i da ga rešite. U tom slučaju, izaberite <guibutton>Uredi Konflikt</guibutton> koji će pokrenuti vaš alat stapanja. Kada ste zadovoljni rezultatom kliknite na <guibutton>Rešen</guibutton>.

note: (para)
en: The last option is to postpone resolution and continue with merging. You can choose to do that for the current conflicted file, or for all files in the rest of the merge. However, if there are further changes in that file, it will not be possible to complete the merge.
target: Poslednja opcija je odlaganje rešavanja i nastaviti stapanje. Možete izabrati da uradite to za tekuće fajlove u konfliktu, ili za fajlove u ostatku stapanja. Kakogod, ako ima daljih izmena u tom fajlu neće biti moguće kompletirati stapanje.

note: (para)
en: When a conflict occurs during the merge, you have three ways to handle it. <placeholder-1/>
target: Kada se konflikt pojavi u toku stapanja imate tri načina da ga opslužite. <placeholder-1/>

note: (para)
en: If you do not want to use this interactive callback, there is a checkbox in the merge progress dialog <guilabel>Merge non-interactive</guilabel>. If this is set for a merge and the merge would result in a conflict, the file is marked as in conflict and the merge goes on. You will have to resolve the conflicts after the whole merge is finished. If it is not set, then before a file is marked as conflicted you get the chance to resolve the conflict <emphasis>during</emphasis> the merge. This has the advantage that if a file gets multiple merges (multiple revisions apply a change to that file), subsequent merges might succeed depending on which lines are affected. But of course you can't walk away to get a coffee while the merge is running ;)
target: Ako ne želite da koristite interaktivan povratni poziv postoji čekboks u progres dijalogu  stapanja <guilabel>Stopi ne-interaktivno</guilabel>. Ako je ovo odabrano  za stapanje  i stapanje prouzrokuje konflikt, fajl je markiran da je u konfliktu i stapanje se nastavlja. Vi ćete rešiti konflikt posle svršetka ukupnog stapanja. Ako nije podešeno onda pre nego se fajl markira kao konfliktan dobijate šansu da rešite konflikt <emphasis>tokom</emphasis> stapanja.Ovo ima prednost ako fajl dobije višestruka spajanja (višestruke revizije primenjuju izmene tog fajl), sukcesivna stapanja se mogu nastaviti u zavisnosti na koje linije se odnosi. Ali svakako ne možete šetati okolo po kafu dok stapanje radi ;)

note: (title)
en: Merge a Completed Branch
target: Spajanje cele grane

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

note: (title)
en: The Merge reintegrate Dialog
target: Dijalog reintegrisanog spajanja

note: (para)
en: If you want to merge all changes from a feature branch back to trunk, then you can use the <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Merge reintegrate...</guimenuitem></menuchoice> from the extended context menu (hold down the <keycap>Shift</keycap> key while you right click on the file). <placeholder-1/> This dialog is very easy. All you have to do is set the options for the merge, as described in <xref linkend="tsvn-dug-merge-options"/>. The rest is done by TortoiseSVN automatically using merge tracking.
target: Ako želite stopiti sve izmene posebne grane nazad u deblo tada možete koristiti <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Stopiti reintegrisano...</guimenuitem></menuchoice> iz proširenog kontekst menija (drži <keycap>Shift</keycap> taster dok desno kliknete na fajl). <placeholder-1/> Ovaj dijalog je veoma lak. Sve što imate da uradite je da podesite opcije za stapanje kako je opisano <xref linkend="tsvn-dug-merge-options"/>. preostalo je dato sa TortoiseSVN automatski koristeći praćenje stapanja.

note: (title)
en: Feature Branch Maintenance
target: Osobina održavanja grane

note: (para)
en: When you develop a new feature on a separate branch it is a good idea to work out a policy for re-integration when the feature is complete. If other work is going on in <literal>trunk</literal> at the same time you may find that the differences become significant over time, and merging back becomes a nightmare.
target: Kada razvijate nove osobine na izdvojenoj grani dobra je ideja da se radi plan reintegracije kda osobina bude kompletna. Ako ostali rad na <literal>deblu</literal> u isto vreme može se ispostaviti da su razlike postale značajne posle nekog vremena i stapanje nazad postaje noćna mora.

note: (para)
en: If the feature is relatively simple and development will not take long then you can adopt a simple approach, which is to keep the branch entirely separate until the feature is complete, then merge the branch changes back into trunk. In the merge wizard this would be a simple <guilabel>Merge a range of revisions</guilabel>, with the revision range being the revision span of the branch.
target: Ako je osobina relativno jednostavna i razvoj nije bio dug možete prihvatiti jednostavan pristup, koji drži celu granu izdvojenu dok se osobina ne kompletira, zatim se stapa izmena grane nazad u deblo. U čarobnjaku stapanja to će biti jednostavno <guilabel>Stopi opseg revizija</guilabel>, sa opsegom revizija koji je revizioni opseg grane.

note: (para)
en: If the feature is going to take longer and you need to account for changes in <literal>trunk</literal>, then you need to keep the branch synchronised. This simply means that periodically you merge trunk changes into the branch, so that the branch contains all the trunk changes <emphasis>plus</emphasis> the new feature. The synchronisation process uses <guilabel>Merge a range of revisions</guilabel>. When the feature is complete then you can merge it back to <literal>trunk</literal> using either <guilabel>Reintegrate a branch</guilabel> or <guilabel>Merge two different trees</guilabel>.
target: Ako osobina uzima mnogo vremena i treba vam račun za izmene u <literal>deblu</literal>, potrbno je da zadržite sinhronizaciju grane. To jednostavno znači da periodično stapate izmene debla u granu, tako da grana sadrži sve izmene debla <emphasis>plus</emphasis> nove osobine. Proces sinhronizacije koristi <guilabel>Stopi opseg revizija</guilabel>. Kada je osobina kompletna možete je stopiti nazad na <literal>deblo</literal> koristeći ili <guilabel>Reintegriši granu</guilabel> ili <guilabel>Stopi dva različita stabla</guilabel>.

note: (title)
en: Locking
target: Zaključavanje

note: (primary)
en: locking
target: zaključavanje

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

note: (para)
en: You are using <quote>unmergeable</quote> files, for example, graphics files. If two people change the same file, merging is not possible, so one of you will lose their changes.
target: Vi koristite <quote>nestopive</quote> fajlove, grafičke fajlove. Ako dva čoveka izmene isti fajl, stapanje nije moguće, tako da jedan od vas će izgubiti svoje izmene.

note: (para)
en: Your company has always used a locking revision control system in the past and there has been a management decision that <quote>locking is best</quote>.
target: Vaša kompanija je uvek koristila zaključan sistema kontrole verzija u prošlosti i postoji  odluka uprave da <quote>zaključavanje je najbolje</quote>.

note: (para)
en: Subversion generally works best without locking, using the <quote>Copy-Modify-Merge</quote> methods described earlier in <xref linkend="tsvn-basics-versioning-copymodifymerge"/>. However there are a few instances when you may need to implement some form of locking policy. <placeholder-1/>
target: Subverzija generalno radi najbolje bez zaključavanja, koristeći <quote>Kopiraj-Izmeni-Stopi</quote> metode opisane ranije u <xref linkend="tsvn-basics-versioning-copymodifymerge"/>. Ipak, postoji nekoliko primera kada možete imati potrebu da primenite neku vrstu politike zaključavanja. <placeholder-1/>

note: (para)
en: Firstly you need to ensure that your Subversion server is upgraded to at least version 1.2. Earlier versions do not support locking at all. If you are using <literal>file://</literal> access, then of course only your client needs to be updated.
target: Najpre treba obezbediti da Subverzioni server dograđen najmanje na verziju 1.2. Ranije verzije uopšte ne podržavaju zaključavanje. Ako koristite <literal>file://</literal> pristup, svakako samo vaš klijent treba da bude ažuriran.

note: (title)
en: How Locking Works in Subversion
target: Kako zaključavanje radi na Subverziji

note: (para)
en: By default, nothing is locked and anyone who has commit access can commit changes to any file at any time. Others will update their working copies periodically and changes in the repository will be merged with local changes.
target: Uobičajeno, ništa nije zaključano i svako ko ima pristup urezivanju može urezivati izmene u svaki fajl u bilo koje vreme. Ostali će ažurirati svoje radne kopije periodično i izmene u spremištu će biti stopljene sa lokalnim izmenama.

note: (para)
en: If you <firstterm>Get a Lock</firstterm> on a file, then only you can commit that file. Commits by all other users will be blocked until you release the lock. A locked file cannot be modified in any way in the repository, so it cannot be deleted or renamed either, except by the lock owner.
target: Ako vi <firstterm>Stavite Katanac</firstterm> na fajl, onda samo vi možete urezivati taj fajl. Urezivanje svih ostalih korisnika je blokirano sve dok ne skinete katanac. Zaključan fajl ne može biti izmenjen na bilo koji način u spremištu, on ne može biti obrisan ili preimenovan, osim od vlasnika katanca.

note: (para)
en: However, other users will not necessarily know that you have taken out a lock. Unless they check the lock status regularly, the first they will know about it is when their commit fails, which in most cases is not very useful. To make it easier to manage locks, there is a new Subversion property <literal>svn:needs-lock</literal>. When this property is set (to any value) on a file, whenever the file is checked out or updated, the local copy is made read-only <emphasis>unless</emphasis> that working copy holds a lock for the file. This acts as a warning that you should not edit that file unless you have first acquired a lock. Files which are versioned and read-only are marked with a special overlay in TortoiseSVN to indicate that you need to acquire a lock before editing.
target: Međutim, drugi korisnici neće neophodno znati da ste uklonili katanac. Osim da provere status zaključavanja regularno, najpre oni moraju znati  o tome kada urezivanje utkaže, što u većini slučajeva nije mnogo krisno. Da biste učinili to lakšim za manipulaciju postoji nova Subverziona osobina <literal>svn:needs-lock</literal>. Kada je ova osobina podešena (na bilo koju vrednost) na fajlu, kadgod se fajl preuzima ili ažurira, lokalna kopija postaje samo za čitanje <emphasis>osim</emphasis> ako ta radna kopija drži katanac za fajl. Ovo deluje kao upozorenje tako da ne možete uređivati taj fajl osim ako najpre ne dobijete katanac. Fajlovi koji su verzionisani i samo za čitanje označeni su specijalnim prekrivačem u TortoiseSVN da ukažu da treba da dobijete katanac pre uređenja.

note: (para)
en: Locks are recorded by working copy location as well as by owner. If you have several working copies (at home, at work) then you can only hold a lock in <emphasis>one</emphasis> of those working copies.
target: Zaključavanje je upisano u lokaciji radne kopije kao i vlasnik. Ako imate više radnih kopija (kući, na poslu) vi možete samo da držite katanac na <emphasis>jednoj</emphasis> od tih radnih kopija.

note: (para)
en: If one of your co-workers acquires a lock and then goes on holiday without releasing it, what do you do? Subversion provides a means to force locks. Releasing a lock held by someone else is referred to as <firstterm>Breaking</firstterm> the lock, and forcibly acquiring a lock which someone else already holds is referred to as <firstterm>Stealing</firstterm> the lock. Naturally these are not things you should do lightly if you want to remain friends with your co-workers.
target: Ako jedan od vaših saradnika traži katanac i ode na odmor bez otključavanja šta da se radi? Subverzija omogućava način da se forsira zaključavanje. Otključavanje od još nekog označeno je kao <firstterm>Razbijanje</firstterm> katanca, a nasilno otključavanje koje neko uradi zove se <firstterm>Krađa</firstterm> katanca. Prirodno, ovo nisu stvari koje treba da radite olako ako želite da ostanete prijatelj sa saradnicima

note: (para)
en: Locks are recorded in the repository, and a lock token is created in your local working copy. If there is a discrepancy, for example if someone else has broken the lock, the local lock token becomes invalid. The repository is always the definitive reference.
target: Zaključavanje se upisuje u spremištu i katanac žeton se kreira u vašoj lokalnoj radnoj kopiji. Ako postoji različitos, na primer ako još neko ima slomljen katanac, lokalni žeton katanac postaje neispravan. Spremište je uvek definitivna referenca.

note: (title)
en: Getting a Lock
target: Zaključavanje

note: (title)
en: The Locking Dialog
target: Dijalog zaključavanja

note: (para)
en: Select the file(s) in your working copy for which you want to acquire a lock, then select the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Get Lock...</guimenuitem></menuchoice>. <placeholder-1/> A dialog appears, allowing you to enter a comment, so others can see why you have locked the file. The comment is optional and currently only used with Svnserve based repositories. If (and <emphasis>only</emphasis> if) you need to steal the lock from someone else, check the <guilabel>Steal lock</guilabel> box, then click on <guibutton>OK</guibutton>.
target: Izaberite fajl(ove) u vašoj radnoj kopiji za koje želite da dobijete katanac, zatim izaberite komandu <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Zaključaj...</guimenuitem></menuchoice>. <placeholder-1/> Dijalog se pojavljuje dozvoljavajući da unesete komentar, tako ostali mogu videti zašto ste zaključali fajl. Komentar nije obavezan i trenutno se koristi samo  sa Svnserve osnovanim spremištima. Ako ( i <emphasis>samo</emphasis> i) trebate da ukradete katanac od nekog proverite <guilabel>Još uvek zaključan</guilabel> boks, zatim kliknite na <guibutton>OK</guibutton>.

note: (para)
en: If you select a folder and then use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Get Lock...</guimenuitem></menuchoice> the lock dialog will open with <emphasis>every</emphasis> file in <emphasis>every</emphasis> sub-folder selected for locking. If you really want to lock an entire hierarchy, that is the way to do it, but you could become very unpopular with your co-workers if you lock them out of the whole project. Use with care ...
target: Ako izaberete imenik i onda koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Zaključaj...</guimenuitem></menuchoice> dijalog zaključavanja će se otvoriti sa <emphasis>svakim</emphasis> fajlom u <emphasis>svakom</emphasis> pod-imeniku izabranom za zaključavanje. Ako stvarno želite da zaključate celu hijerarhiju, ovo je način da to uradite, ali ćete postati jako nepopularni među saradnicima ako im zaključate ceo projekat. Koristite pažljivo...

note: (title)
en: Releasing a Lock
target: Otključavanje

note: (para)
en: To make sure you don't forget to release a lock you don't need any more, locked files are shown in the commit dialog and selected by default. If you continue with the commit, locks you hold on the selected files are removed, even if the files haven't been modified. If you don't want to release a lock on certain files, you can uncheck them (if they're not modified). If you want to keep a lock on a file you've modified, you have to enable the <guilabel>Keep locks</guilabel> checkbox before you commit your changes.
target: Da biste osigurali da ne zaboravite da otključate ne treba vam ništa posebno, zaključani fajlovi su prikazani u dijalogu urezivanja i izabrani podrazumevano. Ako nastavite sa urezivanjem, katanac koji držite na izabranim fajlvima se uklanja, čak i ako fajlovi nisu izmenjeni. Ako ne želite da uklonite katanac sa nekih fajlva možete ih otčekirati (ako nisu izmenjeni). Ako želite da držite katanac na fajlu koji ste izmenili imate da omogućite <guilabel>Drži katanac</guilabel> čekboks pre urezivanja izmena.

note: (para)
en: To release a lock manually, select the file(s) in your working copy for which you want to release the lock, then select the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Release Lock</guimenuitem></menuchoice> There is nothing further to enter so TortoiseSVN will contact the repository and release the locks. You can also use this command on a folder to release all locks recursively.
target: Da se ukloni katanac ručno, izaberite fajl(ove) u vašoj radnoj kopiji za koje hoćete da uklonite katanac, zatim izaberite komandu  <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Otključaj</guimenuitem></menuchoice> Ništa dalje ne treba uneti jer TortoiseSVN kontaktira spremište i uklanja katance. Takođe možete koristiti komandu na imeniku da uklonite sve katance rekurzivno.

note: (title)
en: Checking Lock Status
target: Provera statusa zaključavanja

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

note: (para)
en: <placeholder-1/> To see what locks you and others hold, you can use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Check for Modifications...</guimenuitem></menuchoice>. Locally held lock tokens show up immediately. To check for locks held by others (and to see if any of your locks are broken or stolen) you need to click on <guibutton>Check Repository</guibutton>.
target: <placeholder-1/> Da vidite koje katance vi i drugi držite, koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Provera izmena...</guimenuitem></menuchoice>.  Lokalno držan katanac žetoni se prikažu trenutno. Da biste proverili koje katance drže ostali (i da vidite da li je neki vaš katanac slomljen ili ukraden) treba da kliknete na <guibutton>Proveri Spremište</guibutton>.

note: (para)
en: From the context menu here, you can also get and release locks, as well as breaking and stealing locks held by others.
target: Iz kontekst menija ovde možete takođe staviti ili otkačiti katanac, kao i slomljene i ukradene katance koje drže drugi.

note: (title)
en: Avoid Breaking and Stealing Locks
target: Izbegavanje razbijanja i krađa katanca

note: (para)
en: If you break or steal someone else's lock without telling them, you could potentially cause loss of work. If you are working with unmergeable file types and you steal someone else's lock, once you release the lock they are free to check in their changes and overwrite yours. Subversion doesn't lose data, but you have lost the team-working protection that locking gave you.
target: Ako slomite ili ukradete nekom drugom katanac bez pitanja možete potencijalno uzrokovati gubitak posla. Ako radite sa nestopivim tipom fajlva i nekom ukradete katanac kada vratite katanac oni su slobodni da provere svoje izmene i prekriju vaše. Subverzija ne gubi podatke ali vi možete izgubiti radnu zaštitu tima koje va zaključavanje omogućava.

note: (title)
en: Making Non-locked Files Read-Only
target: Pravljenje nezaključanih fajlova samo za čitanje

note: (para)
en: As mentioned above, the most effective way to use locking is to set the <literal>svn:needs-lock</literal> property on files. Refer to <xref linkend="tsvn-dug-propertypage"/> for instructions on how to set properties. Files with this property set will always be checked out and updated with the read-only flag set unless your working copy holds a lock. <graphic fileref="../images/ReadOnlyIcon.png"/> As a reminder, TortoiseSVN uses a special overlay to indicate this.
target: Kako je napomenuto gore, mnogo efektivniji način za korišćenje zaključavanja je podešavanjem <literal>svn:needs-lock</literal> osobine na fajlu. Uporedite sa <xref linkend="tsvn-dug-propertypage"/> za instrukcije kako podesiti te osobine. Fajlovi sa tim osobinama podešenim će uvek biti preuzimani i ažurirani sa setovanim flegom samo-za-čitanje osim ako vaša kopija drži katanac. <graphic fileref="../images/ReadOnlyIcon.png"/> Kao podsetnik, TortoiseSVN koristi specijalni prekrivač da označi to.

note: (para)
en: If you operate a policy where every file has to be locked then you may find it easier to use Subversion's auto-props feature to set the property automatically every time you add new files. Read <xref linkend="tsvn-dug-propertypage-auto-props"/> for further information.
target: Ako radite sa politikom da svaki fajl može biti zaključan tada možda shvatite da je lakše da koristite Subverzionu suto-props osobinu da podesite osobine automatski svaki put kad dodajete novi fajl. Pročitajte <xref linkend="tsvn-dug-propertypage-auto-props"/> za dalje informacije.

note: (title)
en: The Locking Hook Scripts
target: Zakačive skripte za zaključavanje

note: (para)
en: When you create a new repository with Subversion 1.2 or higher, four hook templates are created in the repository <filename>hooks</filename> directory. These are called before and after getting a lock, and before and after releasing a lock.
target: Kada kreirate novo spremište sa Subverzijom 1.2 ili višom, četiri modela zakačaljki se kreira u spremištu  <filename>zakačaljke</filename> imenik.One se pozivaju pre i posle postavljanja katanca i pre i posle skidanja katanca.

note: (para)
en: It is a good idea to install a <literal>post-lock</literal> and <literal>post-unlock</literal> hook script on the server which sends out an email indicating the file which has been locked. With such a script in place, all your users can be notified if someone locks/unlocks a file. You can find an example hook script <filename>hooks/post-lock.tmpl</filename> in your repository folder.
target: Dobra je ideja da se instalira literal>post-zaključavanja</literal> and <literal>post-otključavanjak</literal> zakačiva skripta na serveru koja šalje epoštu označivši fajl koji je zaključan. Sa takvom skriptom svi vaši korisnici mogu biti obavešteni ako neko zaključa/otključa fajl. Možete naći primer zakačive skripte <filename>hooks/post-lock.tmpl</filename> u vašem imeniku spremišta

note: (para)
en: You might also use hooks to disallow breaking or stealing of locks, or perhaps limit it to a named administrator. Or maybe you want to email the owner when one of their locks is broken or stolen.
target: Možete takođe koristiti zakačljke da onemogućite lomljenje i krađu katanaca, ili možda graničiti to na imenovanog administratora. Ili možda želite da pošaljete epoštu vlasnicima kada je neki od njihovih katanaca slomljen ili ukraden.

note: (para)
en: Read <xref linkend="tsvn-repository-hooks"/> to find out more.
target: Pročitajte <xref linkend="tsvn-repository-hooks"/> za više infižormacija.

note: (title)
en: Creating and Applying Patches
target: Kreiranje i primena zakrpa

note: (primary)
en: patch
target: zakrpa

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

note: (para)
en: For open source projects (like this one) everyone has read access to the repository, and anyone can make a contribution to the project. So how are those contributions controlled? If just anyone could commit changes, the project would be permanently unstable and probably permanently broken. In this situation the change is managed by submitting a <firstterm>patch</firstterm> file to the development team, who do have write access. They can review the patch first, and then either submit it to the repository or reject it back to the author.
target: Za projekte otvorenog koda (kao ovaj) svako može da ima pristup čitanju spremišta, i svako može da doprinese projektu. Dakle kako se ti doprinosi kontrolišu? Ako samo svako urezuje izmene projekat će biti stalno nestabilan i moguće permanentno slomljen. U ovoj situaciji izmene se upravljaju predlaganjem <firstterm>zakrpa</firstterm> fajlova razvojnom timu koji ima pristup upisivanju. Oni mogu pregledati zakrpu najpre i onda ili je uneti u spremište ili je vratiti nazad autoru.

note: (para)
en: Patch files are simply Unified-Diff files showing the differences between your working copy and the base revision.
target: Fajlovi zakrpa su jednostavno Jedinstveni-Diff fajlovi koji prikazuju razlike između vaše radne kopije i osnovne revizije.

note: (title)
en: Creating a Patch File
target: Kreiranje fajla zakrpe

note: (para)
en: First you need to make <emphasis>and test</emphasis> your changes. Then instead of using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Commit...</guimenuitem></menuchoice> on the parent folder, you select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Create Patch...</guimenuitem></menuchoice>
target: Najpre treba da napravite <emphasis>i test</emphasis> vaših izmena. Zatim umesto da koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ureži...</guimenuitem></menuchoice> na predačkom imeniku, izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Kreiraj Zakrpu...</guimenuitem></menuchoice>

note: (title)
en: The Create Patch dialog
target: Kreiranje dijaloga zakrpe

note: (para)
en: you can now select the files you want included in the patch, just as you would with a full commit. This will produce a single file containing a summary of all the changes you have made to the selected files since the last update from the repository.
target: možete sada izabrati fajlove koje hoćete da uključite u zakrpu, isto kako želite sa punim urezivanjem. Ovo će proizvesti pojedinačni fajl kji sadrži rezultat svih izmena kaoje ste uradili na izabranim fajlovima od zadnjeg ađuriranja iz spremišta.

note: (para)
en: You can produce separate patches containing changes to different sets of files. Of course, if you create a patch file, make some more changes to the <emphasis>same</emphasis> files and then create another patch, the second patch file will include <emphasis>both</emphasis> sets of changes.
target: Možete proizvesti izdvojene zakrpe koje sadrže izmene različitih skupova fajlova. Svakako, ako kreirate fajl zakrpu, uradite još neku izmenu na <emphasis>istim</emphasis> fajlovima i onda kreirajte sledeću zakrpu, drugi fajl zakrpe će uključivati <emphasis>oba</emphasis> skupa izmena.

note: (para)
en: Just save the file using a filename of your choice. Patch files can have any extension you like, but by convention they should use the <filename>.patch</filename> or <filename>.diff</filename> extension. You are now ready to submit your patch file.
target: Samo sačuvajte fajl koristeći fajlime po vašem izboru. Fajlovi zakrpa imaju ekstenziju koju god želite, ali konvencionalno bi trebalo da koriste filename>.patch</filename> ili <filename>.diff</filename> ekstenziju. Sada ste spremni da podnesete vaš fajl zakrpu.

note: (para)
en: You can also save the patch to the clipboard instead of to a file. You might want to do this so that you can paste it into an email for review by others. Or if you have two working copies on one machine and you want to transfer changes from one to the other, a patch on the clipboard is a convenient way of doing this.
target: Možete takođe da sačuvate zakrpu u klipbordu umesto u fajlu. Možete želeti da to uradite tako da ga nalepite u epoštu da ga pregledaju ostali. Ili ako imate radnu kopiju na jednoj mašini i želite da prenesete izmene sa jedne na drugu, zakrpa na klipbordu je konvencionalni način da to uradite.

note: (title)
en: Applying a Patch File
target: Primena fajla zakrpe

note: (para)
en: Patch files are applied to your working copy. This should be done from the same folder level as was used to create the patch. If you are not sure what this is, just look at the first line of the patch file. For example, if the first file being worked on was <filename>doc/source/english/chapter1.xml</filename> and the first line in the patch file is <filename>Index: english/chapter1.xml</filename> then you need to apply the patch to the <filename>doc/source/</filename> folder. However, provided you are in the correct working copy, if you pick the wrong folder level, TortoiseSVN will notice and suggest the correct level.
target: Fajlovi zakrpa se primenjuju na vašu radnu kopiju. Biće urađeni na istom nivou imenika koji su korišćeni kada je kreirana zakrpa. Ako niste sigurni šta je to, samo pogledajte prvu liniju fajla zakrpe. Na primer, ako je prvi fajl radio na s <filename>doc/source/english/chapter1.xml</filename> i prva linija fajla zakrpe je <filename>Index: english/chapter1.xml</filename> tada je potrebno da primenite zakrpu na <filename>doc/source/</filename> imenik. Međutim, omogućava vam da ste na korektnoj radnoj kopiji, ako izaberete neispravan nivo foldera, TortoiseSVN će to notirati i predložiti vam korektan nivo.

note: (para)
en: In order to apply a patch file to your working copy, you need to have at least read access to the repository. The reason for this is that the merge program must reference the changes back to the revision against which they were made by the remote developer.
target: Da bi primenili fajl zakrpe na vašu radnu kopiju potrebno vm je da imate najmanje pristup za čitanje spremišta. Razlog za ovo je da program stapanja mora da uporedi izmene nazad sa revizijom prema kojoj je urađen od udaljenog saradnika.

note: (para)
en: From the context menu for that folder, click on <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Apply Patch...</guimenuitem></menuchoice> This will bring up a file open dialog allowing you to select the patch file to apply. By default only <filename>.patch</filename> or <filename>.diff</filename> files are shown, but you can opt for <quote>All files</quote>. If you previously saved a patch to the clipboard, you can use <guibutton>Open from clipboard...</guibutton> in the file open dialog.
target: Iz kontekst menija za taj imenik, kliknite na menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Primeni Zakrpu...</guimenuitem></menuchoice> Ovo će otvoriti fajl otvori dijalog dozvoljavajući vam da izaberete fajl zakrpu za primenu. Uobičajeno samo <filename>.patch</filename> ili <filename>.diff</filename> fajlovi su prikazani, ali može se izabrati opcija za <quote>All files</quote>. Ako ste prethodno sačuvali zakrpu u klipbord možete koristiti <guibutton>Otvori iz klipborda...</guibutton> u fajl open dijalogu.

note: (para)
en: Alternatively, if the patch file has a <filename>.patch</filename> or <filename>.diff</filename> extension, you can right click on it directly and select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Apply Patch...</guimenuitem></menuchoice>. In this case you will be prompted to enter a working copy location.
target: Alternativno, ako fajl zakrpa ima <filename>.patch</filename> ili <filename>.diff</filename> ekstenziju, možete desnim klikom na taj direktorijum da izaberete <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Primeni Zakrpu...</guimenuitem></menuchoice>. U tom slučaju bićete pitani da unesete lokaciju radne kopije.

note: (para)
en: These two methods just offer different ways of doing the same thing. With the first method you select the WC and browse to the patch file. With the second you select the patch file and browse to the WC.
target: Ova dva metoda tek nude različite načine da se uradi ista stvar. Sa prvim metodom birate RK i pretražujete fajl zakrpa. Drugim birate fajl zakrpe i pretražujete RK.

note: (para)
en: Once you have selected the patch file and working copy location, TortoiseMerge runs to merge the changes from the patch file with your working copy. A small window lists the files which have been changed. Double click on each one in turn, review the changes and save the merged files.
target: Jednom kad izaberete fajl zakrpa i lokaciju radne kopije, TortoiseSVN kreće da stapa izmene iz fajla zakrpa sa vašom radnom kopijom. Mali prozor lista fajlove  koji će biti izmenjeni. Dvostruki klik na svaki  redom prikazaće izmene i sačuvati stopljene fajlove.

note: (para)
en: The remote developer's patch has now been applied to your working copy, so you need to commit to allow everyone else to access the changes from the repository.
target: Daljinski razvojne zakrpe  su primenjene na vašoj radnoj kopiji tako da je potrebno urezati da se dozvoljava još nekom da menja iz spremišta.

note: (title)
en: Who Changed Which Line?
target: Ko je izmenio koju liniju?

note: (primary)
en: blame
target: okriviti

note: (primary)
en: annotate
target: obeleži

note: (primary)
en: praise
target: veličina

note: (para)
en: Sometimes you need to know not only what lines have changed, but also who exactly changed specific lines in a file. That's when the <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Blame...</guimenuitem></menuchoice> command, sometimes also referred to as <firstterm>annotate</firstterm> command comes in handy.
target: Ponekad treba da znate ne samo linije koje su izmenjene, ali takođe ko je tačno  izmenio određene linije u fajlu. Kada <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Okrivi...</guimenuitem></menuchoice> komanda, ponekad se takođe poziva na <firstterm>anotiranje</firstterm> korisnih komandi.

note: (para)
en: This command lists, for every line in a file, the author and the revision the line was changed.
target: Ova komanda lista, za svaku liniju u fajlu, autora i reviziju linije koja je izmenjena.

note: (title)
en: Blame for Files
target: Krivac za fajl

note: (title)
en: The Annotate / Blame Dialog
target: Beleška/Krivac dijalog

note: (para)
en: <placeholder-1/> If you're not interested in changes from earlier revisions you can set the revision from which the blame should start. Set this to <literal>1</literal>, if you want the blame for <emphasis>every</emphasis> revision.
target: <placeholder-1/> Ako vas ne interesuju izmene iz ranijih revizija možete podesiti reviziju odakle će okrivljavanje početi. Podesite to na <literal>1</literal>, ako želite da okrivite  <emphasis>svaku</emphasis> reviziju.

note: (para)
en: By default the blame file is viewed using <firstterm>TortoiseBlame</firstterm>, which highlights the different revisions to make it easier to read. If you wish to print or edit the blame file, select <guilabel>Use Text viewer to view blames</guilabel>
target: Uobičajeno je da okrivljavanje fajl se pregleda koristeći <firstterm>TortoiseBlame</firstterm>, što osvetljava različite revizije što ih čini lakšim za čitanjem. Ako želite da štampate ili uredite fajl okrivljavanja, izaberite <guilabel>Koristi Tekst pregledač da vidite okrivljavanje</guilabel>

note: (para)
en: You can specify the way that line ending and whitespace changes are handled. These options are described in <xref linkend="tsvn-dug-diff-eol-whitespace"/>. The default behaviour is to treat all whitespace and line-end differences as real changes, but if you want to ignore an indentation change and find the original author, you can choose an appropriate option here.
target: Možete specificirati način rukovanja završetkom linije i izmenom belihpolja. Ove opcije su opisane u <xref linkend="tsvn-dug-diff-eol-whitespace"/>. Uobičajeno ponašanje se tretiraju sva belapolja i kraj linija razlike kao realne izmene, ali ako želite da zanemarite uvlačenje izmene i naći originalne autore možete izabrati odgovarajuće opcije ovde.

note: (para)
en: Once you press <guibutton>OK</guibutton> TortoiseSVN starts retrieving the data to create the blame file. Please note: This can take several minutes to finish, depending on how much the file has changed and of course your network connection to the repository. Once the blame process has finished the result is written into a temporary file and you can view the results.
target: Kada jednom pritisnete <guibutton>OK</guibutton> TortoiseSVN počinje vraćati podatke da kreira fajl okrivljavanja. Molim primetite: Ovo može uzeti nekoliko minuta da se završi, u zavisnosti od toga koliko je fajl izmenjen i svakako mrežne konekcije u spremištu. Jednom kada proces okrivljavanja završi rezultat je upisan u privremeni fajl i vi možete videti rezultat.

note: (title)
en: TortoiseBlame
target: TortozBlame

note: (para)
en: <placeholder-1/> TortoiseBlame, which is included with TortoiseSVN, makes the blame file easier to read. When you hover the mouse over a line in the blame info column, all lines with the same revision are shown with a darker background. Lines from other revisions which were changed by the same author are shown with a light background. The colouring may not work as clearly if you have your display set to 256 colour mode.
target: <placeholder-1/> TortoiseBlame, koji koji je uključen sa TortoiseSVN, čini fajl okrivljavanja lakši za čitanje. Kada letite mišem preko linije u info kolonama okrivljavanja, sve linije sa istom revizijom su prikazani sa mračnijom osnovom. Linije iz raznih revizija koje su izmenjene od istih autora su prikazani sa svetlom osnovom. Bojenje ne može raditi tako kjasno ako je displej podešen u 256 boja modu.

note: (para)
en: If you <action>left click</action> on a line, all lines with the same revision are highlighted, and lines from other revisions by the same author are highlighted in a lighter colour. This highlighting is sticky, allowing you to move the mouse without losing the highlights. Click on that revision again to turn off highlighting.
target: Ako uradite <action>levi klik</action> na liniju, sve linijesa istom revizijom su osvetljene, i linije od drugih revizija od istog autora su osvetljene svetlijom bojom. Ovo osvetljavanje je prilepljivo, omogućava pomeranje miša bez gubljenja osvetljenja. Kliknite na tu reviziju ponovo da biste isključili osvetljavanje.

note: (para)
en: The revision comments (log message) are shown in a hint box whenever the mouse hovers over the blame info column. If you want to copy the log message for that revision, use the context menu which appears when you right click on the blame info column.
target: Revizioni komentari (dnevnik poruke) su prikazani u boksu napomena kadgod miš leti preko info kolone okrivljavanja. Ako želite da kopirate dnevnik poruku za tu reviziju, koristite kontekst meni koji se pojavljuje kada uradite desni klik na info kolonu okrivljavanja.

note: (para)
en: You can search within the Blame report using <menuchoice><guimenu>Edit</guimenu><guimenuitem>Find...</guimenuitem></menuchoice>. This allows you to search for revision numbers, authors and the content of the file itself. Log messages are not included in the search - you should use the Log Dialog to search those.
target: Možete pretraživati unutar Okrivi izveštaja koristeći <menuchoice><guimenu>Uredi</guimenu><guimenuitem>Nađi...</guimenuitem></menuchoice>. Ovo dopušta da pretražujete revizione brojeve, autore i sadržaj samog fajla. Dnevnik poruke nisu uključene u pretraživanje - treba da koristite  Dnevnik Dijalog da pretraažujete njih.

note: (para)
en: You can also jump to a specific line number using <menuchoice><guimenu>Edit</guimenu><guimenuitem>Go To Line...</guimenuitem></menuchoice>.
target: Možete takođe skočiti na specifični broj linije koristeći <menuchoice><guimenu>Uredi</guimenu><guimenuitem>Idi Na Liniju...</guimenuitem></menuchoice>.

note: (para)
en: When the mouse is over the blame info columns, a context menu is available which helps with comparing revisions and examining history, using the revision number of the line under the mouse as a reference. <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Blame previous revision</guimenuitem></menuchoice> generates a blame report for the same file, but using the previous revision as the upper limit. This gives you the blame report for the state of the file just before the line you are looking at was last changed. <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Show changes</guimenuitem></menuchoice> starts your diff viewer, showing you what changed in the referenced revision. <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Show log</guimenuitem></menuchoice> displays the revision log dialog starting with the referenced revision.
target: Kada miš leti preko info kolona okrivljavanja, kontekst meni je dostupan što vam pomaže poređenjem revizija i pregledom istorije, koristeći revizione brojeve linija pod mišem kao referencu. <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Okrivi prethodnu reviziju</guimenuitem></menuchoice> generiše izveštaj okrivljavanja za iste fajlve, ali koristeći prethodnu reviziju kao gornju granicu. Ovo daje izveštaj okrivljavanja za stanje fajla baš pre linije koju gledate koja je zadnja izmenjena. <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Prikaži Izmene</guimenuitem></menuchoice> pokreće vaš diff pregledač, prikazujući vam šta je izmenjeno u referentnoj reviziji. <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Prikaži Dnevnik</guimenuitem></menuchoice> prikazuje revizioni dnevnik dijalog počevši sa referentnom revizijom.

note: (para)
en: If you need a better visual indicator of where the oldest and newest changes are, select <menuchoice><guimenu>View</guimenu><guimenuitem>Color age of lines</guimenuitem></menuchoice>. This will use a colour gradient to show newer lines in red and older lines in blue. The default colouring is quite light, but you can change it using the TortoiseBlame settings.
target: Ako vam treba bolji vizualni indikator gde su najstarije i najnovije izmene, izaberi  <menuchoice><guimenu>Vidi</guimenu><guimenuitem>Boja starosti linija</guimenuitem></menuchoice>. Obojenje ja sasvim svetlo, vo će koristiti gradijent boje da prikaže novije linije plavo. Uobičajeno bojenje je sasvim svetlo, ali možete ga promeniti koristeći TortoiseBlame podešavanje.

note: (para)
en: If you are using Merge Tracking, where lines have changed as a result of merging from another path, TortoiseBlame will show the revision and author of the last change in the original file rather than the revision where the merge took place. These lines are indicated by showing the revision and author in italics. If you do not want merged lines shown in this way, uncheck the <guilabel>Include merge info</guilabel> checkbox.
target: Ako koristite Stapanje Praćenje, gde su linije izmenjene kao rezultat stapanjaiz druge putanje, TortoiseBlame će pokazati reviziju i autora zadnje izmene u originalnom fajlu radije nego revizija gde se stapanje desilo. Ove linije su označene prikazivanjem revizije i autora u italiku. Ako ne želite da stopite linije prikazane ovog puta otčekiraj <guilabel>Uključi info stapanja</guilabel> checkbox.

note: (para)
en: If you want to see the paths involved in the merge, select <menuchoice><guimenu>View</guimenu><guimenuitem>Merge paths</guimenuitem></menuchoice>.
target: Ako želite da vidite putanju umešane u stapanje, izaberite <menuchoice><guimenu>Vidi</guimenu><guimenuitem>Putanja stapanja</guimenuitem></menuchoice>.

note: (para)
en: The settings for TortoiseBlame can be accessed using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Settings...</guimenuitem></menuchoice> on the TortoiseBlame tab. Refer to <xref linkend="tsvn-dug-settings-tortoiseblame"/>.
target: Podešavanju TortoiseBlame može ste pristupiti koristeći  <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Podešavanja...</guimenuitem></menuchoice> na TortoiseBlame tab. Uporedite sa <xref linkend="tsvn-dug-settings-tortoiseblame"/>.

note: (title)
en: Blame Differences
target: Razlikeke okrivljavanja

note: (para)
en: One of the limitations of the Blame report is that it only shows the file as it was in a particular revision, and shows the last person to change each line. Sometimes you want to know what change was made, as well as who made it. What you need here is a combination of the diff and blame reports.
target: Jedno od ograničenja izveštaja Okrivljavanja je da se samo prikazuje fajl kakav je bio u partikularnoj reviziji, i prikazuje zadnju osobu koja menja svaku liniju. Ponekad želite da znate koje izmene su urađene, kao i ko ih je uradio. Sve što vam je ovde potrebno je kombinacija diff i okrivljavanja izveštaj.

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

note: (para)
en: In the top pane, select 2 revisions, then select <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Blame revisions</guimenuitem></menuchoice>. This will fetch the blame data for the 2 revisions, then use the diff viewer to compare the two blame files.
target: U gornjem panelu izaberite 2 revizije, zatim izaberite <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Okrivljavanje revizija</guimenuitem></menuchoice>. Ovo će naći podatke okrivaljavanja za 2 revizije, zatim koristite diff pregledač da uporedite dva fajla okrivljavanja.

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

note: (para)
en: Select one revision in the top pane, then pick one file in the bottom pane and select <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Blame changes</guimenuitem></menuchoice>. This will fetch the blame data for the selected revision and the previous revision, then use the diff viewer to compare the two blame files.
target: Izaberite jednu reviziju u gornjem panelu, zatim izaberite jedan fajl u donjem panelu i izaberite <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Okrivi izmene</guimenuitem></menuchoice>. Ovo će naći podatke okrivljavanja za izabrane revizije i prethodnih revizija, zatim koristite diff pregledač da uporedite dva fajla okrivljavanja.

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

note: (para)
en: Show the log for a single file, and in the top pane, select a single revision, then select <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Compare and Blame with Working BASE</guimenuitem></menuchoice>. This will fetch the blame data for the selected revision, and for the file in the working BASE, then use the diff viewer to compare the two blame files.
target: Prikažite dnevnik za pojedinačni fajl, i na gornjem  panelu, izaberite pojdinačnu reviziju, zatim izaberite <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Uporedite sa Radnom OSNOVOM</guimenuitem></menuchoice>. Ovo će naći podatke okrivljavanja za izabrane revizije, i za fajlove u radnoj OSNOVI, zatim koristite diff pregledač da uporedite dva fajla okrivljavanja.

note: (para)
en: The revision log dialog includes several options which allow you to do this. <placeholder-1/>
target: Dijalog dnevnika revizije uključuje više opcija koje omogućavaj da to uradite. <placeholder-1/>

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

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

note: (primary)
en: server-side actions
target: akcije serverske strane

note: (primary)
en: server viewer
target: server pregledač

note: (para)
en: Sometimes you need to work directly on the repository, without having a working copy. That's what the <firstterm>Repository Browser</firstterm> is for. Just as the explorer and the icon overlays allow you to view your working copy, so the Repository Browser allows you to view the structure and status of the repository. <placeholder-1/> With the Repository Browser you can execute commands like copy, move, rename, ... directly on the repository.
target: Ponekad vam treba da radite direktno na spremištu, bez radne kopije. To je za šta je <firstterm>Pretraživač Spremišta</firstterm>. Kao pretraživač i prekrivač ikona dopušta da vidite vašu radnu kopiju tako Pretraživač Spremišta dopušta da vidite strukturu i status spremišta. <placeholder-1/> Sa Pretraživačem Spremišta možete izvršiti komande kao kopiraj, pomeri, preimenuj, ... direktno u spremištu.

note: (para)
en: The repository browser looks very similar to the Windows explorer, except that it is showing the content of the repository at a particular revision rather than files on your computer. In the left pane you can see a directory tree, and in the right pane are the contents of the selected directory. At the top of the Repository Browser Window you can enter the URL of the repository and the revision you want to browse.
target: Pretraživač spremišta izgleda veoma slično  Vindouz eksploreru, osim što prikazuje sadržaj spremišta u partikularnoj reviziji radije nego fajlove u vašem računaru. U levom panelu možete videti stablo imenika, au desnom panelu su sadžaji izabranih imenika. U gornjem Prozoru Pretraživača Spremišta možete uneti URL spremišta i reviziju koju hoćete da pretražite.

note: (para)
en: Just like Windows explorer, you can click on the column headings in the right pane if you want to set the sort order. And as in explorer there are context menus available in both panes.
target: Isto kao Vindouz eksplorer, možete kliknuti na zaglavlje kolone u desnom panelu ako želite da podesite red sortiranja. I kao u eksploreru postoji kontekst meni dostupan u oba panela.

note: (para)
en: Save an unversioned copy of the file to your hard drive.
target: Sačubajte neverzionisanu kopiju fajla na vaš tvrdi disk.

note: (para)
en: Show the revision log for that file, or show a graph of all revisions so you can see where the file came from.
target: Prikažite revizioni dnevnik za taj fajl, ili prikažite graf revizije tako da možete videti odakle fajl dolazi.

note: (para)
en: Blame the file, to see who changed which line and when.
target: Okrivite fajl da vidite ko je menjao koju liniju i kada.

note: (para)
en: Delete or rename the file.
target: Izbriši ili preimenuj fajl.

note: (para)
en: Make a copy of the file, either to a different part of the repository, or to a working copy rooted in the same repository.
target: Napravite kopiju fajla, ili u različitom delu spremišta , ili u radnoj kopiji sa korenom u isto spremištu.

note: (para)
en: View/Edit the file's properties.
target: Vidi/Uredi osobine fajla.

note: (para)
en: The context menu for a file allows you to: <placeholder-1/>
target: Kontekst meni za fajl dopušta vam da: <placeholder-1/>

note: (para)
en: Show the revision log for that folder, or show a graph of all revisions so you can see where the folder came from.
target: Prikažite revizioni dnevnik za imenik, ili prikažite graf svih revizija tako da možete videti odakle imenik dolazi.

note: (para)
en: Export the folder to a local unversioned copy on your hard drive.
target: Izvezite imenik u lokalnu neverzionisanu kopiju na vašem čvrstom disku.

note: (para)
en: Checkout the folder to produce a local working copy on your hard drive.
target: Preuzmite imenik da napravite lokalnu radnu kopiju na čvrstom disku.

note: (para)
en: Create a new folder in the repository.
target: Kreiraj novi imenik u spremištu.

note: (para)
en: Add files or folders directly to the repository.
target: Dodaj fajlove ili imenike direktno u spremište.

note: (para)
en: Delete or rename the folder.
target: Izbriši ili preimenuj imenik.

note: (para)
en: Make a copy of the folder, either to a different part of the repository, or to a working copy rooted in the same repository.
target: Napravite kopiju imenika, ili u različit deo spremišta, ili u radnu kopiju sa korenom u istom spremištu.

note: (para)
en: View/Edit the folder's properties.
target: Vidi/Uredi osobine imenika.

note: (para)
en: Mark the folder for comparison. A marked folder is shown in bold.
target: Napravite imenik za poređenje. Označeni imenik je prikazan masno.

note: (para)
en: Compare the folder with a previously marked folder, either as a unified diff, or as a list of changed files which can then be visually diffed using the default diff tool. This can be particularly useful for comparing two tags, or trunk and branch to see what changed.
target: Upoređuje imenik sa prethodno označenim imenikom, ili kao ujedinjene diff, ili kao lista izmenjenih fajlova koji zatim mogu biti vizualno razlikovani koristeći uobičajen diff alat. Ovo može biti posebno korisno za poređenje dva znaka, ili debla i grane da se vidi šta se promenilo.

note: (para)
en: The context menu for a folder allows you to: <placeholder-1/>
target: Kontekst meni za imenik vam omogućava da: <placeholder-1/>

note: (para)
en: If you select two folders in the right pane, you can view the differences either as a unified-diff, or as a list of files which can be visually diffed using the default diff tool.
target: Ako izaberete dva imenika u desnom panelu, možete videti razlike ili kao ujedinjeni-diff, ili listu fajlova koja može biti vizualno razlikovana korišćenjem uobičajenog diff alata.

note: (para)
en: If you select multiple folders in the right pane, you can checkout all of them at once into a common parent folder.
target: Ako izaberete više imenika u desnom panelu možete  preuzeti sve njih u zajednički predački imenik.

note: (para)
en: If you select 2 tags which are copied from the same root (typically <literal>/trunk/</literal>), you can use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Show Log...</guimenuitem></menuchoice> to view the list of revisions between the two tag points.
target: Ako izaberete 2 znaka koji su kopirani iz istog korena (tipično <literal>/trunk/</literal>), možete koristiti <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Pokaži Dnevnik...</guimenuitem></menuchoice> da vidite listu revizija između dve nak tačke.

note: (para)
en: You can use <keycap>F5</keycap> to refresh the view as usual. This will refresh everything which is currently displayed. If you want to pre-fetch or refresh the information for nodes which have not been opened yet, use <keycap>Ctrl-F5</keycap>. After that, expanding any node will happen instantly without a network delay while the information is fetched.
target: Možete koristiti <keycap>F5</keycap>  da osvežite pregled kao ubično. To će osvežiti sve što se trenutno prikazuje. Ako želite da pretražite ili osvežite informacije za čvorove koji još nisu otvoreni, koristite <keycap>Ctrl-F5</keycap>. Posle toga, proširenjem bilo kog čvora desiće se trenutno bez obzira na mrežno kašnjenje dok se informacija tražila.

note: (para)
en: You can also use the repository browser for drag-and-drop operations. If you drag a folder from explorer into the repo-browser, it will be imported into the repository. Note that if you drag multiple items, they will be imported in separate commits.
target: Možete takođe koristiti pretraživač spremišta za vuci-i-baci operaciju. Ako vučete imenik iz eksplorera u repo-pretraživač biće uvezen u spremište. Primetite da ako vučete više stavki one će biti uvezene u odvojenim urezivanjima.

note: (para)
en: If you want to move an item within the repository, just <action>left drag</action> it to the new location. If you want to create a copy rather than moving the item, <keycap>Ctrl</keycap>-<action>left drag</action> instead. When copying, the cursor has a <quote>plus</quote> symbol on it, just as it does in Explorer.
target: Ako želite da pomerite stavke u okviru spremišta, samo <action>levo vučenje</action> na novu lokaciju. Ako želite da kreirate kopiju radije nego pomeranje stavke, <keycap>Ctrl</keycap>-<action>levo vučenje</action> umesto. Kada kopirate, kursor ima <quote>plus</quote> simbol na sebi, isto kako je to u Eksploreru.

note: (para)
en: If you want to copy/move a file or folder to another location and also give it a new name at the same time, you can <action>right drag</action> or <keycap>Ctrl</keycap>-<action>right drag</action> the item instead of using <action>left drag</action>. In that case, a rename dialog is shown where you can enter a new name for the file or folder.
target: Ako želite da kopirate/pomerite fajl ili folder na drugu lokaciju i takođe dajte mu novo ime u isto vreme, možete <action>desno vučenje</action> ili <keycap>Ctrl</keycap>-<action>desno vučenje</action> stavke umesto korišćenja <action>levo vučenje</action>. U ovom slučaju  dijalog preimenovanja je prikazan gde možete uneti novo ime za fajl ili imenik.

note: (para)
en: Whenever you make changes in the repository using one of these methods, you will be presented with a log message entry dialog. If you dragged something by mistake, this is also your chance to cancel the action.
target: Kadgod napravite izmenu u spremištu koristeći jedan od ovih metoda, bićete predstavljeni dnevnik poruke ulazom dijaloga. Ako vučete nešto greškom, to je takođe vaša šansa da završite akciju.

note: (para)
en: Sometimes when you try to open a path you will get an error message in place of the item details. This might happen if you specified an invalid URL, or if you don't have access permission, or if there is some other server problem. If you need to copy this message to include it in an email, just right click on it and use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Copy error message to clipboard</guimenuitem></menuchoice>, or simply use <keycap>Ctrl+C</keycap>.
target: Ponekad kada pokušate da otvorite putanju dobićete poruku greške umesto detalja stavke. Ovo se može desiti ako specificirate neispravan URL, ili ako nemate pristupnu dozvolu, ili ako ima neki drugi problem servera. Ako  vam treba da kopirate ovu poruku da je uključite u epoštu, samo desno kliknite na nju i koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Kopiraj poruku greške u klipbord</guimenuitem></menuchoice>, ili jednostavno koristite <keycap>Ctrl+C</keycap>.

note: (title)
en: Revision Graphs
target: Revizioni Graf

note: (primary)
en: graph
target: graf

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

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

note: (para)
en: <placeholder-1/> Sometimes you need to know where branches and tags were taken from the trunk, and the ideal way to view this sort of information is as a graph or tree structure. That's when you need to use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revision Graph...</guimenuitem></menuchoice>
target: <placeholder-1/> Ponekad vam treba da znate odakle uzeti grane i znake iz debla, i idealan način da vidite ovu vrstu informavija je graf strukture stabla. Tamo gde treba da koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revizioni Graf...</guimenuitem></menuchoice>

note: (para)
en: This command analyses the revision history and attempts to create a tree showing the points at which copies were taken, and when branches/tags were deleted.
target: Ova komanda analizira istoriju revizija i pokušava da kreira stablo koje će prikazati iz koje kopije je uzeto, i kada su grane/znaci obrisani.

note: (para)
en: In order to generate the graph, TortoiseSVN must fetch all log messages from the repository root. Needless to say this can take several minutes even with a repository of a few thousand revisions, depending on server speed, network bandwidth, etc. If you try this with something like the <emphasis>Apache</emphasis> project which currently has over 500,000 revisions you could be waiting for some time.
target: Da bi generisali graf, TortoiseSVN mora naći poruke dnevnika iz korena spremišta. nepotrebno je reći da ovo mora uzeti nekoliko minuta čak sa spremištem od oko više hiljada revizija, u zavisnosti od brzine servera, propusnog opsega mreže, itd. Ako pokušate ovo sa nečim kao <emphasis>Apaš</emphasis> projekat koji trenutno ima preko 500.000 revizija morali bi da čekate izvsno vreme.

note: (para)
en: The good news is that if you are using Log Caching, you only have to suffer this delay once. After that, log data is held locally. Log caching is enabled in TortoiseSVN's settings.
target: Dobre novosti su da ako koristite Dnevnik Keširanja, vi samo imate da trpite ovo kašnjenje jedanput. Posle toga, dnevnik podaci se drže lokalno. Dnevnik keširanje je omogućeno u TortoiseSVN podešavanju.

note: (title)
en: Revision Graph Nodes
target: Čvor revizionog grafa

note: (term)
en: Added file/folder
target: Dodat fajl/imenik

note: (para)
en: Items which have been added, or created by copying another file/folder are shown using a rounded rectangle.
target: Stavke koje su dodate, ili kreirane kopiranjem drugog fajla/imenika su prikazane koristeći zaokružen pravougaonik.

note: (term)
en: Deleted file/folder
target: Obrisan fajl/imenik

note: (para)
en: Deleted items eg. a branch which is no longer required, are shown using an octagon (rectangle with corners cut off).
target: Obrisane stavke npr. grana koja više nije potrebna, su prikazane koristeći oktagon (pravougaonik sa uglovima koji su presečeni).

note: (term)
en: Branch tip revision
target: Grana tip revizije

note: (para)
en: Where a branch (or trunk or tag) has been modified since the last branch node, this is shown using an ellipse. Shown when the <guilabel>Show HEAD revisions</guilabel> option is selected.
target: Gde je grana (ili deblo ili znak) modifikovan od poslednjeg čvora grane, ovo je prikazano koristeći elipsu. Prikazano je kada <guilabel>Prikaži GLAVNE revizije</guilabel> opcija je izabrana.

note: (term)
en: Normal file/folder
target: Normalan fajl/imenik

note: (para)
en: All other items are shown using a plain rectangle.
target: Sve druge stavke su prikazane koristeći pun pravougaonik.

note: (para)
en: The revision graph shows several types of node: <placeholder-1/>
target: Revizioni graf prikazuje više tipova čvorova: <placeholder-1/>

note: (para)
en: Note that by default the graph only shows the points at which items were added or deleted. Showing every revision of a project will generate a very large graph for non-trivial cases. If you really want to see <emphasis>all</emphasis> revisions where changes were made, there is an option to do this in the <guilabel>View</guilabel> menu and on the toolbar.
target: primetimo da je uobičajeno da graf samo prikazuje tačke u kojima su stavke dodate ili izbrisane. Prikazujući svaku reviziju projekta će generisati veoma veliki graf u ne-trivijalnim slučajevima. Ako zaista želite da vidite <emphasis>sve</emphasis> revizije gde su uurađene izmene, ima jedna opcija da se to uradi u <guilabel>Vidi</guilabel> meniju i alatpultu.

note: (title)
en: Changing the View
target: Izmena pogleda.

note: (term)
en: Group branches
target: Grupa grana

note: (para)
en: The default behavior (grouping off) will use one row per revision and all rows are sorted strictly by revision. As a result, long-living branches occupy a whole column for only a few changes and the graph becomes very broad.
target: Uobičajeno ponašanje (bez grupiranja) će koristiti jedan red po reviziji i sve redove sortirane tačno po reviziji. Kao rezultat, dugo-živeće grane zauzmu celu kolonu za samo nekoliko izmena i graf postaje veoma široko.

note: (para)
en: This mode groups changes by branch, so that there is no global revision ordering: Consecutive revisions on a branch will be shown in (often) consecutive lines. Sub-branches, however, are arranged in such a way that later branches will be shown in the same column above older branches to keep the graph slim. As a result, a given row may contain changes from different revisions.
target: Ovaj mod grupiše izmene grana, tako da nema globalnog uređenja revizije: Kosekutivne revizije grana biće prikazane u (često) konsekutivnim linijama. Sub-grane, međutim, su uređene na takav način da kasnije grane budu prikazane u istoj koloni iznad starih grana da sačuvaju vitkost grafa. Kao rezultat dat red može sadržati izmene iz različitih revizija.

note: (term)
en: Oldest on top
target: Najstariji na vrhu

note: (para)
en: Normally the graph shows the oldest revision at the bottom, and the tree grows upwards. Use this option to grow down from the top instead.
target: Normalno graf prikazuje najstariju reviziju na dnu, i stablo raste. Koristite ove opcije da se smanji sa vrha umesto toga.

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

note: (para)
en: This ensures that the latest revision on every branch is always shown on the graph.
target: Da bi se omogućilo da zadnja revizija na svakoj grani uvek se prikazuje na grafu.

note: (term)
en: Exact copy sources
target: Tačna kopija izvora

note: (para)
en: When a branch/tag is made, the default behaviour is to show the branch as taken from the last node where a change was made. Strictly speaking this is inaccurate since the branches are often made from the current HEAD rather than a specific revision. So it is possible to show the more correct (but less useful) revision that was used to create the copy.
target: Kada je grana/znak napravljen, uobičajeno ponašanje je da se prikaže kao dobijen od zadnjeg čvora gde su izmene naoravljene. GTačno govoreći ovo je netačno od kad su grane često napracljene od tekuće GLAVE radije nego od specifične revizije. Tak oje moguće da se pokaže mnogo tačnije (ali manje korisno) revizija koja je korišćena da se kreira kopija.

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

note: (para)
en: If you want to see a graph of software development, tagged releases may be of little interest to you. This option hides the nodes for tags and shows them instead in the tooltip for the node that they were copied from. A tag icon on the right side of the source node indicates that tags were made.
target: Ako želite da vidite graf razvoja softvera, označene realizacije mogu biti od malog interesa za vas. Opcija skriva čvorove za znake i prikazuje ih umesto njih u alatsavetu za čvorove koji su odatle kopirani. Ikona znaka s desne strane izvornog čvora pokazuje da je taj znak napravljen.

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

note: (para)
en: If the layout of the graph has produced a lot of crossing lines, use this option to clean it up. This may make the layout columns appear in less logical places, for example in a diagonal line rather than a column, and it may take a little time to optimise.
target: Izgled grafa je napravio mnogo presečnih linija, koristite ovu opciju da ih obrišete. Ovo može napraviti izgled kolona da se pojave u manje logičkih mesta, na primer u dijagonalnoj liniji radije nego u koloni i mogu uzeti malo vremena za optimizaciju.

note: (para)
en: Sometimes the revision graph contains more revisions than you want to see. This option opens a dialog which allows you to restrict the range of revisions displayed, and to hide particular paths by name.
target: Ponekad revizioni graf sadrži više revizija od onog što želite da vidite. Opcija otvara dijalog koji omogućava da ograničite opseg revizija koje su prikazae, i da sakrijete pojedine putanje pomoću imena.

note: (para)
en: Because a revision graph is often quite complex, there are a number of features which can be used to tailor the view the way you want it. These are available in the <guilabel>View</guilabel> menu and from the toolbar. <placeholder-1/>
target: Pošto je revizioni graf često jako kompleksan, postoje brojne osobine koje se mogu koristiti da urede izgled na način kako želite. One su dostupne u <guilabel>Pregled</guilabel> meniju i iz alatpulta. <placeholder-1/>

note: (title)
en: Using the Graph
target: Korišćenje grafa

note: (para)
en: To make it easier to navigate a large graph, use the overview window. This shows the entire graph in a small window, with the currently displayed portion highlighted. You can drag the highlighted area to change the displayed region.
target: Da bi se učinilo lakim kretanje po velikom grafu koristite pregledni prozor. On prikazuje ceo graf u malom prozoru, sa prikazanim tekućim delom koji je osvetljen. Možete vući osvetljenu oblast da izmenite prikazani region.

note: (para)
en: The revision date, author and comments are shown in a hint box whenever the mouse hovers over a revision box.
target: Revizioni datum, autor i komentari su prikazani u boksu napomena kadgod miš klizi preko revizionog boksa.

note: (para)
en: If you select two revisions (Use <keycap>Ctrl</keycap>-<action>left click</action>), you can use the context menu to show the differences between these revisions. You can choose to show differences as at the branch creation points, but usually you will want to show the differences at the branch end points, i.e. at the HEAD revision.
target: Ako izaberete dve revizije (Koristite <keycap>Ctrl</keycap>-<action>levi klik</action>), možete koristiti kontekst meni da prikažete razlike izmeu ovih revizija. Možete izabrati da prikažete razlike kao u tačkama kreiranja grana, ali obično ćete želeti da prikažete u krajnjim tačkama grana, tj. u GLAVNOJ reviziji.

note: (para)
en: You can view the differences as a Unified-Diff file, which shows all differences in a single file with minimal context. If you opt to <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Compare Revisions</guimenuitem></menuchoice> you will be presented with a list of changed files. <action>Double click</action> on a file name to fetch both revisions of the file and compare them using the visual difference tool.
target: Možete videti razlike kao Objedinjene-Diff fajl, koji prikazuje sve razlike u pojedinačnom fajlu sa minimalnim sadržajem. Ako izaberete<menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Uporedi Revizije</guimenuitem></menuchoice> biće vam prikazana lista izmenjenih fajlova. <action>Dvostruki klik</action>  na ime fajla da se dobiju revizije fajla i uporede koristeći vizualni alat za razlikovanje.

note: (para)
en: If you <action>right click</action> on a revision you can use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Show Log</guimenuitem></menuchoice> to view the history.
target: Ako uradite <action>desni klik</action> na reviziju možete koristiti <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Prikaži Dnevnik</guimenuitem></menuchoice> da vidite istoriju.

note: (para)
en: You can also merge changes in the selected revision(s) into a different working copy. A folder selection dialog allows you to choose the working copy to merge into, but after that there is no confirmation dialog, nor any opportunity to try a dry run. It is a good idea to merge into an unmodified working copy so that you can revert the changes if it doesn't work out! This is a useful feature if you want to merge selected revisions from one branch to another.
target: Možete takođe stopiti izmene u izabranim revizijama u različitim radnim kopijama. Dijalog izbora imenika dopušta da izaberete radnu kopiju u koju stapate, ali posle toga nema dijloga potvrde, niti bilo kakvog sprečavanja da se pokuša neproduktivan rad. Dobra je ideja da se stopi u neizmenjenu radnu kopiju tako da možete vratiti izmene ako to ne radi! Ovo je korisna osobina ako želite da stopite izabrane revizije iz jedne grane u drugu.

note: (para)
en: Because Subversion cannot provide all the information required, a certain amount of interpretation is required, which can sometimes give strange results. Nevertheless, the output for the trunk will generally give useful results.
target: Zato što Subverzija ne može obezbediti sve informacije koje se traže izvestan deo interpretacije je potreban,koji ponekad daje čudne rzultate. Ipak, izlaz  za deblo će generalno dati koristan rezultat.

note: (para)
en: If you want to check the server again for newer information, you can simply refresh the view using <keycap>F5</keycap>. If you are using the log cache (enabled by default), this will check the repository for newer commits and fetch only the new ones. If the log cache was in offline mode, this will also attempt to go back online.
target: Ako želite da proverite ponovo server za nove informacije, možete jednostavno osvežiti pregled koristeći <keycap>F5</keycap>. Ako koristite dnevnik keš (omogućen podrazumevano), ovo će proveriti spremište za nova urezivanja i naći samo nove. Ako je dnevnik keš isključen, ovo će pokušati da se ode na uključenje.

note: (para)
en: If you are using the log cache and you think the message content or author may have changed, you should use the log dialog to refresh the messages you need. Since the revision graph works from the repository root, we would have to invalidate the entire log cache, and refilling it could take a <emphasis>very</emphasis> long time.
target: Ako koristite dnevnik keš i mislite da je sadržaj poruke ili autor možda imao izmene, treba da koristite dnevnik dijalog da osvežite poruke koje vam trebaju. Kako revizioni graf radi iz korena spremišta, mi bi imali da učinimo neispravnim ceo dnevnik keš, i da ga ponovo napunimo što bi uzelo <emphasis>veoma</emphasis> mnogo vremena.

note: (title)
en: Exporting a Subversion Working Copy
target: Izvoz Subverzione radne kopije

note: (primary)
en: export
target: izvoz

note: (primary)
en: unversioned 'working copy'
target: neverzionisana 'radna kopija'

note: (para)
en: Sometimes you may want a copy of your working tree without any of those <filename>.svn</filename> directories, e.g. to create a zipped tarball of your source, or to export to a web server. Instead of making a copy and then deleting all those <filename>.svn</filename> directories manually, TortoiseSVN offers the command <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Export...</guimenuitem></menuchoice>. Exporting from a URL and exporting from a working copy are treated slightly differently.
target: Ponekad možete želeti kopiju vašeg radnog stabla bez ikakvog <filename>.svn</filename> imenika, tj. da kreirate zipovanu crnu loptu vašeg izvornog koda, ili da ga izvezete na veb server. Umesto da pravite kopiju i onda brišete sve te  <filename>.svn</filename> imenike ručno, TortoiseSVN omogućava komandu <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Izvoz...</guimenuitem></menuchoice>. Izvoz iz URL i izvoz iz radne kopije se trtira malo drugačije.

note: (title)
en: The Export-from-URL Dialog
target: Izvoz-iz-URL dijalog

note: (para)
en: <placeholder-1/> If you execute this command on an unversioned folder, TortoiseSVN will assume that the selected folder is the target, and open a dialog for you to enter the URL and revision to export from. This dialog has options to export only the top level folder, to omit external references, and to override the line end style for files which have the <literal>svn:eol-style</literal> property set.
target: <placeholder-1/> Ako izvršite ovu komandu na neverzionisani imenik, TortoiseSVN će uzeti da je izabrani imenik cilj, i otvoriće dijalog da unesete URL i reviziju da izvezete iz njega. Ovaj dijalog ima opcije da izveze samo imenik vršnog nivoa, da se izbegnu spoljašne reference, i da prekrije linije i stil za fajlove koji imaju <literal>svn:eol-style</literal> podešenu osobinu.

note: (para)
en: Of course you can export directly from the repository too. Use the Repository Browser to navigate to the relevant subtree in your repository, then use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Export</guimenuitem></menuchoice>. You will get the <guilabel>Export from URL</guilabel> dialog described above.
target: Svakako da možete izvesti direktno iz spremišta takođe. Koristite Pretraživač Spremišta da upravljate do relevantnog podstabla u vašem spremištu, zatim koristite menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Izvoz</guimenuitem></menuchoice>. Dobićete <guilabel>Izvoz iz URL</guilabel> dijalog koji je opisan ranije.

note: (para)
en: If you execute this command on your working copy you'll be asked for a place to save the <emphasis>clean</emphasis> working copy without the <filename>.svn</filename> folders. By default, only the versioned files are exported, but you can use the <guilabel>Export unversioned files too</guilabel> checkbox to include any other unversioned files which exist in your WC and not in the repository. External references using <literal>svn:externals</literal> can be omitted if required.
target: Ako izvršite ovu komandu na vašoj radnoj kopiji bićete pitani za mesto da sačuvate <emphasis>čistu</emphasis> radnu kopiju bez <filename>.svn</filename> imenika. Uobučajeno, samo verzionisani fajlovi se izvoze, ali možete koristiti <guilabel>Izvoz neverzionisanih fajlova takođe</guilabel> čekboks da uključite sve ostale neverzionisane fajlove koji postoje u vašoj RK i nisu u spremištu. Spoljašne reference korišćenjem <literal>svn:externals</literal> mogu biti izostavljene ako se traži.

note: (para)
en: Another way to export from a working copy is to <action>right drag</action> the working copy folder to another location and choose <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>SVN Export here</guimenuitem></menuchoice> or <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>SVN Export all here</guimenuitem></menuchoice>. The second option includes the unversioned files as well.
target: Drugi način da se izveze iz radne kopije je da se <action>desno vuče</action> imenik radne kopije u drugu lokaciju i izabere <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>SVN Izvoz ovde</guimenuitem></menuchoice> ili <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>SVN Izvoz sve ovde</guimenuitem></menuchoice>. Druga opcija uključuje neverzionisane fajlove takođe.

note: (para)
en: When exporting from a working copy, if the target folder already contains a folder of the same name as the one you are exporting, you will be given the option to overwrite the existing content, or to create a new folder with an automatically generated name, eg. <literal>Target (1)</literal>.
target: Kada izvozite iz radne kopije, ako ciljni imenik već sadrži imenik istog imena kao onaj koji izvozite, biće vam data opcija da prepišete postojeći sadržaj, ili da kreirate novi imenik sa automatski generisanim imenom, npr.  <literal>Cilj (1)</literal>.

note: (title)
en: Exporting single files
target: Izvoz pojedinačnog fajla

note: (para)
en: The export dialog does not allow exporting single files, even though Subversion can.
target: Izvozni dijalog ne dopušta izvoz pojedinačnih fajlova, bez obzira što Subverzija može.

note: (para)
en: To export single files with TortoiseSVN, you have to use the repository browser (<xref linkend="tsvn-dug-repobrowser"/>). Simply drag the file(s) you want to export from the repository browser to where you want them in the explorer, or use the context menu in the repository browser to export the files.
target: Da izvezete pojedinačne fajlove sa TortoiseSVN, imate da koristite pretraživač spremišta (<xref linkend="tsvn-dug-repobrowser"/>). Jednostavno vucite fajl(ove) koji želite da izvezete iz pretraživača spremišta tamo gde ga želite u eksploreru, ili koristite kontest meni u pretraživaču spremišta da izvezete fajlove.

note: (title)
en: Removing a working copy from version control
target: Izbacivanje radne kopije iz kontrole verzija

note: (primary)
en: unversion
target: neverzionisan

note: (para)
en: Sometimes you have a working copy which you want to convert back to a normal folder without the <literal>.svn</literal> directories. What you really need is an export-in-place command, that just removes the control directories rather than generating a new clean directory tree.
target: Ponekad imate radnu kopiju koju hoćete da konvertujete nazad u normlan imenik bez <literal>.svn</literal> imenika. Šta vam stvarno treba je izvezi-na-mestu komanda, ona samo uklanja kontrolne imenike radije nego da generiše novo čisto stablo imenika.

note: (para)
en: The answer is surprisingly simple - export the folder to itself! TortoiseSVN detects this special case and asks if you want to make the working copy unversioned. If you answer <emphasis>yes</emphasis> the control directories will be removed and you will have a plain, unversioned directory tree.
target: Odgovor je iznenađujuće jednostavan - izvezite imenik u samog sebe! TortoiseSVN otkriva ovaj specijalni slučaj i pita da li želite da napravite radnu kopiju neverzionisanu. Ako odgovorite <emphasis>da</emphasis> kontrolni imenici će biti uklonjeni i imaćete potpuno neverzionisano stablo imenika.

note: (title)
en: Relocating a working copy
target: Relociranje radne kopije

note: (primary)
en: relocate
target: premesti

note: (primary)
en: URL changed
target: URL izmenjen

note: (primary)
en: repository URL changed
target: URL spremišta izmenjen

note: (primary)
en: server moved
target: server pomeren

note: (primary)
en: moved server
target: pomeren server

note: (title)
en: The Relocate Dialog
target: Relociranje dijalog

note: (para)
en: <placeholder-1/> If your repository has for some reason changed it's location (IP/URL). Maybe you're even stuck and can't commit and you don't want to checkout your working copy again from the new location and to move all your changed data back into the new working copy, <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Relocate</guimenuitem></menuchoice> is the command you are looking for. It basically does very little: it scans all <filename>entries</filename> files in the <filename>.svn</filename> folder and changes the URL of the entries to the new value.
target: <placeholder-1/> Ako je vaše spremište iz nekog razloga promenilo svoju lokaciju (IP/URL). Možda ste čak ukočeni i ne možete urezati i ne želite da preuzmete vašu radnu kopiju ponovo sa nove lokacije i pomerite sve izmenjene podatke nazad u novu radnu kopiju, <<menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Relociraj</guimenuitem></menuchoice> je komanda koju tražite. Ona u snovi radi veoma malo: skenira sve <filename>ulaze</filename> fajlova u  <filename>.svn</filename> imeniku i menja URL ulaza u nove vrednosti.

note: (para)
en: The IP address of the server has changed.
target: IP adresa servera je promenjena

note: (para)
en: The protocol has changed (e.g. http:// to https://).
target: Protokol je promenjen (npr. http:// to https://).

note: (para)
en: The repository root path in the server setup has changed.
target: Putanja korena spremišta u server podešavanju je izmenjena.

note: (para)
en: <emphasis>This is a very infrequently used operation</emphasis>. The relocate command is <emphasis>only</emphasis> used if the URL of the repository root has changed. Possible reasons are: <placeholder-1/> Put another way, you need to relocate when your working copy is referring to the same location in the same repository, but the repository itself has moved.
target: <emphasis>Ovo je veoma retko korišćena operacija</emphasis>. Relokaciona komanda je emphasis>samo</emphasis> korišćena ako URL korena spremišta je promenjeno. Mogući razlozi su: <placeholder-1/> Stavite drugi način, potrebno je da relocirate kada vaša radna kopija ukazuje na istu lokaciju u istom spremištu, ali je samo spremište pomereno.

note: (para)
en: You want to move to a different Subversion repository. In that case you should perform a clean checkout from the new repository location.
target: Hoćete da pomerite različita Subverziona spremišta. U tom slučaju treba da izvršite čisto preuzimanje iz nove lokacije spremišta.

note: (para)
en: You want to switch to a different branch or directory within the same repository. To do that you should use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Switch...</guimenuitem></menuchoice>. Read <xref linkend="tsvn-dug-switch-1"/> for more information.
target: Želite da prebacite na različitu granu ili imenik unutar istog spremišta. Da uradite to trba da koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Prebaci...</guimenuitem></menuchoice>. Pročitajte <xref linkend="tsvn-dug-switch-1"/> za više informacija.

note: (para)
en: It does not apply if: <placeholder-1/>
target: To se ne primenjuje ako je: <placeholder-1/>

note: (para)
en: If you use relocate in either of the cases above, it <emphasis>will corrupt your working copy</emphasis> and you will get many unexplainable error messages while updating, committing, etc. Once that has happened, the only fix is a fresh checkout.
target: Ako koristite relociranje u jednom od navedenih slučajeva, to <emphasis>će pokvariti vašu radnu kopiju</emphasis> i vi ćete dobiti mnogo neobjašnjivih poruka o grešci kada ažurirate, urezujete, itd. Kada se to jednom desi fiksiranje je samo sveže preuzimanje.

note: (title)
en: Integration with Bug Tracking Systems / Issue Trackers
target: Integracija sa Bag Praćenja Sistem / Problem Tragači

note: (primary)
en: bug tracking
target: bag praćenje

note: (primary)
en: bug tracker
target: bag tragač

note: (primary)
en: issue tracker
target: problem tragač

note: (primary)
en: bugtracker
target: bagtragač

note: (para)
en: It is very common in Software Development for changes to be related to a specific bug or issue ID. Users of bug tracking systems (issue trackers) would like to associate the changes they make in Subversion with a specific ID in their issue tracker. Most issue trackers therefore provide a pre-commit hook script which parses the log message to find the bug ID with which the commit is associated. This is somewhat error prone since it relies on the user to write the log message properly so that the pre-commit hook script can parse it correctly.
target: Veoma je često u Razvoju Softvera za izmene da imaju specifične bagove ili  problem ID. Korisnici bag tragač sistema (problem tragač) su voleli da pridruže izmene koje su napravili u Subverziji sa specifičnim ID u njihovom problem tragaču. Većina problem tragača zbog toga omogućavaju pre-urezivanja zakačive skripte koje analiziraju dnevnik poruke da nađu bag ID sa kojim je urezivanje povezano. Ovo je ponekad sklono greškama odkad je potrebno da korisnik upiše dnevnik poruku ispravno tako da preurezivanja zakačiv skript može ga analizirati korektno.

note: (para)
en: When the user enters a log message, a well defined line including the issue number associated with the commit can be added automatically. This reduces the risk that the user enters the issue number in a way the bug tracking tools can't parse correctly.
target: Kada korisnik unese dnevnik poruke, dobro definisana linija uključuje problem broj pridružen sa urezivanjem može biti dodat automatski. Ovo umanjuje rizik kada korisnik unosi problem broj na način da alat bag tragača ne može analizirati korektno.

note: (para)
en: Or TortoiseSVN can highlight the part of the entered log message which is recognized by the issue tracker. That way the user knows that the log message can be parsed correctly.
target: Ili TortoiseSVN može osvetliti deo celog dnevnik poruke koji je prepoznao  problem tragač. Na taj način korisnik zna da dnevnik poruke ože biti analiziran korektno.

note: (para)
en: When the user browses the log messages, TortoiseSVN creates a link out of each bug ID in the log message which fires up the browser to the issue mentioned.
target: Kada korisnik pretražuje dnevnik poruke, TortoiseSVN kreira vezu za svaki bag ID u dnevnik poruka koja pokreće pretraživač do nagoveštenog problema.

note: (para)
en: TortoiseSVN can help the user in two ways: <placeholder-1/>
target: TortoiseSVN može pomoći korisniku na dva načina: <placeholder-1/>

note: (title)
en: Adding Issue Numbers to Log Messages
target: Dodavanje Problem Brojeva u Dnevnik Poruka

note: (para)
en: You can integrate a bug tracking tool of your choice in TortoiseSVN. To do this, you have to define some properties, which start with <literal>bugtraq:</literal>. They must be set on Folders: (<xref linkend="tsvn-dug-propertypage"/>)
target: Možete integrisati alat praćenja bagova po vašem izboru u TortoiseSVN. Da to uradite, imate da definišete neke osobine, što se pokreće sa <literal>bugtraq:</literal>. To mora biti podešeno na Imenicima: (<xref linkend="tsvn-dug-propertypage"/>)

note: (para)
en: Set this property to the URL of your bug tracking tool. It must be properly URI encoded and it has to contain <literal>%BUGID%</literal>. <literal>%BUGID%</literal> is replaced with the Issue number you entered. This allows TortoiseSVN to display a link in the log dialog, so when you are looking at the revision log you can jump directly to your bug tracking tool. You do not have to provide this property, but then TortoiseSVN shows only the issue number and not the link to it. e.g the TortoiseSVN project is using <systemitem class="url">http://issues.tortoisesvn.net/?do=details&amp;id=%BUGID%</systemitem>
target: Postavite ovu osobinu na URL vašeg alata za praćenje bagova. To mora biti odgovarajuće kodiran URI i mora sadržati <literal>%BUGID%</literal>. <literal>%BUGID%</literal> je zamenjen sa Problem brojem koji ste uneli. Ovo omogućava TortoiseSVN da prikaže vezu u dnevnik dijalogu, tako da kad glrdate revizioni dnevnik možete samo skočiti direktnona vaš alat za praćenje bagova. Ne morate da omogućite ovu osobinu ali tada TortoiseSVN prikazuje samo problem broj a ne vezu do njega, tj. TortoiseSVN projekat koristi <systemitem class="url">http://issues.tortoisesvn.net/?do=details&amp;id=%BUGID%</systemitem>

note: (para)
en: You can also use relative URLs instead of absolute ones. This is useful when your issue tracker is on the same domain/server as your source repository. In case the domain name ever changes, you don't have to adjust the <literal>bugtraq:url</literal> property. There are two ways to specify a relative URL:
target: Možete takođe koristiti relativi URL umesto apsolutnog. Ovo je korisno kada vaš problem tragač je na istom domen/serveru kao i izvorno spremište. U slučaju da se ime domena ikada promeni, nemate da podešavate <literal>bugtraq:url</literal> osobinu. Postoje dva načina da se specificira relativni URL:

note: (para)
en: If it begins with the string <literal>^/</literal> it is assumed to be relative to the repository root. For example, <literal>^/../?do=details&amp;id=%BUGID%</literal> will resolve to <systemitem class="url">http://tortoisesvn.net/?do=details&amp;id=%BUGID%</systemitem> if your repository is located on <systemitem class="url">http://tortoisesvn.net/svn/trunk/</systemitem>.
target: Ako počinje sa stringom <literal>^/</literal> uzima se da je relativan na koren spremišta. Na primer, <literal>^/../?do=details&amp;id=%BUGID%</literal>  se rešava u <systemitem class="url">http://tortoisesvn.net/?do=details&amp;id=%BUGID%</systemitem> ako je vaše spremište locirano  na   <systemitem class="url">http://tortoisesvn.net/svn/trunk/</systemitem>.

note: (para)
en: A URL beginning with the string <literal>/</literal> is assumed to be relative to the server's hostname. For example <literal>/?do=details&amp;id=%BUGID%</literal> will resolve to <systemitem class="url">http://tortoisesvn.net/?do=details&amp;id=%BUGID%</systemitem> if your repository is located anywhere on <systemitem class="url">http://tortoisesvn.net</systemitem>.
target: URL koji počinje stringom <literal>/</literal> se uzima da je relativno na serverovo imedomaćina. Na primer <literal>/?do=details&amp;id=%BUGID%</literal> će se rešiti u <systemitem class="url">http://tortoisesvn.net/?do=details&amp;id=%BUGID%</systemitem> ako je vaše spremište locirano bil gde na <systemitem class="url">http://tortoisesvn.net</systemitem>.

note: (para)
en: Set this to <literal>true</literal>, if you want TortoiseSVN to warn you because of an empty issue-number text field. Valid values are <literal>true/false</literal>. <emphasis> If not defined, <literal>false</literal> is assumed. </emphasis>
target: Podesite ovo na <literal>istina</literal>, ako želite da vas TortoiseSVN obaveštava o praznom problem-broj tekst polju. Ispravne vrednosti su <literal>istina/laž</literal>. <emphasis> Ako nije definisan, <literal>laž</literal>se pretpostavlja. </emphasis>

note: (para)
en: There are two ways to integrate TortoiseSVN with issue trackers. One is based on simple strings, the other is based on <emphasis>regular expressions</emphasis>. The properties used by both approaches are: <placeholder-1/>
target: Postoji dva načina da se integriše TortoiseSVN sa problem tragačem. Jedna je zasnovana na jednostavnim stringovima, druga se bazira na <emphasis>regularnim izrazima</emphasis>. Osobine korišćene sa oba pristupa su: <placeholder-1/>

note: (title)
en: Issue Number in Text Box
target: Izdavanje brojeva u tekst boksu

note: (para)
en: This property activates the bug tracking system in <emphasis>Input field</emphasis> mode. If this property is set, then TortoiseSVN will prompt you to enter an issue number when you commit your changes. It's used to add a line at the end of the log message. It must contain <literal>%BUGID%</literal>, which is replaced with the issue number on commit. This ensures that your commit log contains a reference to the issue number which is always in a consistent format and can be parsed by your bug tracking tool to associate the issue number with a particular commit. As an example you might use <literal>Issue : %BUGID%</literal>, but this depends on your Tool.
target: Ova osobina aktivira sistem praćenja bagova u <emphasis>Ulazno polje</emphasis> modu. Ako je ova osobina podešena tada TortoiseSVN će vas pitati da unesete problem broj kada urezujete svoje izmene. To se koristi da se dodaju linije na kraj dnevnik poruke. Mora sadržati <literal>%BUGID%</literal>, koji je zamenjen sa problem brojem pri urezivanju. Ovo obezbeđuje da vaš dnevnik urezivanja sadrži referencu na problem broj koji je uvek konzistentnom formatu i može se analizirati vašim alatom za praćenje bagova da se pridruži problem broj sa posebnim urezivanjem. Kao jedan primer možete uzeti <literal>Issue : %BUGID%</literal>, ali ovo zavisi od vašeg Alata.

note: (para)
en: This property defines if the bug-ID is appended (true) to the end of the log message or inserted (false) at the start of the log message. Valid values are <literal>true/false</literal>. <emphasis> If not defined, <literal>true</literal> is assumed, so that existing projects don't break. </emphasis>
target: Ova osobina definiše da li je bag-ID dodat (istina) na kraj dnevnik poruke ili ubačen (laž) na početak dnevnik poruke. Ispravne vrednosti su <literal>istina/laž</literal>. <emphasis> Ako nije definisana, <literal>istina</literal> se podrazumeva, tako da postojeći projekat ne pukne. </emphasis>

note: (para)
en: This text is shown by TortoiseSVN on the commit dialog to label the edit box where you enter the issue number. If it's not set, <literal>Bug-ID / Issue-Nr:</literal> will be displayed. Keep in mind though that the window will not be resized to fit this label, so keep the size of the label below 20-25 characters.
target: Ovaj tekst je prikazan pomoću TortoiseSVN u dijalogu urezivanja da označi boks uređivanja gde unosite problem broj. Ako nije podešen, <literal>Bug-ID / Issue-Nr:</literal> će biti prikazan. Zapamtite to da taj prozor ne može promeniti veličinu da obuhvati ovu oznaku, pa neka je veličina ove oznake ispod 20-25 karaktera.

note: (para)
en: If set to <literal>true</literal> only numbers are allowed in the issue-number text field. An exception is the comma, so you can comma separate several numbers. Valid values are <literal>true/false</literal>. <emphasis> If not defined, <literal>true</literal> is assumed. </emphasis>
target: Ako podesite <literal>istina</literal> samo brojevi su dozvoljeni u problem-broj tekst polju. Izuzetak je zarez, zako da možete zapetom izdvojiti više brojeva. Ispravne vrednosti su <literal>istina/laž</literal>. <emphasis> Ako nije definisana, <literal>istina</literal> se uzima. </emphasis>

note: (para)
en: In the simple approach, TortoiseSVN shows the user a separate input field where a bug ID can be entered. Then a separate line is appended/prepended to the log message the user entered. <placeholder-1/>
target: U jednostavnom pristupu, TortoiseSVN prikazuje korisniku izdvojena ulazna polja gde bag ID može biti unet. Zatim su izdvojene linije dodate/ubačene u dnevnik poruke koju je uneo krisnik. <placeholder-1/>

note: (title)
en: Issue Numbers Using Regular Expressions
target: Izdavanje brojeva koristeći regularne izraze

note: (para)
en: This property activates the bug tracking system in <emphasis>Regex</emphasis> mode. It contains either a single regular expressions, or two regular expressions separated by a newline.
target: Ova osobina aktivira sistem praćenja bagova u <emphasis>Regeks</emphasis> modu. Sadrži ili podenični regularni izraz, ili dva regularna izraza razdvojena novimredom.

note: (para)
en: If two expressions are set, then the first expression is used as a pre-filter to find expressions which contain bug IDs. The second expression then extracts the bare bug IDs from the result of the first regex. This allows you to use a list of bug IDs and natural language expressions if you wish. e.g. you might fix several bugs and include a string something like this: <quote>This change resolves issues #23, #24 and #25</quote>
target: Ako su dva izraza podešena, tada prvi izraz je korišćen kao pre-filte da nađe izraze koji sadrže bag ID. Drugi izraz zatim izdvaja gole bag ID iz rezultata prve regeks. Ovo dozvoljava da se koristi lista bag ID i prirodan jezik izraza ako želite npr. možete fiksirati nekoliko bagova i uključiti string nešto kao ovo: <quote>Ova izmena rešava probleme #23, #24 i #25</quote>

note: (para)
en: If you want to catch bug IDs as used in the expression above inside a log message, you could use the following regex strings, which are the ones used by the TortoiseSVN project: <literal>[Ii]ssues?:?(\s*(,|and)?\s*#\d+)+</literal> and <literal>(\d+)</literal>
target: Ako hoćete da uhvatite bag ID kako su korišćeni u gornjem izrazu unutar dnevnik poruke, možete koristiti sledeće regeks stringove, koji su jedni od korišćenih u TortoiseSVN projektu: <literal>[Ii]ssues?:?(\s*(,|and)?\s*#\d+)+</literal> and <literal>(\d+)</literal>

note: (para)
en: The first expression picks out <quote>issues #23, #24 and #25</quote> from the surrounding log message. The second regex extracts plain decimal numbers from the output of the first regex, so it will return <quote>23</quote>, <quote>24</quote> and <quote>25</quote> to use as bug IDs.
target: Prvi izraz izvlači <quote>issues #23, #24 and #25</quote> iz okruženja dnevnik poruke. Drugi regeks ekstrahuje pune decimalne brojeve iz izlaza prve regeks, tako da će to vratiti  <quote>23</quote>, <quote>24</quote> i <quote>25</quote> da se koristi kao bag ID.

note: (para)
en: Breaking the first regex down a little, it must start with the word <quote>issue</quote>, possibly capitalised. This is optionally followed by an <quote>s</quote> (more than one issue) and optionally a colon. This is followed by one or more groups each having zero or more leading whitespace, an optional comma or <quote>and</quote> and more optional space. Finally there is a mandatory <quote>#</quote> and a mandatory decimal number.
target: Mala greška kod prve regeks, mora se početi rečju <quote>problem</quote>, moguće sa velikim slovima. Ovo je opcionalno praćeno sa jednim <quote>s</quote> (više od jednog problema) i opcionalno tačkom i zarezom. Ovo je praćeno jednim ili više grupe svaki ima nula ili više vodećih belihpolja, opcionalna zapeta ili <quote>i</quote> i više opcionalnih razmaka. Na kraju postoji obavezan <quote>#</quote> i obavezan decimalni broj.

note: (para)
en: If only one expression is set, then the bare bug IDs must be matched in the groups of the regex string. Example: <literal>[Ii]ssue(?:s)? #?(\d+)</literal> This method is required by a few issue trackers, e.g. trac, but it is harder to construct the regex. We recommend that you only use this method if your issue tracker documentation tells you to.
target: Ako je samo jedan izraz podešen onda go bag ID mora biti uhvaćen u grupama regeks stringova. Primer: <literal>[Ii]ssue(?:s)? #?(\d+)</literal> Ovaj metod traži više problem tragača, npr. trac, ali to je teže konstruisati regeks. Preporučujemo da samo koristite ovaj metod ako dokumentacija vašeg problem tragača to kaže.

note: (para)
en: If you are unfamiliar with regular expressions, take a look at the introduction at <ulink url="http://en.wikipedia.org/wiki/Regular_expression"><citetitle>http://en.wikipedia.org/wiki/Regular_expression</citetitle></ulink>, and the online documentation and tutorial at <ulink url="http://www.regular-expressions.info/"><citetitle>http://www.regular-expressions.info/</citetitle></ulink>.
target: Ako niste familijarni sa regeks izrazima pogledajte u uvod na <ulink url="http://en.wikipedia.org/wiki/Regular_expression"><citetitle>http://en.wikipedia.org/wiki/Regular_expression</citetitle></ulink>, i onlajn dokumentaciju i tutorijal na <ulink url="http://www.regular-expressions.info/"><citetitle>http://www.regular-expressions.info/</citetitle></ulink>.

note: (para)
en: In the approach with <emphasis>regular expressions</emphasis>, TortoiseSVN doesn't show a separate input field but marks the part of the log message the user enters which is recognized by the issue tracker. This is done while the user writes the log message. This also means that the bug ID can be anywhere inside a log message! This method is much more flexible, and is the one used by the TortoiseSVN project itself. <placeholder-1/>
target: U pristupu sa <emphasis>regularnim izrazima</emphasis>, TortoiseSVN ne prikazuje izdvojena ulazna polja ali markira deo dnevnik poruku koju korisnik unese što je prepoznato od problem tragača. Ovo je datodok korisnik piše dnevnik poruku. Ovo takođe znači da bag ID može biti bilo gde unutar dnevnika poruke! Ovaj metod  je mnogo više fleksibilan, i jedan je od onih koje projekat TortoiseSVN koristi sam. <placeholder-1/>

note: (para)
en: If both the <literal>bugtraq:message</literal> and <literal>bugtraq:logregex</literal> properties are set, <literal>logregex</literal> takes precedence.
target: Ako oba <literal>bugtraq:message</literal> i <literal>bugtraq:logregex</literal> osobine setovanr, <literal>logregex</literal> ima prednost.

note: (para)
en: Even if you don't have an issue tracker with a pre-commit hook parsing your log messages, you still can use this to turn the issues mentioned in your log messages into links!
target: Čak i ako nemate problem tragač sa pre-urezivanje zakačaljka analizira vaš dnevnik poruka, vi još uvek možete koristiti ovo da okrenete problem zamišljen u vašem dnevniku poruka u vezi!

note: (para)
en: And even if you don't need the links, the issue numbers show up as a separate column in the log dialog, making it easier to find the changes which relate to a particular issue.
target: I čak ako vam ne treba veza, problem brojevi prikazuju kao izdvojena kolona u dnevnik dijalogu, čineći to lakšim da nađete što se odnosi na poseban problem.

note: (title)
en: Set the Properties on Folders
target: Podešavabje osobina imenika

note: (para)
en: These properties must be set on folders for the system to work. When you commit a file or folder the properties are read from that folder. If the properties are not found there, TortoiseSVN will search upwards through the folder tree to find them until it comes to an unversioned folder, or the tree root (eg. <literal>C:\</literal>) is found. If you can be sure that each user checks out only from e.g <filename>trunk/</filename> and not some sub-folder, then it's enough if you set the properties on <filename>trunk/</filename>. If you can't be sure, you should set the properties recursively on each sub-folder. A property setting deeper in the project hierarchy overrides settings on higher levels (closer to <filename>trunk/</filename>).
target: Ove osobine moraju biti podešene na imeniku za sistem koji radi. Kada urezujete fajl ili imenik osobine su pročitane iz imenika. Ako osobine nisu nađene tamo, TortoiseSVN će pretraživati nagore kroz stablo imenika da ga nađete dok ne dođe neverzionisani imenik, ili koren stabla (npr. <literal>C:\</literal>) nađen. Ako možete biti sigurni da svaki korisnik preuzima samo sa npr. <filename>trunk/</filename> a ne neke sub-imenike, zatim to je dovoljno ako podesite osobine  na <filename>trunk/</filename>. Ako možete biti sigurni, morate podesiti osobine rekurzivno na svakom sub-imeniku. osobine podešene dublje u hijerarhiji projekta koja prepisuje podešavanje na višim nivoima (bliže ka <filename>trunk/</filename>).

note: (para)
en: For <literal>tsvn:</literal> properties <emphasis>only</emphasis> you can use the <guilabel>Recursive</guilabel> checkbox to set the property to all sub-folders in the hierarchy, without also setting it on all files.
target: Za <literal>tsvn:</literal> osobine <emphasis>samo</emphasis> možete koristite  <guilabel>Rekurzivno</guilabel> čekboks da podesi osobine na sve sub-imenike u hierarhiji, bez podešavanje na sve fajlove takođe.

note: (para)
en: This issue tracker integration is not restricted to TortoiseSVN; it can be used with any Subversion client. For more information, read the full <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/doc/issuetrackers.txt"><citetitle>Issue Tracker Integration Specification</citetitle></ulink> in the TortoiseSVN source repository. (<xref linkend="tsvn-preface-source"/> explains how to access the repository).
target: Problem tragač integracija nije ograničena na TortoiseSVN; to može biti korišćeno sa bilo kojim Subverzionim klijentom. Za više informacija pročitajte potpunije <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/doc/issuetrackers.txt"><citetitle>Problem Tragač Integracija Specifikacija</citetitle></ulink> u TortoiseSVN izvorno spremište. (<xref linkend="tsvn-preface-source"/> objašnjava kako da pristupite spremištu).

note: (title)
en: Getting Information from the Issue Tracker
target: Dobijanje informacija od poblem tragača

note: (para)
en: The previous section deals with adding issue information to the log messages. But what if you need to get information from the issue tracker? The commit dialog has a Windows COM interface which allows integration an external program that can talk to your tracker. Typically you might want to query the tracker to get a list of open issues assigned to you, so that you can pick the issues that are being addressed in this commit.
target: Prethodni paragraf razmatra dodavanje problem informacija u dnevnik poruka. Ali šta ako vam treba da dobijete informaciju od problem tragača? Dijalog urezivanja ima Vindouz COM interfejs koji dozvoljava integraciju spoljašnjih programa koji mogu govoriti vašem tragaču. Tipično možete želeti da tražite tragaču da da listu otvorenih problema pridruženih vama, tako da možete odabrati problem koji će biti adresiran pri urezivanju.

note: (para)
en: Any such interface is of course highly specific to your system, so we cannot provide this part, and describing how to create such a program is beyond the scope of this manual. The interface definition and sample programs can be obtained from the <literal>contrib</literal> folder in the <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/issue-tracker-plugins"><citetitle>TortoiseSVN repository</citetitle></ulink>. (<xref linkend="tsvn-preface-source"/> explains how to access the repository).
target: Svaki takav interfejs je svakako jako specifično za vaš sistem , tako da ne možete omogućiti ovaj deo, i opisati kako da kreirate takav program je van razmatranja ovog uputstva. Definicija interfejsa i jednostavni programi mogu biti dobijeni iz <literal>contrib</literal> imenika u <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/issue-tracker-plugins"><citetitle>TortoiseSVN spremište</citetitle></ulink>. (<xref linkend="tsvn-preface-source"/> objašnjava kako pristupiti spremištu).

note: (title)
en: Example issue tracker query dialog
target: Primer dijaloga zahteva problem tragača

note: (para)
en: For illustration purposes, let's suppose that your system administrator has provided you with an issue tracker plugin which you have installed, and that you have set up some of your working copies to use the plugin in TortoiseSVN's settings dialog. When you open the commit dialog from a working copy to which the plugin has been assigned, you will see a new button at the top of the dialog. <placeholder-1/> In this example you can select one or more open issues. The plugin can then generate specially formatted text which it adds to your log message.
target: U ilustrativne svrhe, pretpostavimo da je vaš sitem administrator obezbedio problem tragač plagin koji ste instalirali, i da ste podesili neke vaše radne kopije da koriste plagin u TortoiseSVN dijalogu podešavanja. Kada otvorite dijalog urezivanje iz radne kopije na koju je asociran plagin možete videti novo dugme na vrhu dijaloga. <placeholder-1/> U ovom primeru možete izabrati jedan ili više otvorenih problema. Plagin možete generisati specijalno formatirani tekst koji ste dodali vašem dnevniku porke.

note: (title)
en: Integration with Web-based Repository Viewers
target: Integracija sa Veb-zasnovanom pregledaču spremišta

note: (primary)
en: web view
target: veb vidi

note: (primary)
en: repo viewer
target: rep pregledač

note: (primary)
en: ViewCS
target: VidiCS

note: (para)
en: There are several web-based repository viewers available for use with Subversion such as <ulink url="http://www.viewvc.org/"><citetitle>ViewVC</citetitle></ulink> and <ulink url="http://websvn.tigris.org/"><citetitle>WebSVN</citetitle></ulink>. TortoiseSVN provides a means to link with these viewers.
target: Postoji više veb-zasnovanih pregledača spremišta dostupnih za korišćenje kao <ulink url="http://www.viewvc.org/"><citetitle>PregledajVC</citetitle></ulink> and <ulink url="http://websvn.tigris.org/"><citetitle><ulink url="http://www.viewvc.org/"><citetitle>ViewVC</citetitle></ulink> and <ulink url="http://websvn.tigris.org/"><citetitle>WebSVN</citetitle></ulink>VebSVN</citetitle></ulink>. TortoiseSVN omogućava način da povežete sa ovim pregledačem.

note: (para)
en: You can integrate a repo viewer of your choice in TortoiseSVN. To do this, you have to define some properties which define the linkage. They must be set on Folders: (<xref linkend="tsvn-dug-propertypage"/>)
target: Možete integrisati repo pregledač vašeg izbora u TortoiseSVN. Da se to uradi imate da definišete neke osobine koje definišu povezivanju. Oni moraju biti podešene na Imenicima: (<xref linkend="tsvn-dug-propertypage"/>)

note: (para)
en: Set this property to the URL of your repo viewer to view all changes in a specific revision. It must be properly URI encoded and it has to contain <literal>%REVISION%</literal>. <literal>%REVISION%</literal> is replaced with the revision number in question. This allows TortoiseSVN to display a context menu entry in the log dialog <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>View revision in webviewer</guimenuitem></menuchoice>
target: Podesite ove osobine za URL vašeg repo pregledača da vidite izmene u specifičnoj reviziji. Mora biti odgovarajući URI kodiran i mora da sadrži <literal>%REVISION%</literal>. <literal>%REVISION%</literal> je zamenjena sa revizionim brojem u pitanju. Ovo dopušta TrotoiseSVN da prikaže ulaz kontekst menija u dnevnik dijaloga <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Pregledati reviziju na vebsajtu</guimenuitem></menuchoice>

note: (para)
en: Set this property to the URL of your repo viewer to view changes to a specific file in a specific revision. It must be properly URI encoded and it has to contain <literal>%REVISION%</literal> and <literal>%PATH%</literal>. <literal>%PATH%</literal> is replaced with the path relative to the repository root. This allows TortoiseSVN to display a context menu entry in the log dialog <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>View revision and path in webviewer</guimenuitem></menuchoice> For example, if you right-click in the log dialog bottom pane on a file entry <literal>/trunk/src/file</literal> then the <literal>%PATH%</literal> in the URL will be replaced with <literal>/trunk/src/file</literal>.
target: Podeite ove osobine u URL vašeg repo pregledača da vidite izmene posebnih fajlova u posebnoj reviziji. Mora biti ispravno URI kodirano i ima da sadrži <literal>%REVISION%</literal>i <literal>%PATH%</literal>. <literal>%PATH%</literal> se zamenjuje sa putanjom relativnom sa korenom spremišta. Ovo omogućava TortoiseSVN da prikaže kontekst meni ulaz u dnevnik dijalogu <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Pregled revizije i putanje u vebpregledaču</guimenuitem></menuchoice> Na primaer, ako uradite desni-klik na donji panel dnevnik dijaloga fajl ulaza <literal>/trunk/src/file</literal> zatim <literal>%PATH%</literal> u URL će biti zamenjen sa <literal>/trunk/src/file</literal>.

note: (para)
en: You can also use relative URLs instead of absolute ones. This is useful in case your web viewer is on the same domain/server as your source repository. In case the domain name ever changes, you don't have to adjust the <literal>webviewer:revision</literal> and <literal>webviewer:pathrevision</literal> property. The format is the same as for the <literal>bugtraq:url</literal> property. See <xref linkend="tsvn-dug-bugtracker"/>.
target: Možete takođe da koristite URL umesto apsolutnih. Ovo je korisno u slučaju da je vaš veb pregledač na istom domen/serveru kao vaše izvorno spremište. U slučaju da se ime domena ikad promeni, vi nemate da podesite <literal>webviewer:revision</literal>i <literal>webviewer:pathrevision</literal> osobinu. Format je isti kao za <literal>bugtraq:url</literal> osobinu. Vidite <xref linkend="tsvn-dug-bugtracker"/>.

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

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

note: (para)
en: To find out what the different settings are for, just leave your mouse pointer a second on the editbox/checkbox... and a helpful tooltip will popup.
target: Da biste našli koja različita podešavanja su za to, samo ostavite pointer miša sekundu na editboks/čekboks.. i pojaviće se alatsavet za pomoć.

note: (title)
en: General Settings
target: Generalno podešavanje

note: (primary)
en: sounds
target: zvuci

note: (title)
en: The Settings Dialog, General Page
target: Dijalog podešavanja, opšta stranica

note: (para)
en: <placeholder-1/> This dialog allows you to specify your preferred language, and the Subversion-specific settings.
target: <placeholder-1/> Ovaj dijalog omogućava da odredite svoj željeni jezik, i Subverziono-specifučna podešavanja.

note: (term)
en: Language
target: Jezik

note: (para)
en: Selects your user interface language. What else did you expect?
target: Izaberite vaš jezik korisnočkog interfejsa. Šta ste još očekivali?

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

note: (para)
en: If checked, TortoiseSVN will contact its download site once a week to see if there is a newer version of the program available. Use <guibutton>Check now</guibutton> if you want an answer right away. The new version will not be downloaded; you simply receive an information dialog telling you that the new version is available.
target: Ako je čekiran, TortoiseSVN će kontaktirati njegov sajt za skidanje jednom nedeljno da vidi dali postoji nova verzija programa. Koristite <guibutton>Proveri sada</guibutton> ako želite odgovor upravo sada. Nova verzija neće biti skinuta; vi jednostavno dobijate informacioni dijalog koji vam kaže da je nova verzija dostupna.

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: (para)
en: TortoiseSVN has three custom sounds which are installed by default. <placeholder-1/> You can select different sounds (or turn these sounds off completely) using the Windows Control Panel. <guibutton>Configure</guibutton> is a shortcut to the Control Panel.
target: TortoiseSVN ima tri obična zvuka koji su instalirani uobičajeno.  <placeholder-1/> Možete izabrati različite zvuke (ili potpuno isključiti zvuk) koristeći Vindouz Kontrolni Panel. guibutton>Konfiguriši</guibutton> je skraćenica za Kontrolni Panel.

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

note: (primary)
en: exclude pattern
target: isključi model

note: (primary)
en: global ignore
target: globalno zanemarivanje

note: (para)
en: Global ignore patterns are used to prevent unversioned files from showing up e.g. in the commit dialog. Files matching the patterns are also ignored by an import. Ignore files or directories by typing in the names or extensions. Patterns are separated by spaces e.g. <literal>*/bin */obj *.bak *.~?? *.jar *.[Tt]mp</literal>. Remember that these patterns may be used against paths which include N levels of parent directory. Setting ignore patterns for anything other than simple file extensions is not as trivial as it first appears, so be sure to read <xref linkend="tsvn-dug-ignore-glob"/> for more information on the pattern-matching syntax, and how paths are checked.
target: Globalni modeli zanemarivanja su korišćeni da preduprede neverzionisane fajlove da budu prikazani npr. u dijalogu urezivanja. Fajlovi koje uhvati model su takođe zanemareni pri uvozu. Zanemarite fajlove ili imenike unošenjem njihovih imena ili ekstenzija. Modeli su razdvojeni razmacima npr.  <literal>*/bin */obj *.bak *.~?? *.jar *.[Tt]mp</literal>. Zapamtite da ovi modeli se mogu koristiti za putanje koje uključuju N nivoa predačkog imenika. Podešavanje modela zanemarivanja za bilo šta drugo osim jednostavnih ekstenzija fajlova nije trivijalno kada se prvi put javi, da biste bili sigurni pročitajte <xref linkend="tsvn-dug-ignore-glob"/> za više informacija o model-hvatanja sintaksi i kako se putanje proveravaju.

note: (para)
en: Note that the ignore patterns you specify here will also affect other Subversion clients running on your PC, including the command line client.
target: Primetimo da se modeli zanemarivanja koje ste ovde specificirali takođe utiču na ostale Subverzione klijente koji rade na vašem PC, uključujući klijente komandne linije.

note: (para)
en: If you use the Subversion configuration file to set a <literal>global-ignores</literal> pattern, it will override the settings you make here. The Subversion configuration file is accessed using the <guibutton>Edit</guibutton> as described below.
target: Ako koristite Subverzioni konfiguracioni fajl da podesite <literal>global-ignores</literal> model, to će premostiti podešavanje koje ste ovde uradili. Subverzioni konfiguracioni fajl je kontaktiran korišćenjem <guibutton>Uredi</guibutton> kako je objašnjeno u daljem tekstu.

note: (para)
en: This ignore pattern will affect all your projects. It is not versioned, so it will not affect other users. By contrast you can also use the versioned <literal>svn:ignore</literal> property to exclude files or directories from version control. Read <xref linkend="tsvn-dug-ignore"/> for more information.
target: Ovaj model zanemarivanja će uticati na sve vaše projekte. On nije verzionisan, tako da neće uticati na druge korisnike. Zbog kontrasta možete takođe koristiti verzionisanu <literal>svn:ignore</literal> osobinu da isključite fajlove ili imenike iz kontrole verzija. Pročitajte <xref linkend="tsvn-dug-ignore"/> za viže informacija.

note: (term)
en: Set file dates to the <quote>last commit time</quote>
target: Podesite datum fajla na <quote>poslednje vreme urezivanja</quote>

note: (para)
en: This option tells TortoiseSVN to set the file dates to the last commit time when doing a checkout or an update. Otherwise TortoiseSVN will use the current date. If you are developing software it is generally best to use the current date because build systems normally look at the date stamps to decide which files need compiling. If you use <quote>last commit time</quote> and revert to an older file revision, your project may not compile as you expect it to.
target: Ova opcija kaže TortoiseSVN da podesi datum fajla na vreme zadnjeg urezivanja kada se radi preuzimanje ili ažuriranje. Drugačije TortoiseSVN će koristiti tekući datum. Ako ste razvijali softver generalno je najbolje da koristite tekući datum jer sistem za izgradnju normalno gleda na datum markicu da odredi koje fajlove treba komajlirati. Ako koristite <quote>last commit time</quote> i vratiti u stariju reviziju, vaš projekat ne može kompajlirati onako kako očekujete od njega.

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

note: (para)
en: Use <guibutton>Edit</guibutton> to edit the Subversion configuration file directly. Some settings cannot be modified directly by TortoiseSVN, and need to be set here instead. For more information about the Subversion <filename>config</filename> file see the <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.confarea.html"><citetitle>Runtime Configuration Area</citetitle></ulink>. The section on <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html#svn.advanced.props.auto"><citetitle>Automatic Property Setting</citetitle></ulink> is of particular interest, and that is configured here. Note that Subversion can read configuration information from several places, and you need to know which one takes priority. Refer to <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.confarea.html#svn.advanced.confarea.windows-registry"><citetitle>Configuration and the Windows Registry</citetitle></ulink> to find out more.
target: Koristite <guibutton>Uredi</guibutton>  da uredite Subverzioni konfiguracioni fajl direktno. neka podešavanje se ne mogu izmeniti sa TortoiseSVN, i traže da umesto toga budu podešena ovde. Za više informacija o Subverzionom <filename>konfig</filename> fajlu vidite <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.confarea.html"><citetitle>Runtime Configuration Area</citetitle></ulink>. Poglavlje na  <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html#svn.advanced.props.auto"><citetitle>Automatic Property Setting</citetitle></ulink> je od posebnog interesa, i ono je konfigurisano ovde. Primetimo da Subverzija može čitati konfiguracione informacije sa više mesta , i potrebno je da znate koji ima prioritet. Uporedite sa <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.confarea.html#svn.advanced.confarea.windows-registry"><citetitle>Configuration and the Windows Registry</citetitle></ulink> da nađete više o tome.

note: (term)
en: Use <filename>_svn</filename> instead of <filename>.svn</filename> directories
target: Koristite <filename>_svn</filename>umesto <filename>.svn</filename> imenika.

note: (para)
en: VS.NET when used with web projects can't handle the <literal>.svn</literal> folders that Subversion uses to store its internal information. This is not a bug in Subversion. The bug is in VS.NET and the frontpage extensions it uses. Read <xref linkend="tsvn-dug-settings-asp-dot-net"/> to find out more about this issue.
target: VS.NET kada se koristi sa veb projektima ne može da rukuje sa  <literal>.svn</literal> imenicima koje Subverzija koristi da smešta interne informacije. Ovo nije bag u Subverziji. Bag je u VS.NET i prednjoj strani koju koristi. Pročitajte <xref linkend="tsvn-dug-settings-asp-dot-net"/> da nađete više o ovom problemu.

note: (para)
en: If you want to change the behaviour of Subversion and TortoiseSVN, you can use this checkbox to set the environment variable which controls this.
target: Ako želite da izmenite ponašanje Subverzije i TortoiseSVN, možete koristiti čekboks da podesite promenljive okoline koje to kontrolišu.

note: (para)
en: You should note that changing this option will not automatically convert existing working copies to use the new admin directory. You will have to do that yourself using a script (See our FAQ) or simply check out a fresh working copy.
target: Treba da primetite da izmena ovih opcija  ne konvertuje automatski postojeće radne kopije da koriste novi admin imenik. Imaćete da to uradite lično koristeći skript (Vidite naš ČPP) ili jednostavno preuzmite svežu radnu kopiju.

note: (title)
en: Context Menu Settings
target: Podešavanje kontekstnog menija

note: (title)
en: The Settings Dialog, Context Menu Page
target: Dijalog podešavanja, Konetekst meni strana

note: (para)
en: <placeholder-1/> This page allows you to specify which of the TortoiseSVN context menu entries will show up in the main context menu, and which will appear in the TortoiseSVN submenu. By default most items are unchecked and appear in the submenu.
target: <placeholder-1/> Ova strana omogućava da odredite koji od TortoiseSVN kontekst meni ulaz će biti prikazan u glavnom kontekst meniju, i koji će se pojaviti u TortoiseSVN submeni. Uobičajeno je da je većina stavki neproverena i pojavljuju se u submeniju.

note: (para)
en: There is a special case for <guilabel>Get Lock</guilabel>. You can of course promote it to the top level using the list above, but as most files don't need locking this just adds clutter. However, a file with the <literal>svn:needs-lock</literal> property needs this action every time it is edited, so in that case it is very useful to have at the top level. Checking the box here means that when a file is selected which has the <literal>svn:needs-lock</literal> property set, <guilabel>Get Lock</guilabel> will always appear at the top level.
target: Postoji poseban slučaj za <guilabel>Uzmi Katanac</guilabel>. Možete, svakako, pogurati to na vršni nivo koristeći gornju listu, ali kako većina fajlova ne zahteva zaključavanje samo dodaje gužvu. Međutim, fajl sa <literal>svn:needs-lock</literal> osobinom zahteva ovu akciju svaki put kada se uređuje, tako da u tom slučaju to je veoma korisno imati ga na gornjem nivou. Čekiranjem boksa ovde znači to da kada je fajl izabran koji ima <literal>svn:needs-lock</literal> osobinu izabranu, <guilabel>Nabavi Katanac</guilabel> će se uvek pojaviti u gornjem nivou.

note: (title)
en: TortoiseSVN Dialog Settings 1
target: TortoiseSVN dijalog podešavanje 1

note: (title)
en: The Settings Dialog, Dialogs 1 Page
target: Podešavanje dijaloga, dijalog 1 strana

note: (para)
en: <placeholder-1/> This dialog allows you to configure some of TortoiseSVN's dialogs the way you like them.
target: <placeholder-1/> Ovaj dijalog vam dozvoljava da konfigurišete neke TortoiseSVN dijaloge na način kako volite.

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

note: (para)
en: Limits the number of log messages that TortoiseSVN fetches when you first select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Show Log</guimenuitem></menuchoice> Useful for slow server connections. You can always use <guibutton>Show All</guibutton> or <guibutton>Next 100</guibutton> to get more messages.
target: Ograničava broj dnevnik poruka koje TortoiseSVN nađe kada najpre izaberete <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Pokaži Dnevnik</guimenuitem></menuchoice> Korisno za spor server vezu. Možete uvek koristiti <guibutton>Prikaži Svel</guibutton> ili <guibutton>Sledećih 100</guibutton> da dobojete više poruka.

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

note: (para)
en: Selects the font face and size used to display the log message itself in the middle pane of the Revision Log dialog, and when composing log messages in the Commit dialog.
target: Izabira oblik pisma i veličinu korišćenu za prikazivanje same dnevnik poruke u srednjem panelu Dnevnik Revizija dijalogu, i kada se sastavlja dnevnik poruke u Ureži dijalogu.

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

note: (para)
en: If the standard long messages use up too much space on your screen use the short format.
target: Ako standardne dugačke poruke koriste suviše prostora na vašem ekranu koristite kratak format.

note: (term)
en: Progress Dialog
target: Progres dijalog

note: (para)
en: TortoiseSVN can automatically close all progress dialogs when the action is finished without error. This setting allows you to select the conditions for closing the dialogs. The default (recommended) setting is <guilabel>Close manually</guilabel> which allows you to review all messages and check what has happened. However, you may decide that you want to ignore some types of message and have the dialog close automatically if there are no critical changes.
target: TortoiseSVN može automatski da završi sve progres dijaloge kada se akcija završi bez greške. Ovo podešavanje vam omogućava da izaberete uslove zatvaranja dijaloga. Uobičajeno (preporučeno) podešavanje je <guilabel>Zatvori ručno</guilabel> što dozvoljava da pregledate sve poruke i proverite šta se desilo. Međutim, možete odlučiti da želite da zanemarite neki tip poruka i dijalog je zatvoren automatski ako nema kritičnih izmena.

note: (para)
en: <guilabel>Auto-close if no merges, adds or deletes</guilabel> means that the progress dialog will close if there were simple updates, but if changes from the repository were merged with yours, or if any files were added or deleted, the dialog will remain open. It will also stay open if there were any conflicts or errors during the operation.
target: <guilabel>Aut-zatvaranje ako nema stapanja, dodaj ili obriši</guilabel> znači da progres dijalog  će se zatvoriti ako je bilo jednostavnog ažuriranja, ali ako su izmene iz spremišta stopljene sa vašim, ili ako je bilo koji fajl dodat ili obrisan, dijalog će ostati otvoren. On će takođe ostati otvoren ako je bio bio koji konflikt ili greška u toku operacije.

note: (para)
en: <guilabel>Auto-close if no merges, adds or deletes for local operations</guilabel> means that the progress dialog will close as for <guilabel>Auto-close if no merges, adds or deletes</guilabel> but only for local operations like adding files or reverting changes. For remote operations the dialog will stay open.
target: <guilabel>Auto-zatvaranje ako nema stapanja, dodavanja ili brisanja za lokalne operacije</guilabel> znači da će se progres dijalog zatvoriti kao za <guilabel>Auto-zatvaranje ako nema stapanja, dodavanja i brisanja</guilabel> ali samo za lokalne operacije kao dodavanje fajlova ili vraćanje izmena. Za daljinske operacije dijalog će ostati otvoren.

note: (para)
en: <guilabel>Auto-close if no conflicts</guilabel> relaxes the criteria further and will close the dialog even if there were merges, adds or deletes. However, if there were any conflicts or errors, the dialog remains open.
target: <guilabel>Auto-zatvaranje ako nema konflikta</guilabel> dalje oslabljuje kriterijume i zatvoriće dijalog čak i ako ima stapanja, dodavanja i brisanja. Međutim, ako je bilo bilo kakvog konflikta ili grešaka, dijalog ostaje otvoren.

note: (para)
en: <guilabel>Auto-close if no errors</guilabel> always closes the dialog even if there were conflicts. The only condition that keeps the dialog open is an error condition, which occurs when Subversion is unable to complete the task. For example, an update fails because the server is inaccessible, or a commit fails because the working copy is out-of-date.
target: <guilabel>Auto-zatvaranje ako nema grešaka</guilabel> uvek zatvara dijalog čak i ako je bio konflikata. Jedini uslov koji drži otvoren dijalog je uslov greške, što se javlja kada je Subverzija  omogućenada kompletira zadatak. Na primer, ažuriranje je neuspešno zato što  je server nedostupan, ili urezivanje je neuspešno zato što je radna kopija zastarela.

note: (term)
en: Use URL of WC as the default <quote>From:</quote> URL
target: Koristi URL od RK kao uobičajeno <quote>Od:</quote> URL

note: (para)
en: In the merge dialog, the default behaviour is for the <guilabel>From:</guilabel> URL to be remembered between merges. However, some people like to perform merges from many different points in their hierarchy, and find it easier to start out with the URL of the current working copy. This can then be edited to refer to a parallel path on another branch.
target: U dijalogu stapanja, uobičajeno ponašanje je za <guilabel>Od:</guilabel> URL biće zapamćen između stapanja. Međutim, neki ljudi vole da primene stapanje od mnogo različitih tačaka u njihovoj hijerarhiji, i nađe da je lakše da počne sa URL tekuće radne kopije. Ovo može biti uređeno da se odnosi na paralelnu putanju na drugoj grani.

note: (term)
en: Default checkout path
target: Uobičajena putanja preuzimanja

note: (para)
en: You can specify the default path for checkouts. If you keep all your checkouts in one place, it is useful to have the drive and folder pre-filled so you only have to add the new folder name to the end.
target: Možete specificirati uobičajenu putanju za preuzimanje. Ako čuvate sva preuzimanja na jednom mestu, korisno je imati drajv i imenik popunjen tako da samo imate da dodate novo ime  imenika na kraju.

note: (term)
en: Default checkout URL
target: Uobičajen URL preuzimanja

note: (para)
en: You can also specify the default URL for checkouts. If you often checkout sub-projects of some very large project, it can be useful to have the URL pre-filled so you only have to add the sub-project name to the end.
target: Možete takođe specificirati uobičajeni URL za preuzimanje. Ako često preuzimate sub-projekte nekih veoma velike projekte, može biti korisno imati URL pre-popunjene tako da se ima samo dodati sub-projekat ime na kraju.

note: (title)
en: TortoiseSVN Dialog Settings 2
target: TortoiseSVN dijalog pdešavanja 2

note: (title)
en: The Settings Dialog, Dialogs 2 Page
target: Dijalog podešavanja, Dijalog 2 stranica

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

note: (para)
en: If this box is checked (default state), then whenever the status of an unversioned folder is shown in the <guilabel>Add</guilabel>, <guilabel>Commit</guilabel> or <guilabel>Check for Modifications</guilabel> dialog, every child file and folder is also shown. If you uncheck this box, only the unversioned parent is shown. Unchecking reduces clutter in these dialogs. In that case if you select an unversioned folder for Add, it is added recursively.
target: Ovaj boks je čekiran (uobičajeno stanje), zatim kadgod je status neverzionisani imenik prikazan u <guilabel>Dodaj</guilabel>, <guilabel>Ureži</guilabel> ili <guilabel>Privera  Modifikacija</guilabel> dijalog, svaki potomački fajl i imenik je takođe prikazan. Ako otčekirate ovaj boks, samo neverzionisani predak je prikazan. Otčekivanje redukuje gužvu u ovim dijalozima. U ovom slučaju ako izaberete neverzionisani imenik za Dodaj, dodaje se rekurzivno.

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

note: (para)
en: The commit dialog includes a facility to parse the list of filenames being committed. When you type the first 3 letters of an item in the list, the auto-completion box pops up, and you can press Enter to complete the filename. Check the box to enable this feature.
target: Dijalog urezivanja uključuje mogućnost da analizira listu imenafajlova koja se urezuje. Kada ukucate prva 3 slova stavke u listu, auto-kompletiranje boks iskoči, i možete pritisnuti Enter da kompletirate fajlime. Čekirajte boks da omogućite ovu osobinu.

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

note: (para)
en: The auto-completion parser can be quite slow if there are a lot of large files to check. This timeout stops the commit dialog being held up for too long. If you are missing important auto-completion information, you can extend the timeout.
target: Auto-kompletiranje analizator može biti sasvim spor ako ima mnogo velikih fajlova da se provere. Tajmaut zaustavlja dijalog urezivanja da bude držan suviše dugo. Ako vam nedostaju važne informacije auto-kompletiranja, možete proširiti tajmaut.

note: (term)
en: Only use spellchecker when <literal>tsvn:projectlanguage</literal> is set
target: Samo koristite proveru pravopisa kada je <literal>tsvn:projectlanguage</literal>  podešen.

note: (para)
en: If you don't wish to use the spellchecker for all commits, check this box. The spellchecker will still be enabled where the project properties require it.
target: Ako ne želite da koristite proveru sintakse za sva urezivanja čekirajte ovaj boks. Provera sintakse će još biti omogućena gde osobine projekta to zahtevaju.

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

note: (para)
en: TortoiseSVN stores the last 25 log messages you entered for each repository. You can customize the number stored here. If you have many different repositories, you may wish to reduce this to avoid filling your registry.
target: TortoiseSVN skladišti zadnjih 25 dnevnik poruka koje ste uneli za svako spremište. Možete prilagoditi brojeve uskladištene ovde.Ako imate mnogo različitih spremišta, možete želeti da redukujete ovo da bi izbegli punjenje registra.

note: (term)
en: Re-open commit and branch/tag dialog after a commit failed
target: Re-otvara urezivanje i grana/znak dijalog posle neipravnog urezivanja.

note: (para)
en: When a commit fails for some reason (working copy needs updating, pre-commit hook rejects commit, network error, etc), you can select this option to keep the commit dialog open ready to try again. However, you should be aware that this can lead to problems. If the failure means you need to update your working copy, and that update leads to conflicts you must resolve those first.
target: kada urezivanje otkaže iz nekog razloga (radna kopija traži ažuriranje, pre-urezivanja zakačaljka odbija urezivanje, mrežna greška, itd.), možete izabrati ovu opciju da držite dijalog urezivanja otvoren i spreman da pokuša ponovo. Međutim, treba da budete oprezni jer ovo može dovesti do problema. Ako kvarvznači da treba da ažurirate radnu kopiju, i to ažuriranje dovodi do konflikta koja morate rešiti najpre.

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

note: (para)
en: The normal behaviour in the commit dialog is for all modified (versioned) items to be selected for commit automatically. If you prefer to start with nothing selected and pick the items for commit manually, uncheck this box.
target: Normalno ponašanje u dijalogu urezivanja za sve modifikovane (verzionisane) stavke je sizabrano za urezivanje automatski. Ako više volite da počnete tako što ništa nije izabrano i odaberemo stavku za urezivanje ručno otčekirajte ovaj boks.

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

note: (para)
en: The Check for Modifications dialog checks the working copy by default, and only contacts the repository when you click <guibutton>Check repository</guibutton>. If you always want to check the repository, you can use this setting to make that action happen automatically.
target: Provera Modifikacija dijalog čekira radnu kopiju uobičajeno, i samo kontakt spremišta kada kliknete <guibutton>Provera spremišta</guibutton>. Ako uvek želite da čekirate spremište, možete koristiti ovo podešavanje da učinite tu akciju koja se dešava automatski.

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

note: (para)
en: When you select one or more files and then use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Lock</guimenuitem></menuchoice> to take out a lock on those files, on some projects it is customary to write a lock message explaining why you have locked the files. If you do not use lock messages, you can uncheck this box to skip that dialog and lock the files immediately.
target: Kada izaberete jedan ili više fajlova i onda koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Katanac</guimenuitem></menuchoice> da uklonite katanac na ove fajlove, na nekim projektima je uobičajeno da se napiše katanac poruka koja objašnjava zašto imate zaključane fajlove. Ako ne koristite katanac poruke, možete otčekirati ovaj boks da preskočite taj dijalog i zaključate fajlove trenutno.

note: (para)
en: If you use the lock command on a folder, you are always presented with the lock dialog as that also gives you the option to select files for locking.
target: Ako koristite zaključaj komandu na imenik, vama je predstavljen dijalog zaključavanja kao nešto što vam daje opcije da izaberete fajlve za zaključavanje.

note: (para)
en: If your project is using the <literal>tsvn:lockmsgminsize</literal> property, you will see the lock dialog regardless of this setting because the project <emphasis>requires</emphasis> lock messages.
target: Ako vaš projekat koristi <literal>tsvn:lockmsgminsize</literal> osobinu, videćete dijalog zaključavanja bezobzira na ovo podešavanje jer projekat <emphasis>zahteva</emphasis> poruke zaključavanja.

note: (title)
en: TortoiseSVN Colour Settings
target: TortoiseSVN podešavanje boja

note: (title)
en: The Settings Dialog, Colours Page
target: Dijalog Podešavanja, Stranica Boja

note: (para)
en: <placeholder-1/> This dialog allows you to configure the text colours used in TortoiseSVN's dialogs the way you like them.
target: <placeholder-1/> Ovaj dijalog dopušta da konfigurišete boje teksta korišćene u TortoiseSVN dijalozima na način kakav volite.

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

note: (para)
en: A conflict has occurred during update, or may occur during merge. Update is obstructed by an existing unversioned file/folder of the same name as a versioned one.
target: Konflikt se može pojaviti tokom ažuriranja, ili se može pojaviti u toku stapanja. Ažurriranje je ometeno postojećim neverzionisanim fajlom/imenikom istog imena kao neki verzionisan.

note: (para)
en: This colour is also used for error messages in the progress dialogs.
target: Boja se takođe koristi za poruke greške u progres dijalozima.

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

note: (para)
en: Items added to the repository.
target: Stavke dodate u spremište

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

note: (para)
en: Items deleted from the repository, missing from the working copy, or deleted from the working copy and replaced with another file of the same name.
target: Obrisane stavke iz spremišta, koje nedostaju u radnoj kopiji, ili obrisane iz radne kopije i zamenjene sa drugim fajlom istog imena.

note: (term)
en: Merged
target: Stopljeno

note: (para)
en: Changes from the repository successfully merged into the WC without creating any conflicts.
target: Izmene u spremištu sukcesivno stopljene u RK bez kreiranja bilo kakvog konflikta.

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

note: (para)
en: Add with history, or paths copied in the repository. Also used in the log dialog for entries which include copied items.
target: Dodavanje sa istorijom, ili putanja kopirana u spremište. Takođe u dnevnik dijalogu za ulaze koje uključuje kopirana stavka.

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

note: (para)
en: An item which has been deleted from the repository.
target: Stavka koja je obrisana u spremištu.

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

note: (para)
en: An item which has been added to the repository, by an add, copy or move operation.
target: Stavka koja je dodata u spremište, pomoču dodaj, kopiraj ili pomeri operacije.

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

note: (para)
en: An item which has been renamed within the repository.
target: Stavka koja je preimenovana u okviru spremišta.

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

note: (para)
en: The original item has been deleted and a new item with the same name replaces it.
target: Originalna stavka je obrisana i nova stavka istog imena je zamenila.

note: (title)
en: Icon Overlay Settings
target: Ikona prekrivač podešavanje

note: (title)
en: The Settings Dialog, Icon Overlays Page
target: Dijalog podešavanja, Ikona prekrivači stranica

note: (para)
en: <placeholder-1/> This page allows you to choose the items for which TortoiseSVN will display icon overlays.
target: <placeholder-1/> Ova strana dopušta da izaberete stavku za koju TortoiseSVN će prikazati prekrivnu ikonu.

note: (para)
en: By default, overlay icons and context menus will appear in all open/save dialogs as well as in Windows Explorer. If you want them to appear <emphasis>only</emphasis> in Windows Explorer, check the <guilabel>Show overlays and context menu only in explorer</guilabel> box.
target: Uobičajeno, prekrivne ikone i kontekst meniji će se pojaviti u svim otvori/sačuvaj dijalozima kao u Vindouz Eksploreru. Ako želite da se oni pojave <emphasis>samo</emphasis> u Vindouz Eksploreru, čekirajte <guilabel>Prikaži prekrivače i kontekst meni samo u eksploreru</guilabel> boks.

note: (para)
en: Ignored items and Unversioned items are not usually given an overlay. If you want to show an overlay in these cases, just check the boxes.
target: Zanemarene stavke i Neverzionisane stavke obično nemaju prekrivač. Ako želite da prikažete prekrivač u ovim slučajevima, samo čekirajte boksove.

note: (para)
en: You can also choose to mark folders as modified if they contain unversioned items. This could be useful for reminding you that you have created new files which are not yet versioned. This option is only available when you use the <emphasis>default</emphasis> status cache option (see below).
target: Možete takođe izabrati da označite imenik kao izmenjen ako on sadrži neverzionisane stavke. Ovo može biti korisno da vas podseti da ste kreirali nove fajlove koji još nisu verzionisani. Ova opcija je dostupna samo ako koristite <emphasis>uobičajen</emphasis> status keš opciju (vidi dole).

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

note: (para)
en: Caches all status information in a separate process (<filename>TSVNCache.exe</filename>). That process watches all drives for changes and fetches the status again if files inside a working copy get modified. The process runs with the least possible priority so other programs don't get hogged because of it. That also means that the status information is not <emphasis>real time</emphasis> but it can take a few seconds for the overlays to change.
target: Kešira sve status informacije u odvojenim procesima  (<filename>TSVNCache.exe</filename>). Taj proces posmatra sve drajvove za izmene i nalazi ponovo status ako su fajlovi unutar radne kopije modifikovani. Proces radi sa najmanjim mogućim prioritetom tako da drugi programi blokirani zbog njega. To takođe znači da status informacija nije <emphasis>u realnom vremenu</emphasis> ali može uzeti nekoliko sekundi da se prekrivač promeni.

note: (para)
en: Advantage: the overlays show the status recursively, i.e. if a file deep inside a working copy is modified, all folders up to the working copy root will also show the modified overlay. And since the process can send notifications to the shell, the overlays on the left tree view usually change too.
target: Pogodnosti: prekrivači prikazuju status rekurzivno, tj. ako je fajl duboku unutar radne kopije izmenjen, svi imenici do korena radne kopije biće takođe prikazani izmenjenom ikonom. I kako proces može poslati notifikaciju školjci, prekrivači  u ostalom stablu će se takođe promeniti.

note: (para)
en: Disadvantage: the process runs constantly, even if you're not working on your projects. It also uses around 10-50 MB of RAM depending on number and size of your working copies.
target: Nepogodnosti: proces stalno radi, čak i ako ne radite na vašem projektima. On takođe koristi oko 10-50 MB od RAM zavisno od broja i veličine vaših radnih kopija.

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

note: (para)
en: Caching is done directly inside the shell extension dll, but only for the currently visible folder. Each time you navigate to another folder, the status information is fetched again.
target: Hvatanje je dato direktno unutar dll ekstenzije školjke, ali samo za tekući vidljivi imenik. Svaki put kad se krećete ka drugom imeniku status informacija se nalazi ponovo.

note: (para)
en: Advantage: needs only very little memory (around 1 MB of RAM) and can show the status in <emphasis>real time</emphasis>.
target: Pogodnosti: zahteva samo veoma maku memoriju (oko 1 MB RAMa) i može prikazati status u <emphasis>realnom vremenu</emphasis>.

note: (para)
en: Disadvantage: Since only one folder is cached, the overlays don't show the status recursively. For big working copies, it can take more time to show a folder in explorer than with the default cache. Also the mime-type column is not available.
target: Nepogodnosti: Pošto je samo jedan imenik uhvaćen, prekrivači ne pokazuju status rekurzivno. Za velike radne kopije može uzeti mnogo vremena da prikaže imenik u eksploreru sa uobičajenim hvatanjem. Takođe mime-tip kolone nije dostupan.

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

note: (para)
en: With this setting, the TortoiseSVN does not fetch the status at all in Explorer. Because of that, files don't get an overlay and folders only get a 'normal' overlay if they're versioned. No other overlays are shown, and no extra columns are available either.
target: Sa ovim podešavanjem TortoiseSVN uopšte ne hvata status u Eksploreru. Zato što, fajlovi ne dobijaju prekrivače i imenici samo dobijaju 'normalne' prekrivače ako su verzionisani. Drugi prekrivači su prikazani i nema dodatnih kolona da su dostupne.

note: (para)
en: Advantage: uses absolutely no additional memory and does not slow down the Explorer at all while browsing.
target: Pogodnost: apsolutno ne koristi dodatnu memoriju i uopšte ne usporava Eksplorer dok pretražuje.

note: (para)
en: Disadvantage: Status information of files and folders is not shown in Explorer. To see if your working copies are modified, you have to use the <quote>Check for modifications</quote> dialog.
target: Nepogodnost: SDtatus informacija fajlova i imenika nije prikazana u Eksploreru. Da vidite da li je vaša radna kopija izmenjena, treba da koristite <quote>Provera izmena</quote> dijalog.

note: (para)
en: Since it takes quite a while to fetch the status of a working copy, TortoiseSVN uses a cache to store the status so the explorer doesn't get hogged too much when showing the overlays. You can choose which type of cache TortoiseSVN should use according to your system and working copy size here: <placeholder-1/>
target: Pošto uzima sasvim malo da nađe status radne kopije, TortoiseSVN koristi keš da smesti status tako da eksplorer ne blokira mnogo dok prikazuje prekrivače. Možete izabrati koji tip keša TortoiseSVN treba da koristi u skladu sa vašim sistemom i veličinom radne kopije ovde:  <placeholder-1/>

note: (para)
en: The next group allows you to select which classes of storage should show overlays. By default, only hard drives are selected. You can even disable all icon overlays, but where's the fun in that?
target: Sledeća grupa dopušta vam da izaberete koju klasu skladištenja će prikazati prekrivač. Uobičajeno, samo tvrdi diskovi su izabrani. Možete čak onemogućiti prekrivače ikona, ali gde je zabava u tome?

note: (para)
en: Network drives can be very slow, so by default icons are not shown for working copies located on network shares.
target: Mrežni drajvovi mogu biti veoma spori, tako da uobičajeno ikone nisu prikazane za radnu kopiju lociranu na mrežnoj podeli.

note: (para)
en: USB Flash drives appear to be a special case in that the drive type is identified by the device itself. Some appear as fixed drives, and some as removable drives.
target: USB Fleš drajv se javlja kao specijalan slučaj u to drajv tipu se identificira od samog uređaja. Neki se javljaju kao fiksni diskovi, a neki kao pokretni drajvovi.

note: (para)
en: The <guilabel>Exclude Paths</guilabel> are used to tell TortoiseSVN those paths for which it should <emphasis>not</emphasis> show icon overlays and status columns. This is useful if you have some very big working copies containing only libraries which you won't change at all and therefore don't need the overlays. For example:
target: <guilabel>Isključi Putanje</guilabel> se koristi da kaže TortoiseSVN te putanje za koje <emphasis>ne</emphasis> treba prikazati prekrivač ikona i status kolone. Ovo je korisno ako imate neke veoma velike radne kopije koje sadrže samo biblioteke koje želite uopšte da menjate i zato ne traži prekrivače. Na primer:

note: (para)
en: <filename>f:\development\SVN\Subversion</filename> will disable the overlays <emphasis>only</emphasis> on that specific folder. You still can see the overlays on all files and folder inside that folder.
target: <filename>f:\development\SVN\Subversion</filename> će onemogućiti prekrivače <emphasis>samo</emphasis> na specifičnom imeniku. Vi još možete videti prekrivače na svim fajlovima unutar imenika.

note: (para)
en: <filename>f:\development\SVN\Subversion*</filename> will disable the overlays on <emphasis>all</emphasis> files and folders whose path starts with <filename>f:\development\SVN\Subversion</filename>. That means you won't see overlays for any files and folders below that path.
target: <filename>f:\development\SVN\Subversion*</filename> će  onemogućiti prekrivače na <emphasis>sve</emphasis> fajlove i imenike čije putanje počinju sa <filename>f:\development\SVN\Subversion</filename>. To znači da vi želite da vidite prekrivače za svaki fajl i imenik ispod putanje.

note: (para)
en: The same applies to the <guilabel>Include Paths</guilabel>. Except that for those paths the overlays are shown even if the overlays are disabled for that specific drive type, or by an exclude path specified above.
target: Isto se primenjuje na <guilabel>Uključi Putanje</guilabel>. Osim toga za te putanje prekrivači su prikazani čak ako su prekrivači onemogućeni za specifične tipove drajvova, ili isključenjem putanje specificirane gore.

note: (para)
en: Users sometimes ask how these three settings interact, and the definitive answer is: <screen>
    if (path is in include list)
      show overlays
    if (path is allowed drive type) AND (path is not in exclude list)
      show overlays
    </screen> The include list <emphasis>always</emphasis> makes the overlays show. Otherwise, overlays are shown for all marked drive types <emphasis>unless</emphasis> the path is excluded.
target: Korisnici ponekad pita kako ovo podešavanje stabla međusobno zavise, i definitivan odgovor je: <screen>
    if (path is in include list)
      show overlays
    if (path is allowed drive type) AND (path is not in exclude list)
      show overlays
    </screen> Lista uključivanja <emphasis>uvek</emphasis> čini da se prekrivači prikažu. Drugačije, prekrivači su prikazani za sve označene tipove drajvova <emphasis>osim</emphasis> putanje koja je isključena.

note: (para)
en: TSVNCache.exe also uses these paths to restrict its scanning. If you want it to look only in particular folders, disable all drive types and include only the folders you specifically want to be scanned.
target: TSVNCache.exe takođe koristi ove putanje da ograniči skeniranje. Ako želite da pogledate samo u pojedinačni imenik, onemogućite sve tipove drajvova i uključiti vaše specifične želje da budu skenirane.

note: (title)
en: Exclude <literal>SUBST</literal> Drives
target: Iskljućiti <literal>SUBST</literal>  Drajvovi

note: (primary)
en: SUBST drives
target: SUBST diskovi

note: (para)
en: It is often convenient to use a <literal>SUBST</literal> drive to access your working copies, e.g. using the command <screen>
    subst T: C:\TortoiseSVN\trunk\doc
    </screen> However this can cause the overlays not to update, as <literal>TSVNCache</literal> will only receive one notification when a file changes, and that is normally for the original path. This means that your overlays on the <literal>subst</literal> path may never be updated.
target: Često je običaj da se koristi <literal>SUBST</literal> drajv  da pristupi  vašim radnim kopijama, tj. koristeći komandu <screen>
    subst T: C:\TortoiseSVN\trunk\doc
    </screen> Međutim ovo može prouzrokovati prekrivanja nisu ažurirani, kao <literal>TSVNCache</literal>  će samo primiti jednu notifikaciju kada se fajl izmeni, i to je normalno za originalnu putanju. Ovo znači da vaši prekrivači na <literal>subst</literal> putanji može biti da se nikad ne ažurira.

note: (para)
en: An easy way to work around this is to exclude the original path from showing overlays, so that the overlays show up on the <literal>subst</literal> path instead.
target: Lak način da se radi oko ovoga je da se isključi originalna putanja iz prikazanih prekrivača, tako prekrivači su prikazani na <literal>subst</literal> putanji umesto toga.

note: (para)
en: Sometimes you will exclude areas that contain working copies, which saves TSVNCache from scanning and monitoring for changes, but you still want a visual indication that such folders are versioned. The <guilabel>Show excluded folders as 'normal'</guilabel> checkbox allows you to do this. With this option, versioned folders in any excluded area (drive type not checked, or specifically excluded) will show up as normal and up-to-date, with a green check mark. This reminds you that you are looking at a working copy, even though the folder overlays may not be correct. Files do not get an overlay at all. Note that the context menus still work, even though the overlays are not shown.
target: Ponekad vi ćete isključiti  polja koja sadrže radne kopije, koji čuva TSVNCache od skeniranja i nadgledanja za izmene, ali vi još uvek želite vizuelnu indikaciju  tamo gde su takvi imenici verzionisani. <guilabel>Prikaži isključene imenike kao  'normalne'</guilabel> čekboksove dopušta vam da uradite ovo. Sa ovom opcijom, verzionisani imenici u bilo kojoj isključenoj oblasti (tip drrajva nije čekiran, ili je specifično isključen) će prikazati kao normalno i savremen, sa zelenom ček oznakom. Ovo vas podseća da gledate radnu kopiju, čak ako imenik prekrivači ne moraju biti korektni. Fajlovi uopšte ne dobijaju prekrivače.  Primetimo da kontekst meniji još rade, čak i ako prekrivači nisu uključeni.

note: (para)
en: As a special exception to this, drives <literal>A:</literal> and <literal>B:</literal> are never considered for the <guilabel>Show excluded folders as 'normal'</guilabel> option. This is because Windows is forced to look on the drive, which can result in a delay of several seconds when starting Explorer, even if your PC does have a floppy drive.
target: Kao specijalni izuzetak na to, drajvi <literal>A:</literal> i <literal>B:</literal> se nikad ne uzimaju u obzir za <guilabel>Prikaži isključene imnjnike kao  'normalan'</guilabel>  opciju. Ovo se zbog Vindouza  forsirano da gleda na drajv, što može prouzrokovati kašnjenje od nekoliko sekundi kada se pokrene Eksplorer, čak ako vaš PC ima flopi drajv.

note: (title)
en: Icon Set Selection
target: Skup podešavanja ikona

note: (title)
en: The Settings Dialog, Icon Set Page
target: Dijalog podešavanja, Podešavanje ikona stranica

note: (para)
en: <placeholder-1/> You can change the overlay icon set to the one you like best. Note that if you change overlay set, you may have to restart your computer for the changes to take effect.
target: e<placeholder-1/>  Možete izmeniti podešavanje pokrivne ikone na ono što najviše volite. Primetimo da ako izmenimo podešavanje pokrivanja, možete restartovati vaš računar da bi izmene postale efikasne.

note: (title)
en: Network Settings
target: Mrežna podešavanja

note: (primary)
en: proxy server
target: proksi server

note: (title)
en: The Settings Dialog, Network Page
target: Dijalog podešavanja, Mrežna stranica

note: (para)
en: <placeholder-1/> Here you can configure your proxy server, if you need one to get through your company's firewall.
target: <placeholder-1/>  Ovde možete konfigurisat vaš proksi server, ako vam treba da provlačite kroz fajervol vaše kompanije.

note: (para)
en: If you need to set up per-repository proxy settings, you will need to use the Subversion <filename>servers</filename> file to configure this. Use <guibutton>Edit</guibutton> to get there directly. Consult the <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.confarea.html"><citetitle>Runtime Configuration Area</citetitle></ulink> for details on how to use this file.
target: Ako vam je potrebno da podesite po-spremištu proksi podešavanja, potrebno je da koristite Subverzioni <filename>server</filename> fajl da konfiguriše ovo. Koristi <guibutton>Uredi</guibutton> da dobiješ to direktno. Konsultujte <ulink url="http://svnbook.red-bean.com/en/1.5/svn.advanced.confarea.html"><citetitle>Runtime Configuration Area</citetitle></ulink> za detalje kako koristiti ovaj fajl.

note: (para)
en: You can also specify which program TortoiseSVN should use to establish a secure connection to a svn+ssh repository. We recommend that you use TortoisePlink.exe. This is a version of the popular Plink program, and is included with TortoiseSVN, but it is compiled as a Windowless app, so you don't get a DOS box popping up every time you authenticate.
target: Možete takođe specificirati koji program TortoiseSVN treba da koristi da postavi sigurnu vezu ka svn+ssh spremišta. Preporučujemo da koristite TortoisePlink.exe. Ovo je verzija popularnog Plink programa, i uključeno je sa TortoiseSVN, ali to je kompajlirano kao Vindouzbez aplikacija, tako da ne možete dobiti DOS boks koji iskače svaki put kada se prijavljujete.

note: (para)
en: You must specify the full path to the executable. For TortoisePlink.exe this is the standard TortoiseSVN bin directory. Use the <guibutton>Browse</guibutton> button to help locate it.
target: Morate specificirati punu putanju za izvršne programe. Za TortoisePlink.exe ovo je standardni TortoiseSVN bin imenik. Koristite <guibutton>Pretraži</guibutton> dugme da pomogne da ga nađe.

note: (para)
en: One side-effect of not having a window is that there is nowhere for any error messages to go, so if authentication fails you will simply get a message saying something like <quote>Unable to write to standard output</quote>. For this reason we recommend that you first set up using standard Plink. When everything is working, you can use TortoisePlink with exactly the same parameters.
target: Jedan ivični-efekat koji nema prozor je to da nema nigde da ode bilo kakva poruka greške, tako ako autentifikacija ne uspe vi ćete jednostavno dobiti poruku koja kaže nešto kao <quote>Nesposoban da piše na standardnom izlazu</quote>. Iz ovog razloga preporučujemo da najpre izvršite podešavanje koristeći standardni Plink. Kada sve radi, možete koristiti TortoisePlink sa tačno istim parametrima.

note: (para)
en: TortoisePlink does not have any documentation of its own because it is just a minor variant of Plink. Find out about command line parameters from the <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/putty/"><citetitle>PuTTY website</citetitle></ulink>
target: TortoisePlink nema nikakvu dokumentaciju o sebi zato što je minorna varijanta Plinka. Nađite o parametrima komandne linije na <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/putty/"><citetitle>PuTTY website</citetitle></ulink>

note: (para)
en: To avoid being prompted for a password repeatedly, you might also consider using a password caching tool such as Pageant. This is also available for download from the PuTTY website.
target: Da bi izbegli da budete pitani za lozinku neprestano možete takođe razmotriti koristeći alat nalaženja lozinke kao Pageant. Ovo je takođe dozvoljeno za skidanje sa  PuTTY vebsajta.

note: (para)
en: Finally, setting up SSH on server and clients is a non-trivial process which is beyond the scope of this help file. However, you can find a guide in the TortoiseSVN FAQ listed under <ulink url="http://tortoisesvn.net/ssh_howto"><citetitle>Subversion/TortoiseSVN SSH How-To</citetitle></ulink>.
target: Na kraju, podešavanje SSH na serveru i klijentima je ne-trivijalan proces koji je van interesa ovog fajla pomoći. Međutim, možete naći vodič u TortoiseSVN ČPP izlistanih pod <ulink url="http://tortoisesvn.net/ssh_howto"><citetitle>Subversion/TortoiseSVN SSH How-To</citetitle></ulink>.

note: (title)
en: External Program Settings
target: Spoljašnji program podešavanja

note: (title)
en: The Settings Dialog, Diff Viewer Page
target: Dijalog podešavanja, Razl pregledač stranica

note: (para)
en: <placeholder-1/> Here you can define your own diff/merge programs that TortoiseSVN should use. The default setting is to use TortoiseMerge which is installed alongside TortoiseSVN.
target: <placeholder-1/> Ovde možete definisati vaš lični diff/stopi programi koje TortoiseSVN treba da koristi. Uobičajeno podešavanje je da se koristi TortoiseMerge koji je instaliran kad i TortoiseSVN.

note: (para)
en: Read <xref linkend="tsvn-dug-diff-tools"/> for a list of some of the external diff/merge programs that people are using with TortoiseSVN.
target: Pročitajte xref linkend="tsvn-dug-diff-tools"/> za listu nekih od spoljašnjih diff/stopi programa koje ljudi koriste sa TortoiseSVN.

note: (title)
en: Diff Viewer
target: Razl pregledač

note: (para)
en: The original file without your changes
target: Originalan fajl bez vaših izmena

note: (para)
en: The window title for the base file
target: Vindouz naslov osnovnog fajla

note: (para)
en: Your own file, with your changes
target: Vaš lični fajl, sa vašim izmenama

note: (para)
en: The window title for your file
target: Vindouz naslov za vaš fajl

note: (para)
en: An external diff program may be used for comparing different revisions of files. The external program will need to obtain the filenames from the command line, along with any other command line options. TortoiseSVN uses substitution parameters prefixed with <literal>%</literal>. When it encounters one of these it will substitute the appropriate value. The order of the parameters will depend on the Diff program you use. <placeholder-1/>
target: Spoljašnji diff program može biti korišten za poređenje revizija fajlova. Sponjašnji programi će tražiti da dobijete fajlime iz komandne linije, zajedno sa svakom drugom opcijom komande. TortoiseSVN koristi parametre zamene sa prefiksom <literal>%</literal>.  Kada se uoči jedan od tih koji će biti zamenjeni odgovarajućom vrednošću. Red parametara će zavisiti na Diff programe koje koristite. <placeholder-1/>

note: (para)
en: The window titles are not pure filenames. TortoiseSVN treats that as a name to display and creates the names accordingly. So e.g. if you're doing a diff from a file in revision 123 with a file in your working copy, the names will be <filename>filename : revision 123</filename> and <filename>filename : working copy</filename>
target: Naslov prozora nije čisto fajlime. TortoiseSVN tretira to kao  ime da prikaže i kreira imena u skladu sa tim. Tako npr. ako radite sa diff sa fajlom u reviziji 123 sa fajlom u vašoj radnoj kopiji, imena će biti <filename>filename : revision 123</filename> i <filename>filename : working copy</filename>

note: (para)
en: For example, with ExamDiff Pro: <screen>
    C:\Path-To\ExamDiff.exe %base %mine --left_display_name:%bname
        --right_display_name:%yname
    </screen> or with KDiff3: <screen>
    C:\Path-To\kdiff3.exe %base %mine --L1 %bname --L2 %yname
    </screen> or with WinMerge: <screen>
    C:\Path-To\WinMerge.exe -e -ub -dl %bname -dr %yname %base %mine
    </screen> or with Araxis: <screen>
    C:\Path-To\compare.exe /max /wait /title1:%bname /title2:%yname
        %base %mine
    </screen>
target: Na primer, sa EgzamDiffPro: <screen>
    C:\Path-To\ExamDiff.exe %base %mine --left_display_name:%bname
        --right_display_name:%yname
    </screen> or with KDiff3: <screen>
    C:\Path-To\kdiff3.exe %base %mine --L1 %bname --L2 %yname
    </screen> or with WinMerge: <screen>
    C:\Path-To\WinMerge.exe -e -ub -dl %bname -dr %yname %base %mine
    </screen> or with Araxis: <screen>
    C:\Path-To\compare.exe /max /wait /title1:%bname /title2:%yname
        %base %mine
    </screen>

note: (para)
en: If you use the <literal>svn:keywords</literal> property to expand keywords, and in particular the <emphasis>revision</emphasis> of a file, then there may be a difference between files which is purely due to the current value of the keyword. Also if you use <literal>svn:eol-style = native</literal> the BASE file will have pure <literal>LF</literal> line endings whereas your file will have <literal>CR-LF</literal> line endings. TortoiseSVN will normally hide these differences automatically by first parsing the BASE file to expand keywords and line endings before doing the diff operation. However, this can take a long time with large files. If <guilabel>Convert files when diffing against BASE</guilabel> is unchecked then TortoiseSVN will skip pre-processing the files.
target: Ako koristite <literal>svn:keywords</literal> osobinu da proširite ključne reči i u posebnoj <emphasis>reviziji</emphasis> fajla, zatim ovde može biti razlika između fajlova koji su čisto podesni za tekuću vrednost ključne reči. Takođe vi koristite <literal>svn:eol-style = native</literal> OSNOVNI fajl će imati čist <literal>LF</literal> završetak linije dok vaš fajl ima <literal>CR-LF</literal> kraj linije. TortoiseSVN će normalno sakriti ove razlike automatski najpre analizirajući OSNOVNI fajl da prošire ključne reči i kraj linije pre izvršenja diff operacije. Međutim, ovo može uzeti puno vremena sa velikim fajlovima. Ako <guilabel>Konvertuj fajlove kada se pravi razlika prema OSNOVI</guilabel> je otčekirano zatim TortoiseSVN će preskočiti preprocesiranje fajlova.

note: (para)
en: You can also specify a different diff tool to use on Subversion properties. Since these tend to be short simple text strings, you may want to use a simpler more compact viewer.
target: Možete takođe specifirati različit diff alat da koriste Subverzione osobine. Kako ovo teži da bude skraćen jednostavan tekst string, vi možete želeti jednostavno mnogo kompaktniji pregled.

note: (para)
en: If you have configured an alternate diff tool, you can access TortoiseMerge <emphasis>and</emphasis> the third party tool from the context menus. <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Diff</guimenuitem></menuchoice> uses the primary diff tool, and <keycap>Shift</keycap>+ <menuchoice><guimenu>Context menu</guimenu><guimenuitem>Diff</guimenuitem></menuchoice> uses the secondary diff tool.
target: Ako ste konfigurisali alternativni diff alat, možete pristupiti TortoiseMerge <emphasis>i</emphasis> alatu trećeg lica iz kontekst menija. <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Diff</guimenuitem></menuchoice>  koristi primarni diff alt, a <keycap>Shift</keycap>+ <menuchoice><guimenu>Kontekst meni</guimenu><guimenuitem>Diff</guimenuitem></menuchoice> koristi sekundarni diff alat.

note: (title)
en: Merge Tool
target: Alat spajanja

note: (para)
en: the original file without your or the others changes
target: Originalni fajl bez vaših ili drugih izmena

note: (para)
en: your own file, with your changes
target: vaš lični fajl, sa vašim izmenama

note: (para)
en: the file as it is in the repository
target: fajl kakav je u spremištu

note: (para)
en: The window title for the file in the repository
target: Vindouz naslov fajla u spremištu

note: (para)
en: the conflicted file, the result of the merge operation
target: fajl sa konfliktom, rezultat operacije sajanja

note: (para)
en: The window title for the merged file
target: Vindouz naslov za stopljen fajl

note: (para)
en: An external merge program used to resolve conflicted files. Parameter substitution is used in the same way as with the Diff Program. <placeholder-1/>
target: Eksterni program za stapanje koristi se da reši konfliktne fajlove. Parametar substitucije se koristi na isti način kao sa Diff Programom.  <placeholder-1/>

note: (para)
en: For example, with Perforce Merge: <screen>
    C:\Path-To\P4Merge.exe %base %theirs %mine %merged
    </screen> or with KDiff3: <screen>
    C:\Path-To\kdiff3.exe %base %mine %theirs -o %merged
        --L1 %bname --L2 %yname --L3 %tname
    </screen> or with Araxis: <screen>
    C:\Path-To\compare.exe /max /wait /3 /title1:%tname /title2:%bname
        /title3:%yname %theirs %base %mine %merged /a2
    </screen> or with WinMerge (2.8 or later): <screen>
    C:\Path-To\WinMerge.exe %merged
    </screen>
target: Na primer, sa Perforce Merge:  <screen>
    C:\Path-To\P4Merge.exe %base %theirs %mine %merged
    </screen> or with KDiff3: <screen>
    C:\Path-To\kdiff3.exe %base %mine %theirs -o %merged
        --L1 %bname --L2 %yname --L3 %tname
    </screen> or with Araxis: <screen>
    C:\Path-To\compare.exe /max /wait /3 /title1:%tname /title2:%bname
        /title3:%yname %theirs %base %mine %merged /a2
    </screen> or with WinMerge (2.8 or later): <screen>
    C:\Path-To\WinMerge.exe %merged
    </screen>

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

note: (title)
en: The Settings Dialog, Diff/Merge Advanced Dialog
target: Dijalog podešavanja, Razl/Stopi napredni dijalog

note: (para)
en: <placeholder-1/> In the advanced settings, you can define a different diff and merge program for every file extension. For instance you could associate Photoshop as the <quote>Diff</quote> Program for <filename>.jpg</filename> files :-) You can also associate the <literal>svn:mime-type</literal> property with a diff or merge program.
target: <placeholder-1/> U naprednom podešavanju, možete definisati različite diff i stopi programe za svaku ekstenziju fajla. Na primer možete pridružiti Fotošop kao <quote>Diff</quote>Program za <filename>.jpg</filename> fajlove :-) Takođe pridružite <literal>svn:mime-type</literal> osobinu sa diff ili stopi programom.

note: (para)
en: To associate using a file extension, you need to specify the extension. Use <literal>.bmp</literal> to describe Windows bitmap files. To associate using the <literal>svn:mime-type</literal> property, specify the mime type, including a slash, for example <literal>text/xml</literal>.
target: Da pridružite korišćenjem ekstenziju fajla, potrebno vam je da specificirate ekstenziju. Koristite <literal>.bmp</literal> da opišete Vindouz bitmap fajlove. Da pridružite <literal>svn:mime-type</literal> osobinu, specificirajte mime tip, uključujući kosu crtu, na primer <literal>text/xml</literal>.

note: (title)
en: Unified Diff Viewer
target: Objedinjeni Razl pregledač

note: (para)
en: A viewer program for unified-diff files (patch files). No parameters are required. The <guilabel>Default</guilabel> option is to check for a file association for <filename>.diff</filename> files, and then for <filename>.txt</filename> files. If you don't have a viewer for <filename>.diff</filename> files, you will most likely get NotePad.
target: Program pregledač za ujedinjen-diff fajlve 8fajlove zakrpa). Nisu parametri potrebni. <guilabel>Uobičajena</guilabel> opcija je da se čekira pridruživanje za <filename>.diff</filename> fajlove, i zatim za <filename>.txt</filename> fajlove. Ako nemate pregledač za <filename>.diff</filename> fajlove, možda će vam se dopasti NotePad.

note: (para)
en: The original Windows NotePad program does not behave well on files which do not have standard CR-LF line-endings. Since most unified diff files have pure LF line-endings, they do not view well in NotePad. However, you can download a free NotePad replacement <ulink url="http://www.flos-freeware.ch/notepad2.html"><citetitle>Notepad2</citetitle></ulink> which not only displays the line-endings correctly, but also colour codes the added and removed lines.
target: Originalni Vindouz NotePad program nije dobar za fajlove koji nemaju standardni CR-LF završetak-linija. Kako većina ujedinjeni diff fajlovi imaju čist   LF završetak-linije, oni se neće videti dobro u NotePad. Međutim, možete skinuti besplatnu zamenu NotePad <ulink url="http://www.flos-freeware.ch/notepad2.html"><citetitle>Notepad2</citetitle></ulink> koji ne prikazuje samo kraj-linije korektno, već takođe bojama kodira dodate i uklonjene linije.

note: (title)
en: Saved Data Settings
target: Sčvani podaci podešavanje

note: (title)
en: The Settings Dialog, Saved Data Page
target: Dijalog podešavanja, Sačuvani podaci stranica

note: (para)
en: <placeholder-1/> For your convenience, TortoiseSVN saves many of the settings you use, and remembers where you have been lately. If you want to clear out that cache of data, you can do it here.
target: <placeholder-1/> Za vašu udobnost, TortoiseSVN čuva većinu podešavanja koje koristite, i pamti pređašnje stanje. Ako želite da obrišete keš podataka to možete uraditi ovde.

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

note: (para)
en: Whenever you checkout a working copy, merge changes or use the repository browser, TortoiseSVN keeps a record of recently used URLs and offers them in a combo box. Sometimes that list gets cluttered with outdated URLs so it is useful to flush it out periodically.
target: Kadgod preuzmete radnu kopiju, stopite izmene ili koristite pretraživač spremišta, TortoiseSVN čuva zapis o skorašnje korišćenom URL i nudi ga u kombo boksu. Ponekad taj list postaje blokiran sa zastarelim URL tako da je korisno da se periodično osveži.

note: (para)
en: If you want to remove a single item from one of the combo boxes you can do that in-place. Just click on the arrow to drop the combo box down, move the mouse over the item you want to remove and type <keycap>Shift+Del</keycap>.
target: Ako želite da uklonite pojedinačnu stavku iz jednog od kombo boksova možete to uraditi na licu mesta. Samo kliknite na strelicu da svučete kombo boks, pomerite miša na stavku koju želite da uklonite i otkucajte <keycap>Shift+Del</keycap>.

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

note: (para)
en: TortoiseSVN stores recent commit log messages that you enter. These are stored per repository, so if you access many repositories this list can grow quite large.
target: TortoiseSVN čuva skorašnje dnevnik poruke urezivanja koje ste uneli. One su sačuvane u spremištu, tako da ako pristupate ka više spremišta ova lista može porasti jako mnogo.

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

note: (para)
en: TortoiseSVN caches log messages fetched by the Show Log dialog to save time when you next show the log. If someone else edits a log message and you already have that message cached, you will not see the change until you clear the cache. Log message caching is enabled on the <guilabel>Log Cache</guilabel> tab.
target: TortoiseSVN kešira dnevnik poruke nađene u Prikaži Dnevnik dijalogu da sačuva vreme kada sledeći put prikazijete dnevnik. Ako još neko uređuje dnevnik poruka i vi takođe imate keširanu poruku, nećete  videti izmenu sve dik ne obrišete keš. Dnevnik poruka keširanje je omogućeno na <guilabel>Dnevnik Keš</guilabel> tab.

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

note: (para)
en: Many dialogs remember the size and screen position that you last used.
target: Mnogi dijalozi pamte veličinu i poziciju ekrana koji ste zadnji put koristili.

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

note: (para)
en: When you authenticate with a Subversion server, the username and password are cached locally so you don't have to keep entering them. You may want to clear this for security reasons, or because you want to access the repository under a different username ... does John know you are using his PC?
target: Kada se autentifikujete na Subverzioni server, korisničko ime i lozinka se keširaju lokalno tako da ne morate da ih unosite. Možete želeti da obrišete ovo iz sigurnosnih razloga, ili zato što želite da pristupite spremištu pod drugim korisničkim imenom ... da li DŽon zna da vi koristite njegov PC?

note: (para)
en: If you want to clear authentication data for one particular server only, read <xref linkend="tsvn-dug-general-auth"/> for instructions on how to find the cached data.
target: Ako želite da obrišete autentifikacione podatke samo za jedan poseban server, pročitajte <xref linkend="tsvn-dug-general-auth"/> za instrukcije kako da nađete keširane podatke.

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

note: (para)
en: TortoiseSVN keeps a log of everything written to its progress dialogs. This can be useful when, for example, you want to check what happened in a recent update command.
target: TortoiseSVN čuva dnevnik svega napisanog u progres dijalogu. Ovo može biti korisno kada, na primer, želite da proverite šta se dešava u skoroj komandi ažuriranja.

note: (para)
en: The log file is limited in length and when it grows too big the oldest content is discarded. By default 4000 lines are kept, but you can customize that number.
target: Dnevnik fajl je ograničene dužine i kada poraste mnogo veliki stariji sadržaj se odbacuje. Uobičajeno je da se 4000 linija čuva, ali možete podesiti taj broj.

note: (para)
en: From here you can view the log file content, and also clear it.
target: Odavde možete videti sadržaj dnevnik fajla, i takođe ga obrisati.

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

note: (primary)
en: log cache
target: keš dnevnika

note: (title)
en: The Settings Dialog, Log Cache Page
target: Dijalog podešavanja, Keš dnevnika stranica

note: (para)
en: <placeholder-1/> This dialog allows you to configure the log caching feature of TortoiseSVN, which retains a local copy of log messages and changed paths to avoid time-consuming downloads from the server. Using the log cache can dramatically speed up the log dialog and the revision graph. Another useful feature is that the log messages can still be accessed when offline.
target: <placeholder-1/>  Ovaj dijalog vam omogućava da konfigurišete dnevnik keš osobine TortoiseSVN, koje čuvaju lokalnu kopiju dnebnik poruka i izmenjenih putanja da se izbegne vremenski-zahtevno skidanje sa servera. Koristeći dnevnik keš može dramatično ubrzati dnevnik dijalog i revizioni graf. Sledeća korisna osobina je da dnevnik poruka može biti kontaktiran kada niste povezani.

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

note: (para)
en: Enables log caching whenever log data is requested. If checked, data will be retrieved from the cache when available, and any messages not in the cache will be retrieved from the server and added to the cache.
target: Omogućava dnevnik keširanje kadgod su dnevnik podaci zatraženi. Ako je proveren, podaci će biti vraćeni iz keša ako su dostupni, i ako bilo koja poruka nije u kešu biće uzeta sa servera i dodata kešu.

note: (para)
en: If caching is disabled, data will always be retrieved directly from the server and not stored locally.
target: Ako je keširanje onemogućeno, podaci će uvek biti uzeti direktno sa servera i neće biti sačuvano lokalno.

note: (term)
en: If the repository cannot be contacted
target: Ako spremište ne može biti spojeno

note: (para)
en: If you are working offline, or if the repository server is down, the log cache can still be used to supply log messages already held in the cache. Of course the cache may not be up-to-date, so there are options to allow you to select whether this feature should be used.
target: Ako radite van linije, ili ako je spremište palo, dnevnik keš može još biti korišćen da snabde dnevnik poruke koje se već drže u kešu. Svakako keš ne mora biti ažuran, tako postoje opcije da dozvole da izaberete da li treba ovu osobinu da koristite.

note: (para)
en: When log data is being taken from the cache without contacting the server, the dialog using those message will show the offline state in its title bar.
target: Kada se dnevnik podaci uzmu iz keša bez kontaktiranja servera, dijalog koji koristi te poruke će prikazati isključeno stanje na naslovnom pultu.

note: (term)
en: Timeout before updating the HEAD revision
target: Isteklo vreme pre ažuriranja GLAVNE revizije

note: (para)
en: When you invoke the log dialog you will normally want to contact the server to check for any newer log messages. If the timeout set here is non-zero then the server will only be contacted when the timeout has elapsed since the last time contact. This can reduce server round-trips if you open the log dialog frequently and the server is slow, but the data shown may not be completely up-to-date. If you want to use this feature we suggest using a value of 300 (5 minutes) as a compromise.
target: Kada pozovete dnevnik dijalog normalno ćete želeti da kontaktirate server da proverite za neku novu dnevnik poruku. Ako je postavljeno granično vreme veće od nule server će samo biti kontaktiran kada prođe ograničeno vreme od zadnjeg vremena kontakta. Ovo može redukovati serverov obilazak ako otvarate dnevnik dijalog često a server je spor, ali prikazani podaci ne moraju biti kompletno ažurirani. Ako želite da koristite ovu osobinu preporučujemo vam vrednost 300 (5 minuta) kao kompromis.

note: (para)
en: Below the settings you can see a list of the repositories that are cached locally, and the space used for the cache. If you select one of the repositories you can then use the buttons underneath.
target: Ispod podešavanja možete videti listu spremišta lokalno keširanih, i prostor korišćen za keš. Ako izaberete jedno od spremišta možete tada koristiti skrivene dugmiće.

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

note: (title)
en: The Settings Dialog, Log Cache Statistics
target: Dijalog podešavanja, Keš dnevnika statistika

note: (para)
en: The amount of memory required to service this cache.
target: Iznos memorije potrebne za opsluživanje keša

note: (para)
en: The amount of disk space used for the cache. Data is compressed, so disk usage is generally fairly modest.
target: Iznos prostora na disku korišćen za keš. Podaci su komprimovani, tako da je korišćenje diska generalno sasvim skromno.

note: (term)
en: Connection
target: Veza

note: (para)
en: Shows whether the repository was available last time the cache was used.
target: Prikazuje da li je spremište dostupno zadnji put kada je keš korišćen

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: (para)
en: The last time we requested the HEAD revision from the server.
target: Poslednje vreme zahteva GLAVNE revizije sa servera.

note: (term)
en: Authors
target: Autori

note: (para)
en: The number of different authors with messages recorded in the cache.
target: Broj različitih autora sa porukama zabeleženim u kešu.

note: (term)
en: Paths
target: Putanje

note: (para)
en: The number of paths listed, as you would see using <literal>svn log -v</literal>.
target: Broj putanja izlistanih, kao što možete videti koristeći <literal>svn log -v</literal>.

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

note: (para)
en: The number of revision ranges which we have not fetched, simply because they haven't been requested. This is a measure of the number of holes in the cache.
target: Broj opsega revizija koji nisu nađeni, jednostavno zato zato što nisu traženi.

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

note: (para)
en: The highest revision number stored in the cache.
target: Najviši revizioni broj smešten u keš.

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

note: (para)
en: The number of revisions stored in the cache. This is another measure of cache completeness.
target: Broj revizija sačuvanih u kešu. Ovo je druga mera kompletnosti keša.

note: (para)
en: <placeholder-1/> Click on the <guibutton>Details</guibutton> button to see detailed statistics for a particular cache. Many of the fields shown here are mainly of interest to the developers of TortoiseSVN, so they are not all described in detail. <placeholder-2/>
target: <placeholder-1/> Kliknite na <guibutton>Detalji</guibutton> dugme da vidite detaljnu statistiku za partikularni keš. Mnoga od polja prikazana ovde su uglavnom od onteresa za razvojni tim TortoiseSVN, tako da svi nisu opisani dataljno.<placeholder-2/>

note: (para)
en: Click on the <guibutton>Update</guibutton> to completely refresh the cache and fill in any holes. For a large repository this could be very time consuming, but useful if you are about to go offline and want the best available cache.
target: Kliknite na <guibutton>Ažuriraj</guibutton> da kompletirate osvežavanje keša i popunite nek praznine. Za velika spremišta ovo će uzeti mnogo vremena, ali je korisno ako ako nameravate da radite bez veze i želite potpuno dostupan keš.

note: (para)
en: Click on the <guibutton>Export</guibutton> button to export the entire cache as a set of CSV files. This could be useful if you want to process the log data using an external program, although it is mainly useful to the developers.
target: Kliknite na <guibutton>Izvezi</guibutton> dugme da izvezete ceo keš kao skup CVS fajlova. Ovo bi bilo korisno ako želite da procesirate dnevnik podataka koristeći spoljašnji program, takođe to je uglavnom korisno razvojnom timu.

note: (para)
en: Click on <guibutton>Delete</guibutton> to remove all cached data for the selected repositories. This does not disable caching for the repository so the next time you request log data, a new cache will be created.
target: Kliknite na  <guibutton>Obriši</guibutton> da uklonite sve keširane podatke za izabrno spremište. Ovo ne onemogućava keširanje za spremište tako da sledeće put kada tražite podatke dnevnika, kreiraće se novi keš.

note: (title)
en: Client Side Hook Scripts
target: Zakačiv skript klijentske strane

note: (primary)
en: client hooks
target: klijentska zakačaljka

note: (title)
en: The Settings Dialog, Hook Scripts Page
target: Dijalog podešavanja, Zakačiv skript stranica

note: (para)
en: <placeholder-1/> This dialog allows you to set up hook scripts which will be executed automatically when certain Subversion actions are performed. As opposed to the hook scripts explained in <xref linkend="tsvn-repository-hooks"/>, these scripts are executed locally on the client.
target: <placeholder-1/> Ovaj dijalog omogućava da podesite zakačive skripte koje će se izvršiti automatski kada se izvesne Subverzione akcije izvršavaju. Suprotno zakačivim skriptama objašnjenim u <xref linkend="tsvn-repository-hooks"/>, ove skripte se izvršavaju lokalno na klijentu.

note: (para)
en: One application for such hooks might be to call a program like <literal>SubWCRev.exe</literal> to update version numbers after a commit, and perhaps to trigger a rebuild.
target: Jedna aplikacija za takve zakačaljke može biti pozivanje programa kao <literal>SubWCRev.exe</literal> da se ažurira broj verzije posle urezivanja, i možda da se pokrene reizrada.

note: (para)
en: For various security and implementation reasons, hook scripts are defined locally on a machine, rather than as project properties. You define what happens, no matter what someone else commits to the repository. Of course you can always choose to call a script which is itself under version control.
target: Zbog različitih sigurnosnih i primenljivih razloga, zakačive skripte su definisane lokalno na mašini, radije nego osobine projekta. Definišite šta će se desiti, nije važno što još neko urezije u spremište. Svakako uvek možete izabrati da zovete skript koji je sam pod kontrolom verzija.

note: (title)
en: The Settings Dialog, Configure Hook Scripts
target: Dijalog podešavanja, Konfiguracija zakačivog skripta

note: (para)
en: <placeholder-1/> To add a new hook script, simply click <guibutton>Add</guibutton> and fill in the details.
target: <placeholder-1/> Da bi se dodala zakačiva skripta, jednostavno kliknite <guibutton>Dodaj</guibutton> i popunite detalje.

note: (term)
en: Start-commit
target: Start-urezivanja

note: (para)
en: Called before the commit dialog is shown. You might want to use this if the hook modifies a versioned file and affects the list of files that need to be committed and/or commit message.
target: Pozvan pre nego se pojavi dijalog urezivanja. Možete žieleti da koristite ovo ako zakačaljke menjaju verzionisane fajlove i utiču na listu fajlova koji zahtevaju da budu urezani i/ili poruku urezivanja.

note: (term)
en: Pre-commit
target: Pre-urezivanje

note: (para)
en: Called after the user clicks <guibutton>OK</guibutton> in the commit dialog, and before the actual commit begins.
target: Pozvan posle korisnikovof klika na <guibutton>OK</guibutton> u dijalogu urezivanja, i pre nego počne aktuelno urezivanje.

note: (term)
en: Post-commit
target: Post-urezivanje

note: (para)
en: Called after the commit finishes (whether successful or not).
target: Poziva se posle završetka urezivanja (bilo da je uspešno ili ne).

note: (term)
en: Start-update
target: Start-ažuriranja

note: (para)
en: Called before the update-to-revision dialog is shown.
target: Pozivan pre nego je prikazan ažuriraj-do-revizije  dijalog.

note: (term)
en: Pre-update
target: Pre-ažuriraj

note: (para)
en: Called before the actual Subversion update begins.
target: Pozivana pre nego aktuelno Subverzono ažuriranje počne.

note: (term)
en: Post-update
target: Post-ažuriranje

note: (para)
en: Called after the update finishes (whether successful or not).
target: Pozivano posle završetka ažuriranja (bilo uspešno ili ne).

note: (para)
en: There are currently six types of hook script available <placeholder-1/>
target: Postoji tekućih šest tipova zakačivih skripti dostupan <placeholder-1/>

note: (para)
en: A hook is defined for a particular working copy path. You only need to specify the top level path; if you perform an operation in a sub-folder, TortoiseSVN will automatically search upwards for a matching path.
target: Zakačaljka je definisana za posebnu radnu kopiju. Samo vam je potrebno da odredite putalju vršnog nivoa; ako izvršite operaciju u sub-imeniku, TortoiseSVN će automatski tražiti prema traženoj putanji.

note: (para)
en: Next you must specify the command line to execute, starting with the path to the hook script or executable. This could be a batch file, an executable file or any other file which has a valid windows file association, eg. a perl script.
target: Sledeće morate specificirati komandnu liniju da izvršiti, poćevši sa putaljom ka zakačivoj skripti ili izvršnom programu. Ovo bi mogao biti beč fajl, izvršni fajl ili bilo koji fajl koji ima isparvan prozor pridruživanja, npr. perl skript.

note: (para)
en: The command line includes several parameters which get filled in by TortoiseSVN. The parameters passed depend upon which hook is called. Each hook has its own parameters which are passed in the following order: <placeholder-1/>
target: Komandna linija uključuje izvesne parametre koji su popunjeni sa TortoiseSVN. Prošli parametri zavise od toga koja zakačaljka je pozvana. Svaka zakačaljka ima svoje lične parametre koji prolaze u sledećem redosledu: <placeholder-1/>

note: (para)
en: A path to a temporary file which contains all the paths for which the operation was started. Each path is on a separate line in the temp file.
target: Putanja ka privremenom fajlu koji sadrži sve putanje za koje operacija počinje. Svaka putanja je na odvojenoj liniji u temp fajlu.

note: (para)
en: The depth with which the commit/update is done.
target: Dubina sa kojom je urezivanje/ažuriranje urađeno

note: (literal)
en: svn_depth_unknown
target: svn_dubina_nepoznata

note: (literal)
en: svn_depth_exclude
target: svn_dubina_isključena

note: (literal)
en: svn_depth_empty
target: svn_dubina_prazna

note: (literal)
en: svn_depth_files
target: svn_dubina_fajlova

note: (literal)
en: svn_depth_immediates
target: svn_dubina_trenutni

note: (literal)
en: svn_depth_infinity
target: svn_dubina_beskonačno

note: (para)
en: Possible values are: <placeholder-1/>
target: Moguće vrednosti su: <placeholder-1/>

note: (para)
en: Path to a file containing the log message for the commit. The file contains the text in UTF-8 encoding. After successful execution of the start-commit hook, the log message is read back, giving the hook a chance to modify it.
target: Putanja ka fajlu koji sadrži dnevnik poruke za urezivanje. Fajl sadrži tekst u UTF-8 kodiranju. Posle uspešnog izvršenja početak-urezivanja zakačaljke, dnevnik poruka je ponovo pročitan, dajući zakačaljki šansu da ga izmeni.

note: (para)
en: The repository revision to which the update should be done or after a commit completes.
target: Revizija spremišta za koju bi ažuriranje bilo dato ili se urezivanje kompletiralo.

note: (para)
en: Path to a file containing the error message. If there was no error, the file will be empty.
target: Putanja ka fajlu koji sadrži poruku greške. Ako nema greške, fajl će biti prazan.

note: (para)
en: The current working directory with which the script is run. This is set to the common root directory of all affected paths.
target: Tekući radni imenik sa koji skript radi. Ovo je skup ka zajdničkom korenu imenika svih odgovarajućih piutanja.

note: (para)
en: The meaning of each of these parameters is described here: <placeholder-1/>
target: Značenje svakog od ovih parametara opisan je ovde: <placeholder-1/>

note: (para)
en: Note that although we have given these parameters names for convenience, you do not have to refer to those names in the hook settings. All parameters listed for a particular hook are always passed, whether you want them or not ;-)
target: Primetimo takođe da imamo data imena tih parametarakonvencionalno, ne možete se pozvati na ta imena u podešavanju zakačaljki. Svi izlistani parametri za pojedinačne zakačaljke su uvek prošli, bez obzira da li ih želite ili ne  ;-)

note: (para)
en: If you want the Subversion operation to hold off until the hook has completed, check <guilabel>Wait for the script to finish</guilabel>.
target: Ako želite da Subervezione operacije drže isključeno sve dok se zakačaljka kompletira, proverite <guilabel>Čekajte dok skript završi</guilabel>.

note: (para)
en: Normally you will want to hide ugly DOS boxes when the script runs, so <guilabel>Hide the script while running</guilabel> is checked by default.
target: Normalno želte da sakrijete ružne DOS boksove dok skript radi, tako <guilabel>Sakri skript dok radi</guilabel> je čekiran uobičajeno.

note: (para)
en: Sample client hook scripts can be found in the <literal>contrib</literal> folder in the <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/hook-scripts"><citetitle>TortoiseSVN repository</citetitle></ulink>. (<xref linkend="tsvn-preface-source"/> explains how to access the repository).
target: Jednostavna klijent zakačaljka skripta može biti nađeno u  <literal>kontrib</literal> imeniku u <ulink url="http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/hook-scripts"><citetitle>TortoiseSVN spremište</citetitle></ulink>. (<xref linkend="tsvn-preface-source"/> objašljava kako pristupiti spremištu).

note: (title)
en: Issue Tracker Integration
target: Integracija problem tragača

note: (para)
en: TortoiseSVN can use a COM plugin to query issue trackers when in the commit dialog. The use of such plugins is described in <xref linkend="tsvn-dug-bugtracker-ref"/>. If your system administrator has provided you with a plugin, which you have already installed and registered, this is the place to specify how it integrates with your working copy.
target: TortoiseSVN može koristiti COM plagin da nađe problem tragač kada je u dijalogu urezivanja. Korišćenje takvih plagina opisano je u  <xref linkend="tsvn-dug-bugtracker-ref"/>. Ako je sistem administator snabdeo plagin koji ste već instalirali i registrovali, ovo je mesto da se specificira kako se integriše sa vašom radnom kopijom.

note: (title)
en: The Settings Dialog, Issue Tracker Integration Page
target: Dijalog podešavanja, Stranica integracije problem tragača

note: (para)
en: <placeholder-1/> Click on <guibutton>Add...</guibutton> to use the plugin with a particular working copy. Here you can specify the working copy path, choose which plugin to use from a drop down list of all registered issue tracker plugins, and any parameters to pass. The parameters will be specific to the plugin, but might include your user name on the issue tracker so that the plugin can query for issues which are assigned to you.
target: <placeholder-1/> Kliknite na <guibutton>Dodaj...</guibutton> da koristite plagin sa posebnom radnom kopijom. Ovde možete specificirati putanju radne kopije, izaberite koji plagin da se koristi iz padajuće liste svih registrovanih problem tragača, i neke parametre da doda. Parametri će biti specificirani plaginu, ali mogu uključiti vaše korisničko ime za problem tragač  tako da plagin može tražiti probleme koji su vama ozančeni.

note: (para)
en: This property specifies the COM UUID of the IBugTraqProvider, for example <literal>{91974081-2DC7-4FB1-B3BE-0DE1C8D6CE4E}</literal>.
target: Ovo osobine specificiraju COM UUID od IBugTraqProvider, na primer <literal>{91974081-2DC7-4FB1-B3BE-0DE1C8D6CE4E}</literal>.

note: (para)
en: This property specifies the parameters passed to the IBugTraqProvider.
target: Ova osobina određuje parametre poslate u  IBugTraqProvider.

note: (para)
en: If you want all users to use the same COM plugin for your project, you can specify the plugin also with the properties <literal>bugtraq:provideruuid</literal> and <literal>bugtraq:providerparams</literal>. <placeholder-1/> Please check the documentation of your IBugTraqProvider plugin to find out what to specify in these two properties.
target: Ako želite da svi korisnici koriste iste COM plagin za vaš projekat, možete specificirati plagin takođe sa osobinama <literal>bugtraq:provideruuid</literal>i <literal>bugtraq:providerparams</literal>. <placeholder-1/> Molimo proverite dokumentaciju vašeg  IBugTraqProvider plagina da nađete šta specificirati u ove dve osobine.

note: (title)
en: TortoiseBlame Settings
target: TortozBlame podešavanje

note: (title)
en: The Settings Dialog, TortoiseBlame Page
target: Dijalog podešavanja, TortozBlame stranica

note: (para)
en: <placeholder-1/> The settings used by TortoiseBlame are controlled from the main context menu, not directly with TortoiseBlame itself.
target: <placeholder-1/> Podešavanja korišćena sa TortoiseBlame su kontrolisani iz glavnog kontekst menija, ne direktno sa samim TortoiseBlame.

note: (term)
en: Colors
target: Boje

note: (para)
en: TortoiseBlame can use the background colour to indicate the age of lines in a file. You set the endpoints by specifying the colours for the newest and oldest revisions, and TortoiseBlame uses a linear interpolation between these colours according to the repository revision indicated for each line.
target: TortoiseBlame može koristiti boju osnove da indicira starost linija u fajlu. Podesite krajnje tačke specificirajući boje za novije i starije revizije, i TortoiseBlame koristi linearnu interpolaciju između ovih boja u skladu revizijom spremišta označenu za svaku liniju.

note: (term)
en: Font
target: Pismo

note: (para)
en: You can select the font used to display the text, and the point size to use. This applies both to the file content, and to the author and revision information shown in the left pane.
target: Možete izabrati pismo koje se koristi da se prikaže tekst, i njegovu veličinu. Ovo se primenjuje na sadržaj fajla, i autore i revizione informacije prikazane u levom panelu.

note: (term)
en: Tabs
target: Tabovi

note: (para)
en: Defines how many spaces to use for expansion when a tab character is found in the file content.
target: Definiše koliko razmaka koristiti za ekspanziju kada se tab karakter naže u sadržaju fajla.

note: (title)
en: Registry Settings
target: Podešavanje registra

note: (primary)
en: registry
target: registri

note: (para)
en: A few infrequently used settings are available only by editing the registry directly.
target: Sasvim retko korišćena podešavanja su omogućena samo uređivanjem registra direktno.

note: (para)
en: You can specify a different location for the Subversion configuration file using registry location <literal>HKCU\Software\TortoiseSVN\ConfigDir</literal>. This will affect all TortoiseSVN operations.
target: Možete specificirati različitu lokaciju za Subverzioni konfiguracioni fajl koristeći registri lokaciju <literal>HKCU\Software\TortoiseSVN\ConfigDir</literal>. Ovo će uticati na sve TortoiseSVN operacije.

note: (term)
en: Cache tray icon
target: Ikona keš kutije

note: (para)
en: To add a cache tray icon for the TSVNCache program, create a <literal>DWORD</literal> key with a value of 1 at <literal>HKCU\Software\TortoiseSVN\CacheTrayIcon</literal>. This is really only useful for developers as it allows you to terminate the program gracefully.
target: Da bi dodali keš ikonu za TSVNCashe program, kreirajte <literal>DWORD</literal> taster sa vrednošću 1 na <literal>HKCU\Software\TortoiseSVN\CacheTrayIcon</literal>. Ovo je stvarno korisno samo za razvojni tim kada vam ljubazno dozvoljavaju da završite program.

note: (term)
en: Filenames without extensions in auto-completion list
target: Fajlime bez ekstenzije u auto-kompletirajućoj listi.

note: (para)
en: The auto-completion list shown in the commit message editor displays the names of files listed for commit. To also include these names with extensions removed, create a <literal>DWORD</literal> key with a value of 1 at <literal>HKCU\Software\TortoiseSVN\AutocompleteRemovesExtensions</literal>.
target: Auto-kompletirajuća lista prikazana u editoru poruka urezivanja prikazuje imena fajlova izlistanih za urezivanje. Takođe obuhvata  ova imena sa uklonjenom ekstenzijom, kreirajte  <literal>DWORD</literal> tater sa vrednošću 1 na  literal>HKCU\Software\TortoiseSVN\AutocompleteRemovesExtensions</literal>.

note: (term)
en: Explorer columns everywhere
target: Eksplorer kolumne bilo gde

note: (para)
en: The extra columns the TortoiseSVN adds to the details view in Windows Explorer are normally only active in a working copy. If you want those to be accessible everywhere, not just in working copies, create a <literal>DWORD</literal> key with a value of 1 at <literal>HKCU\Software\TortoiseSVN\ColumnsEveryWhere</literal>.
target: Dodatne kolone TortoiseSVN koje dodaje detaljnom pregledu u Vindouz Eksploreru aktivne su samo u radnoj kopiji. Ako želite da budu dostupne  bilo gde, ne samo u radnoj kopiji, kreirajte  <literal>DWORD</literal> taster sa vrednošću 1 u <literal>HKCU\Software\TortoiseSVN\ColumnsEveryWhere</literal>.

note: (term)
en: Merge log separator
target: Stopi separator dnevnika

note: (para)
en: When you merge revisions from another branch, and merge tracking information is available, the log messages from the revisions you merge will be collected to make up a commit log message. A pre-defined string is used to separate the individual log messages of the merged revisions. If you prefer, you can create a <literal>SZ</literal> key at <literal>HKCU\Software\TortoiseSVN\MergeLogSeparator</literal> containing a separator string of your choice.
target: Kada stapate revizije iz druge grane, i informacije praćenja stapanja su dostupne, dnevnik poruke iz revizija koje stapate se sakupljaju da naprave dnevnik poruku urezivanja. Predefinisani string se koristi da odvoji pojedinačne dnevnik poruke stopljenih revizija. Ako više volite, možete kreirati <literal>SZ</literal> taster u <literal>HKCU\Software\TortoiseSVN\MergeLogSeparator</literal>koji sadrži separator string po vašem izboru.

note: (term)
en: Always blame changes with TortoiseMerge
target: Uvek okrivi izmene sa TortoiseMerge

note: (para)
en: TortoiseSVN allows you to assign external diff viewer. Most such viewers, however, are not suited for change blaming (<xref linkend="tsvn-dug-blame-diffs"/>), so you might wish to fall back to TortoiseMerge in this case. To do so, create a <literal>DWORD</literal> key with a value of 1 at <literal>HKCU\Software\TortoiseSVN\DiffBlamesWithTortoiseMerge</literal>.
target: TortoiseSVN dopušta da označite spoljašnji diff pregledač. Većina takvih pregledača, međutim, ne odgovara za izmenu okrivljavanja  (<xref linkend="tsvn-dug-blame-diffs"/>), tako da možete želeti da se vratite TortoiseMerge u tom slučaju. Da biste to uradili  kreirajte  <literal>DWORD</literal>  taster sa vrednošću 1 u <literal>HKCU\Software\TortoiseSVN\DiffBlamesWithTortoiseMerge</literal>.

note: (term)
en: Current revision highlighting for folders in log dialog
target: Tekuće revizijsko osvetljavanje za imenike u dnevnik dijalogu

note: (para)
en: The log dialog highlights the current working copy revision when the log is shown for a file. To do the same thing for a folder requires a working copy crawl, which can be a slow operation for large working copies. If you want to enable this feature you must create a <literal>DWORD</literal> registry key with value 1 at <literal>HKCU\Software\TortoiseSVN\RecursiveLogRev</literal>.
target: Dnevnik dijalog osvetljava tekuću reviziju radne kopije kada je prikazan dnevnik fajla. Da se uradi ista stvar za imenik zahteva se puzanje kroz radnu kopiju, što može biti spora operacija za velike radne kopije. Ako želite da omogućite ovu osobinu morate kreirati <literal>DWORD</literal> registar taster sa vrednošću 1 u <literal>HKCU\Software\TortoiseSVN\RecursiveLogRev</literal>.

note: (title)
en: Subversion Working Folders
target: Subverzioni Radni Imenici

note: (primary)
en: .svn folder
target: .svn imenik

note: (primary)
en: _svn folder
target: _svn imenik

note: (para)
en: VS.NET 2003 when used with web projects can't handle the <literal>.svn</literal> folders that Subversion uses to store its internal information. This is not a bug in Subversion. The bug is in VS.NET 2003 and the frontpage extensions it uses.
target: VS.NET 2003 kada se koristi sa veb projektima ne može rukovati sa <literal>.svn</literal> imenicima koje Subverzija koristi da smesti interne informacije. Ovo nije bag u Subverziji. Bag je u VS.NET 2003 i ulazne stranice koje koristi kao proširenje.

note: (para)
en: Note that the bug is fixed in VS2005 and later versions.
target: Primetimo da je bag fiksiran u VS2005 i daljim verzijama.

note: (para)
en: As of Version 1.3.0 of Subversion and TortoiseSVN, you can set the environment variable <literal>SVN_ASP_DOT_NET_HACK</literal>. If that variable is set, then Subversion will use <literal>_svn</literal> folders instead of <literal>.svn</literal> folders. You must restart your shell for that environment variable to take effect. Normally that means rebooting your PC. To make this easier, you can now do this from the general settings page using a simple checkbox - refer to <xref linkend="tsvn-dug-settings-main"/>.
target: Od  Verzije 1.3.0 Subverzije i TortoiseSVN, možete podesiti promenljivu okruženja <literal>SVN_ASP_DOT_NET_HACK</literal>. Ako je ta promenljiva podešena Subverzija će koristiti <literal>_svn</literal> imenik umesto <literal>.svn</literal> imenik. Morate restartovati vašu školjku za tu promenljivu okoline da postane efektna. Normalno to znači rebutovanje PC. Da se to olakša, možete sada uraditi to sa stranice generalnog podešavanja koristeći jednostavan čekboks - obratite se na <xref linkend="tsvn-dug-settings-main"/>.

note: (para)
en: For more information, and other ways to avoid this problem in the first place, check out the article about this in our <ulink url="http://tortoisesvn.net/aspdotnethack"><citetitle>FAQ</citetitle></ulink>.
target: Za više informacija, i druge načine da se izbegne ovaj problem na prvo mest, preuzmite naš članak  <ulink url="http://tortoisesvn.net/aspdotnethack"><citetitle>FAQ</citetitle></ulink>.

note: (title)
en: Final Step
target: Finalni korak

note: (title)
en: Donate!
target: Donirajte!

note: (para)
en: Even though TortoiseSVN and TortoiseMerge are free, you can support the developers by sending in patches and play an active role in the development. You can also help to cheer us up during the endless hours we spend in front of our computers.
target: Bez obzira što su TortoiseSVN i TortoiseMerge besplatni, možete pomoći razvojni tim slanjem zakrpa i igrati aktivnu ulogu u razvoju. Možete pomoći da nas ohrabrite u toku dugih sati koje trošimo ispred računara.

note: (para)
en: While working on TortoiseSVN we love to listen to music. And since we spend many hours on the project we need a <emphasis>lot</emphasis> of music. Therefore we have set up some wish-lists with our favourite music CDs and DVDs: <ulink url="http://tortoisesvn.tigris.org/donate.html"><citetitle>http://tortoisesvn.tigris.org/donate.html</citetitle></ulink> Please also have a look at the list of people who contributed to the project by sending in patches or translations.
target: Dok radimo na TortoiseSVN mi volimo da slušamo muziku. Kako trošimo mnogo vremena na projektu potrebno nam je <emphasis>mnogo</emphasis> muzike. Zbog toga smo napravili listu želja  sa muzikom koju volimo na CD ili DVD: <ulink url="http://tortoisesvn.tigris.org/donate.html"><citetitle>http://tortoisesvn.tigris.org/donate.html</citetitle></ulink> Molimo da takođe pogledate listu ljudi koji pomažu projektu slanjem zakrpa ili prevoda.

note: (title)
en: The SubWCRev Program
target: SubVCRev program

note: (primary)
en: version extraction
target: izdvajanje verzije

note: (primary)
en: SubWCRev
target: SubVCRev

note: (primary)
en: version number in files
target: broj verzije u fajlovima

note: (para)
en: SubWCRev is Windows console program which can be used to read the status of a Subversion working copy and optionally perform keyword substitution in a template file. This is often used as part of the build process as a means of incorporating working copy information into the object you are building. Typically it might be used to include the revision number in an <quote>About</quote> box.
target: SubWCRev je Vindouz konzolni program koji se može koristiti da se pročita status Subverzione radne kopije i omogući zamena ključnih reči u fajl modelu. Ovo se često koristi kao deo procesa izrade u značenju unošenja informacije radne kopije u objekat koji izrađujete. Tipično to može biti korišženo da se uključi revizioni broj u <quote>Opis programa</quote> boks.

note: (title)
en: The SubWCRev Command Line
target: SubVCRev komandna linija

note: (para)
en: SubWCRev reads the Subversion status of all files in a working copy, excluding externals by default. It records the highest commit revision number found, and the commit timestamp of that revision, It also records whether there are local modifications in the working copy, or mixed update revisions. The revision number, update revision range and modification status are displayed on stdout.
target: SubWCRev čita Subverzioni status svih fajlova u radnoj kopiji, izostavljajući spoljašnje uobičajeno. Zapisuje najveći nađen broj  urezane revizije, i vremensku oznaku urezivanja te revizije. Takođe zapisuje da li postoje lokalne izmene u radnoj kopiji, ili pomešano ažurirane revizije. Revizioni broj, opseg ažuriranja revizija i status izmena su prikazani na stdout.

note: (para)
en: SubWCRev.exe is called from the command line or a script, and is controlled using the command line parameters. <screen>
    SubWCRev WorkingCopyPath [SrcVersionFile DstVersionFile] [-nmdfe]
    </screen>
target: SubWCRev.exe je pozvan iz komandne linije ili skripta, i kontrolisan koristeći parametre komandne linije. <screen>
    SubWCRev WorkingCopyPath [SrcVersionFile DstVersionFile] [-nmdfe]
    </screen>

note: (para)
en: <literal>WorkingCopyPath</literal> is the path to the working copy being checked. You can only use SubWCRev on working copies, not directly on the repository. The path may be absolute or relative to the current working directory.
target: <literal>WorkingCopyPath</literal> je putanja do radne kopije koja se proverava. Možete samo koristiti SubWCRev na radnim kopijama, ne direktno na spremištu. Putanja može biti apsolutna ili relativna ka tekućem radnom imeniku.

note: (para)
en: If you want SubWCRev to perform keyword substitution, so that fields like repository revision and URL are saved to a text file, you need to supply a template file <literal>SrcVersionFile</literal> and an output file <literal>DstVersionFile</literal> which contains the substituted version of the template.
target: Ako želite SubWCRev da izvrši zamenu ključne reči, ta polja kao reviziju spremišta i URL se čuvaju u tekst fahlu, potrebno je da obezbedite model fajl <literal>SrcVersionFile</literal> i izlazni fajl <literal>DstVersionFile</literal> koji sadrže zamenjenu verziju modela.

note: (title)
en: List of available command line switches
target: Lista dostupnih prekidača komandne linije

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

note: (entry)
en: Description
target: Opis

note: (literal)
en: ERRORLEVEL 7
target: NIVOGREŠKE 7

note: (entry)
en: If this switch is given, SubWCRev will exit with <placeholder-1/> if the working copy contains local modifications. This may be used to prevent building with uncommitted changes present.
target: Ako je ovaj prekidač dat,  SubWCRev  će izaći sa <placeholder-1/> ako radna kopija sadrži lokalne izmene. Ovo može biti korišćeno da se predupredi izrada sa neurezanim izmenama koje su prisutne.

note: (literal)
en: ERRORLEVEL 8
target: NIVOGREŠKE 8

note: (entry)
en: If this switch is given, SubWCRev will exit with <placeholder-1/> if the working copy contains mixed revisions. This may be used to prevent building with a partially updated working copy.
target: Ako je ovaj prekidač dat, SubWCRev će izaći sa <placeholder-1/>  ako radna kopija sadrži pomešane revizije. Ovo  se može koristiti da se spreči izrada sa parcijalno ažuriranom radnom kopijom.

note: (literal)
en: ERRORLEVEL 9
target: NIVOGREŠKE 9

note: (entry)
en: If this switch is given, SubWCRev will exit with <placeholder-1/> if the destination file already exists.
target: Ako je ovaj prekidač dat, SubWCRev će izaći sa <placeholder-1/> ako destinacioni fajl već postoji.

note: (entry)
en: If this switch is given, SubWCRev will include the last-changed revision of folders. The default behaviour is to use only files when getting the revision numbers.
target: Ako je ovaj prekidač dat, SubWCRev će uključiti zadlju-izmenjenu reviziju imenika. Uobičajeno ponašanje je da se koriste samo fajlovi kada se uzimaju revizioni brojevi.

note: (entry)
en: If this switch is given, SubWCRev will examine directories which are included with <placeholder-1/>, but only if they are from the same repository. The default behaviour is to ignore externals.
target: Ako je ovaj prekidač dat,  SubWCRev će pregledati imenike koji su uključeni sa <placeholder-1/>, ali samo ako su iz istog spremišta. Uobičajeno ponašanje je da se zanemare eksternali.

note: (entry)
en: If this switch is given, SubWCRev will output the revision numbers in HEX.
target: Ako je ovaj prekidač dat,  SubWCRev će dati na izlazu revizione brojeve u HEKS.

note: (entry)
en: If this switch is given, SubWCRev will output the revision numbers in HEX, with '0X' prepended.
target: Ako je ovaj prekidač dat,  SubWCRev će dati na izlazu revizione brojeve u HEKS, sa '0X' ispred.

note: (para)
en: There are a number of optional switches which affect the way SubWCRev works. If you use more than one, they must be specified as a single group, eg. <literal>-nm</literal>, not <literal>-n -m</literal>. <placeholder-1/>
target: Postoji veliki broj opcionih prekidača koji utiču na način rada  SubWCRev. Ako koristite više od jednog on mora biti specificiran kao pojedinačna grupa, npr. <literal>-nm</literal>, ne <literal>-n -m</literal>. <placeholder-1/>

note: (title)
en: Keyword Substitution
target: Zamena ključnih reči

note: (entry)
en: Keyword
target: Ključna reč

note: (entry)
en: Replaced with the highest commit revision in the working copy.
target: Zamenjeno najvišom urezanom revizijom u radnoj kopiji.

note: (citetitle)
en: online reference
target: onlajn reference

note: (entry)
en: Replaced with the commit date/time of the highest commit revision. By default, international format is used: <placeholder-1/>. Alternatively, you can specify a custom format which will be used with <placeholder-2/>, for example: <placeholder-3/>. For a list of available formatting characters, look at the <ulink url="http://www.cppreference.com/stddate/strftime.html"><placeholder-4/></ulink>.
target: Zamenjeno sa datum/vreme urezivanja najviše urezane revizije. Uobičajeno, internacionalni format se koristi: <placeholder-1/>. Alternativno, možete specificirati običan format koji će se koristiti sa <placeholder-2/>, na primer: <placeholder-3/>. Za listu dostupnih karaktera za formatiranje pogledajte <ulink url="http://www.cppreference.com/stddate/strftime.html"><placeholder-4/></ulink>.

note: (entry)
en: Replaced with the current system date/time. This can be used to indicate the build time. Time formatting is as described above.
target: Zamenjeno sa tekućim sistemskim datum/vreme. Ovo se može koristiti da označi vreme izrade. Formatiranje vremena je opisano gore.

note: (entry)
en: Replaced with the update revision range in the working copy. If the working copy is in a consistent state, this will be a single revision. If the working copy contains mixed revisions, either due to being out of date, or due to a deliberate update-to-revision, then the range will be shown in the form 100:200
target: Zamenjeno sa opsegom ažuriranih revizija u radnoj kopiji. Ako je radna kopija u konzistentnom stanju ovo je pojedinačna revizija. Ako radna kopija sadrži mešane revizije, ili zbog toga što je zastarela, ili zato što planski ažurirana-ka-reviziji, onda će opseg biti prikazan u obliku  100:200

note: (literal)
en: TText
target: TTekst

note: (literal)
en: FText
target: FTekst

note: (entry)
en: <placeholder-1/> is replaced with <placeholder-2/> if there are mixed update revisions, or <placeholder-3/> if not.
target: <placeholder-1/> je zamenjen sa <placeholder-2/>  ako postoji pomešane ažurirane revizije, ili <placeholder-3/> ako ne.

note: (entry)
en: <placeholder-1/> is replaced with <placeholder-2/> if there are local modifications, or <placeholder-3/> if not.
target: <placeholder-1/> je zamenjeno sa <placeholder-2/> ako postoje lokalne izmene, ili <placeholder-3/> ako ne.

note: (entry)
en: Replaced with the repository URL of the working copy path passed to SubWCRev.
target: Zamenjeno sa spremišta URL putanje radne kopije poslate u SubWCRev.

note: (entry)
en: Replaced with the current time and date
target: Zamenjeno sa tekućim vremenom i datumom

note: (entry)
en: Replaced with the current time and date in standard format
target: Zamenjeno sa tekućim vremenom i datumom u standardnom formatu

note: (entry)
en: <placeholder-1/> is replaced with <placeholder-2/> if the entry is versioned, or <placeholder-3/> if not.
target: <placeholder-1/>je zamenjeno sa <placeholder-2/> ako je ulaz verzionisan, ili <placeholder-3/> ako nije.

note: (literal)
en: svn:needs-lock
target: svn:traži-ključ

note: (entry)
en: <placeholder-1/> is replaced with <placeholder-2/> if the entry has the <placeholder-3/> property set, or <placeholder-4/> if not.
target: <placeholder-1/>je zamenjeno sa <placeholder-2/> ako je ulaz ima<placeholder-3/> podešenu osobinu, ili <placeholder-4/> ako nema.

note: (entry)
en: <placeholder-1/> is replaced with <placeholder-2/> if the entry is locked, or <placeholder-3/> if not.
target: <placeholder-1/>je zamenjeno sa <placeholder-2/> ako je ulaz zaključan, ili <placeholder-3/> ako nije.

note: (entry)
en: Replaced with the lock date
target: Zamenjenom sa datum ključem

note: (entry)
en: Replaced with the name of the lock owner
target: Zamenjeno imenom vlasnika ključa

note: (entry)
en: Replaced with the comment of the lock
target: Zamenjeno komentarom ključa

note: (para)
en: If a source and destination files are supplied, SubWCRev copies source to destination, performing keyword substitution as follows: <placeholder-1/>
target: Ako su izvorni i odredišni fajlovi snabdeveni, SubWCRev kopira izvor u odredište, izvršavajući zamenu ključnih reči na sledeći način: <placeholder-1/>

note: (title)
en: Keyword Example
target: Primer ključne reči

note: (para)
en: The example below shows how keywords in a template file are substituted in the output file.
target: Sledeći primer prikazuje kako ključne reči u model fajlu budu zamenjene u izlazom fajlu.

note: (para)
en: After running <literal>SubWCRev.exe path\to\workingcopy testfile.tmpl testfile.txt</literal>, the output file <literal>testfile.txt</literal> would looks like this:
target: Posle izvršenja <literal>SubWCRev.exe path\to\workingcopy testfile.tmpl testfile.txt</literal>,izlazni fajl <literal>testfile.txt</literal> će izgledati kao ovo:

note: (para)
en: A file like this will be included in the build so you would expect it to be versioned. Be sure to version the template file, not the generated file, otherwise each time you regenerate the version file you need to commit the change, which in turn means the version file needs to be updated.
target: Ovakav fajl će biti uključen u izradu tako da možete očekivati da je verzionisan. Budite sigurni da verzionišete model fajl, ne generisani fajl, u drugom slučaju  svaki put kad generišete verzionisan fajl moraćete da urezujete izmene, što ne znači da verzion fajl treba da bude ažuriran.

note: (title)
en: COM interface
target: COM interfejs

note: (primary)
en: COM SubWCRev interface
target: COM SubVCRev interfejs

note: (title)
en: COM/automation methods supported
target: COM/automatizacija metode podržane

note: (entry)
en: Method
target: Metod

note: (entry)
en: This method traverses the working copy gathering the revision information. Naturally you must call this before you can access the information using the remaining methods. The first parameter is the path. The second parameter should be true if you want to include folder revisions. Equivalent to the <placeholder-1/> command line switch. The third parameter should be true if you want to include svn:externals. Equivalent to the <placeholder-2/> command line switch.
target: Ovaj metod prelazi radnu kopiju sakupljajući revizione informacije. Prirodno morate ovo pozvati pre nego pristupite informacijama koristeći preostale motode. Prvi parametar je putanja. Drugi parametar treba da bude istinit ako želite da uključite  reviziju imenika. Ekvivalent sa <placeholder-1/> prekidačima komandne linije. Treći parametar treba da bude istina ako želite da uključite  svn:externals. Ekvivalent sa <placeholder-2/> prekidačima komandne linije.

note: (entry)
en: The highest commit revision in the working copy. Equivalent to <placeholder-1/>
target: Najviša urezana revizija u radnoj kopiji. Ekvivalent sa <placeholder-1/>

note: (entry)
en: The commit date/time of the highest commit revision. Equivalent to <placeholder-1/>
target: Urezivanje datm/vreme najviše urezane revizije. Ekvivalent sa <placeholder-1/>

note: (entry)
en: The author of the highest commit revision, that is, the last person to commit changes to the working copy.
target: Autor najviše urezane revizije, to je, poslednja osoba koja je urezala izmene u radnu kopiju.

note: (entry)
en: The minimum update revision, as shown in <placeholder-1/>
target: Minimum ažurirana revizija, kao što je prikazano u <placeholder-1/>

note: (entry)
en: The maximum update revision, as shown in <placeholder-1/>
target: Maksimum ažurirana revizija, kao što je prikazano u <placeholder-1/>

note: (entry)
en: True if there are local modifications
target: Tačno ako postoji lokalna izmena

note: (literal)
en: GetWCInfo
target: GetVCInfo

note: (entry)
en: Replaced with the repository URL of the working copy path used in <placeholder-1/>. Equivalent to <placeholder-2/>
target: Zamenjeno sa spremištem URL putanje radne kopije korišćene u <placeholder-1/>.Ekvivalent sa <placeholder-2/>

note: (entry)
en: True if the item is versioned.
target: Istina ako je stavka verzionisana.

note: (entry)
en: True if the item has the <placeholder-1/> property set.
target: Istina ako stavka ima <placeholder-1/> posešenu osobinu.

note: (entry)
en: True if the item is locked.
target: Istina ako je stavka zaključana.

note: (entry)
en: String representing the date when the lock was created, or an empty string if the item is not locked.
target: String koji reprezentuje datum kada je katanac kreiran, ili prazan string ako stavka nije zaključana.

note: (entry)
en: String representing the lock owner, or an empty string if the item is not locked.
target: String koji rprezentuje vlasnika katanca, ili prazan string ako stavka nije zaključana.

note: (entry)
en: The message entered when the lock was created.
target: Poruka uneta kada je katanac kreiran.

note: (para)
en: If you need to access Subversion revision information from other programs, you can use the COM interface of SubWCRev. The object to create is <literal>SubWCRev.object</literal>, and the following methods are supported: <placeholder-1/>
target: Ako treba da pristupite Subverzijinoj reviziojinoj informaciji iz drugih programa, možete koristiti COM interfejs SubWCRev. Objekat koji se kreira je literal>SubWCRev.object</literal>, i sledeći metodi su podržani: <placeholder-1/>

note: (para)
en: The following example shows how the interface might be used. <placeholder-1/>
target: Sledeći primer prikazuje kako interfejs može da se koristi. <placeholder-1/>

note: (title)
en: Frequently Asked Questions (FAQ)
target: Često postavljana pitanja (ČPP)

note: (primary)
en: FAQ
target: ČPP

note: (para)
en: Because TortoiseSVN is being developed all the time it is sometimes hard to keep the documentation completely up to date. We maintain an <ulink url="http://tortoisesvn.tigris.org/faq.html"><citetitle>online FAQ</citetitle></ulink> which contains a selection of the questions we are asked the most on the TortoiseSVN mailing lists <email>dev@tortoisesvn.tigris.org</email> and <email>users@tortoisesvn.tigris.org</email>.
target: Pošto se TortoiseSVN razvija sve vreme ponekad je teško da se dokumentacija drži ažurno. Mi održavamo <ulink url="http://tortoisesvn.tigris.org/faq.html"><citetitle>online FAQ</citetitle></ulink> koji sadrži izbor pitanja koja su najviše postavljana na TortoiseSVN mejling listama <email>dev@tortoisesvn.tigris.org</email> i <email>users@tortoisesvn.tigris.org</email>.

note: (para)
en: We also maintain a project <ulink url="http://issues.tortoisesvn.net"><citetitle>Issue Tracker</citetitle></ulink> which tells you about some of the things we have on our To-Do list, and bugs which have already been fixed. If you think you have found a bug, or want to request a new feature, check here first to see if someone else got there before you.
target: Takođe podržavamo projekat <ulink url="http://issues.tortoisesvn.net"><citetitle>Issue Tracker</citetitle></ulink>  koji vam govori o nekim stvarima koje imamo na našoj Šta-Uraditi listi, i bagove koji su već fiksirani. Ako mislite da ste našli bag, ili želite da zatražite novu mogućnost, proverite najpre ovde da vidite da li je neko to uradio pre vas.

note: (para)
en: If you have a question which is not answered anywhere else, the best place to ask it is on one of the mailing lists. <email>users@tortoisesvn.tigris.org</email> is the one to use if you have questions about using TortoiseSVN. If you want to help out with the development of TortoiseSVN, then you should take part in discussions on <email>dev@tortoisesvn.tigris.org</email>.
target: Ako imate pitanje na koje nije odgovoreno bilo gde drugde, najbolje mesto da pitate je jedna od mejling listi. <email>users@tortoisesvn.tigris.org</email> je jedna da služi ako imate pitanja o korišćelju TortoiseSVN. Ako želite pomoć u razvoju TortoiseSVN, treba da uzmete učešće u diskusiji na <email>dev@tortoisesvn.tigris.org</email>.

note: (title)
en: How Do I...
target: Kako da ja...

note: (para)
en: This appendix contains solutions to problems/questions you might have when using TortoiseSVN.
target: Dodatak sadrži rešenje problema/pitanja koja možete imati dok koristite TortoiseSVN.

note: (title)
en: Move/copy a lot of files at once
target: Pomeri/kopiraj mnogo fajlova ođednom

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

note: (primary)
en: reorganize
target: reorganizuj

note: (para)
en: Moving/Copying single files can be done by using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Rename...</guimenuitem></menuchoice>. But if you want to move/copy a lot of files, this way is just too slow and too much work.
target: Pomeranje/Kopiranje pojedinčnih fajlova može biti urađeno korišćenjem <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Preimenuj...</guimenuitem></menuchoice>. Ali ako želite pomeri/kopiraj mnogo fajlova, ovaj način je suviše spor i zahteva mnogo rada.

note: (para)
en: The recommended way is by <action>right-dragging</action> the files to the new location. Simply <action>right-click</action> on the files you want to move/copy without releasing the mouse button. Then drag the files to the new location and release the mouse button. A context menu will appear where you can either choose <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>SVN Copy versioned files here</guimenuitem></menuchoice>. or <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>SVN Move versioned files here</guimenuitem></menuchoice>.
target: Preporučen način je pomoću <action>desno-vučenje</action> fajlova u novu lokaciju. Jednostavno <action>desni-klik</action> na fajlove koje želite da pomeri/kopiraj bez otpuštanja dugmeta miša. Zatim vucite fajlove u novu lokaciju i otpustite dugme miša. Kontekst meni će se pojaviti gde možete ili izabrati <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>SVN Kopiraj verzionisane fajlove ovde</guimenuitem></menuchoice>. ili <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>SVN Pomeri verzionisane fajlove ovde</guimenuitem></menuchoice>.

note: (title)
en: Force users to enter a log message
target: Forsirati korisnike da unesu poruke dnevnika

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

note: (primary)
en: commit message
target: poruka urezivanja

note: (primary)
en: empty message
target: prazna poruka

note: (para)
en: There are two ways to prevent users from committing with an empty log message. One is specific to TortoiseSVN, the other works for all Subversion clients, but requires access to the server directly.
target: Postoji dva načina da se spreče korisnici da urezuju sa praznom dnevnik porukom. Jedan je specifičan za TortoiseSVN, drugi radi za sve Subverzione klijente, ali zahteva pristup serveru direktno.

note: (title)
en: Hook-script on the server
target: Zakačiv skript na serveru

note: (para)
en: If you have direct access to the repository server, you can install a pre-commit hook script which rejects all commits with an empty or too short log message.
target: Ako imate direktan pristup serveru spremišta, možete instalirati pre-urezivanja zakačiv skript koji odbija sva urezivanja sa praznom ili suviše kratkom dnevnik porukom.

note: (para)
en: In the repository folder on the server, there's a sub-folder <filename>hooks</filename> which contains some example hook scripts you can use. The file <filename>pre-commit.tmpl</filename> contains a sample script which will reject commits if no log message is supplied, or the message is too short. The file also contains comments on how to install/use this script. Just follow the instructions in that file.
target: U imeniku spremišta na serveru postoji sub-imenik <filename>hooks</filename> koji sadrži neke primere zakačivih skripti koje možete koristiti. Fajl <filename>pre-commit.tmpl</filename> sadrži jednostavan skript koji odbija urezivanje ako nema dnevnik poruke upisane, ili je poruka suviše kratka. Fajl takođe sadrži komentar kako da instalirate/koristite ovaj skript. Samo pratite instrukcije u tom fajlu.

note: (para)
en: This method is the recommended way if your users also use other Subversion clients than TortoiseSVN. The drawback is that the commit is rejected by the server and therefore users will get an error message. The client can't know before the commit that it will be rejected. If you want to make TortoiseSVN have the <guibutton>OK</guibutton> button disabled until the log message is long enough then please use the method described below.
target: Ovaj metod je preporučen način ako vaš korisnik takođe koristi druge Subverzione klijente osim TortoiseSVN.  Neugodnodt je da je urezivanje odbijeno od servera i tada korisnik dobija poruku o grešci. Klijent ne može znati pre urezivanja da će biti odbijen. Ako želite da učinite TortoiseSVN da ima <guibutton>OK</guibutton>  dugme onemogućeno dok dnevnik poruka ne bude dovoljno dugačka koristite metod opisan dole.

note: (title)
en: Project properties
target: Osobine projekta

note: (para)
en: TortoiseSVN uses properties to control some of its features. One of those properties is the <literal>tsvn:logminsize</literal> property.
target: TortoiseSVN koristi karakteristike da kontroliše neke od svojih mogućnosti. Jedna od tih karakteristika je <literal>tsvn:logminsize</literal> karakteristika.

note: (para)
en: If you set that property on a folder, then TortoiseSVN will disable the <guibutton>OK</guibutton> button in all commit dialogs until the user has entered a log message with at least the length specified in the property.
target: Ako podesite te karakteristike na imenik, onda TortoiseSVN može onemogućiti <guibutton>OK</guibutton> dugme u svim dijalozima urezivanja sve dok korisnik ne unese dnevnik poruku sa najmanje sa dužinom specificiranom u krakteristikama.

note: (para)
en: For detailed information on those project properties, please refer to <xref linkend="tsvn-dug-propertypage"/>
target: Detaljne informacije o tim karakteristikama projekta, molim pogledajte u <xref linkend="tsvn-dug-propertypage"/>

note: (title)
en: Update selected files from the repository
target: Ažuriranje izabranih fajlova iz spremišta

note: (para)
en: Normally you update your working copy using <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Update</guimenuitem></menuchoice>. But if you only want to pick up some new files that a colleague has added without merging in any changes to other files at the same time, you need a different approach.
target: Normalno vi ažurirate vašu radnu kopiju koristeći <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ažuriraj</guimenuitem></menuchoice>. Ali ako samo želite da pokupite neke nove fajlove koje su kolege dodale bez stapanja sa izmenama drugih fajlova u isto vreme, potreban vam je drugačiji pristup.

note: (para)
en: Use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Check for Modifications</guimenuitem></menuchoice>. and click on <guibutton>Check repository</guibutton> to see what has changed in the repository. Select the files you want to update locally, then use the context menu to update just those files.
target: Koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Proveri Izmene</guimenuitem></menuchoice>. i kliknite na <guibutton>Proveri spremište</guibutton> da vidite šta je izmenjeno u spremištu. Izaberite fajlove koje želite da ažurirate lokalno, zatim koristite kontekst meni da ažurirate samo te fajlove.

note: (title)
en: Roll back (Undo) revisions in the repository
target: Vrati nazad (poništi) revizije u spremištu

note: (primary)
en: rollback
target: premotavanje

note: (primary)
en: undo commit
target: poništavanje urezivanja

note: (primary)
en: undo change
target: poništavanje izmena

note: (title)
en: Use the revision log dialog
target: Koristi dijalog dnevnika revizija

note: (para)
en: The easiest way to revert the changes from a single revision, or from a range of revisions, is to use the revision log dialog. This is also the method to use of you want to discard recent changes and make an earlier revision the new HEAD.
target: Najlakši način da vratite izmene iz pojedinačne revizije, ili iz opsega revizija, je da koristite revizioni dnevnik dijalog. Ovo je takođe metod  koji se koristi ako želite da izbacite skore izmene i napravite raniju reviziju kao novu GLAVNU.

note: (para)
en: Select the file or folder in which you need to revert the changes. If you want to revert all changes, this should be the top level folder.
target: Izaberite fajl ili imenik u kome želite da vratite izmene. Ako želite da vratite sve izmene, ovo će biti imenik na vrhu.

note: (para)
en: Select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Show Log</guimenuitem></menuchoice> to display a list of revisions. You may need to use <guibutton>Show All</guibutton> or <guibutton>Next 100</guibutton> to show the revision(s) you are interested in.
target: Izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Prikaži dnevnik</guimenuitem></menuchoice> da prikažete listu revizija. Možda će vam trebati da koristite <guibutton>Prikaži Sve</guibutton> ili <guibutton>Sledećih 100</guibutton>  da prikažete reviziju(e) koja vas interesuje.

note: (para)
en: Select the revision you wish to revert. If you want to undo a range of revisions, select the first one and hold the <keycap>Shift</keycap> key while selecting the last one. Note that for multiple revisions, the range must be unbroken with no gaps. <action>Right click</action> on the selected revision(s), then select <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Revert changes from this revision</guimenuitem></menuchoice>.
target: Izaberite reviziju koju želite da vratite. Ako želite da poništite opseg revizija, izaberite najpre jednu i držite  <keycap>Shift</keycap> taster dok birate poslednji. Primetimo da za višestruke revizije opseg mora biti neprekinut bez rupa. <action>Desni klik</action> na izabranu reviziju(e), zatim izaberite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Vratite izmene iz ove revizije</guimenuitem></menuchoice>.

note: (para)
en: Or if you want to make an earlier revision the new HEAD revision, <action>right click</action> on the selected revision, then select <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Revert to this revision</guimenuitem></menuchoice>. This will discard <emphasis>all</emphasis> changes after the selected revision.
target: Ili ako želite da učinite raniju reviziju novu GLAVNU reviziju,  <action>desni klik</action> na izabranu reviziju, zatim izaberite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Vrati u ovu reviziju</guimenuitem></menuchoice>. Ovo će uništiti <emphasis>sve</emphasis> izmene posle izabrane revizije.

note: (para)
en: You have reverted the changes within your working copy. Check the results, then commit the changes.
target: Vi ste vratili izmene u okviru radne kopije. Proverite rezultat, zatim urežite izmene.

note: (title)
en: Use the merge dialog
target: Koristi dijalog spajanja

note: (para)
en: To undo a larger range of revisions, you can use the Merge dialog. The previous method uses merging behind the scenes; this method uses it explicitly.
target: Da se poništi veći opseg revizija, možete koristiti Stopi dijalog. Prethodni metod koristi stapanje iza scene; ovaj metod ga koristi eksplicitno.

note: (para)
en: In your working copy select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Merge</guimenuitem></menuchoice>.
target: U vašoj radnoj kopiji izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Stopi</guimenuitem></menuchoice>.

note: (para)
en: In the <guilabel>From:</guilabel> field enter the full folder URL of the branch or tag containing the changes you want to revert in your working copy. This should come up as the default URL.
target: U <guilabel>Iz:</guilabel> polju unesite pun imenik URL grane ili znaka koji sadrži izmene koje želite da vratite u vašu radnu kopiju. Ovo treba da dođe kao uobičajeni URL.

note: (para)
en: In the <guilabel>From Revision</guilabel> field enter the revision number that you are currently at. If you are sure there is no-one else making changes, you can use the HEAD revision.
target: U <guilabel>Iz Revizije</guilabel> polju unesite revizioni broj gde ste trebtno. Ako ste sigurni da niko ne radi izmene možete koristiti GLAVNU reviziju.

note: (para)
en: make sure the <guilabel>Use "From:" URL</guilabel> checkbox is checked.
target: budite sigurni  da <guilabel>Koristi "Iz:" URL</guilabel> čekboks čekiran.

note: (para)
en: In the <guilabel>To Revision</guilabel> field enter the revision number that you want to revert to, namely the one <emphasis>before</emphasis> the first revision to be reverted.
target: U <guilabel>U Reviziju</guilabel> polju unesite revizioni broj gde želite da vratite, recimo jedan <emphasis>pre</emphasis> prve revizije koja će biti vraćena.

note: (para)
en: Click <guibutton>OK</guibutton> to complete the merge.
target: Kliknite <guibutton>OK</guibutton> da kompletirate stapanje.

note: (title)
en: Use <literal>svndumpfilter</literal>
target: Koristi <literal>svndumpfilter</literal>

note: (para)
en: Since TortoiseSVN never loses data, your <quote>rolled back</quote> revisions still exist as intermediate revisions in the repository. Only the HEAD revision was changed to a previous state. If you want to make revisions disappear completely from your repository, erasing all trace that they ever existed, you have to use more extreme measures. Unless there is a really good reason to do this, it is <emphasis>not recommended</emphasis>. One possible reason would be that someone committed a confidential document to a public repository.
target: Pošto TortoiseSVN nikad ne gubi podatke, vaša <quote>vraćena nazad</quote> revizija još uvek postoji kao intermedijalna revizija u spremištu. Samo GLAVNA revizija je izmenjena u prethodno stanje. Ako želite da napravite da revizije nestanu kompletno iz spremišta, brisanjem svih staza koje su ikad postojale, morate koristiti mnogo ekstremnije mere. Osim ako ne postoji veoma dobar razlog da se to radi, to emphasis>nije preporučljivo</emphasis>. Jedan poseban razlog bi bio da neko urezuje poverljiv dokument u javno spremište.

note: (para)
en: The only way to remove data from the repository is to use the Subversion command line tool <literal>svnadmin</literal>. You can find a description of how this works in the <ulink url="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.maint.html"><citetitle>Repository Maintenance</citetitle></ulink>.
target: Jedini način da se izbace podaci iz spremišta je da se alat Subverzione komandne linije <literal>svnadmin</literal>. Možete naći opis kako ovo radi u <ulink url="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.maint.html"><citetitle>Održavanje spremišta</citetitle></ulink>.

note: (title)
en: Compare two revisions of a file
target: Uporedi dve revizije fajla

note: (primary)
en: compare files
target: uporedi fajlove

note: (primary)
en: changes
target: izmene

note: (para)
en: If you want to compare two revisions in a file's history, for example revisions 100 and 200 of the same file, just use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Show Log</guimenuitem></menuchoice> to list the revision history for that file. Pick the two revisions you want to compare then use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Compare Revisions</guimenuitem></menuchoice>.
target: Ako želite uporediti dve revizije u istoriji fajla, na primer revizije 100 i 200 istog fajla, samo koristite  <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Prikaži Dnevnik</guimenuitem></menuchoice> da izlistate istoriju revizija za taj fajl. Odaberite dve revizije koje želite da uporedite i koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Uporedi Revizije</guimenuitem></menuchoice>.

note: (para)
en: If you want to compare the same file in two different trees, for example the trunk and a branch, you can use the repository browser to open up both trees, select the file in both places, then use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Compare Revisions</guimenuitem></menuchoice>.
target: Ako želite da uporedite isti fajl u dva različita stabla, na primer deblo i granu, možete koristiti pretraživač spremišta da otvorite oba stabla, izaberite fajl na oba mesta, zatim koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Uporedi Revizije</guimenuitem></menuchoice>.

note: (para)
en: If you want to compare two trees to see what has changed, for example the trunk and a tagged release, you can use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revision Graph</guimenuitem></menuchoice> Select the two nodes to compare, then use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Compare HEAD Revisions</guimenuitem></menuchoice>. This will show a list of changed files, and you can then select individual files to view the changes in detail. Alternatively use <menuchoice><guimenu>Context Menu</guimenu><guimenuitem>Unified Diff of HEAD Revisions</guimenuitem></menuchoice> to see a summary of all differences, with minimal context.
target: Ako želite da uporedite dva stabla da vidite šta se izmenilo, na primer deblo i znakovnu realizaciju, možete koristiti <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revizioni Graf</guimenuitem></menuchoice> Izaberite dva čvora za poređenje, zatim koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Uporedi GLAVNE Revizije</guimenuitem></menuchoice>.  Ovo će prikazati listu izmenjenih fajlova, i možete zatim izabrati pojedine fajlove da vidite izmene detaljno. Alternativno koristite <menuchoice><guimenu>Kontekst Meni</guimenu><guimenuitem>Ujedinjene Diff od GLAVNIH Revizija</guimenuitem></menuchoice> da vidite rezultat svih razlika, sa minimalnim sadržajem.

note: (title)
en: Include a common sub-project
target: Uključi sličan sub-projekat

note: (primary)
en: common projects
target: slični projekti

note: (primary)
en: vendor projects
target: distributerski projekti

note: (para)
en: Sometimes you will want to include another project within your working copy, perhaps some library code. You don't want to make a duplicate of this code in your repository because then you would lose connection with the original (and maintained) code. Or maybe you have several projects which share core code. There are at least 3 ways of dealing with this.
target: Ponekad ćete želeti da uključite drugi projekat u okviru vaše radne kopije, možda neki bibliotečki kod. Vi ne želite da napravite duplikat ovog koda u vašem spremištu jer onda gubite vezu sa originalnim (i podržanim) kodom. Ili možda imate više projekata koji dele osnovni kod. Postoji najmanje 3 načina da se radi sa ovim.

note: (title)
en: Use svn:externals
target: Koristite svn:externals

note: (para)
en: Set the <literal>svn:externals</literal> property for a folder in your project. This property consists of one or more lines; each line has the name of a sub-folder which you want to use as the checkout folder for common code, and the repository URL that you want to be checked out there. For full details refer to <xref linkend="tsvn-dug-import-4"/>.
target: Podesite <literal>svn:externals</literal> karakteristiku za imenik u vašem projektu. Ova karakteristika se sastoji od jedne ili više linija; svaka linija ima ime pod-imenikakoji želite da koristite kao imenik za preuzimanje zajdničkog koda, i URL spremišta odakle želite da preuzimate. Za potpune detalje pogledajte <xref linkend="tsvn-dug-import-4"/>.

note: (para)
en: Commit the new folder. Now when you update, Subversion will pull a copy of that project from its repository into your working copy. The sub-folders will be created automatically if required. Each time you update your main working copy, you will also receive the latest version of all external projects.
target: Urežite novi imenik. Sada kada ažurirate, Subverzija će vući kopiju projekta iz spremišta u vašu radnu kopiju. Pod-imenici će biti kreirani automatski ako se zahteva. Svaki put kada ažurirate vašu glavnu radnu kopiju, vi ćete takođe dobiti zadnju verziju svih spoljašnjih projekata.

note: (para)
en: Of the three methods described, this is the only one which needs no setup on the client side. Once externals are specified in the folder properties, all clients will get populated folders when they update.
target: Jedan od tri metoda je opisan, ovo je samo jedno što vam treba pri podešavanju na strani klijenta. Kada se eksternali jednom specificiraju u karakteristikama imenika, svi klijenti će dobiti popunjene imenike kada se ažuriraju.

note: (title)
en: Use a nested working copy
target: Koristi ugnježdenu radnu kopiju

note: (para)
en: Create a new folder within your project to contain the common code, but do not add it to Subversion
target: Kreirajte novi imenik u okviru vašeg projekta da sadrži zajedničke kodove, ali ne dodajte to Subverziji.

note: (para)
en: Select <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Checkout</guimenuitem></menuchoice> for the new folder and checkout a copy of the common code into it. You now have a separate working copy nested within your main working copy.
target: Izaberite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Preuzimanje</guimenuitem></menuchoice>  za nove imenike i preuzmite kopiju zajedničkih kodova u njega.

note: (para)
en: The two working copies are independent. When you commit changes to the parent, changes to the nested WC are ignored. Likewise when you update the parent, the nested WC is not updated.
target: ve radne kopije su nezavisne. Kada urežete izmene u predačku, izmene u ugnježdenu RK se ignorišu. Slično ako ažurirate predačku, ugnježdena RK se ne ažurira.

note: (title)
en: Use a relative location
target: Koristi relativnu lokaciju

note: (para)
en: If you use the same common core code in several projects, and you do not want to keep multiple working copies of it for every project that uses it, you can just check it out to a separate location which is related to all the other projects which use it. For example: <screen>
    C:\Projects\Proj1
    C:\Projects\Proj2
    C:\Projects\Proj3
    C:\Projects\Common
    </screen> and refer to the common code using a relative path, eg. <filename>..\..\Common\DSPcore</filename>.
target: Ako koristite isti zajednički osnovni kod u više projekata, i ne želite da čuvate višestruke radne kopije za svaki projekat koji ih koristi, možete ih samo preuzeti u izdvojene lokacije koje su povezane sa svim ostalim projektima koji ih koriste. Na primer: <screen>
    C:\Projects\Proj1
    C:\Projects\Proj2
    C:\Projects\Proj3
    C:\Projects\Common
    </screen> i pozovite se na zajednički kod koristeći relativnu putanju, npr. <filename>..\..\Common\DSPcore</filename>.

note: (para)
en: If your projects are scattered in unrelated locations you can use a variant of this, which is to put the common code in one location and use drive letter substitution to map that location to something you can hard code in your projects, eg. Checkout the common code to <filename>D:\Documents\Framework</filename> or <filename>C:\Documents and Settings\{login}\My Documents\framework</filename> then use <screen>
    SUBST X: "D:\Documents\framework"
    </screen> to create the drive mapping used in your source code. Your code can then use absolute locations. <screen>
    #include "X:\superio\superio.h"
    </screen>
target: Ako je vaš projekat razbacan u nevezanim lokacijama možete koristiti varijantu ovoga, što će staviti zajednički kod u jednu lokaciju i koristiti slovo drajva kao zmenu da označi lokaciju ka nečemu što teško kodirate u vašem projektu, npr. Preuzimanje zajedničkog koda sa <filename>D:\Documents\Framework</filename> ili <filename>C:\Documents and Settings\{login}\My Documents\framework</filename>  zatim koristite <screen>
    SUBST X: "D:\Documents\framework"
    </screen> to create the drive mapping used in your source code. Your code can then use absolute locations. <screen>
    #include "X:\superio\superio.h"
    </screen>

note: (para)
en: This method will only work in an all-PC environment, and you will need to document the required drive mappings so your team know where these mysterious files are. This method is strictly for use in closed development environments, and not recommended for general use.
target: Ovaj metod će samo raditi na potpun-PC okolini, i trebaće vam da dokumentujete zahtevano obeležavanje drajva tako da vaš tim zna gde se ovi misteriozni fajlovi nalaze. Ovaj metod je striktno za korišćenje u okolini bliskoj razvoju, i ne preporučuje se za opštu upotrebu.

note: (title)
en: Create a shortcut to a repository
target: Kreiraj skraćenicu za spremište

note: (primary)
en: shortcut
target: skraćenica

note: (para)
en: If you frequently need to open the repository browser at a particular location, you can create a desktop shortcut using the automation interface to TortoiseProc. Just create a new shortcut and set the target to: <screen>
    TortoiseProc.exe /command:repobrowser /path:"url/to/repository"
    </screen> Of course you need to include the real repository URL.
target: Ako vam često treba da otvarate pretraživač spremišta na posebnoj lokaciji, možete kreirati prečicu na desktopu koristeći automtizovani interfejs ka TortoiseProc. Samo kreirajte novu prečicu i podesite cilj ka <screen>
    TortoiseProc.exe /command:repobrowser /path:"url/to/repository"
    </screen> Svakako potrebno je da uključite pravi URL spremišta.

note: (title)
en: Ignore files which are already versioned
target: Zanemarivanje fajlova koji su već verzionisani.

note: (primary)
en: remove versioning
target: ukloni verzionisanje

note: (primary)
en: detach from repository
target: otkači od spremišta

note: (para)
en: If you accidentally added some files which should have been ignored, how do you get them out of version control without losing them? Maybe you have your own IDE configuration file which is not part of the project, but which took you a long time to set up just the way you like it.
target: Ako greško dodate neke fajlove koji bi trebalo da budu zanemareni, kako ih izvući iz kontrojžle verzija a da ih ne izgubimo? Možda imate vaš lični IDE konfiguracioni fajl koji nije deo projekta, ali koji uzima dosta vremena da se podesi na način kako volite.

note: (para)
en: If you have not yet committed the add, then all you have to do is use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Revert...</guimenuitem></menuchoice> to undo the add. You should then add the file(s) to the ignore list so they don't get added again later by mistake.
target: Ako još niste urezali dodavanje, tada imate da koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Vrati...</guimenuitem></menuchoice> da poništite dodavanje. Zatim treba da dodate fajl(ove) u listu zanemarenih tako da ih greškom ne dodate ponovo kasnije.

note: (para)
en: Hold the <keycap>Shift</keycap> key to get the extended context menu and use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Delete (keep local)</guimenuitem></menuchoice> to mark the file/folder for deletion from the repository without losing the local copy.
target: Držite <keycap>Shift</keycap> taster da dobijete prošireni kontekst meni i koristite <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Briši(drži lokalnol)</guimenuitem></menuchoice> da označite fajl/imenik za brisanje iz spremišta bez gubljenja lokalne kopije.

note: (para)
en: <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Commit</guimenuitem></menuchoice> the parent folder.
target: <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Ureži</guimenuitem></menuchoice> predački imenik.

note: (para)
en: Add the file/folder to the ignore list so you don't get into the same trouble again.
target: Dodajte fajl/imenik u listu zanemarenih tako da ne dođete u isti problem ponovo.

note: (para)
en: If the files are already in the repository, you have to do a little more work. <placeholder-1/>
target: Ako su fajlovi već u spremištu, morate uraditi malo više posla. <placeholder-1/>

note: (title)
en: Unversion a working copy
target: Neverzionisana radna kopija

note: (para)
en: If you have a working copy which you want to convert back to a plain folder tree without the <literal>.svn</literal> directories, you can simply export it to itself. Read <xref linkend="tsvn-dug-export-unversion"/> to find out how.
target: Ako imate radnu kopiju koju želite da konvertujete nazad u čisto stablo imenika bez <literal>.svn</literal> imenika, možete je jednostavno izvesti u sebe samu. Pročitajte <xref linkend="tsvn-dug-export-unversion"/> da nađete više detalja.

note: (title)
en: Remove a working copy
target: Ukloni radnu kopiju

note: (para)
en: If you have a working copy which you no longer need, how do you get rid of it cleanly? Easy - just delete it in Windows Explorer! Working copies are private local entities, and they are self-contained.
target: Ako imate radnu kopiju koja vam više nije potrebna, kako ćete se nje osloboditi potpuno? Jednostavno - samo je obrišite u Vindouz Eksploreru! Radne kopije su privatni lokalni entiteti, i one su sveobuhvatne.

note: (title)
en: Useful Tips For Administrators
target: Korisni saveti za administratore

note: (para)
en: This appendix contains solutions to problems/questions you might have when you are responsible for deploying TortoiseSVN to multiple client computers.
target: Ovaj dodatak sadrži rešenja problema/pitanja koja biste mogli imati kada ste odgovorni za razmeštanje TortoiseSVN na više računara klijenata.

note: (title)
en: Deploy TortoiseSVN via group policies
target: Raspoređivanje TortoiseSVN preko grupne polise

note: (primary)
en: group policies
target: grupne polise

note: (primary)
en: domain controller
target: kontrolor domena

note: (primary)
en: deploy
target: raspoređivanje

note: (para)
en: The TortoiseSVN installer comes as an MSI file, which means you should have no problems adding that MSI file to the group policies of your domain controller.
target: TortoiseSVN instalacija dolazi kao MSI fajl, što unači da ne bi trbalo  da imate probleme pri dodavanju tog MSI fajla grupi vašeg kontrolora domena.

note: (para)
en: A good walk-through on how to do that can be found in the knowledge base article 314934 from Microsoft: <ulink url="http://support.microsoft.com/?kbid=314934"><citetitle>http://support.microsoft.com/?kbid=314934</citetitle></ulink>.
target: Dobar pregled kako da se to uradi može se naći u bazi znanja u Mikrosoftovom članku 314934:  <ulink url="http://support.microsoft.com/?kbid=314934"><citetitle>http://support.microsoft.com/?kbid=314934</citetitle></ulink>.

note: (para)
en: Versions 1.3.0 and later of TortoiseSVN must be installed under <emphasis>Computer Configuration</emphasis> and not under <emphasis>User Configuration</emphasis>. This is because those versions need the new CRT and MFC DLLs, which can only be deployed <emphasis>per computer</emphasis> and not <emphasis>per user</emphasis>. If you really must install TortoiseSVN on a per user basis, then you must first install the MFC and CRT package version 8 from Microsoft on each computer you want to install TortoiseSVN as per user.
target: Verzije 1.3.0 i kasnije TortoiseSVN moraju biti instalirane pod <emphasis>Računar Konfiguracija</emphasis> a ne pod <emphasis>Korisnik Konfiguracija</emphasis>. Ovo je zbog toga što ove verzije traže novi CRT i MFC DLLove, koji se mogu rasporediti samo <emphasis>za računar</emphasis> a ne <emphasis>za korisnika</emphasis>. Ako stvarno morate instalirati TortoiseSVN po osnovi za korisnika, onda morate najpre instalirati MFC i CRT paket verziu 8 od Mikrosofta na svaki kompjuter na koji želite da instalirate TortoiseSVN po korisniku.

note: (title)
en: Redirect the upgrade check
target: Preusmeravanje provere nadogradnje

note: (primary)
en: upgrade check
target: provera nadogradnje

note: (primary)
en: check new version
target: provera nove verzije

note: (primary)
en: version
target: verzija

note: (para)
en: TortoiseSVN checks if there's a new version available every few days. If there is a newer version available, a dialog shows up informing the user about that.
target: TortoiseSVN proverava da li je dostupna nova verzija svakih nekoliko dana. Ako postoji nova verzija, dijalog se otvara informišući korisnika o tome.

note: (title)
en: The upgrade dialog
target: dijalog nadogradnje

note: (para)
en: If you're responsible for a lot of users in your domain, you might want your users to use only versions you have approved and not have them install always the latest version. You probably don't want that upgrade dialog to show up so your users don't go and upgrade immediately.
target: Ako ste odgovorni za više korisnika na vašem domenu, možda želite da vaši korisnici koriste samo verzije koje ste vi odobrili i nećete imati instalisanu poslednju verziju. Verovatno ne želite taj dijalog za dogradnju da se pojavi i da vaši korisnici odu i izvrše trenutnu dogradnju.

note: (para)
en: Versions 1.4.0 and later of TortoiseSVN allow you to redirect that upgrade check to your intranet server. You can set the registry key <filename>HKCU\Software\TortoiseSVN\UpdateCheckURL</filename> (string value) to an URL pointing to a text file in your intranet. That text file must have the following format: <screen>
    1.4.1.6000
    A new version of TortoiseSVN is available for you to download!
    http://192.168.2.1/downloads/TortoiseSVN-1.4.1.6000-svn-1.4.0.msi
    </screen> The first line in that file is the version string. You must make sure that it matches the exact version string of the TortoiseSVN installation package. The second line is a custom text, shown in the upgrade dialog. You can write there whatever you want. Just note that the space in the upgrade dialog is limited. Too long messages will get truncated! The third line is the URL to the new installation package. This URL is opened when the user clicks on the custom message label in the upgrade dialog. You can also just point the user to a web page instead of the MSI file directly. The URL is opened with the default web browser, so if you specify a web page, that page is opened and shown to the user. If you specify the MSI package, the browser will ask the user to save the MSI file locally.
target: Verzija 1.4.0 i dalje TortoiseSVN dozvoljavaju da preusmerite proveru dogradnje  ka vašem internet serveru. Možete podesiti ključ registra <filename>HKCU\Software\TortoiseSVN\UpdateCheckURL</filename> (string vrednost) ka URL koji pokazuje na tekst fajl vašeg intraneta. Taj tekst fajl mora imati sledeći format: <screen>
    1.4.1.6000
    A new version of TortoiseSVN is available for you to download!
    http://192.168.2.1/downloads/TortoiseSVN-1.4.1.6000-svn-1.4.0.msi
    </screen> Prva linija u tom fajlu je string verzije. Morate osigurati da to tačno opisuje string verzije TortoiseSVN instalacionog paketa. Druga linija je uobičajen tekst prikazan u dijalogu dogradnje. Tu možete napisati što god želite. Obratite pažnju da je prostor u dijalogu dogradnje ograničen. Suviše dugačke poruke će biti skraćene! Treća linija je URL ka novom instalacionom paketu. URL je otvoren kada korisnik klikne na oznaku uobičajene poruke u dijalogo dogradnje. Možete takođe samo uputiti korisnika na veb stranicu umesto na MSI fajl direktno. URL se otvara podrazumevanim pretraživačem veba, tako da ako specificirate veb stranicu, ta stranica se otvorila i prikazuje se korisniku. Ako specificirate MSI paket, pretraživač će pitati korisnika da sačuva MSI fajl lkalno.

note: (title)
en: Setting the <literal>SVN_ASP_DOT_NET_HACK</literal> environment variable
target: Podešavanje <literal>SVN_ASP_DOT_NET_HACK</literal> promenljive okruženja.

note: (primary)
en: ASP projects
target: ASP projekti

note: (para)
en: As of version 1.4.0 and later, the TortoiseSVN installer doesn't provide the user with the option to set the <literal>SVN_ASP_DOT_NET_HACK</literal> environment variable anymore, since that caused many problems and confusions with users which always install <emphasis>everything</emphasis> no matter if they know what it is for.
target: Od verzije 1.4.0 i dalje, instalacija TortoiseSVN više ne omogućava korisniku da podesi  <literal>SVN_ASP_DOT_NET_HACK</literal> promenljivu okruženja, jer je to uzrokovalo mnoge probleme i konfuziju kod korisnika koji uvek instaliraju <emphasis>sve</emphasis>  ne brinući šta to u stvari znači.

note: (para)
en: But that option is only hidden for the user. You still can force the TortoiseSVN installer to set that environment variable by setting the <literal>ASPDOTNETHACK</literal> property to TRUE. For example, you can start the installer like this: <screen>
    msiexec /i TortoiseSVN-1.4.0.msi ASPDOTNETHACK=TRUE
    </screen>
target: Ali ta opcija je samo sakrivena za korisnika. Vi još možete naterati TortoiseSVN unstalaciju da podesi tu promenljivu okruženja podešavanjem <literal>ASPDOTNETHACK</literal> karakteristike na ISTINA. Na primer, možete početi instalaciju kao: <screen>
    msiexec /i TortoiseSVN-1.4.0.msi ASPDOTNETHACK=TRUE
    </screen>

note: (title)
en: Disable context menu entries
target: Onemugući ulaz kontekstnog menija

note: (primary)
en: context menu entries
target: ulazi kontekstnog menija

note: (primary)
en: disable functions
target: funkcije onemogućavanja

note: (para)
en: As of version 1.5.0 and later, TortoiseSVN allows you to disable (actually, hide) context menu entries. Since this is a feature which should not be used lightly but only if there is a compelling reason, there is no GUI for this and it has to be done directly in the registry. This can be used to disable certain commands for users who should not use them. But please note that only the context menu entries in the <emphasis>explorer</emphasis> are hidden, and the commands are still available through other means, e.g. the command line or even other dialogs in TortoiseSVN itself!
target: Od verzije 1.5.0 i dalje, TortoiseSVN omogućava da onemogućite (stvarno, sakrijete) ulaze kontekst menija. Pošto je to mogućnost koja ne bi trebalo da se koristi olako osim ako ne postoji obavezujući razlog, ne postoji GUI za to i to se mora uraditi dirktno u registru. Ovo se može koristiti da se onemoguće izvesne komande za korisnike koji ih ne bi koristio. Ali molim primetite da samo ulazi kontekst menija u <emphasis>eksploreru</emphasis> su sakrivene, a komande su i dalje dostupne kroz druge načine, npr. komandne linije i čak dijaloga u samoj TortoiseSVN!

note: (para)
en: The registry keys which hold the information on which context menus to show are <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskLow</filename> and <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskHigh</filename>.
target: Registri ključevi koji sadrže informacije po kojim se prikazuju kontekst meniji su <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskLow</filename> i <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskHigh</filename>.

note: (para)
en: Each of these registry entries is a <literal>DWORD</literal> value, with each bit corresponding to a specific menu entry. A set bit means the corresponding menu entry is deactivated.
target: Svaki od ovih ulaza registra je <literal>DWORD</literal> vrednost, sa svakim bitom koji odgovara posebnom ulazu menija. Podešen bit znači da je odgovarajući ulaz menija deaktiviran.

note: (title)
en: Menu entries and their values
target: Ulazi menija i njihove vrednosti

note: (entry)
en: Value
target: Vrednost

note: (entry)
en: Menu entry
target: Ulazi menija

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)
en: Create Repository here
target: Kreiraj spremište ovde

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

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

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: Remove Lock
target: Ukloni ključ

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: (entry)
en: About
target: O

note: (para)
en: Example: to disable the <quote>Relocate</quote> the <quote>Delete unversioned items</quote> and the <quote>Settings</quote> menu entries, add the values assigned to the entries like this: <screen>
      0x0000000000080000
    + 0x0000000080000000
    + 0x2000000000000000
    = 0x2000000080080000
    </screen> The lower <literal>DWORD</literal> value (<literal>0x80080000</literal>) must then be stored in <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskLow</filename>, the higher <literal>DWORD</literal> value (<literal>0x20000000</literal>) in <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskHigh</filename>.
target: Primer: da se onemogući <quote>Relociraj</quote>  <quote>Obriši neverzionisane stavke</quote> i <quote>Podešavanja</quote> ulazi menija, dodajte vrednosti pridružene ulazima kao ove: <screen>
      0x0000000000080000
    + 0x0000000080000000
    + 0x2000000000000000
    = 0x2000000080080000
    </screen> Manja <literal>DWORD</literal> vrednost (<literal>0x80080000</literal>) mora biti smeštena u <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskLow</filename>, veća <literal>DWORD</literal> vrednost (<literal>0x20000000</literal>) u <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskHigh</filename>.

note: (para)
en: To enable the menu entries again, simply delete the two registry keys.
target: Da biste ponovo omogućili ulaze menija, jednostavno obrišite dva registar ključa.

note: (title)
en: Automating TortoiseSVN
target: Automatizovanje TortoiseSVN

note: (para)
en: Since all commands for TortoiseSVN are controlled through command line parameters, you can automate it with batch scripts or start specific commands and dialogs from other programs (e.g. your favourite text editor).
target: Pošto su sve komande TortoiseSVN kontrolisane kroz parametre kontrolne linije, možete automatizovati to sa beč skriptom da pokrenete posebne komande i dijaloge iz drugih programa (npr. vašeg najdražeg tekst uređivača).

note: (para)
en: Remember that TortoiseSVN is a GUI client, and this automation guide shows you how to make the TortoiseSVN dialogs appear to collect user input. If you want to write a script which requires no input, you should use the official Subversion command line client instead.
target: Zapamtite da je TortoiseSVN GUI klijent, i ovaj automatizacioni vodič prikazuje kako da učinite da se TortoiseSVN dijalog pojavi da sakupi korisnikove ulaze. Ako želite da napišete skript koji ne zahteva ulaz, treba da koristite zvaničan Subverzioni linijski klijent umesto toga.

note: (title)
en: TortoiseSVN Commands
target: TortoiseSVN komande

note: (primary)
en: automation
target: utomatizovanje

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

note: (para)
en: The TortoiseSVN GUI program is called <literal>TortoiseProc.exe</literal>. All commands are specified with the parameter <option>/command:abcd</option> where <literal>abcd</literal> is the required command name. Most of these commands need at least one path argument, which is given with <option>/path:"some\path"</option>. In the following table the command refers to the <option>/command:abcd</option> parameter and the path refers to the <option>/path:"some\path"</option> parameter.
target: TortoiseSVN GUI program se zove  <literal>TortoiseProc.exe</literal>. Sve komande su specificirane sa parametrom  <option>/command:abcd</option> gde je <literal>abcd</literal>  željeno ime komande. Većina od ovih komandi zahteva najmanje jednu putanju kao argument, što je dato sa <option>/path:"some\path"</option>. U sledećoj tabeli komande se odnose na <option>/command:abcd</option> parametar i putanju koja se odnosi na <option>/path:"some\path"</option> parametar.

note: (para)
en: Since some of the commands can take a list of target paths (e.g. committing several specific files) the <option>/path</option> parameter can take several paths, separated by a <literal>*</literal> character.
target: Kako neke od komandi mogu uzeti listu ciljnih putanja (npr. urezivanje više specifičnih fajlova) <option>/path</option> parametar može uzeti više putalji, odvojenih sa <literal>*</literal> karakterom.

note: (para)
en: TortoiseSVN uses temporary files to pass multiple arguments between the shell extension and the main program. From TortoiseSVN 1.5.0 on and later, <option>/notempfile</option> parameter is obsolete and there is no need to add it anymore.
target: TortoiseSVN koristi privremene fajlove da provuče višestruke argumente između proširenja školjke i glavnog programa. Iz TortoiseSVN 1.5.0 i dalje, <option>/notempfile</option> parametar je napušten i nema potrebe da se više dodaje.

note: (para)
en: The progress dialog which is used for commits, updates and many more commands usually stays open after the command has finished until the user presses the <guibutton>OK</guibutton> button. This can be changed by checking the corresponding option in the settings dialog. But using that setting will close the progress dialog, no matter if you start the command from your batch file or from the TortoiseSVN context menu.
target: Progres dijalog koji se koristi za urezivanje, ažurira i mnogo više komandi obično ostaje otvoreno posle zavreštka rada komande dok korisnik ne pritisne <guibutton>OK</guibutton> dugme. Ovo bi se moglo promeniti proverom odgovarajiće opvžcije u dijalogu podešavanja. Koristeći to  podešavanje zatvoriće se progres dijalog, nije bitno da li ste počeli komandu iz beč fajla ili iz TortoiseSVN kontekst menija.

note: (para)
en: To specify a different location of the configuration file, use the parameter <option>/configdir:"path\to\config\directory"</option>. This will override the default path, including any registry setting.
target: Da se specificira različita lokacija konfiguracionog fajla, koristite parametar <option>/configdir:"path\to\config\directory"</option>. Ovo će promeniti uobičajenu putanju, uključujući i podešavanje registra.

note: (para)
en: <option>/closeonend:0</option> don't close the dialog automatically
target: <option>/closeonend:0</option> ne zatvara dijalog automatski

note: (para)
en: <option>/closeonend:1</option> auto close if no errors
target: <option>/closeonend:1</option> auto zatvaranje ako nema grešaka

note: (para)
en: <option>/closeonend:2</option> auto close if no errors and conflicts
target: <option>/closeonend:2</option> auto zatvaranje ako nema grešaka i konflikata

note: (para)
en: <option>/closeonend:3</option> auto close if no errors, conflicts and merges
target: <option>/closeonend:3</option>auto zatvaranje ako nema grešaka, konflikata i stapanja

note: (para)
en: <option>/closeonend:4</option> auto close if no errors, conflicts and merges for local operations
target: <option>/closeonend:4</option>auto zatvaranje ako nema grešaka, konflikata i stapanja za lokalne operacije

note: (para)
en: To close the progress dialog at the end of a command automatically without using the permanent setting you can pass the <option>/closeonend</option> parameter. <placeholder-1/>
target: Da bi se zatvorio progres dijalog na kraju komande bez korišćenja stalnog podešavanja treba da provučete  <option>/closeonend</option> parametar. <placeholder-1/>

note: (para)
en: The table below lists all the commands which can be accessed using the TortoiseProc.exe command line. As described above, these should be used in the form <literal>/command:abcd</literal>. In the table, the <literal>/command</literal> prefix is omitted to save space.
target: Tabela koja sledi lista sve komande kojima treba da pristupi TortoiseProc.egze komandna linija. Kako je ranije opisano, ovo treba da se koristi u obliku <literal>/command:abcd</literal>. U tabeli, <literal>/command</literal> prefiks nedostaje da se uštedi na prostoru.

note: (title)
en: List of available commands and options
target: Lista dostupnih komandnih opcija

note: (entry)
en: Command
target: Komanda

note: (entry)
en: Shows the about dialog. This is also shown if no command is given.
target: Prikazuje dijalog sa opisom programa. Ovaj dijalog je takođe prikazan ako komanda nije data.

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

note: (entry)
en: Opens the log dialog. The <placeholder-1/> specifies the file or folder for which the log should be shown. Three additional options can be set: <placeholder-2/>, <placeholder-3/> and <placeholder-4/>
target: Otvara dnevnik dijalog. <placeholder-1/> specificira fajl ili imenik za koji dnevnik treba da bude prikazan. Tri dodatne opcije treba da budu podeene: <placeholder-2/>, <placeholder-3/> i <placeholder-4/>

note: (entry)
en: Opens the checkout dialog. The <placeholder-1/> specifies the target directory and the <placeholder-2/> specifies the URL to checkout from.
target: Otvara dijalog preuzimanja. <placeholder-1/> specificire ciljni imenik i <placeholder-2/> specificire URL iz kog se  preuzima.

note: (entry)
en: Opens the import dialog. The <placeholder-1/> specifies the directory with the data to import.
target: Otvara dijalog uvoza. <placeholder-1/> specificira imenik sa podacima za uvoz.

note: (entry)
en: Updates the working copy in <placeholder-1/> to HEAD. If the option <placeholder-2/> is given then a dialog is shown to ask the user to which revision the update should go. To avoid the dialog specify a revision number <placeholder-3/>. Other options are <placeholder-4/> and <placeholder-5/>.
target: Ažurira radnu kopiju u <placeholder-1/> ka GLAVNOJ. Ako je opcija <placeholder-2/> data tada je prikazani dijalog da pita korisnika ka kojoj reviziji ažuriranje treba da ide. Da bi se izbegao dijalog specificirajte broj revizije <placeholder-3/>. Druge opcije su <placeholder-4/> i <placeholder-5/>.

note: (option)
en: path
target: putanja

note: (option)
en: /bugid:"the bug id here"
target: /bugid:"bag id ovde"

note: (entry)
en: Opens the commit dialog. The <placeholder-1/> specifies the target directory or the list of files to commit. You can also specify the <placeholder-2/> switch to pass a predefined log message to the commit dialog. Or, if you don't want to pass the log message on the command line, use <placeholder-3/>, where <placeholder-4/> points to a file containing the log message. To pre-fill the bug ID box (in case you've set up integration with bug trackers properly), you can use the <placeholder-5/> to do that.
target: Otvara dijalog urezivanja. <placeholder-1/> specificira ciljni imenik ili listu fajlova za ažuriranje. Možete takođe specificirati <placeholder-2/> prekidač da provučete predefinisane dnevnik poruke u dijalog urezivanja. Svakako, ako ne želite da provučete dnevnik poruku na  komandnoj liniji, koristite <placeholder-3/>, gde <placeholder-4/> ukazije na fajl koji sadrži dnevnik poruku. Da bi se pre-popunio bag ID (u slučaju da ste odgovarajuće podesili integraciju sa  bag tragačem), možete koristiti <placeholder-5/> da to uradite.

note: (entry)
en: Adds the files in <placeholder-1/> to version control.
target: Dodaje fajlove u <placeholder-1/> za kontrolu verzije.

note: (entry)
en: Reverts local modifications of a working copy. The <placeholder-1/> tells which items to revert.
target: Vraća lokalne izmene radne kopije. <placeholder-1/> kaže koje stavke vratiti.

note: (entry)
en: Cleans up interrupted or aborted operations and unlocks the working copy in <placeholder-1/>.
target: Čisti prekinute ili zaustavljene operacije i otključava radnu kopiju u <placeholder-1/>.

note: (entry)
en: Marks a conflicted file specified in <placeholder-1/> as resolved. If <placeholder-2/> is given, then resolving is done without asking the user first if it really should be done.
target: Označava konfliktne fajlove specificirane u  <placeholder-1/> kao rešene. Ako je <placeholder-2/> dat, rešavanje je dato bez prethodnog pitanja korisnika da li da se to uradi.

note: (entry)
en: Creates a repository in <placeholder-1/>
target: Kreira spremište u <placeholder-1/>

note: (entry)
en: Opens the switch dialog. The <placeholder-1/> specifies the target directory.
target: Otvara prekidač dijalog. <placeholder-1/> specificira ciljni imenik.

note: (entry)
en: Exports the working copy in <placeholder-1/> to another directory. If the <placeholder-2/> points to an unversioned directory, a dialog will ask for an URL to export to the directory in <placeholder-3/>.
target: Izvozi radnu kopiju u <placeholder-1/> za dugi imenik. Ako <placeholder-2/> ukazuje na neverzionisani imenik, dijalog će vas pitati za URL za izvoz u imenik u  <placeholder-3/>.

note: (entry)
en: Opens the merge dialog. The <placeholder-1/> specifies the target directory. For merging a revision range, the following options are available: <placeholder-2/>, <placeholder-3/>. For merging two repository trees, the following options are available: <placeholder-4/>, <placeholder-5/>, <placeholder-6/> and <placeholder-7/>. These pre-fill the relevant fields in the merge dialog.
target: Otvara dijalog stapanja. <placeholder-1/>  specificira ciljni imenik. Za stapanje opsega revizija sledeće opcije su dostupne: <placeholder-2/>, <placeholder-3/>. Za stapanja dva stabla spremišta sledeće opcije su dostupne:  <placeholder-4/>, <placeholder-5/>, <placeholder-6/> i <placeholder-7/>. Ovo pre-popuni relevantna polja u dijalogu stapanja.

note: (entry)
en: Opens the merge all dialog. The <placeholder-1/> specifies the target directory.
target: Otvara dijalog stapanja. <placeholder-1/>  specificira ciljni imenik.

note: (entry)
en: Brings up the branch/tag dialog. The <placeholder-1/> is the working copy to branch/tag from. And the <placeholder-2/> is the target URL. You can also specify the <placeholder-3/> switch to pass a predefined log message to the branch/tag dialog. Or, if you don't want to pass the log message on the command line, use <placeholder-4/>, where <placeholder-5/> points to a file containing the log message.
target: Dovodi grana/znak dijalog. <placeholder-1/>  je radna kopija iz grana-znak. I <placeholder-2/> je cilj URL. Možete takođe specificirati <placeholder-3/>  prekidač da provučete predefinisanu dnevnik poruku do grana/znak dijaloga. Ili, ako ne želite da provučete dnevnik poruku na komandnu liniju, koristite <placeholder-4/>, gde <placeholder-5/> ukazuje na fajl koji sadrži dnevnik poruku.

note: (entry)
en: Opens the settings dialog.
target: Otvara dijalog podešavanja.

note: (entry)
en: Removes the file(s) in <placeholder-1/> from version control.
target: Uklanja fajl(ove) u <placeholder-1/> iz kontrole verzija.

note: (entry)
en: Renames the file in <placeholder-1/>. The new name for the file is asked with a dialog. To avoid the question about renaming similar files in one step, pass <placeholder-2/>.
target: Preimenuje fajl u <placeholder-1/>. Novo ime za fajl pita dijalog. Da se izbegne pitanje o preimenovanju sličnih fajlova u jednom koraku, prevuci <placeholder-2/>.

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

note: (entry)
en: Starts the external diff program specified in the TortoiseSVN settings. The <placeholder-1/> specifies the first file. If the option <placeholder-2/> is set, then the diff program is started with those two files. If <placeholder-3/> is omitted, then the diff is done between the file in <placeholder-4/> and its BASE. To explicitly set the revision numbers use <placeholder-5/> and <placeholder-6/>. If <placeholder-7/> is set and <placeholder-8/> is not set, then the diff is done by first blaming the files with the given revisions.
target: Pokreće spoljašnji diff program specificiran u TortoiseSVN podešavanju. <placeholder-1/>  specificira prvi fajl. Ako je opcija <placeholder-2/> podešena, onda diff program počinje sa ta dva fajla. Ako  je <placeholder-3/> izostavljen, onda diffovi između fajlova u <placeholder-4/> i njenu OSNOVU. Da se eksplicitno podesi broj revizije koristite <placeholder-5/> i <placeholder-6/>. Ako <placeholder-7/> je podešen i <placeholder-8/> nije podešen, onda je diff urađen najpre okrivljavanjem fajlova sa datim revizijama.

note: (para)
en: Depending on the URLs and revisions to compare, this either shows a unified diff (if the option <option>unified</option> is set), a dialog with a list of files that have changed or if the URLs point to files starts the diff viewer for those two files.
target: U zavisnosti od URLa i revizija za poređenje, ovo ili prikazuje diff (ako je opcija <option>ujedinjen</option> podešen), dijalog sa listom fajlova koji su izmenjeni ili ako URL ukazuju na fajlove koji pokreću diff pregledač za ta dva fajla.

note: (para)
en: The options <option>url1</option>, <option>url2</option>, <option>revision1</option> and <option>revision2</option> must be specified. The options <option>pegrevision</option>, <option>ignoreancestry</option>, <option>blame</option> and <option>unified</option> are optional.
target: Opcije  <option>url1</option>, <option>url2</option>, <option>revision1</option> i <option>revision2</option> moraju biti specificirani. Opcije <option>pegrevision</option>, <option>ignoreancestry</option>, <option>blame</option> i <option>unified</option> su opcionalni.

note: (entry)
en: Starts the conflict editor specified in the TortoiseSVN settings with the correct files for the conflicted file in <placeholder-1/>.
target: Pokreće konflikt uređivač specificiran u TortoiseSVN podešavanju sa korektnim fajlovima za konfliktni fajl u <placeholder-1/>.

note: (entry)
en: Opens the relocate dialog. The <placeholder-1/> specifies the working copy path to relocate.
target: Otvara dijalog relociranja. <placeholder-1/> specificira putanju radne kopije za relociranje.

note: (entry)
en: Opens the help file.
target: Otvara fajl pomoći.

note: (entry)
en: Opens the check-for-modifications dialog. The <placeholder-1/> specifies the working copy directory.
target: Otvara proveri-za-izmene dijalog. <placeholder-1/> specificira imenik radne kopije.

note: (entry)
en: Starts the repository browser dialog, pointing to the URL of the working copy given in <placeholder-1/> or <placeholder-2/> points directly to an URL. An additional option <placeholder-3/> can be used to specify the revision which the repository browser should show. If the <placeholder-4/> is omitted, it defaults to HEAD. If <placeholder-5/> points to an URL, the <placeholder-6/> specifies the path from where to read and use the project properties.
target: Pokreće dijalog pretraživača spremišta, ukazuje na URL radne kopije dat u <placeholder-1/> ili <placeholder-2/> ukazuju direktno na URL. Dodatna opcija <placeholder-3/> može biti korišćen da specificira reviziju koju pretraživač spremišta treba da prikaže. Ako <placeholder-4/> nedostaje, uobičajeno ide na GLAVNU. Ako <placeholder-5/> ukazuje na URL, <placeholder-6/>  specificira putanju odakle se čita i koriste karakteristike projekta.

note: (entry)
en: Adds all targets in <placeholder-1/> to the ignore list, i.e. adds the <placeholder-2/> property to those files.
target: Dodaje sve ciljeve u <placeholder-1/> u listu zanemarivanja, tj. dodaje <placeholder-2/> karakteristike tim fajlovima.

note: (para)
en: Opens the blame dialog for the file specified in <option>/path</option>.
target: Otvara dijalog okrivljavanja za fajlove specificirane u <option>/path</option>.

note: (para)
en: If the options <option>/startrev</option> and <option>/endrev</option> are set, then the dialog asking for the blame range is not shown but the revision values of those options are used instead.
target: Ako opcije <option>/startrev</option> i <option>/endrev</option> su podešeni, zatim se poziva dijalog za opseg okrivljavanja koji nije prikazan ali revizione vrednosti ovih opcija su korišćene umesto toga.

note: (para)
en: If the option <option>/line:nnn</option> is set, TortoiseBlame will open with the specified line number showing.
target: Ako je opcija <option>/line:nnn</option> podešena, TortoiseBLAME će se otvoriti sa prikazanim specifičnim brojevima linija.

note: (para)
en: The options <option>/ignoreeol</option>, <option>/ignorespaces</option> and <option>/ignoreallspaces</option> are also supported.
target: Opcije <option>/ignoreeol</option>, <option>/ignorespaces</option> i <option>/ignoreallspaces</option> su takođe podržani.

note: (entry)
en: Saves a file from an URL or working copy path given in <placeholder-1/> to the location given in <placeholder-2/>. The revision is given in <placeholder-3/>. This can be used to get a file with a specific revision.
target: Čuva fajlove iz URL ili imenika radne kopije dat u <placeholder-1/>  ka lokaciji datoj u <placeholder-2/>.  Revizija je data u <placeholder-3/>. Ovo može biti korišćeno da se dobije fajl sa specifičnom revizijom.

note: (entry)
en: Creates a patch file for the path given in <placeholder-1/>.
target: Kreira fajl zakrpu za putanju datu u <placeholder-1/>.

note: (entry)
en: Shows the revision graph for the path given in <placeholder-1/>.
target: Priakzuje revizioni graf za putanju datu u <placeholder-1/>.

note: (entry)
en: Locks a file or all files in a directory given in <placeholder-1/>. The 'lock' dialog is shown so the user can enter a comment for the lock.
target: Zaključava fajl u imeniku datom u <placeholder-1/>. 'Katanac' dijalog je prikazan tako da korisnik može unese urezivanje za katanac.

note: (entry)
en: Unlocks a file or all files in a directory given in <placeholder-1/>.
target: Otključaj fajl ili sve fajlove u imeniku datom u <placeholder-1/>.

note: (entry)
en: Rebuilds the windows icon cache. Only use this in case the windows icons are corrupted. A side effect of this (which can't be avoided) is that the icons on the desktop get rearranged. To suppress the message box, pass <placeholder-1/>.
target: Prerađuje keš ikona prozora. Samo koristite ovo u slučaju da su ikone prozora uništene. Sporedni efekat ovoga je (koji može biti izbegnut) to da ikone na desktopu budu preuređene. Da se spreči boks poruke, provucite <placeholder-1/>.

note: (entry)
en: Shows the properties dialog for the path given in <placeholder-1/>.
target: Prikazuje dijalog karakteristika za putanju u <placeholder-1/>.

note: (para)
en: Examples (which should be entered on one line): <screen>
    TortoiseProc.exe /command:commit
                     /path:"c:\svn_wc\file1.txt*c:\svn_wc\file2.txt"
                     /logmsg:"test log message" /closeonend:0
    
    TortoiseProc.exe /command:update /path:"c:\svn_wc\" /closeonend:0
    
    TortoiseProc.exe /command:log /path:"c:\svn_wc\file1.txt"
                     /startrev:50 /endrev:60 /closeonend:0
    </screen>
target: Primer (koji će biti unet na jednoj liniji): <screen>
    TortoiseProc.exe /command:commit
                     /path:"c:\svn_wc\file1.txt*c:\svn_wc\file2.txt"
                     /logmsg:"test log message" /closeonend:0
    
    TortoiseProc.exe /command:update /path:"c:\svn_wc\" /closeonend:0
    
    TortoiseProc.exe /command:log /path:"c:\svn_wc\file1.txt"
                     /startrev:50 /endrev:60 /closeonend:0
    </screen>

note: (title)
en: TortoiseIDiff Commands
target: TortozIDif komande

note: (para)
en: The image diff tool has a few command line options which you can use to control how the tool is started. The program is called <literal>TortoiseIDiff.exe</literal>.
target: Slike diff alat ima nekoliko opcija komandnih linija koje možete koristiti da kontrolišete kako se alat pokreće. Program se zove <literal>TortoiseIDiff.exe</literal>.

note: (para)
en: The table below lists all the options which can be passed to the image diff tool on the command line.
target: Tabela koja sledi lista svih opcija koje mogu biti prenete u diff slike alatu na komandnoj liniji.

note: (title)
en: List of available options
target: Lista raspoloživih opcija

note: (entry)
en: Option
target: Opcije

note: (entry)
en: Path to the file shown on the left.
target: Putanja do fajla prikazanog  levo.

note: (entry)
en: A title string. This string is used in the image view title instead of the full path to the image file.
target: String naslova. Ovaj string se koristi u naslovu pregledača slika umesto pune putanje fajlova slika.

note: (entry)
en: Path to the file shown on the right.
target: Putanja do fajla prikazanog desno.

note: (entry)
en: If specified, the image diff tool switches to the overlay mode (alpha blend).
target: Ako je specificiran, dif alat slika prebacuje mod prekrivača (alfa mešavina).

note: (entry)
en: If specified, the image diff tool fits both images together.
target: Ako je specificiran, diff alat slike uglavljuje obe slike zajedno.

note: (entry)
en: Shows the image info box.
target: Prikazuje info boks slike.

note: (para)
en: Example (which should be entered on one line): <screen>
    TortoiseIDiff.exe /left:"c:\images\img1.jpg" /lefttitle:"image 1"
                      /right:"c:\images\img2.jpg" /righttitle:"image 2"
                      /fit /overlay
    </screen>
target: Primer (koji treba da bude unet na jednoj liniji): <screen>
    TortoiseIDiff.exe /left:"c:\images\img1.jpg" /lefttitle:"image 1"
                      /right:"c:\images\img2.jpg" /righttitle:"image 2"
                      /fit /overlay
    </screen>

note: (title)
en: Command Line Interface Cross Reference
target: Komandna Linija Interfejs Unakrsne Reference

note: (primary)
en: command line client
target: komand linija klijent

note: (para)
en: Sometimes this manual refers you to the main Subversion documentation, which describes Subversion in terms of the Command Line Interface (CLI). To help you understand what TortoiseSVN is doing behind the scenes, we have compiled a list showing the equivalent CLI commands for each of TortoiseSVN's GUI operations.
target: Ponekad ovo uputstvo ukazuje na glavne Subverzione dokumente, koji opisuju Subverziju u terminima Interfejsa  Komandne Linije (IKL). Da bi vam se pomoglo da razumete šta TortoiseSVN radi iza scene sastavili smo listu koja pokazuje ekvivalentne IKL komande za svaki TortoiseSVN GUI.

note: (para)
en: Even though there are CLI equivalents to what TortoiseSVN does, remember that TortoiseSVN does <emphasis>not</emphasis> call the CLI but uses the Subversion library directly.
target: Bez obzira što postoji IKL ekvivalent na ono što TortoiseSVN radi setite se da TortoiseSVN <emphasis>ne</emphasis> poziva IKL već koristi Subverzionu biblioteku direktno.

note: (para)
en: If you think you have found a bug in TortoiseSVN, we may ask you to try to reproduce it using the CLI, so that we can distinguish TortoiseSVN issues from Subversion issues. This reference tells you which command to try.
target: Ako mislite da ste našli bag u TortoiseSVN, možemo vam zatražiti da pokušate da reprodukujete to koristeći IKL, tako da možemo razdvojiti TortoiseSVN odziv od Subverzionog odiva. Ove reference vam kažu sa kojim komandama da pokušate.

note: (title)
en: Conventions and Basic Rules
target: Konvencije i osnovna pravila

note: (para)
en: In the descriptions which follow, the URL for a repository location is shown simply as <literal>URL</literal>, and an example might be <systemitem class="url">http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk</systemitem>. The working copy path is shown simply as <literal>PATH</literal>, and an example might be <filename>C:\TortoiseSVN\trunk</filename>.
target: U opisu koji sledi, URL za lokaciju spremišta prikazan je jednostavno kao <literal>URL</literal>, i primer može biti <systemitem class="url">http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk</systemitem>. Putanja radne kopije je prikazana jednostavno kao <literal>PUTANJA</literal>, i primer može biti <filename>C:\TortoiseSVN\trunk</filename>.

note: (para)
en: Because TortoiseSVN is a Windows Shell Extension, it is not able to use the notion of a current working directory. All working copy paths must be given using the absolute path, not a relative path.
target: Pošto je TortoiseSVN Vindouz Ekstenzija Školjke, nje moguće koristiti pojam tekućeg radnog direktorijuma. Sve putanje radne kopije moraju biti date koristeći apsulutnu putanju, ne realnu putanju.

note: (para)
en: Certain items are optional, and these are often controlled by checkboxes or radio buttons in TortoiseSVN. These options are shown in [square brackets] in the command line definitions.
target: Neke stavke su opcionalne i one su često kontrolisane čekboksovima ili radio dugmićima u TortoiseSVn. Ove opcije su prikazane u  [srednjim zagradama] u definiciji komandne linije.

note: (para)
en: If <guilabel>Only checkout the top folder</guilabel> is checked, use the <literal>-N</literal> switch.
target: Ako je <guilabel>Preuzmi samo vršni imenik</guilabel> čekirano, koristite <literal>-N</literal> prekidač.

note: (para)
en: If <guilabel>Omit externals</guilabel> is checked, use the <literal>--ignore-externals</literal> switch.
target: Ako je <guilabel>Izostavi spoljašnje</guilabel>  čekirano, koristite <literal>--ignore-externals</literal> prekidač.

note: (para)
en: If you are checking out a specific revision, specify that after the URL using <literal>-r</literal> switch.
target: Ako preuzimate specifičnu reviziju, specificirajte to posle URL koristeći <literal>-r</literal> prekidač.

note: (para)
en: Updating multiple items is currently not an atomic operation in Subversion. So TortoiseSVN first finds the HEAD revision of the repository, and then updates all items to that particular revision number to avoid creating a mixed revision working copy.
target: Ažuriranjem višestrukih stavki trenutno nije atomik operacija u Sbverziji. TortoiseSVN prvo nađe GLAVNU reviziju spremišta, zatim ažurira sve stavke ka tom posebnom revizionom broju da izbegne radnu kopiju pomešanih revizija.

note: (para)
en: If only one item is selected for updating or the selected items are not all from the same repository, TortoiseSVN just updates to HEAD.
target: Ako je samo jedna stavka odabrana za ažuriranje ili odabrane stavke nisu sve iz istog spremišta, TortoiseSVN samo ažurira do GLAVE.

note: (para)
en: No command line options are used here. <guilabel>Update to revision</guilabel> also implements the update command, but offers more options.
target: Ovde se ne koriste opcije komandne linije. <guilabel>Ažuriraj u reviziju</guilabel> takođe primenjuje komandu ažuriralja, ali često više opcija.

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

note: (para)
en: If <guilabel>Only update the top folder</guilabel> is checked, use the <literal>-N</literal> switch.
target: Ako je <guilabel>Samo ažuriraj vršni imenik</guilabel> čekirano, koristite <literal>-N</literal> prekidač.

note: (para)
en: In TortoiseSVN, the commit dialog uses several Subversion commands. The first stage is a status check which determines the items in your working copy which can potentially be committed. You can review the list, diff files against BASE and select the items you want to be included in the commit.
target: U TortoiseSVN, dijalog urezivanja koristi više Subverzionih komandi. Prvi period je provera statusa koja određuje stavke u vašoj radnoj kopiji koje mogu biti potencijalno urezanje. Možete vratiti listu, diff fajlovi nasuprot OSNOVE i izabrati stavke koje želite da budu uključene u urezivanje.

note: (para)
en: If <guilabel>Show unversioned files</guilabel> is checked, TortoiseSVN will also show all unversioned files and folders in the working copy hierarchy, taking account of the ignore rules. This particular feature has no direct equivalent in Subversion, as the <literal>svn status</literal> command does not descend into unversioned folders.
target: Ako je <guilabel>Prikaži neverzionisane fajlove</guilabel> čekirano, TortoiseSVn će takođe prikazati sve neverzionisane fajlove i imenike u hijerarhiji radne kopije, uzimajući u obzir pravila zanemarivanja. Ova posebna osobina nema direktni ekvivalent u Subverziji, kao što < literal>svn status</literal>  komanda ne silazi u neverzionisane imenike.

note: (para)
en: If you check any unversioned files and folders, those items will first be added to your working copy.
target: Ako proverite neke neverzionisane fajlove i imenike, te stavke će prvo biti dodate u vašu radnu kopiju.

note: (para)
en: When you click on OK, the Subversion commit takes place. If you have left all the file selection checkboxes in their default state, TortoiseSVN uses a single recursive commit of the working copy. If you deselect some files, then a non-recursive commit (<literal>-N</literal>) must be used, and every path must be specified individually on the commit command line.
target: Kada kliknete OK, Subverziono urezivanje počinje. Ako ostavite sve selekcione čekboksove fajlova u njihovom uobičajenom stanju, TortoiseSVN koristi jedno rekurzivno urezivanje radne kopije. Ako deselektujete neke fajlove, onda ne-rekurzivno urezivanje (<literal>-N</literal>) mora da bude uzeto, i svaka putanja mora biti specificirana individualno u komandnoj liniji urezivanja.

note: (para)
en: <literal>LogMessage</literal> here represents the contents of the log message edit box. This can be empty.
target: <literal>LogMessage</literal> ovde redstavlja sadržaj dnevnik poruke boksa uređenja. Ovo može biti prazno.

note: (para)
en: If <guilabel>Keep locks</guilabel> is checked, use the <literal>--no-unlock</literal> switch.
target: Ako je  <guilabel>Keep locks</guilabel> čekirano, koristite <literal>--no-unlock</literal> prekidač.

note: (para)
en: If you use Diff from the main context menu, you are diffing a modified file against its BASE revision. The output from the CLI command above also does this and produces output in unified-diff format. However, this is not what TortoiseSVN is using. TortoiseSVN uses TortoiseMerge (or a diff program of your choosing) to display differences visually between full-text files, so there is no direct CLI equivalent.
target: Ako koristite Diff iz glavnog kontekst menija vi razlikujete izmenjene fajlove rema OSNOVNOJ reviziji. Izlaz iz IKL komande u ranijem tekstu takođe radi ovo i proizvodi izlaz u ujedinjeni-diff formatu. Međutim, ovo nije to što TortoiseSVN koristi. TortoiseSVN koristi ToroiseMerge (ili diff program koji ste izabrali) da prikaže razlike vizualno između pun-tekst fajlova, tako da nema IKL ekvivalenta.

note: (para)
en: You can also diff any 2 files using TortoiseSVN, whether or not they are version controlled. TortoiseSVN just feeds the two files into the chosen diff program and lets it work out where the differences lie.
target: Možete takođe diff neka dva fajla koristeći TortoiseSVN, da li su ili nisu pod kontrolom verzija. TtortoiseSVN smo unese dva fajla u izabrani diff program i pušta ga da traži gde leže razlike.

note: (para)
en: By default, TortoiseSVN tries to fetch 100 log messages using the --limit method. If the settings instruct it to use old APIs, then the second form is used to fetch the log messages for 100 repository revisions.
target: Uobičajeni, TortoiseSVN pokušava da nađe 100 dnevnik poruka koristeći  --limit metod. Ako podešavanje zahteva da se koristi stari API, onda druga forma se koristi da se nađe dnevnik poruka za 100 revizija spremišta.

note: (para)
en: If <guilabel>Stop on copy/rename</guilabel> is checked, use the <literal>--stop-on-copy</literal> switch.
target: Ako je <guilabel>Stop na kopiraj/preimenuj</guilabel> čekirano, koristite <literal>--stop-on-copy</literal> prekidač.

note: (para)
en: The initial status check looks only at your working copy. If you click on <guibutton>Check repository</guibutton> then the repository is also checked to see which files would be changed by an update, which requires the <literal>-u</literal> switch.
target: Početna provera statusa gleda samo u vašu radnu kopiju. Ako kliknete na <guibutton>Proveri spremište</guibutton> zatim se spremište takođe proveri da se vidi  koji fajlovi će biti izmenjeni ažuriranjem, što zahteva <literal>-u</literal> prekidač.

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

note: (para)
en: The revision graph is a feature of TortoiseSVN only. There's no equivalent in the command line client.
target: Revizioni graf je mogućnost samo TortoiseSVN. Nema ekvivalenta u klijentu komande linije.

note: (para)
en: What TortoiseSVN does is an <screen>
    svn info URL_of_WC
    svn log -v URL
    </screen> where URL is the repository <emphasis>root</emphasis> and then analyzes the data returned.
target: Ono što TortoiseSVN radi je <screen>
    svn info URL_of_WC
    svn log -v URL
    </screen> gde je URL spremište <emphasis>koren</emphasis> i onda analizira vraćene podatke.

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

note: (para)
en: You can use <literal>svn info</literal> to determine the repository root, which is the top level shown in the repository browser. You cannot navigate <literal>Up</literal> above this level. Also, this command returns all the locking information shown in the repository browser.
target: Možete koristiti <literal>svn info</literal> da odredite koren spremišta, koji je na vršnom nivou prikazan u pretraživaču spremišta. Ne možete se kretati  <literal>Gore</literal> iznad ovog nivoa. Takođe, ova komanda vraća sve informcije o zaključavanju prikazane u pretraživaču spremišta.

note: (para)
en: The <literal>svn list</literal> call will list the contents of a directory, given a URL and revision.
target: Poziv <literal>svn list</literal> će izlistati sadržaj imenika datog sa URL i revizijom.

note: (para)
en: This command has no CLI equivalent. It invokes TortoiseMerge or an external 3-way diff/merge tool to look at the files involved in the conflict and sort out which lines to use.
target: Ova komanda im IKL ekvivalent. Ona poziva TortoiseMerge ili neki spoljašnji 3-načina diff-stopi alat da vidi u fajlovima obuhvaćenih konfliktima i uređuje koje linije da se koriste.

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

note: (para)
en: The first stage is a status check which determines the items in your working copy which can potentially be reverted. You can review the list, diff files against BASE and select the items you want to be included in the revert.
target: Prvi stepen je provera statusa koja određuje stavke u vašoj radnoj kopiji koje će potencijalno biti vraćene. Možete pregledati listu, diff fajlovi nasuprot OSNOVE, i izabrati stavke koje želite da uključite u vraćanje.

note: (para)
en: When you click on OK, the Subversion revert takes place. If you have left all the file selection checkboxes in their default state, TortoiseSVN uses a single recursive (<literal>-R</literal>) revert of the working copy. If you deselect some files, then every path must be specified individually on the revert command line.
target: Kada kliknete OK, Subverziono vraćanje se dešava. Ako ostavite izbor fajlova čekboks u uobičajenom statusu, TortoiseSVN koristi pojedinačno rekurzivno (<literal>-R</literal>) vraćanje radne kopije. Ako deselektujete neke fajlove, onda svaka putanja mora biti specificirana individualno u komandnoj liniji vraćanja.

note: (title)
en: Get Lock
target: Zaključaj

note: (para)
en: The first stage is a status check which determines the files in your working copy which can potentially be locked. You can select the items you want to be locked.
target: Prva faza u proveri statusa koja određuje fajlove u vašoj radnij kopiji koji će potencijalno biti zaključani. Možete izabrati stavke koje želite da budu zaključane.

note: (para)
en: <literal>LockMessage</literal> here represents the contents of the lock message edit box. This can be empty.
target: <literal>LockMessage</literal> ovde predstavlja sadržaj katanac poruka boks uređenja. On može biti prazan.

note: (para)
en: If <guilabel>Steal the locks</guilabel> is checked, use the <literal>--force</literal> switch.
target: Ako je <guilabel>Ukrasti katance</guilabel> čekiran, koristite <literal>--force</literal> prekidače.

note: (title)
en: Release Lock
target: Skini Katanac

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

note: (para)
en: The Branch/Tag dialog performs a copy to the repository. There are 3 radio button options: <placeholder-1/> which correspond to the 3 command line variants above.
target: Grana/Znak dijalog omogućava kopiranje u spremište. Postoje 3 radio dugmeta opcija: <placeholder-1/> koje odgovaraju 3 varijante komandnih linija gore.

note: (para)
en: The <guibutton>Dry run</guibutton> performs the same merge with the <literal>--dry-run</literal> switch.
target: <guibutton>Čist rad</guibutton> omogućava isto stapanje kao <literal>--dry-run</literal> prekidač.

note: (para)
en: The <guibutton>Unified diff</guibutton> shows the diff operation which will be used to do the merge.
target: <guibutton>Ujedinjene diff</guibutton> prikazuju diff operaciju koja će biti korišćena za stapanje.

note: (para)
en: This form is used when accessed from an unversioned folder, and the folder is used as the destination.
target: Ovaj oblik se koristi kada se pristupa iz neverzionisanog imenika, i imenik se koristi kao odredište.

note: (para)
en: Exporting a working copy to a different location is done without using the Subversion library, so there's no matching command line equivalent.
target: Izvozom radne kopije u različitu lokaciju dato je bez korišćenja Subverzione biblioteke, tako da nema odgovarajućeg ekvivalenta komandne linije.

note: (para)
en: What TortoiseSVN does is to copy all files to the new location while showing you the progress of the operation. Unversioned files/folders can optionally be exported too.
target: Ono što TortoiseSVN radi je da kopira sve fajlove u novu lokaciju dok prikazuje progres operacije. Neverzionisani fajlovi/imenici mogu neobavezno biti takođe izvezeni.

note: (para)
en: In both cases, if <guilabel>Omit externals</guilabel> is checked, use the <literal>--ignore-externals</literal> switch.
target: U oba slučaja, ako je <guilabel>Nedostaju eksternali</guilabel> čekiran, koristite <literal>--ignore-externals</literal> prekidač.

note: (title)
en: Create Repository Here
target: Kreuraj spremište ovde

note: (para)
en: If you selected a folder, TortoiseSVN first scans it recursively for items which can be added.
target: Ako izaberete imenik, TortoiseSVN prvo pregleda sve rekurzivno za stavke koje mogu biti dodate.

note: (para)
en: If you use TortoiseBlame to view the blame info, the file log is also required to show log messages in a tooltip. If you view blame as a text file, this information is not required.
target: Ako koristite TortoiseBlame da vidite info okrivljavanja, fajl dnevnik je takođe potreban da prikaže dnevnik poruke u alatsavetu. Ako vidite okrivljavanje kao tekst fajl ova informacija nije potrebna.

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

note: (para)
en: Because the <literal>svn:ignore</literal> property is often a multi-line value, it is shown here as being changed via a text file rather than directly on the command line.
target: Zato što  <literal>svn:ignore</literal>  osobina je često viš-linijska vrednost, to je ovde prikazano kao da je izmenjena preko tekat fajla radije nego direktno u komandnoj liniji.

note: (para)
en: TortoiseSVN creates a patch file in unified diff format by comparing the working copy with its BASE version.
target: TortoiseSVN kreira fajl zakrpu u ujedinjenom diff formatu poredeći radnu kopiju sa OSNOVNOM verzijom.

note: (para)
en: Applying patches is a tricky business unless the patch and working copy are at the same revision. Luckily for you, you can use TortoiseMerge, which has no direct equivalent in Subversion.
target: Primena zakrpa je trik posao sve dok zakrpa i radna kopija su iste revizije. Srećom za vas, možete koristiti TortoiseMerge, koji nema direktni ekvivalent u Subverziji.

note: (title)
en: Implementation Details
target: Implementacioni detalji

note: (primary)
en: overlay priority
target: prioritet prekrivanja

note: (title)
en: Securing Svnserve using SSH
target: Osiguranje Svnserva koristeći SSH

note: (title)
en: Setting Up a Linux Server
target: Podešavanje Linuks servera

note: (title)
en: Setting Up a Windows Server
target: Podešavanje Vindouz servera

note: (title)
en: SSH Client Tools for use with TortoiseSVN
target: SSJ klijent alat za korišćenje sa TortoiseSVN

note: (title)
en: Creating OpenSSH Certificates
target: Kreiranje OpenSSH certifikata

note: (title)
en: Create Keys using ssh-keygen
target: Kreiranje tastera koristeći ssh-kijgen

note: (title)
en: Create Keys using PuTTYgen
target: Kreiranje tastera korišćenjem PuTTIgen

note: (title)
en: Test using PuTTY
target: Test koristeći PuTTI

note: (title)
en: Testing SSH with TortoiseSVN
target: Testiranje SSH sa TortoiseSVN

note: (title)
en: SSH Configuration Variants
target: SSH konfiguracione varijante

note: (title)
en: Glossary
target: Pojmovnik

note: (glossterm)
en: BASE revision
target: OSNOVNA revizija

note: (glossterm)
en: Branch
target: Grana

note: (glossterm)
en: Conflict
target: Konflikt

note: (glossterm)
en: Copy
target: Kopiraj

note: (para)
en: Group policy object
target: Objekat grupne polise

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

note: (glossterm)
en: Log
target: Dnevnik

note: (glossterm)
en: History
target: Istorija

note: (glossterm)
en: Patch
target: Zakrpa

note: (glossterm)
en: Property
target: Svojstvo

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

note: (glossterm)
en: Revision
target: Revizija

note: (glossterm)
en: Revision Property (revprop)
target: Osobine revizije (revosob)

note: (para)
en: A frequently-used abbreviation for Subversion.
target: Često-koriišćene skraćenice u Subverziji

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

note: Place the translation of 'translation' here. (None)
en: translator-translation
target: Prevod
