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
Dutch				4	69	45	2		69/45	5	Jean-Marc van Leerdam, Yves Reynhout, Bob Hulst, Dennis Siemensma, Mariska Hoogenboom, Jeroen van Amstel

---

GUI history graph:

---

TSVN doc history graph:

---

TMerge doc history graph:

---

Revision: 20088

PO Check (nl)

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		Assuming your repository is located in <filename>c:\\repos\\TestRepo</filename>, and your server is called <filename>localhost</filename>, enter: <screen>\n svn://localhost/repos/TestRepo\n </screen> when prompted by the repo browser.	1463	Stel dat je archief opgeslagen is op <filename>c:\\repos\\TestRepo</filename> en je server heeft de naam <filename>localhost</filename>, voer dan: <screen>\n svn://localhost/repos/TestRepo\n </screen> in als de archief-verkenner daar om vraagt.
2		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>\n svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n </screen> Using the previous test as a guide, svnserve would now run as: <screen>\n svnserve.exe --daemon --root c:\\repos\n </screen> And in TortoiseSVN our repo-browser URL is now shortened to: <screen>\n svn://localhost/TestRepo\n </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.	1467	Het is ook mogelijk in de veiligheid te verhogen en tijd te besparen bij het invoeren van URLs met svnserve door gebruik te maken van de --root optie voor het instellen van de hoofd map en het beperken van toegang tot een bepaalde map op de server: <screen>\n svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n </screen> Met de vorige test kan svnserve opstarten als: <screen>\n svnserve.exe --daemon --root c:\\repos\n </screen> En in TortoiseSVN is de archief-verkenner URL verkort tot: : <screen>\n svn://localhost/TestRepo\n </screen> Merk op dat de --root optie ook nodig als het archief op een andere partitie of schijf dan svnserve is opgeslagen.
3		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>\n sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service\n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip\n start= auto\n </screen> If any of the paths include spaces, you have to use (escaped) quotes around the path, like this: <screen>\n sc create svnserve binpath= \"\n \\\"C:\\Program Files\\Subversion\\bin\\svnserve.exe\\\"\n --service --root c:\\repos\" displayname= \"Subversion\"\n depend= tcpip start= auto\n </screen> You can also add a description after creating the service. This will show up in the Windows Services Manager. <screen>\n sc description svnserve \"Subversion server (svnserve)\"\n </screen>	1483	Om svnserve als Windows service te installeren, zodat deze automatisch start bij het opstarten van Windows, moet het volgende commando in zijn geheel gegeven worden: <screen>\n sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service \n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip \n start= auto\n </screen> Als één van de paden spaties bevat, dan moet je quotes gebruiken, zoals volgt: <screen>\n sc create svnserve binpath= \"\n \\\"C:\\Program Files\\Subversion\\bin\\svnserve.exe\\\"\n --service --root c:\\repos\" displayname= \"Subversion\" \n depend= tcpip start= auto\n </screen> Het is ook mogelijk om een beschrijving achter het commando op te geven. Dit wordt dan weergegeven in de Windows Service Manager. <screen>\n sc description svnserve \"Subversion server (svnserve)\"\n </screen>
4	11583	translator-credits	11583	Jeroen van Amstel\n Eddo Harkema\n Ewout Muller\n Christan Peper\n Guus Raaphorst\n Christophe de Wagter\n Johannes Zwart

