TSVN poChecker

This tool, to be used before committing your work, should help you locate problems in translation files. Please consider it as work-in-progress, as we are still working on it.

First of all, it will help you find missing accelerators - Luebbe's translation status page shows counts but not strings themselves, so the table below will help you fix these problems.

The analysis also includes some other useful lists, it checks for instance for correct new line styles, untranslated strings and spelling mistakes. As we prefer to err on the side of caution, you may find a lot of false positives. Anyway I hope this will help you improve the quality of your translation.

Oto

---

---

For new translators

Please follow this link if you think you may help with translation.
-> TortoiseSVN translation

---

Precommit checker

You can upload file for check before you make actual commit, so you can fix errors in one commit.

Make sure you are going to check translation against proper branch.

Choose a file to upload:

---

Revision: 20088 of trunk

Last update: September 05 2010 17:08 CET (GMT+1/GMT+2(DST))
Go to STABLE.

Language	GUI check								DOC		Author(s)
	Flag	PAR!!	ACC!	NLS	UNT	FUZ	ESC	Note
Croatian				1	59	47			-	59/47	Helix d.o.o: (Dinko Srkoc, Mario Saric), Boris Musa, Dusko Vuksanovic, Ivan Vucica

---

GUI history graph:

---

TSVN doc history graph:

---

TMerge doc history graph:

---

Revision: 20088

PO Check (hr)

Parameter strings test

This test is necessary to pass or you can expect crashing of TSVN - specially true when you use longer type as is in English like %s instead of %d, %ld instead of %d, etc. Also having more parameters lead to crash TSVN. When TSVN not crash, the information is still wrong. For example number instead of text.

PASS

Missing/Unexpected Key Accelerator test

This is accessibility test. Passing this test is recommended. If you are interesting in more details about accelerator key overlapping I may enable such test for your language, but in fact there not too much to do against it. According Luebbe and Stefan there is no problem about it you just have to use accelerator more time to select element and then use enter or space for activate button.

PASS

Differences in new line style

This tests if new line style from pot match localized new line style. This test may have false positives when English text has new line style inconsistence. Using more lines for Native when English use just one is also alowed for most of translation even here reported.

Index	Line	English	Line	Native
1	1287	translator-credits	1287	Mario Šarić <mario.saric@helix.hr>\n Dinko Srkoč <dinko.srkoc@helix.hr>

^{Note: Line numbers are as in committed file, it may differ when you update to use newer .pot, also edited multi line messages may shift line position.}

Total:1

Not translated strings test

This tests if all strings has been translated. Translated mean that there in native string set. If English and native are same it is not marked as not translated, this just can happen.