^{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:4

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	398	This section is aimed at people who would like to find out what TortoiseSVN is all about and give it a test drive. It explains how to install TortoiseSVN and set up a local repository, and it walks you through the most commonly used operations.	413
2	410	TortoiseSVN runs on Windows XP or higher and is available in both 32-bit and 64-bit flavours. If you are running 64-bit Windows you may want to install both versions.	425
3	434	Language packs are available which translate the TortoiseSVN user interface into many different languages. Please check for more information on how to install these.	449
4	446	Before we get stuck into working with some real files, it is important to get an overview of how subversion works and the terms that are used.	463
5	457	Subversion uses a central database which contains all your version-controlled files with their complete history. This database is referred to as the repository. The repository normally lives on a file server running the Subversion server program, which supplies content to Subversion clients (like TortoiseSVN) on request. If you only back up one thing, back up your repository as it is the definitive master copy of all your data.	474
6	466	This is where you do the real work. Every developer has his own working copy, sometimes known as a sandbox, on his local PC. You can pull down the latest version from the repository, work on it locally without affecting anyone else, then when you are happy with the changes you made commit them back to the repository.	483
7	470	A Subversion working copy does not contain the history of the project, but it does keep a copy of the files as they exist in the repository before you started making changes. This means that it is easy to check exactly what changes you have made.	487
8	479	You also need to know where to find TortoiseSVN because there is not much to see from the Start Menu. This is because TortoiseSVN is a Shell extension, so first of all, start Windows Explorer. Right click on a folder in Explorer and you should see some new entries in the context menu like this:	496
9	487	This section shows you how to try out some of the most commonly used features on a small test repository. Naturally it doesn't explain everything - this is just the Quick Start Guide after all. Once you are up and running you should take the time to read the rest of this user guide, which takes you through things in much more detail. It also explains more about setting up a proper Subversion server.	504
10	495	For a real project you will have a repository set up somewhere safe and a Subversion server to control it. For the purposes of this tutorial we are going to use Subversion's local repository feature which allows direct access to a repository created on your hard drive without needing a server at all.	513
11	499	First create a new empty directory on your PC. It can go anywhere, but in this tutorial we are going to call it C:\\svn_repos. Now right click on the new folder and from the context menu choose TortoiseSVNCreate Repository here.... The repository is then created inside the folder, ready for you to use.	517
12	503	The local repository feature is very useful for test and evaluation but unless you are working as a sole developer on one PC you should always use a proper Subversion server. It is tempting in a small company to avoid the work of setting up a server and just access your repository on a network share. Don't ever do that. You will lose data. Read to find out why this is a bad idea, and how to set up a server.	521
13	516	Now we have a repository, but it is completely empty at the moment. Let's assume I have a set of files in C:\\Projects\\Widget1 that I would like to add. Navigate to the Widget1 folder in Explorer and right click on it. Now select TortoiseSVNImport... which brings up a dialog A Subversion repository is referred to by URL, which allows us to specify a repository anywhere on the Internet. In this case we need to point to our own local repository which has a URL of file:///c:/svn_repos/Widget1 Note that there are 3 slashes after file: and that the forward slashes are used throughout.	535
14	520	The other important feature of this dialog is the Import Message box which allows you to enter a message describing what you are doing. When you come to look through your project history, these commit messages are a valuable guide to what changes have been made and why. In this case we can say something simple like Import the Widget1 project. Click on OK and the folder is added to your repository.	539
15	528	Now that we have a project in our repository, we need to create a working copy to use for day-to-day work. Note that the act of importing a folder does not automatically turn that folder into a working copy. The Subversion term for creating a fresh working copy is Checkout. We are going to checkout the Widget1 folder of our repository into a development folder on the PC called C:\\Projects\\Widget1-Dev. Create that folder, then right click on it and select TortoiseSVNCheckout.... Enter the URL to checkout, in this case file:///c:/svn_repos/Widget1 and click on OK. Our development folder is then populated with files from the repository.	548
16	532	You will notice that the appearance of this folder is different from our original folder. Every file has a green check mark in the bottom left corner. These are TortoiseSVN's status icons which are only present in a working copy. The green state indicates that the file is unchanged from the version in the repository.	552
17	540	Time to get to work. In the Widget1-Dev we start editing files - let's say we make changes to Widget1.c and ReadMe.txt. Notice that the icon overlays on these files have now changed to red, indicating that changes have been made locally.	561
18	552	OK, so we are happy with the changes, let's update the repository. This action is referred to as a Commit of the changes. Right click on the Widget1-Dev folder and select TortoiseSVNCommit. The commit dialog lists the changed files, each with a checkbox. You might want to choose only a subset of those files, but in this case we are going to commit the changes to both files. Enter up a message to describe what the change is all about and click on OK. The progress dialog shows the files being uploaded to the repository and you're done.	575
19	560	As the project develops you will need to add new files - let's say you add some new features in Extras.c and add a reference in the existing Makefile. Right click on the folder and TortoiseSVNAdd. The Add dialog now shows you all unversioned files and you can select which ones you want to add. Another way of adding files would be to right click on the file itself and select TortoiseSVNAdd.	584
20	564	Now when you go to commit the folder, the new file shows up as Added and the existing file as Modified. Note that you can double click on the modified file to check exactly what changes were made.	588
21	568	Viewing the Project History	592
22	576	One of the most useful features of TortoiseSVN is the Log dialog. This shows you a list of all the commits you made to a file or folder, and shows those detailed commit messages that you entered ;-) OK, so I cheated a little here and used a screenshot from the TortoiseSVN repository.	601
23	580	The top pane shows a list of revisions committed along with the start of the commit message. If you select one of these revisions, the middle pane will show the full log message for that revision and the bottom pane will show a list of changed files and folders.	605
24	584	Each of these panes has a context menu which provides you with lots more ways of using the information. In the bottom pane you can double click on a file to see exactly what changes were made in that revision. Read to get the full story.	609
25	592	One feature of all revision control systems is that they let you undo changes that you made previously. As you would expect, TortoiseSVN makes this easy to access.	618
26	596	If you want to get rid of changes that you have not yet committed and reset your file to the way it was before you started editing, TortoiseSVNRevert is your friend. This discards your changes (to the Recycle bin, just in case) and reverts to the committed version you started with. If you want to get rid of just some of the changes, you can use TortoiseMerge to view the differences and selectively revert changed lines.	622
27	604	Moving On ...	631
28	608	This guide has given you a very quick tour of some of TortoiseSVN's most important and useful features, but of course there is far more that we haven't covered. We strongly recommend that you take the time to read the rest of this manual, especially which gives you a lot more detail on day-to-day operations.	635
29	612	We have taken a lot of trouble to make sure that it is both informative and easy to read, but we recognise that there is a lot of it! Take your time and don't be afraid to try things out on a test repository as you go along. The best way to learn is by using it.	639
30	1115	You will also be asked whether you want to create a directory structure within the repository. Find out about layout options in .	1187
31	1119	TortoiseSVN will set a custom folder icon when it creates a repository so you can identify local repositories more easily. If you create a repository using the official command line client this folder icon is not assigned.	1191
32	1208	Because this layout is so commonly used, when you create a new repository using TortoiseSVN, it will also offer to create the directory structure for you.	1289
33	2522	In windows explorer, Right click on the checked out folder, then use TortoiseSVNRepo-Browser to bring up the repository browser. Find the sub-folder you would like to add to your working copy, then use Context menuUpdate item to revision... That menu will only be visible if the selected item does not exist yet in your working copy, but the parent item does exist.
34	5230	Because properties are versioned, you cannot edit the properties of previous revisions. If you look at properties from the log dialog, or from a non-HEAD revision in the repository browser, you will see a list of properties and values, but no edit controls.	5961
35	6065	Choosing Prefer local will select your local changes in every conflict. Likewise, Prefer repository will select the repository changes in every conflict. This sounds easy, but the conflicts often cover more lines than you think they will and you may get unexpected results.	6849
36	6077	It is likely that some of the changes will have merged smoothly, while other local changes conflict with changes already committed to the repository. All changes which can be merged are merged. The Merge Conflict Callback dialog gives you three different ways of handling the lines which are in conflict.	6862
37	7511	Always close dialogs for local operations	8302
38	7515	Local operations like adding files or reverting changes do not need to contact the repository and complete quickly, so the progress dialog is often of little interest. Select this option if you want the progress dialog to close automatically after these operations, unless there are errors.	8306
39	7739	When using filtering in the log dialog, search terms are highlighted in the results using this colour.	8531
40	7975	Any path you specify here is assumed to apply recursively, so none of the child folders will show overlays either. If you want to exclude only the named folder, append ? after the path.	8768
41	7983	Users sometimes ask how these three settings interact. For any given path check the include and exclude lists, seeking upwards through the directory structure until a match is found. When the first match is found, obey that include or exclude rule. If there is a conflict, a single directory spec takes precedence over a recursive spec, then inclusion takes precedence over exclusion.	8776
42	7987	An example will help here: \n Exclude:\n C:\n C:\\develop\\?\n C:\\develop\\tsvn\\obj\n C:\\develop\\tsvn\\bin\n \n Include:\n C:\\develop\n These settings disable icon overlays for the C: drive, except for c:\\develop. All projects below that directory will show overlays, except the c:\\develop folder itself, which is specifically ignored. The high-churn binary folders are also excluded.	8780
43	8031	Enabled Overlay Handlers	8840
44	8039	Because the number of overlays available is severely restricted, you can choose to disable some handlers to ensure that the ones you want will be loaded. Because TortoiseSVN uses the common TortoiseOverlays component which is shared with other Tortoise clients (e.g. TortoiseCVS, TortoiseHG) this setting will affect those clients too.	8849
45	8580	Called before an attempt to contact the repository. Called at most once in five minutes.	9447
46	8672	A small tool is included in the TortoiseSVN installation folder named ConnectVPN.exe. You can use this tool configured as a pre-connect hook to connect automatically to your VPN before TortoiseSVN tries to connect to a repository. Just pass the name of the VPN connection as the first parameter to the tool.
47	8696	This is the same as bugtraq:provideruuid, but for the 64-bit version of the IBugtraqProvider.	9561
48	8868	Sometimes multiple users use the same account on the same computer. In such situations it's not really wanted to save the authentication data. Setting this value to false disables the save authentication button in the authentication dialog.	9734
49	9313	This is the main method of the plugin. This method is called from the TortoiseSVN commit dialog when the user clicks on the plugin button.	10604
50	9317	The parameters string is the string the user has to enter in the settings dialog when he configures the plugin. Usually a plugin would use this to find the URL of the issue tracker and/or login information or more.	10608
51	9321	The commonRoot string contains the parent path of all items selected to bring up the commit dialog. Note that this is not the root path of all items which the user has selected in the commit dialog. For the branch/tag dialog, this is the path which is to be copied.	10612
52	9325	The pathList parameter contains an array of paths (as strings) which the user has selected for the commit.	10616
53	9329	The originalMessage parameter contains the text entered in the log message box in the commit dialog. If the user has not yet entered any text, this string will be empty.	10620
54	9333	The newMessage return string is copied into the log message edit box in the commit dialog, replacing whatever is already there. If a plugin does not modify the originalMessage string, it must return the same string again here, otherwise any text the user has entered will be lost.	10624
55	9350	This method is called from the TortoiseSVN commit dialog when the user clicks on the plugin button. This method is called instead of GetCommitMessage(). Please refer to the documentation for GetCommitMessage for the parameters that are also used there.	10717
56	9354	The parameter commonURL is the parent URL of all items selected to bring up the commit dialog. This is basically the URL of the commonRoot path.	10721
57	9358	The parameter bugID contains the content of the bug-ID field (if it is shown, configured with the property bugtraq:message).	10725
58	9362	The return parameter bugIDOut is used to fill the bug-ID field when the method returns.	10729
59	9366	The revPropNames and revPropValues return parameters can contain name/value pairs for revision properties that the commit should set. A plugin must make sure that both arrays have the same size on return! Each property name in revPropNames must also have a corresponding value in revPropValues. If no revision properties are to be set, the plugin must return empty arrays.	10733
60	9379	For the branch/tag dialog, the commonURL is the source URL of the copy, and commonRoot is set to the target URL of the copy.	10767
61	9410	This method is called from the settings dialog when the user clicks on the \"Options\" button that is shown if HasOptions returns TRUE. A plugin can show an options dialog to make it easier for the user to configure the plugin.	10879
62	9414	The parameters string contains the plugin parameters string that is already set/entered.	10883
63	9759	If the files are already in the repository, they have to be deleted from the repository and added to the ignore list. Fortunately TortoiseSVN has a convenient shortcut for doing this. TortoiseSVNUnversion and add to ignore list will first mark the file/folder for deletion from the repository, keeping the local copy. It also adds this item to the ignore list so that it will not be added back into Subversion again by mistake. Once this is done you just need to commit the parent folder.	11257
64	11282	Language Packs and Spell Checkers	13085
65	11286	The standard installer has support only for English, but you can download separate language packs and spell check dictionaries separately after installation.	13089
66	11302	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 translation status page. And if there is no language pack available, why not join the team and submit your own translation ;-)
67	11306	Each language pack is packaged as a .msi installer. Just run the install program and follow the instructions. After the installation finishes, the translation will be available.
68	11310	The documentation has also been translated into several different languages. You can download translated manuals from the support page on our website.	13113
69	11330	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. After the installation finishes, the dictionary will be available too.

^{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:69

Fuzzy mark test

String marked as fuzzy is not in final shape.

Index	Line	English	Line	Native
1	-	If you encounter any problems during or after installing TortoiseSVN please refer to our online FAQ at http://tortoisesvn.tigris.org/faq.html	453	Als je een probleem tijdens of na installatie van TortoiseSVN tegenkomt, raadpleeg dan eerst de .
2	-	Basic Concepts	458	Basis Versie-Beheer Concepten
3	-	Creating a Repository	508	Maak hier archief aan
4	-	Importing a Project	525	Invoeren op zijn Plaats
5	-	Checking out a Working Copy	543	Een lokale werkkopie (WC) ophalen
6	-	Making Changes	556	Wijzigingen ongedaan maken
7	-	File Difference Viewer	565	Bestandsverschillen
8	-	But what are the changes? Right click on one of the changed files and select TortoiseSVNDiff. TortoiseSVN's file compare tool starts, showing you exactly which lines have changed.	570	Het is mogelijk om het Opgelost commando op meerdere bestanden toe te passen. Klik met rechts op de bovenliggende map en selecteer TortoiseSVNOpgelost.... Er wordt dan een venster geopend met alle conflicterende bestanden in die map. Je kunt dan selecteren welke bestanden gemarkeerd moeten worden als Opgelost.
9	-	Adding More Files	579	Toevoegen van eigenschappen
10	-	The Log Dialog	596	Het blokkeringsscherm
11	-	Undoing Changes	613	Wijzigingen ongedaan maken
12	-	If you want to undo the effects of a particular revision, start with the Log dialog and find the offending revision. Select Context MenuRevert changes from this revision and those changes will be undone.	626	Of als je een eerdere revisie de nieuwe HEAD revisie wilt maken, klik met rechts op de geselecteerde revisie en selecteer vervolgens Context MenuOngedaan maken tot deze revisie. Hiermee worden alle wijzigingen na de geselecteerde revisie ongedaan gemaakt.
13	-	TortoiseSVN does not support file:// 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 svn://, http:// or https:// protocols.	1199	In toekomstige versies van TortoiseSVN wordt de file:// toegangsmethode naar BDB archieven door deze compatibiliteitsproblemen niet meer ondersteund. Natuurlijk blijft er wel de mogelijkheid om zo’n archief te benaderen met het svn://, http:// of https:// protocol. Daarom adviseren we met klem nieuwe archieven die d.m.v. het file:// protocol altijd aan te maken als FSFS.
14	-	import this structure into the repository via a right click on the folder that contains this folder structure and selecting TortoiseSVNImport... In the import dialog enter the URL to your repository and click OK. This will import your temp folder into the repository root to create the basic repository layout.	1367	Importeer deze structuur in je archief, klik met rechter muisknop op de map en kies TortoiseSVNImporteren.... Hiermee wordt je tijdelijke map in de hoofdmap van het archief gezet waarmee de basis van het archief gecreëerd is.
15	-	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. \n sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service\n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip\n start= auto\n If any of the paths include spaces, you have to use (escaped) quotes around the path, like this: \n sc create svnserve binpath= \"\n \\\"C:\\Program Files\\Subversion\\bin\\svnserve.exe\\\"\n --service --root c:\\repos\" displayname= \"Subversion\"\n depend= tcpip start= auto\n You can also add a description after creating the service. This will show up in the Windows Services Manager. \n sc description svnserve \"Subversion server (svnserve)\"\n	1673	Om svnserve als Windows service te installeren, zodat deze automatisch start bij het opstarten van Windows, moet het volgende commando in zijn geheel gegeven worden: \n sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service \n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip \n start= auto\n Als één van de paden spaties bevat, dan moet je quotes gebruiken, zoals volgt: \n sc create svnserve binpath= \"\n \\\"C:\\Program Files\\Subversion\\bin\\svnserve.exe\\\"\n --service --root c:\\repos\" displayname= \"Subversion\" \n depend= tcpip start= auto\n Het is ook mogelijk om een beschrijving achter het commando op te geven. Dit wordt dan weergegeven in de Windows Service Manager. \n sc description svnserve \"Subversion server (svnserve)\"\n
16	-	You can get those three files directly from our source repository at http://tortoisesvn.googlecode.com/svn/trunk/contrib/svnindex. ( explains how to access the TortoiseSVN source repository).	2227	Deze drie bestanden kun je direct uit ons archief halen via http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/svnindex. ( geeft een beschrijving hoe je het TortoiseSVN bronbestanden archief moet benaderen).
17	-	To summarise, the relevant lines of the Apache configuration are: \n SSLVerifyClient Optional\n \n ### Virtual host configuration for the PUBLIC host\n ### (not requiring a certificate)\n \n <VirtualHost 127.0.0.1:443>\n <Directory \"pathtopublicfileroot\">\n </Directory>\n </VirtualHost>\n \n ### Virtual host configuration for SUBVERSION\n ### (requiring a client certificate)\n <VirtualHost 127.0.0.1:443>\n <Directory \"subversion host root path\">\n SSLRequire %{SSL_CLIENT_VERIFY} eq \"SUCCESS\"\n </Directory>\n \n <Location /svn>\n DAV svn\n SVNParentPath /pathtorepository\n </Location>\n </VirtualHost>\n	2718	Samenvattend zijn dit de relevante regels in de Apache configuratie: \n SSLVerifyClient Optional\n \n ### Virtual host configuration for the PUBLIC host \n ### (not requiring a certificate)\n \n <VirtualHost 127.0.0.1:443>\n <Directory \"pathtopublicfileroot\">\n </Directory>\n </VirtualHost>\n \n ### Virtual host configuration for SUBVERSION \n ### (requiring a client certificate)\n <VirtualHost 127.0.0.1:443>\n <Directory \"subversion host root path\">\n SSLRequire %{SSL_CLIENT_VERIFY} eq \"SUCCESS\"\n </Directory>\n \n <Location /svn>\n DAV svn\n SVNParentPath /pathtorepository\n </Location>\n </VirtualHost>\n
18	-	A file 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 <<<<<<<. The conflicting area is marked like this: \n <<<<<<< filename\n your changes\n =======\n code merged from repository\n >>>>>>> revision\n Also, for every conflicted file Subversion places three additional files in your directory:	3697	Een bestandsconflict treedt op als twee of meer ontwikkelaars dezelfde regels in een bestand hebben gewijzigd. Omdat Subversion niets van de projecten weer, laat het het oplossen van conflicten over aan de gebruikers. Als er een conflict gemeld wordt, dan moet je het bestand in kwestie openen en de regels zoeken die beginnen met <<<<<<<. Het conflicterende gedeelte wordt als volgt gemarkeerd: \n \t<<<<<<< filename\n \t\tyour changes\n \t=======\n \t\tcode merged from repository\n \t>>>>>>> revision\n \t Daarnaast plaatst Subversion drie additionele bestanden in je map:
19	-	Edit properties at HEAD revision	5956	Timeout in seconden voordat de HEAD revisie ververst wordt
20	-	Normally you will want to look at the conflicts and resolve them yourself. In that case, choose the Edit Conflict which will start up your merge tool. When you are satisfied with the result, click Resolved.	6853	Normaliter zou je de conflicten willen bekijken en deze oplossen. In dat geval klik je op Bewerk Conflict, waardoor je samenvoeg programma gestart wordt. Als je tevreden bent met het resultaat klik je op Opgelost.
21	-	This issue tracker integration is not restricted to TortoiseSVN; it can be used with any Subversion client. For more information, read the full Issue Tracker Integration Specification in the TortoiseSVN source repository. ( explains how to access the repository).	8020	Deze issue tracker integratie is niet exclusief voor TortoiseSVN; het kan worden gebruikt met elke Subversion client. Voor meer informatie, lees de volledige Issue Tracker Integratie Specificatie in het TortoiseSVN bron archief. ( geeft een uitleg over hoe het archief te benaderen).
22	-	Any such interface is of course highly specific to your issue tracker 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 plugins in C# and C++/ATL can be obtained from the contrib folder in the TortoiseSVN repository. ( explains how to access the repository). A summary of the API is also given in Another (working) example plugin in C# is Gurtle which implements the required COM interface to interact with the Google Code issue tracker.	8033	Zo'n interface is natuurlijk specifiek voor uw issue tracker systeem, zodat we dit niet kunnen leveren. De beschrijving van hoe zo'n programma te schrijven valt buiten de scope van deze handleiding. De interface definitie en voorbeeld plugins in C# en C++/ATL zijn beschikbaar in de contrib map in het TortoiseSVN archief. ( geeft uitleg over hoe het archief te benaderen). Ook is een samenvatting van de API beschikbaar op Een andere (werkende) voorbeeld plugin in C# is Gurtle welke gebruik maakt van de vereiste COM interface om met de Google Code issue tracker samen te werken.
23	-	Check for updates	8127	Controleer op Wijzigingen
24	-	TortoiseSVN will contact its download site periodically to see if there is a newer version of the program available. If there is it will show a notification link in the commit dialog. Use Check now 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.	8132	Als dit is aangevinkt zal TortoiseSVN elke week contact maken met de download site om te kijken of er een nieuwere versie van het programma beschikbaar is. Gebruik Nu controleren wanneer je direct wilt controleren op nieuwe versies. De nieuwe versie zal niet worden gedownload, maar er wordt alleen aangegeven dat er een nieuwe versie beschikbaar is.
25	-	Auto-close	8281	auto-props
26	-	Filter match	8526	Filter
27	-	The Exclude Paths are used to tell TortoiseSVN those paths for which it should not 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, or if you only want TortoiseSVN to look in specific folders.	8763	De Exclusief paden worden gebruikt om aan TortoiseSVN door te geven voor welke paden geen overlappende pictogrammen en statuskolommen moeten worden getoond. Dit is handig als u enkele zeer grote werkkopieën heeft, welke enkel bibliotheken bevatten die u nooit wilt wijzigen en waarvoor u daarom geen overlappende pictogrammen nodig heeft. Bijvoorbeeld:
28	-	The Settings Dialog, Icon Handlers Page	8844	Het instellingen scherm, Pictogramset pagina
29	-	Called before the actual Subversion update or switch begins.	9426	Wordt aangeroepen voordat de Subversion verversing begint.
30	-	Called after the update, switch or checkout finishes (whether successful or not).	9436	Wordt aangeroepen nadat een verversing klaar is (succesvol of niet).
31	-	Pre-connect	9442	Pre-commit
32	-	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. Note that the script must not be specified using a UNC path as Windows shell execute will not allow such scripts to run due to security restrictions.	9459	Vervolgens moet je de opdrachtregel specificeren die uitgevoerd moet worden, beginnend met het pad naar het hook script of de toepassing. Dit kan een batch bestand zijn, een toepassing of elk ander bestand die een geldig associatie in windows heeft, bijv. een perl script.
33	-	Sample client hook scripts can be found in the contrib folder in the TortoiseSVN repository. ( explains how to access the repository).	9536	Voorbeeld client hook scripts kunnen gevonden worden in de contrib map in het TortoiseSVNarchief . beschrijft hoe je het archief benadert.
34	-	If you want all users to use the same COM plugin for your project, you can specify the plugin also with the properties bugtraq:provideruuid, bugtraq:provideruuid64 and bugtraq:providerparams. Please check the documentation of your IBugtraqProvider plugin to find out what to specify in these two properties.	9569	Als je wilt dat alle gebruikers dezelfde COM plugin gebruiken voor je project, dan kun je de plugin ook specificeren met de eigenschap bugtraq:provideruuid en bugtraq:providerparams. Sla de documentatie van je IBugtraqProvider er op na om te achterhalen wat je moet invullen bij deze twee eigenschappen.
35	-	Some of these keywords apply to single files rather than to an entire working copy, so it only makes sense to use these when SubWCRev is called to scan a single file. This applies to $WCINSVN$, $WCISLOCKED$, $WCLOCKDATE$, $WCLOCKOWNER$ and $WCLOCKCOMMENT$.	9985	Enkele van deze trefwoorden zijn toepassing op bestanden in plaats van een hele werkkopie. Het is dus alleen logisch om deze te gebruiken als SubWCRev wordt aangeroepen op een enkel bestand. Dit heeft betrekking op $WCINSVN$, $WCNEEDSLOCK$, $WCISLOCKED$, $WCLOCKDATE$, $WCLOCKOWNER$ en $WCLOCKCOMMENT$.
36	-	\n // testCOM.js - javascript file\n // test script for the SubWCRev COM/Automation-object\n \n filesystem = new ActiveXObject(\"Scripting.FileSystemObject\");\n \n revObject1 = new ActiveXObject(\"SubWCRev.object\");\n revObject2 = new ActiveXObject(\"SubWCRev.object\");\n revObject3 = new ActiveXObject(\"SubWCRev.object\");\n revObject4 = new ActiveXObject(\"SubWCRev.object\");\n \n revObject1.GetWCInfo(\n filesystem.GetAbsolutePathName(\".\"), 1, 1);\n revObject2.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\"), 1, 1);\n revObject3.GetWCInfo(\n filesystem.GetAbsolutePathName(\"SubWCRev.cpp\"), 1, 1);\n revObject4.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\\\\..\"), 1, 1);\n \n wcInfoString1 = \"Revision = \" + revObject1.Revision +\n \"\\n Min Revision = \" + revObject1.MinRev +\n \"\\n Max Revision = \" + revObject1.MaxRev +\n \"\\n Date = \" + revObject1.Date +\n \"\\n URL = \" + revObject1.Url + \"\\n Author = \" +\n revObject1.Author + \"\\n HasMods = \" +\n revObject1.HasModifications + \"\\n IsSvnItem = \" +\n revObject1.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject1.IsLocked + \"\\n LockCreationDate = \" +\n revObject1.LockCreationDate + \"\\n LockOwner = \" +\n revObject1.LockOwner + \"\\n LockComment = \" +\n revObject1.LockComment;\n wcInfoString2 = \"Revision = \" + revObject2.Revision +\n \"\\n Min Revision = \" + revObject2.MinRev +\n \"\\n Max Revision = \" + revObject2.MaxRev +\n \"\\n Date = \" + revObject2.Date +\n \"\\n URL = \" + revObject2.Url + \"\\n Author = \" +\n revObject2.Author + \"\\n HasMods = \" +\n revObject2.HasModifications + \"\\n IsSvnItem = \" +\n revObject2.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject2.IsLocked + \"\\n LockCreationDate = \" +\n revObject2.LockCreationDate + \"\\n LockOwner = \" +\n revObject2.LockOwner + \"\\n LockComment = \" +\n revObject2.LockComment;\n wcInfoString3 = \"Revision = \" + revObject3.Revision +\n \"\\n Min Revision = \" + revObject3.MinRev +\n \"\\n Max Revision = \" + revObject3.MaxRev +\n \"\\n Date = \" + revObject3.Date +\n \"\\n URL = \" + revObject3.Url + \"\\n Author = \" +\n revObject3.Author + \"\\n HasMods = \" +\n revObject3.HasModifications + \"\\n IsSvnItem = \" +\n revObject3.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject3.IsLocked + \"\\n LockCreationDate = \" +\n revObject3.LockCreationDate + \"\\n LockOwner = \" +\n revObject3.LockOwner + \"\\n LockComment = \" +\n revObject3.LockComment;\n wcInfoString4 = \"Revision = \" + revObject4.Revision +\n \"\\n Min Revision = \" + revObject4.MinRev +\n \"\\n Max Revision = \" + revObject4.MaxRev +\n \"\\n Date = \" + revObject4.Date +\n \"\\n URL = \" + revObject4.Url + \"\\n Author = \" +\n revObject4.Author + \"\\n HasMods = \" +\n revObject4.HasModifications + \"\\n IsSvnItem = \" +\n revObject4.IsSvnItem + \"\\n NeedsLocking = \" +\n revObject4.IsLocked + \"\\n LockCreationDate = \" +\n revObject4.LockCreationDate + \"\\n LockOwner = \" +\n revObject4.LockOwner + \"\\n LockComment = \" +\n revObject4.LockComment;\n \n WScript.Echo(wcInfoString1);\n WScript.Echo(wcInfoString2);\n WScript.Echo(wcInfoString3);\n WScript.Echo(wcInfoString4);\n \n	10173	\n // testCOM.js - javascript file\n // test script voor de SubWCRev COM/Automation-object\n \n filesystem = new ActiveXObject(\"Scripting.FileSystemObject\");\n \n revObject1 = new ActiveXObject(\"SubWCRev.object\");\n revObject2 = new ActiveXObject(\"SubWCRev.object\");\n revObject3 = new ActiveXObject(\"SubWCRev.object\");\n revObject4 = new ActiveXObject(\"SubWCRev.object\");\n \n revObject1.GetWCInfo(\n filesystem.GetAbsolutePathName(\".\"), 1, 1);\n revObject2.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\"), 1, 1);\n revObject3.GetWCInfo(\n filesystem.GetAbsolutePathName(\"SubWCRev.cpp\"), 1, 1);\n revObject4.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\\\\..\"), 1, 1);\n \n wcInfoString1 = \"Revision = \" + revObject1.Revision + \n \t\t\t\t\"\\n Min Revision = \" + revObject1.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject1.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject1.Date + \n \t\t\t\t\"\\n URL = \" + revObject1.Url + \"\\n Author = \" + \n \t\t\t\trevObject1.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject1.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject1.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject1.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject1.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject1.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject1.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject1.LockComment;\n wcInfoString2 = \"Revision = \" + revObject2.Revision + \n \t\t\t\t\"\\n Min Revision = \" + revObject2.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject2.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject2.Date + \n \t\t\t\t\"\\n URL = \" + revObject2.Url + \"\\n Author = \" + \n \t\t\t\trevObject2.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject2.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject2.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject2.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject2.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject2.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject2.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject2.LockComment;\n wcInfoString3 = \"Revision = \" + revObject3.Revision + \n \t\t\t\t\"\\n Min Revision = \" + revObject3.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject3.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject3.Date + \n \t\t\t\t\"\\n URL = \" + revObject3.Url + \"\\n Author = \" + \n \t\t\t\trevObject3.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject3.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject3.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject3.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject3.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject3.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject3.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject3.LockComment;\n wcInfoString4 = \"Revision = \" + revObject4.Revision + \n \t\t\t\t\"\\n Min Revision = \" + revObject4.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject4.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject4.Date + \n \t\t\t\t\"\\n URL = \" + revObject4.Url + \"\\n Author = \" + \n \t\t\t\trevObject4.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject4.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject4.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject4.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject4.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject4.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject4.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject4.LockComment;\n \n WScript.Echo(wcInfoString1);\n WScript.Echo(wcInfoString2);\n WScript.Echo(wcInfoString3);\n WScript.Echo(wcInfoString4);\n \n
37	-	This method is called from the settings dialog where the user can add and configure the plugin. The parameters string can be used by a plugin to get additional required information, e.g., the URL to the issue tracker, login information, etc. The plugin should verify the parameters string and show an error dialog if the string is not valid. The hParentWnd parameter should be used for any dialog the plugin shows as the parent window. The plugin must return TRUE if the validation of the parameters string is successful. If the plugin returns FALSE, the settings dialog won't allow the user to add the plugin to a working copy path.	10520	Deze mothode wordt aangeroepen vanuit het instellingen scherm waar de gebruiker de plugin kan toevoegen en instellen. De parameters tekst kan door de plugin gebruikt worden om meer information te verkrijgen, bijv. de URL naar de issue tracker, inlog gegevens, etc. De plugin moet de parameters controleren en een foutmeldingsscherm tonen als er een fout in de parameters zit. De hParentWnd parameter moet gebruikt worden voor elk scherm dat door de plugin getoond wordt. De plugin moet TRUE teruggeven als de validatie van de parameters succesvol is. Als de plugin FALSE teruggeeft, zal het instellingen scherm de gebruiker verhinderen de plugin aan het pad van de werkkopie toe te voegen.
38	-	The plugin can provide a string here which is used in the TortoiseSVN commit dialog for the button which invokes the plugin, e.g., \"Choose issue\" or \"Select ticket\". Make sure the string is not too long, otherwise it might not fit into the button. If the method returns an error (e.g., E_NOTIMPL), a default text is used for the button.	10556	De plugin kan een tekst aanbieden, welke gebruikt wordt in het TortoiseSVN vastleg scherm voor de knop waarmee de plugin gestart wordt, bijv. \"Kies issue\" of \"Selecteer ticket\". Zorg er voor dat de tekst niet te lang is, anders past het misschien niet in de knop. Als de methode een foutmelding teruggeeft (bijv. E_NOTIMPL), dan zal er een standaard tekst gebruikt worden.
39	-	This method is called right before the commit dialog is closed and the commit begins. A plugin can use this method to validate the selected files/folders for the commit and/or the commit message entered by the user. The parameters are the same as for GetCommitMessage2(), with the difference that commonURL is now the common URL of all checked items, and commonRoot the root path of all checked items.	10762	Deze functie wordt aangeroepen voordat het vastleg scherm afgesloten worden en het vastleggen start. Een plugin kan deze functie gebruiken om de geselecteerde bestanden/mappen te valideren voor vastlegging en/of het vastlegbericht van de gebruiker. De parameters worden net zo ingesteld als bij GetCommitMessage2(), maar dan met het verschil dat commonURL nu de gemeenschappelijke URL is van alle geselecteerde objecten, en de commonRoot het basispad van alle geselecteerde objecten. De return paramter errorMessage moet of een foutmeldig bevatten, die door TortoiseSVN aan de gebruiker getoond wordt, of leeg zijn, zodat de vastlegging kan starten. Als er een foutmelding terug wordt gegeven, zal TortoiseSVN de foutmelding in een scherm weergeven en houdt blijft het vastleg scherm geopend, zodat de gebruiker kan corrigeren wat er fout is. Een plugin moet dus een foutmelding geven die aan de gebruiker laat weten wat er fout is en hoe het gecorrigeerd moet worden.
40	-	The return parameter errorMessage must either contain an error message which TortoiseSVN shows to the user or be empty for the commit to start. If an error message is returned, TortoiseSVN shows the error string in a dialog and keeps the commit dialog open so the user can correct whatever is wrong. A plugin should therefore return an error string which informs the user what is wrong and how to correct it.	10771	Deze functie wordt aangeroepen voordat het vastleg scherm afgesloten worden en het vastleggen start. Een plugin kan deze functie gebruiken om de geselecteerde bestanden/mappen te valideren voor vastlegging en/of het vastlegbericht van de gebruiker. De parameters worden net zo ingesteld als bij GetCommitMessage2(), maar dan met het verschil dat commonURL nu de gemeenschappelijke URL is van alle geselecteerde objecten, en de commonRoot het basispad van alle geselecteerde objecten. De return paramter errorMessage moet of een foutmeldig bevatten, die door TortoiseSVN aan de gebruiker getoond wordt, of leeg zijn, zodat de vastlegging kan starten. Als er een foutmelding terug wordt gegeven, zal TortoiseSVN de foutmelding in een scherm weergeven en houdt blijft het vastleg scherm geopend, zodat de gebruiker kan corrigeren wat er fout is. Een plugin moet dus een foutmelding geven die aan de gebruiker laat weten wat er fout is en hoe het gecorrigeerd moet worden.
41	-	This method is called after a successful commit. A plugin can use this method to e.g., close the selected issue or add information about the commit to the issue. The parameters are the same as for GetCommitMessage2.	10827	Deze functie wordt aangeroepen na een succesvolle vastlegging. Een plugin kan deze functie gebruiken om bijv. de geselecteerde bevinding de sluiten of informatie aan de bevinding toe te voegen over de vastleggin. De parameters zijn gelijk aan die voor GetCommitMessage2.
42	-	This method is called from the settings dialog where the user can configure the plugins. If a plugin provides its own configuration dialog with ShowOptionsDialog, it must return TRUE here, otherwise it must return FALSE.	10847	Deze functie wordt aangeroepen vanuit het instellingen scherm waar de gebruiker de plugins kan instellen. Als een plugin een eigen configuratiescherm heeft met ShowOptionsDialog, dan moet deze TRUE teruggeven, anders moet deze FALSE teruggeven.
43	-	The newparameters return parameter must contain the parameters string which the plugin constructed from the info it gathered in its options dialog. That paramameters string is passed to all other IBugtraqProvider and IBugtraqProvider2 methods.	10887	Deze functie wordt aangeroepen vanuit het instellingen scherm als de gebruiker op de \"Options\" knop klikt, welke getoond wordt als HasOptions TRUE antwoord. Een plugin kan een instellingenscherm weergeven om het configureren van de plugin te vereenvoudigen. De parameter tekst bevat de plugin parameters die al ingesteld zijn. De newparameters antwoordparameter moet de parameter tekst bevatten die de plugin samengesteld heeft uit de informatie van het instellingenscherm. Die paramameter tekst wordt doorgegeven aan alle IBugtraqProvider and IBugtraqProvider2 functies.
44	-	As of version 1.4.0 and later, the TortoiseSVN installer doesn't provide the user with the option to set the SVN_ASP_DOT_NET_HACK environment variable anymore, since that caused many problems and confusion for users who always install everything no matter whether they know what it is for.	11381	Vanaf versie 1.4.0 en hoger, verschaft de TortoiseSVN installatie niet meer de optie aan de gebruiker om de SVN_ASP_DOT_NET_HACK omgevingsvariabele te zetten, omdat deze vele problemen opleverde en verwarring zaaide bij gebruikers die altijd alles installeren ongeacht of ze weten waar het voor is.
45	-	In the descriptions which follow, the URL for a repository location is shown simply as URL, and an example might be http://tortoisesvn.googlecode.com/svn/trunk/. The working copy path is shown simply as PATH, and an example might be C:\\TortoiseSVN\\trunk.	12221	In de volgende beschrijvingen wordt de URL van een archief eenvoudig weergegeven als URL, met als voorbeeld http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk. Het pad van de werkkopie wordt aangegeven als PATH, met als voorbeeld C:\\TortoiseSVN\\trunk.

^{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:45

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 \".

Index	Line	English	Line	Native
1		A file 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>\n &lt;&lt;&lt;&lt;&lt;&lt;&lt; filename\n your changes\n =======\n code merged from repository\n &gt;&gt;&gt;&gt;&gt;&gt;&gt; revision\n </screen> Also, for every conflicted file Subversion places three additional files in your directory: <placeholder-1/>	3008	Een bestandsconflict treedt op als twee of meer ontwikkelaars dezelfde regels in een bestand hebben gewijzigd. Omdat Subversion niets van de projecten weer, laat het het oplossen van conflicten over aan de gebruikers. Als er een conflict gemeld wordt, dan moet je het bestand in kwestie openen en de regels zoeken die beginnen met <literal>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</literal>. Het conflicterende gedeelte wordt als volgt gemarkeerd: <screen>\n \t&lt;&lt;&lt;&lt;&lt;&lt;&lt; filename\n \t\tyour changes\n \t=======\n \t\tcode merged from repository\n \t&gt;&gt;&gt;&gt;&gt;&gt;&gt; revision\n \t</screen> Daarnaast plaatst Subversion drie additionele bestanden in je map: <placeholder-1/>
2		\n // testCOM.js - javascript file\n // test script for the SubWCRev COM/Automation-object\n \n filesystem = new ActiveXObject(\"Scripting.FileSystemObject\");\n \n revObject1 = new ActiveXObject(\"SubWCRev.object\");\n revObject2 = new ActiveXObject(\"SubWCRev.object\");\n revObject3 = new ActiveXObject(\"SubWCRev.object\");\n revObject4 = new ActiveXObject(\"SubWCRev.object\");\n \n revObject1.GetWCInfo(\n filesystem.GetAbsolutePathName(\".\"), 1, 1);\n revObject2.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\"), 1, 1);\n revObject3.GetWCInfo(\n filesystem.GetAbsolutePathName(\"SubWCRev.cpp\"), 1, 1);\n revObject4.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\\\\..\"), 1, 1);\n \n wcInfoString1 = \"Revision = \" + revObject1.Revision +\n \"\\nMin Revision = \" + revObject1.MinRev +\n \"\\nMax Revision = \" + revObject1.MaxRev +\n \"\\nDate = \" + revObject1.Date +\n \"\\nURL = \" + revObject1.Url + \"\\nAuthor = \" +\n revObject1.Author + \"\\nHasMods = \" +\n revObject1.HasModifications + \"\\nIsSvnItem = \" +\n revObject1.IsSvnItem + \"\\nNeedsLocking = \" +\n revObject1.IsLocked + \"\\nLockCreationDate = \" +\n revObject1.LockCreationDate + \"\\nLockOwner = \" +\n revObject1.LockOwner + \"\\nLockComment = \" +\n revObject1.LockComment;\n wcInfoString2 = \"Revision = \" + revObject2.Revision +\n \"\\nMin Revision = \" + revObject2.MinRev +\n \"\\nMax Revision = \" + revObject2.MaxRev +\n \"\\nDate = \" + revObject2.Date +\n \"\\nURL = \" + revObject2.Url + \"\\nAuthor = \" +\n revObject2.Author + \"\\nHasMods = \" +\n revObject2.HasModifications + \"\\nIsSvnItem = \" +\n revObject2.IsSvnItem + \"\\nNeedsLocking = \" +\n revObject2.IsLocked + \"\\nLockCreationDate = \" +\n revObject2.LockCreationDate + \"\\nLockOwner = \" +\n revObject2.LockOwner + \"\\nLockComment = \" +\n revObject2.LockComment;\n wcInfoString3 = \"Revision = \" + revObject3.Revision +\n \"\\nMin Revision = \" + revObject3.MinRev +\n \"\\nMax Revision = \" + revObject3.MaxRev +\n \"\\nDate = \" + revObject3.Date +\n \"\\nURL = \" + revObject3.Url + \"\\nAuthor = \" +\n revObject3.Author + \"\\nHasMods = \" +\n revObject3.HasModifications + \"\\nIsSvnItem = \" +\n revObject3.IsSvnItem + \"\\nNeedsLocking = \" +\n revObject3.IsLocked + \"\\nLockCreationDate = \" +\n revObject3.LockCreationDate + \"\\nLockOwner = \" +\n revObject3.LockOwner + \"\\nLockComment = \" +\n revObject3.LockComment;\n wcInfoString4 = \"Revision = \" + revObject4.Revision +\n \"\\nMin Revision = \" + revObject4.MinRev +\n \"\\nMax Revision = \" + revObject4.MaxRev +\n \"\\nDate = \" + revObject4.Date +\n \"\\nURL = \" + revObject4.Url + \"\\nAuthor = \" +\n revObject4.Author + \"\\nHasMods = \" +\n revObject4.HasModifications + \"\\nIsSvnItem = \" +\n revObject4.IsSvnItem + \"\\nNeedsLocking = \" +\n revObject4.IsLocked + \"\\nLockCreationDate = \" +\n revObject4.LockCreationDate + \"\\nLockOwner = \" +\n revObject4.LockOwner + \"\\nLockComment = \" +\n revObject4.LockComment;\n \n WScript.Echo(wcInfoString1);\n WScript.Echo(wcInfoString2);\n WScript.Echo(wcInfoString3);\n WScript.Echo(wcInfoString4);\n \n	9240	\n // testCOM.js - javascript file\n // test script voor de SubWCRev COM/Automation-object\n \n filesystem = new ActiveXObject(\"Scripting.FileSystemObject\");\n \n revObject1 = new ActiveXObject(\"SubWCRev.object\");\n revObject2 = new ActiveXObject(\"SubWCRev.object\");\n revObject3 = new ActiveXObject(\"SubWCRev.object\");\n revObject4 = new ActiveXObject(\"SubWCRev.object\");\n \n revObject1.GetWCInfo(\n filesystem.GetAbsolutePathName(\".\"), 1, 1);\n revObject2.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\"), 1, 1);\n revObject3.GetWCInfo(\n filesystem.GetAbsolutePathName(\"SubWCRev.cpp\"), 1, 1);\n revObject4.GetWCInfo(\n filesystem.GetAbsolutePathName(\"..\\\\..\"), 1, 1);\n \n wcInfoString1 = \"Revision = \" + revObject1.Revision + \n \t\t\t\t\"\\nMin Revision = \" + revObject1.MinRev + \n \t\t\t\t\"\\nMax Revision = \" + revObject1.MaxRev + \n \t\t\t\t\"\\nDate = \" + revObject1.Date + \n \t\t\t\t\"\\nURL = \" + revObject1.Url + \"\\nAuthor = \" + \n \t\t\t\trevObject1.Author + \"\\nHasMods = \" + \n \t\t\t\trevObject1.HasModifications + \"\\nIsSvnItem = \" + \n \t\t\t\trevObject1.IsSvnItem + \"\\nNeedsLocking = \" + \n \t\t\t\trevObject1.NeedsLocking + \"\\nIsLocked = \" + \n \t\t\t\trevObject1.IsLocked + \"\\nLockCreationDate = \" + \n \t\t\t\trevObject1.LockCreationDate + \"\\nLockOwner = \" + \n \t\t\t\trevObject1.LockOwner + \"\\nLockComment = \" + \n \t\t\t\trevObject1.LockComment;\n wcInfoString2 = \"Revision = \" + revObject2.Revision + \n \t\t\t\t\"\\nMin Revision = \" + revObject2.MinRev + \n \t\t\t\t\"\\nMax Revision = \" + revObject2.MaxRev + \n \t\t\t\t\"\\nDate = \" + revObject2.Date + \n \t\t\t\t\"\\nURL = \" + revObject2.Url + \"\\nAuthor = \" + \n \t\t\t\trevObject2.Author + \"\\nHasMods = \" + \n \t\t\t\trevObject2.HasModifications + \"\\nIsSvnItem = \" + \n \t\t\t\trevObject2.IsSvnItem + \"\\nNeedsLocking = \" + \n \t\t\t\trevObject2.NeedsLocking + \"\\nIsLocked = \" + \n \t\t\t\trevObject2.IsLocked + \"\\nLockCreationDate = \" + \n \t\t\t\trevObject2.LockCreationDate + \"\\nLockOwner = \" + \n \t\t\t\trevObject2.LockOwner + \"\\nLockComment = \" + \n \t\t\t\trevObject2.LockComment;\n wcInfoString3 = \"Revision = \" + revObject3.Revision + \n \t\t\t\t\"\\nMin Revision = \" + revObject3.MinRev + \n \t\t\t\t\"\\nMax Revision = \" + revObject3.MaxRev + \n \t\t\t\t\"\\nDate = \" + revObject3.Date + \n \t\t\t\t\"\\nURL = \" + revObject3.Url + \"\\nAuthor = \" + \n \t\t\t\trevObject3.Author + \"\\nHasMods = \" + \n \t\t\t\trevObject3.HasModifications + \"\\nIsSvnItem = \" + \n \t\t\t\trevObject3.IsSvnItem + \"\\nNeedsLocking = \" + \n \t\t\t\trevObject3.NeedsLocking + \"\\nIsLocked = \" + \n \t\t\t\trevObject3.IsLocked + \"\\nLockCreationDate = \" + \n \t\t\t\trevObject3.LockCreationDate + \"\\nLockOwner = \" + \n \t\t\t\trevObject3.LockOwner + \"\\nLockComment = \" + \n \t\t\t\trevObject3.LockComment;\n wcInfoString4 = \"Revision = \" + revObject4.Revision + \n \t\t\t\t\"\\nMin Revision = \" + revObject4.MinRev + \n \t\t\t\t\"\\nMax Revision = \" + revObject4.MaxRev + \n \t\t\t\t\"\\nDate = \" + revObject4.Date + \n \t\t\t\t\"\\nURL = \" + revObject4.Url + \"\\nAuthor = \" + \n \t\t\t\trevObject4.Author + \"\\nHasMods = \" + \n \t\t\t\trevObject4.HasModifications + \"\\nIsSvnItem = \" + \n \t\t\t\trevObject4.IsSvnItem + \"\\nNeedsLocking = \" + \n \t\t\t\trevObject4.NeedsLocking + \"\\nIsLocked = \" + \n \t\t\t\trevObject4.IsLocked + \"\\nLockCreationDate = \" + \n \t\t\t\trevObject4.LockCreationDate + \"\\nLockOwner = \" + \n \t\t\t\trevObject4.LockOwner + \"\\nLockComment = \" + \n \t\t\t\trevObject4.LockComment;\n \n WScript.Echo(wcInfoString1);\n WScript.Echo(wcInfoString2);\n WScript.Echo(wcInfoString3);\n WScript.Echo(wcInfoString4);\n \n

^{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:2

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 (nl)

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