Index	Line	English	Line
1	22	Version $MajorVersion$.$MinorVersion$.$MicroVersion$	40
2	86	TortoiseMerge 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 http://code.google.com/p/tortoisesvn/source/browse/. The most recent version (where we're currently working) is located under /trunk/, and the released versions are located under /tags/.
3	187	While working on TortoiseSVN we found that whenever users sent in patches to enhance the project or just to fix bugs, we had a lot of work just applying those patches. And many times those patches were outdated and couldn't be applied with the command line patch tool http://unxutils.sourceforge.net/ because we were working on those files and had sometimes changed those files already.
4	227	In this mode you are comparing two files. The file in the left pane is considered to be the original file (sometimes referred to as Theirs, and the file in the right pane is the modified file (sometimes referred to as Mine.	256
5	231	Reverting changed lines back to the text shown in the left pane.	260
6	235	Using a combination of both blocks, either Theirs before Mine or Mine before Theirs.	264
7	243	You can also edit the file in the right pane just as you would in a text editor. Such lines are marked using a pencil icon. Please note that if you want to make any of the line/block-based changes described above, it is better to do those first since once you start editing the file yourself it becomes impossible for TortoiseMerge to keep track of the relationship to the original files.	273
8	251	This is sometimes referred to as a three-way merge, and is shown in three panes. However there are actually four files involved. The file which is not shown is the common base file, the last common ancestor of the two files which are now in conflict. The relationships between the three files are explained in the diagram below:	282
9	259	In conflict resolution view, you can choose to use blocks from Mine or Theirs or both. But in this case, the changes are shown in the bottom pane.	291
10	269	A patch file is a Subversion unified diff file, which contains the information required to apply changes to a set of files. The patch may have been supplied by another developer so that you can see changes he has made and possibly commit them to the repository. Or it may have been generated internally by TortoiseSVN when comparing two folders. This happens when you compare a repository revision with your working copy folder, or if you compare two different repository revisions, or if you compare two different repository paths.	301
11	273	In either case TortoiseMerge will show a small window listing the files included in the patch. By double clicking on one of these files you fetch the relevant file and apply the changes. The left pane shows the original file content and the right pane shows it after the patch is applied.	305
12	277	You can edit the file in the right pane exactly as you would in compare/edit mode.	309
13	289	TortoiseMerge has three main viewing modes: one-pane, two-pane and three-pane view. One/two-pane view is used to view changes and three-pane view is used to resolve conflicts.	322
14	318	Hand editing of the file in the right pane is possible in two-pane view. Such changes are marked with a pencil symbol.	352
15	338	If you hover the mouse over the pane title, a tooltip will show the filenames used for the diff in each pane.	373
16	382	Undo implements a multi-level undo, allowing you to reverse any changes you have made within TortoiseMerge.	423
17	398	Use Theirs/Use Mine selects whether to use a block from the left or the right pane. Refer to the next section for more information about editing changes and conflicts.	439
18	402	Theirs before Mine/Mine before Theirs is used when you want to combine changes in a conflicted file. Refer to the next section for more information about editing changes and conflicts.	443
19	414	Wrap long lines toggles the word wrapping at the end of the views. If turned on, long lines which would normally extend beyond the view border are wrapped around, i.e., one long line is split into serveral lines.
20	418	Inline Diff Word-wise toggles the method used to display inline diffs. In word-wise mode, when a character is changed, the whole word is highlighted. In char-wise mode, each individual changed character is highlighted.	456
21	422	Word-wise is the default and in most cases it works better. For example if you change a variable name, the whole name is highlighted in word-wise mode, whereas in char-wise mode you tend to get a mess of added and deleted characters which doesn't make much sense. However, some content does not resolve neatly into words, for example a hex file, and in that case, char-wise display works better.	460
22	426	Compare whitespaces shows all changes in indentation and inline whitespace as added/removed lines (which is how Subversion treats such changes).
23	430	Ignore whitespace changes hides 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.
24	434	Ignore all whitespaces hides all whitespace-only changes.
25	450	Collapse collapses unchanged regions to a single line, leaving only the changed areas and minimal context. You can expand the collapsed areas by double clicking on the collapse line, but you cannot then re-collapse them unless you reload the file.
26	458	Help opens the TortoiseMerge help file, of course.
27	474	Line Status Icons	493
28	478	Changed lines are marked with an icon to indicate what type of change has occurred.	497
29	482	A line has been added.	501
30	486	A line has been removed.	505
31	490	A change has been undone by reverting to the original content of the line.	509
32	494	This line contains only whitespace changes. Where several consecutive lines are marked, the paragraph may have been re-wrapped, causing words to shuffle onto adjacent lines.	513
33	498	A line has been edited by hand, using TortoiseMerge as a text editor.	517
34	502	This line is in conflict.	521
35	506	This line is conflicted, but the effect is hidden by whitespace or line-ending settings.	525
36	522	Sometimes you actually want both text blocks, and the context menu also offers you Context MenuUse both text blocks (this one first) and Context MenuUse both text blocks (this one last).	541
37	526	You can also edit the output file just as you would in a text editor. Such lines are marked using a pencil icon. Please note that if you want to make any of the line/block-based changes described above, it is better to do those first since once you start editing the file yourself it becomes impossible for TortoiseMerge to keep track of the relationship to the original files.	545
38	534	Sometimes a file will be marked as conflicted in Subversion, yet when you view it using TortoiseMerge there are no conflicts shown. This may be due to the whitespace handling you have chosen. If you choose to ignore line-endings or whitespace changes, those lines will be marked using the Conflict-Ignored icon. To resolve the conflict you still need to pick which version you want to use.	553
39	606	Colour code in-line changes uses the same scheme as the line diff bar to show the detailed in-line changes within the main display panes. Lines which have been heavily modified will not be shown using this method as the results are simply confusing. In this case the line will be shown as replaced (old line deleted, new line added).	631
40	658	Modified	686
41	662	unchanged	690
42	666	Colour code in-line changes	694
43	670	Lines which have relatively small changes, and are shown using inline diff. This colour is used for the portion of the line content. Changed portions will be shown using the inline added and deleted colours described below. If is not enabled, this colour will not be used and changed lines will always be shown as replacements.	698
44	698	Inline added text	728
45	702	When inline diffs are shown, added text is shown in this colour.	732
46	706	Inline removed text	736
47	710	When inline diffs are shown, deleted text is shown in this colour.	740
48	714	Misc whitespaces	744
49	718	Characters used to indicate Whitespace are shown in a different colour from normal text.	748
50	782	F7	813
51	798	F8	830
52	970	/origfile:\"path_to_original_file\"	1013
53	974	/modifiedfile:\"path_to_modified_file\"	1017
54	978	/outfile:\"path_to_resulting_patchfile\"	1021
55	982	/outfile	1025
56	986	/createunifieddiff	1029
57	990	Creates a unified diff file (patch file) of two files specified with and . The target path is set with . If is not set, a file save dialog is shown so the user can choose the location to save the patch file. Note: If is set, all other parameters are ignored.	1033
58	994	Specifies a line number to jump to after loading the files.	1037
59	998	You can also supply simple filenames on the command line for compatibility with other diff programs. In this simplified form the command line is \n TortoiseMerge BaseFilePath MyFilePath [ TheirFilePath ]\n If two files are given they will be compared with each other. If three files are given, the first is taken as the BASE file, and the other two are compared with it in a three-way diff.	1041

^{Note: Line numbers are as in committed file, it may differ when you update to use newer .pot, also edited multi line messages may shift line position.}

Total:59

Fuzzy mark test

String marked as fuzzy is not in final shape.

Index	Line	English	Line	Native
1	-	Large	68	Stapanje
2	-	When working on a project, either an open-source project where several people review your code, or a commercial project where you sell a component with your source code, there will be people and customers who find bugs or want to improve your project. To do that they send you patches which you have to review and decide if you want to apply them.	77	U izradi projekata, bilo open-source gdje nekoliko osoba pregledava novi kod, ili u komercijalnim projektima uvijek će postojati korisnici koji će pronalaziti greške ili će htjeti nekako pomoći projektu. Da bi to ostvarili slati će zakrpe koje će trebati pregledati i odlučiti da li ih želite prihvatiti, tj. primjeniti.
3	-	TortoiseMerge 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 http://tortoisesvn.tigris.org/svn/tortoisesvn/. You will be prompted to enter username and password. The username is guest, and the password must be left blank. The most recent version (where we're currently working) is located under /trunk/, and the released versions are located under /tags/.	106	TortoiseMerge je Open Source projekt. To znači da imate potpuni pristup izvornom kodu programa. Možete ga pogledati na ovom linku http://tortoisesvn.tigris.org/svn/tortoisesvn/. (Korisnik guest, password ostavite prazno)Najnovija razvojna verzija (na kojoj trenutno radimo) je smještena na stazi /trunk/, a zadnja gotova verzija se nalazi u /tags/.
4	-	While working on TortoiseSVN we love to listen to music. And since we spend many hours on the project we need a lot of music. Therefore we have set up some wish-lists with our favourite music CDs and DVDs: http://tortoisesvn.tigris.org/donate.html Please also have a look at the list of people who contributed to the project by sending in patches or translations.	119	Dok radimo na TortoiseSVN volimo slušati muziku. I kako provodimo mnoge sate na projektu potrebno nam je puno muzike. Zato smo postavili popis želja s odabranim glazbenim CD-ima i DVD-ovima: http://tortoisesvn.tigris.org/donate.html Molimo Vas da također da pogledate popis osoba koje doprinose projektu tako što šalju zakrpe ili prijevode.
5	-	for the beautiful icons, logo, bug hunting and taking care of the documentation	140	za divne ikone, logo, istjerivanje buha i brigu o dokumentaciji
6	-	A conflict can also occur if you try to apply an outdated patch file. In such cases, without TortoiseMerge, you would either have to ask the person you got that patch file from for a current version or try to apply that patch file manually.	198	Sukob se može dogoditi ako pokušate primjeniti zastarjele zakrpe. U tim slučajevima, bez TortoiseMergea, morali biste tražiti osobu od koje ste dobili zakrpu da vam pošalje trenutnu verziju ili pokušati primjeniti zakrpu ručno.
7	-	But now with TortoiseMerge this isn't necessary anymore - at least not if you're working with a version control system like Subversion. TortoiseMerge parses the patch file for the revision/version the patch was created for and automatically tries to fetch that specific version from your source-control. Then it applies the patch and lets you review both your changes to the file, and theirs. Then you can decide which changes you want to keep.	203	No ako koristite Subversion ili TortoiseMerge to više nije potrebno. TortoiseMerge parsira zakrpu kako bi pronašao verziju za koju je zakrpa namijenjena i automatski pokušava dobaviti tu verziju iz skladišta verzija. Tada primijenjuje zakrpu i omogućava vam pregled promjena \"pokrpanoj\" datoteci i vaših promjena. Vi tada odlučujete koje promjene želite zadržati.
8	-	So we spent a lot of time, searching the Internet for a GUI tool which could apply patch files, but all we found was that such a tool didn't exist. So to cut a long story short: We decided that if no-one else could provide such a tool we would have to write our own. That's when TortoiseMerge was born.	220	Tada smo potrošili dosta vremena u potrazi za GUI alatom kojim bismo mogli primjenti zakrpe, ali sve što smo našli na internetu bilo je da takav alat ne postoji. Da skratimo priču: Odlučili smo da ovakav alat sami napišemo. Tako se rodio TortoiseMerge.
9	-	Since TortoiseSVN already uses the Subversion library, which has a nice diffing engine built in, it was just natural to use this library instead of the GNU diff.	225	Kako TortoiseSVN već upotrebljava Subversion library, koji ima ugrađene spretne razlikovne algoritme, bilo je prirodno da koristimo tu zbirku umjesto GNU programa za razlike. Tako smo dobili uštedu na veličini datoteka programa jer su TortoiseSVN i TortoiseMerge upotrebljavali iste dll-ove.
10	-	TortoiseMerge has several different uses:	246	TortoiseMerge pomaže u oba zadatka:
11	-	Viewing and Merging Differences	251	Pregled / Stapanje
12	-	You can make simple line-based changes to the file in the right pane which include:	268	Dvostrani pogled ima neke mogućnosti koje nisu dostupne u jednostrukom pogledu:
13	-	Editing Conflicts	277	Stapanje / Uređivanje sukoba
14	-	The base file represents the oldest version of a file, from where You and They start making changes. Mine represents the base file with all the changes you made, and Theirs is the file with all the changes someone else made to the file. The left pane shows the changes in Theirs relative to the base file and the right pane shows the changes in Mine relative to the base file. The bottom pane is the output file which is where you are trying to resolve the conflicts.	286	Osnova predstavlja najstariju verziju datoteke od koje ste Vi i Oni počeli raditi izmjene. Moja datoteka predstavlja osnovnu datoteku sa svim promjena koju ste vi napravili, a Njihova je datoteka sa svim promjenama koje je netko drugi napravio na datoteci.
15	-	Viewing Modes	317	Pregled / Stapanje
16	-	Such changes are marked with a white circle symbol on the left side of the views. If you see such a white circle, you know immediately that no real code change is there and you don't have to check the changed block further.	347	Takve promjene su označene bijelim kružnim simbolom na lijevoj strani. Ako vidite takav simbol, odmah znate da tu nema pravih promjena i ne morate provjeravati taj blok.
17	-	The left pane shows you the differences between Their file and the Base file, while the right pane shows you the differences between Mine file and the Base file. The bottom pane shows you the result of merging Base, Mine and Theirs with possible conflicts.	368	Lijevi okvir pokazuje razlike između Njihove datoteke i Osnove, dok desni okvir pokazuje razlike između Moje datoteke i Osnove. Donji okvir pokazuje rezultat stapanja sve tri datoteke (Osnove, Moje i Njihove sa mogućim sukobima. Ako pređete mišem iznad naslova nekog okvira, pojavit će se imena datoteka koje su korištene za razlike prikazane u tom okviru.
18	-	Patch File List	377	Popis zakrpi
19	-	After TortoiseMerge parses the patch file it will show you a small window with all the files which have changes according to the patch file. If the filename is shown in black, then the patch can be applied without any problems. That means the file is not outdated according to the patch. However, if the filename is shown in red, then the patch can't get applied directly because you already changed that file.	382	Ako TortoiseMerge može parsirati zakrpu pokazat će se mali prozor sa svim datotekama koje su se promijenile prema odabranoj zakrpi. Ako je datoteka navedena crnim slovima, tada se zakrpa može primjeniti bez problema. To znači da datoteka nije zastarjela. Kad je datoteka u popisu navedena crvenim slivma, zakrpa se ne može direktno primjeniti jer ste datoteku i sami mijenjali.
20	-	But don't worry. If you're working with Subversion you can retrieve an older version of the file and resolve the conflict. In fact, TortoiseMerge automatically tries to get that older version of the file and then shows you the diff between Base (the older version of the file), Mine (the file as it is currently in your working copy) and Theirs (the older version of the file with the patch already applied). Then you can resolve possible conflicts manually.	387	No, ne brinite. Ako ste radili sa Subversion-om, možete dobaviti stariju verziju datoteke i razriješiti sukob. U stvari, TortoiseMerge automatski pokušava dobiti stariju datoteku i prikazuje razlike izmjeđu Osnove (starija verzija datoteke) i Moje i Njihove datoteke. Tada možete ručno razrijšti moguće sukobe.
21	-	The patch file window has a context menu which allows you to preview the effect of the patch on the current file (apply without saving), to apply and save the changes for the selected file, or to apply and save changes to all files in the list. The double-click action is to preview.	392	Prozor ima izbornik okoline koji omogućava da pregledate rezultat \"krpanja\" (primjene zakrpe), a također i da snimite promjene na odbaranoj datoteci ili da primjenite zakrpe i snimite sve datoteke iz popisa. Duplim klikom dobivate pregled zakrpane datoteke.
22	-	Save saves any changes you have made.	413	Ponovo učitaj odbacuje sve promjene i ponovo učitava datoteke.
23	-	Reload discards any changes you have made in TortoiseMerge and reloads the files from disk.	418	Ponovo učitaj odbacuje sve promjene i ponovo učitava datoteke.
24	-	Show Whitespaces toggles the option to display space and tab characters as symbols so you can distinguish white space changes.	451	Pokaži razmake klacka opciju za pokazivanje razmaka i tabova kao simbola, tako da možete razlikovati razlike u razmacima.
25	-	Below the bottom window is the status bar. This shows the number of lines added and deleted in Theirs and Mine, and the number of unresolved conflicts remaining. You can also see which line-ending style is in use, what encoding (ASCII, UTF-8, etc) is assumed by TortoiseMerge, and whether there is a byte-order-mark (BOM) present in UTF-8 files. The left side of the status bar is used to display hints when you hover the mouse over a control.	488	Ispod donjeg okvira nalazi se traka statusa. Ona pokazuje broj redaka koji su dodani i obrasani u Njihovoj i Mojoj datoteci, a također i broj preostalih neriješenih sukoba. Lijeva strana trake statusa se koristi za ispis savjeta kada se miš nalazi iznad neke kontrole.
26	-	The first thing you have to do is to decide whether you just want to compare/merge files, or whether you want to apply a patch file. Depending on what you choose, the corresponding edit boxes and browse buttons are activated.	577	Prva stvar koju trebate napraviti jest odluka da li želite usporediti ili stopiti dvije verzije iste datoteke, ili želite primjeniti zakrpu. Ovisno o toj odluci, aktiviraju se odgovarajuće komponente na dijalogu.
27	-	If you want to compare / merge files you have to set at least two of the three possible paths for Base, Mine and Theirs. If you select only two files, then TortoiseMerge will show you the differences between those two files, either in a two pane view or in a one pane view.	582	Ako želite usporediti / stopiti datoteke, morate postaviti najmanje dvije od tri moguće staze za Osnovnu, Moju and Njihovu datoteku. Ako odaberete samo dvije datoteke, TortoiseMerge će pokazati razlike između dvije datoteke, ili pomoću dva usporedna okvira ili u jednom okviru. Možete sami odabrati / mijenjati ovaj način pregledavanja razlika pomoću izbornika PogledJednostruke razlike
28	-	If you want to merge three files, TortoiseMerge will show you the differences in a three pane view. This view is generally used if you need to resolve conflicted files. The output file is not named in this case and you will have to use the FileSave As.... to save the results.	587	Ako želite usporediti/stopiti tri datoteke, TortoiseMerge će pokazati razlike u trostrukom pogledu. Ovaj način se koristi i ako želite razriješiti sukobljene datoteke.
29	-	If you want to apply a patch file you have to set both the path to the patch file itself and the path to the folder where the patch file should be applied.	592	Ako želite primjeniti zakrpu morate postaviti datoteku sa zarkpom i datoteku na koju zarkpu želite primjeniti.
30	-	Currently, only patch files in Unified Diff Format are supported. And only files which were generated from a Subversion working copy. Other formats like patch files generated by CVS are currently not supported!	597	Trenutno su podržane samo zakrpe u formatu objedinjenih razlika, te datoteke koje su generirane iz radne kopije Subversiona. Ostali formati kao zakrpe koje generira CVS trenutno nisu podržane!
31	-	Ignore line endings hides changes which are due solely to difference in line-end style.	622	Zanemari završetke redaka sakriva one promjene koje su nastale samo zbog razlike u stilu završetaka redaka.
32	-	Compare whitespaces shows all changes in indentation and inline whitespace as added/removed lines (which is how Subversion treats such changes).	635	Usporedi praznine pokazuje sve promjene u uvlačenju i prazninama unutar retka kao i u dodanim ili obrisanim retcima (kao i Subversion za pohranjivanje verzija)
33	-	Ignore whitespace changes hides 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.	640	Zanemari velika/mala slova sakriva promjene koje su nastale samo zbog razlika u velikim ili malim slovima unutar tekstač. Ovo može biti dosta korisno s aplikacijama kao što je Visual Basic, koji mijenja velika/mala slova u varijablama automatski i bez upozorenja.
34	-	Ignore all whitespaces hides all whitespace-only changes.	645	Zanemari sve praznine sakriva sve promjene nastale zbog praznina.
35	-	Conflict resolved	710	Sukobljeni
36	-	Where the same line has been changed in both files, and you have now selected which version should be used.	715	Gdje je isti redak bio mijenjan u obje datoteke.
37	-	Copy the selected text to the clipboard	776	Kopiraj označene redke u priručni spremnik
38	-	Shift-F7	821	Ctrl-Shift-S
39	-	Shift-F8	838	Ctrl-Shift-S
40	-	Ctrl-mousewheel	872	Ctrl-kotačić miša
41	-	Specifies the resulting file used in three way diffs. This is the file path where the result of the merge/conflict resolving is saved. If this is not set, then TortoiseMerge will ask the user where to save the result.	975	Označava datoteku koja je proizvod stapanja u trostranom načinu. Ovo je ime datoteke u koju će se snimiti rezultat stapanja/sukoba. Ako ovo nije postavljeno, TortoiseMerge će pitati kamo da snimi rezultat.
42	-	The path where a patch should be applied to. If you don't set this path, then TortoiseMerge will try to find the path itself to match the paths in the patch file, but that can take .	988	Puno ime datoteke gdje će zakrpa biti primjenjena. Ako niste postavili stazu, TortoiseMerge će pokušati sam pronaći stazu kako bi je uskladio sa stazama nevedenim u zakrpi, no to može potrajati .
43	-	A term frequently used in revision control systems to describe what happens when development forks at a particular point and follows 2 separate paths. You can create a branch off the main development line so as to develop a new feature without rendering the main line unstable. Or you can branch a stable release to which you make only bug fixes, while new developments take place on the unstable trunk. In Subversion a branch is implemented as a cheap copy.	1088	Ovaj termin se često koristi u sustavima za upravljanje verzijama da bi se opisalo što se događa kad se razvoj razdvoji u nekoj točki i dalje se kreće u dvije odvojene staze. Ponekad se napravi nova grana od glavne razvojne tako da se u njoj implementira neka nova mogućnost bez utjecaja na stabilnost glavne razvoje grane. Ponekad se grana odvoji od neke stabline točke kako bi se u njoj radio samo ispravak grešaka, dok se novi razvoj događa na nestabilnoj glavnoj grani. U Subversionu grana je implementirana kao jeftina/lagana kopija.
44	-	To quote from the Subversion book: Recursively clean up the working copy, removing locks and resuming unfinished operations. If you ever get a working copy locked error, run this command to remove stale locks and get your working copy into a usable state again. Note that in this context lock refers to local filesystem locking, not repository locking.	1105	Da citiramo Subversion knjigu: Rekurzivno čisti radnu kopiju, tako da uklanja zaključavanja i nastavlja nezavršene operacije. Ako ikada dobijete grešku radna kopije je zaključana, pokrenite ovu naredbu da biste uklonili zaključavanja i dobili vašu radnu kopiju u upotrebljivom stanju. Treba znati da se termin zaključavanja ovdje koristi za lokalno zakljućavanje datoteka u datotečnom sustavu, a ne na zaključavanje u skladištu.
45	-	When you delete a versioned item (and commit the change) the item no longer exists in the repository after the committed revision. But of course it still exists in earlier repository revisions, so you can still access it. If necessary, you can copy a deleted item and resurrect it complete with history.	1138	Kada brišete neku datoteku s verzijom (i pohranite ovu izmjenu) ova datoteka više ne postoji u skladištu nakon revizije u kojoj je obrisana. Naravno, ona postoji za ranije revizije tako da ju još uvijek možete dobiti. Ako je potrebno, možete kopirati obrisanu datoteku i time je držati aktivnom sa povijesti na nekom drugom mjestu u skladištu.
46	-	A proprietary Subversion filesystem backend for repositories. Can be used on network shares. Default for 1.2 and newer repositories.	1163	FS datotečni sustav. Ovo je posebni Subversion sustav za skladišta. Može se koristiti i na mrežnim diskovima. Ovaj sustav je osnovni za skladišta Subversiona od verzije 1.2.
47	-	When you take out a lock on a versioned item, you mark it in the repository as non-committable, except from the working copy where the lock was taken out.	1196	Kada želite zaključati datoteku, ona se u skladištu označi tako da nitko ne može pohraniti novu reviziju osim radne kopije koje je zatražila zaključavanje.

^{Note: Line numbers are as in committed file, it may differ when you update to use newer .pot, also edited multi line messages may shift line position.}

Total:47

Escaped chars test

This test check if all escaped chars are known and its using match with English. Even you get red here it may be legal for your language.
This test is in developing now. Ignored are: \r \n (wee new line style test) and \".

PASS

PASS

RC Checks

Next few sections informs about duplicate accelerators in translation. There is no reason to be stressed about this, but some translators like to know it. In a fact even English translation contains duplicate.

Proc RC Check (hr)

RC checking is currently off for this language. If you like enable it for your translation drop me an email.