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
Please follow this link if you think you may help with translation.
-> TortoiseSVN translation
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.
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 |
 |
 |
||
| French |  |
 5 |
244 |
125 |
4 |
244/125 | 5 | Olivier Booklage, Philippe Torche, Jean-Christophe Gigogne, Jérémy Badier, Jean-Christophe Mazenc, Christophe Sauveur, Frédéric Bodin, Matthias Goupil, Dany McCarthy, Yves Mittelmann, Vincent Houde | |||
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
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
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 | En supposant que votre référentiel est placé dans <filename>c:\\repos\\TestRepo</filename> et votre serveur est appelé <filename>localhost</filename>, entrer : <screen>\n svn://localhost/repos/TestRepo\n </screen> quand l'explorateur de référentiel le demande. |
|
| 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 | Vous pouvez aussi augmenter la sécurité et gagner du temps en entrant l'URL avec svnserve en utilisant le commutateur --root pour indiquer l'emplacement racine et limiter l'accès à un répertoire spécifique sur le serveur : <screen>\n svnserve.exe --daemon --root disque:\\chemin\\vers\\racine\\référentiel\n </screen> En utilisant le test précédent comme guide, svnserve fonctionnerait maintenant comme : <screen>\n svnserve.exe --daemon --root c:\\référentiels\n </screen> Et dans TortoiseSVN notre URL de l'explorateur de référentiel est maintenant raccourcie en : <screen>\n svn://localhost/TestRéférentiel\n </screen> Notez que le commutateur --root est aussi nécessaire si votre référentiel est placé sur une partition ou un disque différent de l'emplacement de svnserve sur votre serveur. |
|
| 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 | Pour installer svnserve comme service Windows, exécutez la commande suivante sur une seule ligne. Le service sera alors créé et lancé à chaque démarrage de Windows. <screen>\n sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service\n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip\n start= auto\n </screen> Si l'un des chemins d'accès contient des espaces, vous devrez encapsuler ceux ci dans des double cotes, comme suit :<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> Vous pouvez également ajouter une description après avoir créé le service. Elle sera visible depuis la fenêtre de gestion des services de Windows. <screen>\n sc description svnserve \"Serveur Subversion (svnserve)\"\n </screen> |
|
| 4 | Note that if you are authenticating using SSPI, then you don't need the <literal>AuthUserFile</literal> line to define a password file any more. Apache authenticates your username and password against your windows domain instead. You will need to update the users list in your <filename>svnaccessfile</filename> to reference <literal>DOMAIN\\username</literal> as well. | 1948 | Notez que si vous vous authentifiez en utilisant SSPI, alors vous n'avez plus besoin de la ligne <literal>AuthUserFile</literal> pour définir un fichier de mot de passe. Apache authentifie votre nom d'utilisateur et votre mot de passe avec votre domaine Windows à la place. Vous devrez mettre à jour la liste d'utilisateurs dans votre <filename>svnaccessfile</filename> pour faire aussi référence au <literal>DOMAINE\\n om d'utilisateur</literal>. |
|
| 5 | To specify a different location of the configuration file, use the parameter <option>/configdir:\"path\\to\\config\\directory\"</option>. This will override the default path, including any registry setting. | 10131 | Pour spécifier un emplacement différent du fichier de configuration, utilisez le paramètre <option>/configdir:\"chemin\\vers\\répertoire\\de\\conf\"</option>. Cela remplacera le chemin par défaut, y compris tous les paramètres de la base de registre. |
Total:5
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 | 125 | When you list the changes to a file or folder, you can click on a revision to see the comments for that commit. You can also see a list of changed files - just double click on a file to see exactly what changed. | 155 |
| 2 | 129 | The commit dialog lists all the items that will be included in a commit, and each item has a checkbox so you can choose which items you want to include. Unversioned files can also be listed, in case you forgot to add that new file. | 159 |
| 3 | 197 | TortoiseSVN is an Open Source project developed under the GNU General Public License (GPL). It is free to download and free to use, either personally or commercially, on any number of PCs. | 227 |
| 4 | 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. | 433 |
| 5 | 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. | 445 |
| 6 | 434 | Language packs are available which translate the TortoiseSVN user interface into many different languages. Please check |
469 |
| 7 | 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. | 481 |
| 8 | 457 | Subversion uses a central database which contains all your version-controlled files with their complete history. This database is referred to as the |
492 |
| 9 | 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. | 501 |
| 10 | 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. | 505 |
| 11 | 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: |
514 |
| 12 | 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. | 522 |
| 13 | 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. | 530 |
| 14 | 499 | First create a new empty directory on your PC. It can go anywhere, but in this tutorial we are going to call it |
534 |
| 15 | 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 |
538 |
| 16 | 516 | Now we have a repository, but it is completely empty at the moment. Let's assume I have a set of files in |
551 |
| 17 | 520 | The other important feature of this dialog is the Import the Widget1 project. Click on |
555 |
| 18 | 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 |
563 |
| 19 | 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. | 567 |
| 20 | 540 | Time to get to work. In the |
575 |
| 21 | 552 | OK, so we are happy with the changes, let's update the repository. This action is referred to as a |
588 |
| 22 | 560 | As the project develops you will need to add new files - let's say you add some new features in |
596 |
| 23 | 564 | Now when you go to commit the folder, the new file shows up as |
600 |
| 24 | 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 ;-) |
612 |
| 25 | 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. | 616 |
| 26 | 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 |
620 |
| 27 | 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. | 628 |
| 28 | 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, |
632 |
| 29 | 604 | Moving On ... | 641 |
| 30 | 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 |
645 |
| 31 | 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. | 649 |
| 32 | 1115 | You will also be asked whether you want to create a directory structure within the repository. Find out about layout options in |
1196 |
| 33 | 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. | 1200 |
| 34 | 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. | 1298 |
| 35 | 2285 | If you want to clear authentication for one realm only then you will have to dig into those directories, find the file which contains the information you want to clear and delete the file. | 2966 |
| 36 | 2748 | Getting the regex just right can be tricky, so to help you sort out a suitable expression there is a test dialog which allows you to enter an expression and then type in filenames to test it against. Start it from the command prompt using the command |
3448 |
| 37 | 3280 | There are other cases which are labelled as tree conflicts simply because the conflict involves a folder rather than a file. For example if you add a folder with the same name to both trunk and branch and then try to merge you will get a tree conflict. If you want to keep the folder from the merge target, just mark the conflict as resolved. If you want to use the one in the merge source then you need to SVN delete the one in the target first and run the merge again. If you need anything more complicated then you have to resolve manually. | 3995 |
| 38 | 4123 | Simple sub-string search works in a manner similar to a search engine. Strings to search for are separated by spaces, and all strings must match. You can use a leading Alice Bob -Eve\n !Alice Bob\n !-Alice -Bob\n \"Alice and Bob\"\n Alice and Bob \"\"\n \"Alice says \"\"hi\"\" to Bob\"\n Alice says \"hi\" to Bob |
4841 |
| 39 | 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. | 5964 |
| 40 | 5246 | From the folder(s) where you wish to apply these properties, use |
5980 |
| 41 | 5250 | If you want to add properties to a tree recursively, follow the steps above, then in the property dialog select each property in turn, click on |
5984 |
| 42 | 5254 | The Import file format is binary and proprietary to TortoiseSVN. Its only purpose is to transfer properties using Import and Export, so there is no need to edit these files. | 5988 |
| 43 | 5282 | You can edit the subversion configuration file to enable this feature on your client. The |
6017 |
| 44 | 5286 | An alternative method is to set the |
6021 |
| 45 | 5290 | Whichever method you choose, you should note that auto-props are only applied to files at the time they are added to the repository. Auto-props will never change the properties of files which are already versioned. | 6025 |
| 46 | 5294 | If you want to be absolutely sure that new files have the correct properties applied, you should set up a repository pre-commit hook to reject commits where the required properties are not set. | 6029 |
| 47 | 5342 | Subversion allows you to set autopropswhich will be applied to newly added or imported files, based on the file extension. This depends on every client having set appropriate autoprops in their subversion configuration file. |
6077 |
| 48 | 5374 | The property |
6111 |
| 49 | 5378 | The regular expression must match the whole reference, not just the revision number. The revision number is extracted from the matched reference string automatically. | 6115 |
| 50 | 5382 | If this property is not set, a default regular expression is used to link revision references. | 6119 |
| 51 | 5386 | When you want to add a new property, you can either pick one from the list in the combo box, or you can enter any property name you like. If your project uses some custom properties, and you want those properties to appear in the list in the combo box (to avoid typos when you enter a property name), you can create a list of your custom properties using |
6123 |
| 52 | 5432 | Fetching properties remotely is a slow operation, so some of the features described above will not work in the repository browser as they do in a working copy. | 6173 |
| 53 | 5436 | When you add a property using the repo browser, only the standard |
6177 |
| 54 | 5444 | Project properties will |
6185 |
| 55 | 5452 | Although TortoiseSVN's project properties are extremely useful, they only work with TortoiseSVN, and some will only work in newer versions of TortoiseSVN. If people working on your project use a variety of Subversion clients, or possibly have old versions of TortoiseSVN, you may want to use repository hooks to enforce project policies. project properties can only help to implement a policy, they cannot enforce it. | 6193 |
| 56 | 6065 | Choosing |
6858 |
| 57 | 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. |
6871 |
| 58 | 6578 | You can use |
7374 |
| 59 | 6666 | The graph is normally restricted to showing branch points, but it is often useful to be able to see the respective HEAD revision for each branch too. If you select |
7469 |
| 60 | 6674 | If you invoked the revision graph from a working copy, you can opt to show the BASE revision on the graph using |
7477 |
| 61 | 6682 | If you invoked the revision graph from a working copy, you can opt to show an additional node representing your modified working copy using |
7485 |
| 62 | 6694 | Each revision graph node represents a revision in the repository where something changed in the tree you are looking at. Different types of node can be distinguished by shape and colour. The shapes are fixed, but colours can be set using |
7497 |
| 63 | 6702 | The default view (grouping off) places the nodes such that their vertical position is in strict revision order, so you have a visual cue for the order in which things were done. Where two nodes are in the same column the order is very obvious. When two nodes are in adjacent columns the offset is much smaller because there is no need to prevent the nodes from overlapping, and as a result the order is a little less obvious. Such optimisations are necessary to keep complex graphs to a reasonable size. Please note that this ordering uses the |
7506 |
| 64 | 6714 | The default behavior (grouping off) has all rows sorted strictly by revision. As a result, long-living branches with sparse commits occupy a whole column for only a few changes and the graph becomes very broad. | 7518 |
| 65 | 6718 | This mode groups changes by branch, so that there is no global revision ordering: Consecutive revisions on a branch will be shown in (often) consecutive lines. Sub-branches, however, are arranged in such a way that later branches will be shown in the same column above older branches to keep the graph slim. As a result, a given row may contain changes from different revisions. | 7522 |
| 66 | 6734 | When a graph is broken into several smaller trees, the trees may appear either in natural revision order, or aligned at the bottom of the window, depending on whether you are using the |
7538 |
| 67 | 6742 | If the layout of the graph has produced a lot of crossing lines, use this option to clean it up. This may make the layout columns appear in less logical places, for example in a diagonal line rather than a column, and the graph may require a larger area to draw. | 7546 |
| 68 | 6750 | Long path names can take a lot of space and make the node boxes very large. Use this option to show only the changed part of a path, replacing the common part with dots. E.g. if you create a branch |
7554 |
| 69 | 6758 | This does just what you expect and shows every revision where something (in the tree that you are graphing) has changed. For long histories this can produce a truly huge graph. | 7562 |
| 70 | 6766 | This ensures that the latest revision on every branch is always shown on the graph. | 7570 |
| 71 | 6774 | When a branch/tag is made, the default behaviour is to show the branch as taken from the last node where a change was made. Strictly speaking this is inaccurate since the branches are often made from the current HEAD rather than a specific revision. So it is possible to show the more correct (but less useful) revision that was used to create the copy. Note that this revision may be younger than the HEAD revision of the source branch. | 7578 |
| 72 | 6782 | When a project has many tags, showing every tag as a separate node on the graph takes a lot of space and obscures the more interesting development branch structure. At the same time you may need to be able to access the tag content easily so that you can compare revisions. This option hides the nodes for tags and shows them instead in the tooltip for the node that they were copied from. A tag icon on the right side of the source node indicates that tags were made. | 7586 |
| 73 | 6790 | Hides paths which are no longer present at the HEAD revision of the repository, e.g. deleted branches. | 7594 |
| 74 | 6798 | Hides branches where no changes were committed to the respective file or sub-folder. This does not necessarily indicate that the branch was not used, just that no changes were made to |
7602 |
| 75 | 6806 | Marks the revision on the graph which corresponds to the update revision of the item you fetched the graph for. If you have just updated, this will be HEAD, but if others have committed changes since your last update your WC may be a few revisions lower down. The node is marked by giving it a bold outline. | 7610 |
| 76 | 6814 | If your WC contains local changes, this option draws it as a separate elliptical node, linked back to the node that your WC was last updated to. The default outline colour is red. You may need to refresh the graph using |
7618 |
| 77 | 6822 | Sometimes the revision graph contains more revisions than you want to see. This option opens a dialog which allows you to restrict the range of revisions displayed, and to hide particular paths by name. | 7626 |
| 78 | 6826 | Tree stripes | 7630 |
| 79 | 6830 | Where the graph contains several trees, it is sometimes useful to use alternating colours on the background to help distinguish between trees. | 7634 |
| 80 | 6838 | Shows a small picture of the entire graph, with the current view window as a rectangle which you can drag. This allows you to navigate the graph more easily. Note that for very large graphs the overview may become useless due to the extreme zoom factor and will therefore not be shown in such cases. | 7642 |
| 81 | 6842 | Because a revision graph is often quite complex, there are a number of features which can be used to tailor the view the way you want it. These are available in the |
7646 |
| 82 | 6850 | To make it easier to navigate a large graph, use the overview window. This shows the entire graph in a small window, with the currently displayed portion highlighted. You can drag the highlighted area to change the displayed region. | 7654 |
| 83 | 6870 | You can also merge changes in the selected revision(s) into a different working copy. A folder selection dialog allows you to choose the working copy to merge into, but after that there is no confirmation dialog, nor any opportunity to try a test merge. It is a good idea to merge into an unmodified working copy so that you can revert the changes if it doesn't work out! This is a useful feature if you want to merge selected revisions from one branch to another. | 7675 |
| 84 | 6878 | First-time users may be surprised by the fact that the revision graph shows something that does not match the user's mental model. If a revision changes multiple copies or branches of a file or folder, for instance, then there will be multiple nodes for that single revision. It is a good practice to start with the leftmost options in the toolbar and customize the graph step-by-step until it comes close to your mental model. | 7683 |
| 85 | 6882 | All filter options try lose as little information as possible. That may cause some nodes to change their color, for instance. Whenever the result is unexpected, undo the last filter operation and try to understand what is special about that particular revision or branch. In most cases, the initially expected outcome of the filter operation would either be inaccurate or misleading. | 7687 |
| 86 | 6886 | If you want to check the server again for newer information, you can simply refresh the view using |
7691 |
| 87 | 6890 | If you are using the log cache and you think the message content or author may have changed, you should use the log dialog to refresh the messages you need. Since the revision graph works from the repository root, we would have to invalidate the entire log cache, and refilling it could take a |
7695 |
| 88 | 6894 | Pruning Trees | 7699 |
| 89 | 6898 | A large tree can be difficult to navigate and sometimes you will want to hide parts of it, or break it down into a forest of smaller trees. If you hover the mouse over the point where a node link enters or leaves the node you will see one or more popup buttons which allow you to do this. | 7703 |
| 90 | 6918 | Click on the graph background for the main context menu, which offers options to |
7723 |
| 91 | 6942 | 7748 | |
| 92 | 6970 | To export single files with TortoiseSVN, you have to use the repository browser ( |
7779 |
| 93 | 6978 | If you want to export a copy of your project tree structure but containing only the files which have changed in a particular revision, or between any two revisions, use the compare revisions feature described in |
7787 |
| 94 | 6991 | Sometimes you have a working copy which you want to convert back to a normal folder without the |
7800 |
| 95 | 6995 | The answer is surprisingly simple - export the folder to itself! TortoiseSVN detects this special case and asks if you want to make the working copy unversioned. If you answer |
7804 |
| 96 | 7031 | You may be surprised to find that TortoiseSVN contacts the repository as part of this operation. All it is doing is performing some simple checks to make sure that the new URL really does refer to the same repository as the existing working copy. | 7841 |
| 97 | 7124 | If it begins with the string |
7934 |
| 98 | 7128 | A URL beginning with the string |
7938 |
| 99 | 7172 | If two expressions are set, then the first expression is used as a pre-filter to find expressions which contain bug IDs. The second expression then extracts the bare bug IDs from the result of the first regex. This allows you to use a list of bug IDs and natural language expressions if you wish. e.g. you might fix several bugs and include a string something like this: This change resolves issues #23, #24 and #25 |
7987 |
| 100 | 7180 | The first expression picks out issues #23, #24 and #25from the surrounding log message. The second regex extracts plain decimal numbers from the output of the first regex, so it will return 23, 24and 25to use as bug IDs. |
7995 |
| 101 | 7184 | Breaking the first regex down a little, it must start with the word issue, possibly capitalised. This is optionally followed by an s(more than one issue) and optionally a colon. This is followed by one or more groups each having zero or more leading whitespace, an optional comma or andand more optional space. Finally there is a mandatory #and a mandatory decimal number. |
7999 |
| 102 | 7208 | And even if you don't need the links, the issue numbers show up as a separate column in the log dialog, making it easier to find the changes which relate to a particular issue. | 8026 |
| 103 | 7222 | No Issue Tracker Information from Repository Browser | 8040 |
| 104 | 7231 | For the same reason, project properties will not be propagated automatically when a child folder is added using the repo browser. | 8050 |
| 105 | 7243 | The previous section deals with adding issue information to the log messages. But what if you need to get information from the issue tracker? The commit dialog has a COM interface which allows integration an external program that can talk to your tracker. Typically you might want to query the tracker to get a list of open issues assigned to you, so that you can pick the issues that are being addressed in this commit. | 8063 |
| 106 | 7247 | 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 |
8067 |
| 107 | 7255 | For illustration purposes, let's suppose that your system administrator has provided you with an issue tracker plugin which you have installed, and that you have set up some of your working copies to use the plugin in TortoiseSVN's settings dialog. When you open the commit dialog from a working copy to which the plugin has been assigned, you will see a new button at the top of the dialog. |
8075 |
| 108 | 7511 | Always close dialogs for local operations | 8339 |
| 109 | 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. | 8343 |
| 110 | 7739 | When using filtering in the log dialog, search terms are highlighted in the results using this colour. | 8571 |
| 111 | 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 |
8815 |
| 112 | 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. | 8823 |
| 113 | 7987 | An example will help here: Exclude:\n C:\n C:\\develop\\?\n C:\\develop\\tsvn\\obj\n C:\\develop\\tsvn\\bin\n \n Include:\n C:\\develop\n |
8827 |
| 114 | 8003 | It is often convenient to use a subst T: C:\\TortoiseSVN\\trunk\\doc\n |
8853 |
| 115 | 8007 | An easy way to work around this is to exclude the original path from showing overlays, so that the overlays show up on the |
8860 |
| 116 | 8011 | Sometimes you will exclude areas that contain working copies, which saves TSVNCache from scanning and monitoring for changes, but you still want a visual indication that such folders are versioned. The |
8864 |
| 117 | 8015 | As a special exception to this, drives |
8868 |
| 118 | 8031 | Enabled Overlay Handlers | 8884 |
| 119 | 8039 | 8893 | |
| 120 | 8067 | You must specify the full path to the executable. For TortoisePlink.exe this is the standard TortoiseSVN bin directory. Use the \"C:\\Program Files\\TortoiseSVN\\bin\\TortoisePlink.exe\"\n |
8922 |
| 121 | 8075 | TortoisePlink does not have any documentation of its own because it is just a minor variant of Plink. Find out about command line parameters from the |
8933 |
| 122 | 8083 | Finally, setting up SSH on server and clients is a non-trivial process which is beyond the scope of this help file. However, you can find a guide in the TortoiseSVN FAQ listed under |
8941 |
| 123 | 8233 | If you want to remove a single item from one of the combo boxes you can do that in-place. Just click on the arrow to drop the combo box down, move the mouse over the item you want to remove and type |
9142 |
| 124 | 8249 | TortoiseSVN caches log messages fetched by the Show Log dialog to save time when you next show the log. If someone else edits a log message and you already have that message cached, you will not see the change until you clear the cache. Log message caching is enabled on the |
9158 |
| 125 | 8277 | TortoiseSVN keeps a log of everything written to its progress dialogs. This can be useful when, for example, you want to check what happened in a recent update command. | 9187 |
| 126 | 8281 | The log file is limited in length and when it grows too big the oldest content is discarded. By default 4000 lines are kept, but you can customize that number. | 9191 |
| 127 | 8301 | 9211 | |
| 128 | 8309 | Enables log caching whenever log data is requested. If checked, data will be retrieved from the cache when available, and any messages not in the cache will be retrieved from the server and added to the cache. | 9219 |
| 129 | 8313 | If caching is disabled, data will always be retrieved directly from the server and not stored locally. | 9223 |
| 130 | 8321 | Occasionally you may have to connect to a server which uses the same URL for all repositories. Older versions of |
9231 |
| 131 | 8329 | Some hosting services give all their repositories the same UUID. You may even have done this yourself by copying a repository folder to create a new one. For all sorts of reasons this is a bad idea - a UUID should be |
9239 |
| 132 | 8337 | If you are working offline, or if the repository server is down, the log cache can still be used to supply log messages already held in the cache. Of course the cache may not be up-to-date, so there are options to allow you to select whether this feature should be used. | 9247 |
| 133 | 8341 | When log data is being taken from the cache without contacting the server, the dialog using those message will show the offline state in its title bar. | 9251 |
| 134 | 8349 | When you invoke the log dialog you will normally want to contact the server to check for any newer log messages. If the timeout set here is non-zero then the server will only be contacted when the timeout has elapsed since the last time contact. This can reduce server round-trips if you open the log dialog frequently and the server is slow, but the data shown may not be completely up-to-date. If you want to use this feature we suggest using a value of 300 (5 minutes) as a compromise. | 9259 |
| 135 | 8357 | If you browse around a lot of repositories you will accumulate a lot of log caches. If you're not actively using them, the cache will not grow very big, so TortoiseSVN purges them after a set time by default. Use this item to control cache purging. | 9267 |
| 136 | 8365 | Larger caches are more expensive to reacquire, so TortoiseSVN only purges small caches. Fine tune the threshold with this value. | 9275 |
| 137 | 8373 | Occasionally something goes wrong with the caching and causes a crash. If this happens the cache is normally deleted automatically to prevent a recurrence of the problem. If you use the less stable nightly build you may opt to keep the cache anyway. | 9283 |
| 138 | 8381 | On this page you can see a list of the repositories that are cached locally, and the space used for the cache. If you select one of the repositories you can then use the buttons underneath. | 9291 |
| 139 | 8389 | Click on the |
9299 |
| 140 | 8393 | Click on |
9303 |
| 141 | 8417 | The amount of disk space used for the cache. Data is compressed, so disk usage is generally fairly modest. | 9327 |
| 142 | 8465 | The number of revision ranges which we have not fetched, simply because they haven't been requested. This is a measure of the number of holes in the cache. | 9375 |
| 143 | 8505 | One application for such hooks might be to call a program like |
9416 |
| 144 | 8580 | Called before an attempt to contact the repository. Called at most once in five minutes. | 9492 |
| 145 | 8640 | The repository revision to which the update should be done or after a commit completes. | 9553 |
| 146 | 8644 | Path to a file containing the error message. If there was no error, the file will be empty. | 9557 |
| 147 | 8648 | The current working directory with which the script is run. This is set to the common root directory of all affected paths. | 9561 |
| 148 | 8656 | Note that although we have given these parameters names for convenience, you do not have to refer to those names in the hook settings. All parameters listed for a particular hook are always passed, whether you want them or not ;-) | 9569 |
| 149 | 8660 | If you want the Subversion operation to hold off until the hook has completed, check |
9573 |
| 150 | 8664 | Normally you will want to hide ugly DOS boxes when the script runs, so |
9577 |
| 151 | 8672 | A small tool is included in the TortoiseSVN installation folder named |
9586 |
| 152 | 8680 | TortoiseSVN can use a COM plugin to query issue trackers when in the commit dialog. The use of such plugins is described in |
9594 |
| 153 | 8688 | 9602 | |
| 154 | 8692 | This property specifies the COM UUID of the IBugtraqProvider, for example |
9606 |
| 155 | 8696 | This is the same as |
9610 |
| 156 | 8704 | If you want all users to use the same COM plugin for your project, you can specify the plugin also with the properties |
9618 |
| 157 | 8732 | You can select the font used to display the text, and the point size to use. This applies both to the file content, and to the author and revision information shown in the left pane. | 9646 |
| 158 | 8780 | A few infrequently used settings are available only in the advanced page of the settings dialog. These settings modify the registry directly and you have to know what each of these settings is used for and what it does. Do not modify these settings unless you are sure you need to change them. | 9696 |
| 159 | 8788 | Set this to |
9705 |
| 160 | 8796 | This can be useful if you use something other than the windows explorer or if you get problems with the context menu displaying incorrectly. Set this value to |
9714 |
| 161 | 8800 | If you don't want TortoiseSVN to show icons for the context menus in its own dialogs, set this value to |
9718 |
| 162 | 8804 | The log dialog shows the revision the working copy path is at in bold. But this requires that the log dialog fetches the status of that path. Since for very big working copies this can take a while, you can set this value to |
9722 |
| 163 | 8808 | The status list control which is used in various dialogs (e.g., commit, check-for-modifications, add, revert, ...) uses full row selection (i.e., if you select an entry, the full row is selected, not just the first column). This is fine, but the selected row then also covers the background image on the bottom right, which can look ugly. To disable full row select, set this value to |
9726 |
| 164 | 8812 | The commit and log dialog use styling (e.g. bold, italic) in commit messages (see |
9730 |
| 165 | 8816 | TortoiseSVN uses accelerators for its explorer context menu entries. Since this can lead to doubled accelerators (e.g. the |
9734 |
| 166 | 8820 | As with the explorer, TortoiseSVN shows additional commands if the |
9738 |
| 167 | 8824 | If you don't want the explorer to update the status overlays while another TortoiseSVN command is running (e.g. Update, Commit, ...) then set this value to |
9742 |
| 168 | 8828 | This value contains the URL from which TortoiseSVN tries to download a text file to find out if there are updates available. This might be useful for company admins who don't want their users to update TortoiseSVN until they approve it. | 9746 |
| 169 | 8832 | The extra columns the TortoiseSVN adds to the details view in Windows Explorer are normally only active in a working copy. If you want those to be accessible everywhere, not just in working copies, set this value to |
9750 |
| 170 | 8836 | If an update adds a new file from the repository which already exists in the local working copy as an unversioned file, the default action is to keep the local file, showing it as a (possibly) modified version of the new file from the repository. If you would prefer TortoiseSVN to create a conflict in such situations, set this value to |
9754 |
| 171 | 8840 | TortoiseSVN checks whether there's a new version available about once a week. If an updated version is found, the commit dialog shows a link control with that info. If you prefer the old behavior back where a dialog pops up notifying you about the update, set this value to |
9758 |
| 172 | 8844 | TortoiseSVN checks whether there's a new version available about once a week. If you don't want TortoiseSVN to do this check, set this value to |
9762 |
| 173 | 8848 | The auto-completion list shown in the commit message editor displays the names of files listed for commit. To also include these names with extensions removed, set this value to |
9766 |
| 174 | 8852 | When you merge revisions from another branch, and merge tracking information is available, the log messages from the revisions you merge will be collected to make up a commit log message. A pre-defined string is used to separate the individual log messages of the merged revisions. If you prefer, you can set this to a value containing a separator string of your choice. | 9770 |
| 175 | 8860 | By default, TortoiseSVN always runs an update with externals included. This avoids problems with inconsistent working copies. If you have however a lot of externals set, an update can take quite a while. Set this value to |
9779 |
| 176 | 8864 | In most dialogs in TortoiseSVN, you can use |
9783 |
| 177 | 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 |
9787 |
| 178 | 9029 | Replaced with the commit date/time of the highest commit revision. By default, international format is used: |
9955 |
| 179 | 9097 | Replaced with the lock date. Time formatting can be used as described for |
10024 |
| 180 | 9113 | 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 |
10040 |
| 181 | 9139 | A file like this will be included in the build so you would expect it to be versioned. Be sure to version the template file, not the generated file, otherwise each time you regenerate the version file you need to commit the change, which in turn means the version file needs to be updated. | 10126 |
| 182 | 9167 | This method traverses the working copy gathering the revision information. Naturally you must call this before you can access the information using the remaining methods. The first parameter is the path. The second parameter should be true if you want to include folder revisions. Equivalent to the |
10154 |
| 183 | 9224 | String representing the date when the lock was created, or an empty string if the item is not locked. | 10211 |
| 184 | 9228 | String representing the lock owner, or an empty string if the item is not locked. | 10215 |
| 185 | 9249 | \n using LibSubWCRev;\n SubWCRev sub = new SubWCRev();\n sub.GetWCInfo(\"C:\\\\PathToMyFile\\\\MyFile.cc\", true, true);\n if (sub.IsSvnItem == true)\n {\n MessageBox.Show(\"versioned\");\n }\n else\n {\n MessageBox.Show(\"not versioned\");\n }\n |
10480 |
| 186 | 9270 | To get a tighter integration with issue trackers than by simply using the |
10514 |
| 187 | 9278 | You should provide both a 32-bit and 64-bit version of your plugin. Because the x64-Version of TortoiseSVN can not use a 32-bit plugin and vice-versa. | 10522 |
| 188 | 9308 | \n HRESULT GetCommitMessage (\n // Parent window for your provider's UI.\n [in] HWND hParentWnd,\n \n // Parameters for your provider.\n [in] BSTR parameters,\n [in] BSTR commonRoot,\n [in] SAFEARRAY(BSTR) pathList,\n \n // The text already present in the commit message.\n // Your provider should include this text in the new message,\n // where appropriate.\n [in] BSTR originalMessage,\n \n // The new text for the commit message.\n // This replaces the original message.\n [out, retval] BSTR *newMessage\n );\n |
10605 |
| 189 | 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. | 10629 |
| 190 | 9317 | The |
10633 |
| 191 | 9321 | The |
10637 |
| 192 | 9325 | The |
10641 |
| 193 | 9329 | The |
10645 |
| 194 | 9333 | The |
10649 |
| 195 | 9345 | \n HRESULT GetCommitMessage2 (\n // Parent window for your provider's UI.\n [in] HWND hParentWnd,\n \n // Parameters for your provider.\n [in] BSTR parameters,\n // The common URL of the commit\n [in] BSTR commonURL,\n [in] BSTR commonRoot,\n [in] SAFEARRAY(BSTR) pathList,\n \n // The text already present in the commit message.\n // Your provider should include this text in the new message,\n // where appropriate.\n [in] BSTR originalMessage,\n \n // You can assign custom revision properties to a commit\n // by setting the next two params.\n // note: Both safearrays must be of the same length.\n // For every property name there must be a property value!\n \n // The content of the bugID field (if shown)\n [in] BSTR bugID,\n \n // Modified content of the bugID field\n [out] BSTR * bugIDOut,\n \n // The list of revision property names.\n [out] SAFEARRAY(BSTR) * revPropNames,\n \n // The list of revision property values.\n [out] SAFEARRAY(BSTR) * revPropValues,\n \n // The new text for the commit message.\n // This replaces the original message\n [out, retval] BSTR * newMessage\n );\n |
10661 |
| 196 | 9350 | This method is called from the TortoiseSVN commit dialog when the user clicks on the plugin button. This method is called instead of |
10704 |
| 197 | 9354 | The parameter |
10708 |
| 198 | 9358 | The parameter |
10712 |
| 199 | 9362 | The return parameter |
10716 |
| 200 | 9366 | The |
10720 |
| 201 | 9375 | 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 |
10749 |
| 202 | 9379 | For the branch/tag dialog, the |
10753 |
| 203 | 9383 | The return parameter |
10757 |
| 204 | 9387 | \n HRESULT OnCommitFinished (\n // Parent window for any (error) UI that needs to be displayed.\n [in] HWND hParentWnd,\n \n // The common root of all paths that got committed.\n [in] BSTR commonRoot,\n \n // All the paths that got committed.\n [in] SAFEARRAY(BSTR) pathList,\n \n \n // The text already present in the commit message.\n [in] BSTR logMessage,\n \n // The revision of the commit.\n [in] ULONG revision,\n \n \n // An error to show to the user if this function\n // returns something else than S_OK\n [out, retval] BSTR * error\n );\n |
10761 |
| 205 | 9392 | 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 |
10789 |
| 206 | 9401 | This method is called from the settings dialog where the user can configure the plugins. If a plugin provides its own configuration dialog with |
10808 |
| 207 | 9405 | \n HRESULT ShowOptionsDialog(\n // Parent window for the options dialog\n [in] HWND hParentWnd,\n \n // Parameters for your provider.\n [in] BSTR parameters,\n \n // The parameters string\n [out, retval] BSTR * newparameters\n );\n |
10812 |
| 208 | 9410 | This method is called from the settings dialog when the user clicks on the \"Options\" button that is shown if |
10828 |
| 209 | 9414 | The |
10832 |
| 210 | 9438 | 10860 | |
| 211 | 9442 | If you want to help out with the development of TortoiseSVN, then you should take part in discussions on |
10864 |
| 212 | 9446 | If you want to help with the translation of the TortoiseSVN user interface or the documentation, send an e-mail to |
10868 |
| 213 | 9615 | In the |
11042 |
| 214 | 9671 | vendor projects | 11102 |
| 215 | 9691 | Of the three methods described, this is the only one which needs no setup on the client side. Once externals are specified in the folder properties, all clients will get populated folders when they update. | 11124 |
| 216 | 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. |
11221 |
| 217 | 9775 | If you have a working copy which you no longer need, how do you get rid of it cleanly? Easy - just delete it in Windows Explorer! Working copies are private local entities, and they are self-contained. | 11237 |
| 218 | 9893 | As of version 1.5.0 and later, TortoiseSVN allows you to disable (actually, hide) context menu entries. Since this is a feature which should not be used lightly but only if there is a compelling reason, there is no GUI for this and it has to be done directly in the registry. This can be used to disable certain commands for users who should not use them. But please note that only the context menu entries in the |
11375 |
| 219 | 9897 | The registry keys which hold the information on which context menus to show are |
11379 |
| 220 | 9901 | Each of these registry entries is a |
11383 |
| 221 | 10075 | Example: to disable the Relocatethe Delete unversioned itemsand the Settingsmenu entries, add the values assigned to the entries like this: 0x0000000000080000\n + 0x0000000080000000\n + 0x2000000000000000\n = 0x2000000080080000\n |
11557 |
| 222 | 10123 | You can also specify a file which contains a list of paths, separated by newlines. The file must be in UTF-16 format. If you pass such a file, use instead of . To have TortoiseProc delete that file after the command is finished, you can pass the parameter . | 11611 |
| 223 | 10338 | Cleans up interrupted or aborted operations and unlocks the working copy in |
11829 |
| 224 | 10427 | Depending on the URLs and revisions to compare, this either shows a unified diff (if the option is set), a dialog with a list of files that have changed or if the URLs point to files starts the diff viewer for those two files. | 11919 |
| 225 | 10544 | Using special URLs, it is also possible to call TortoiseProc from a web page. | 12055 |
| 226 | 10548 | TortoiseSVN registers a new protocol |
12059 |
| 227 | 10560 | with |
12071 |
| 228 | 10581 | The image diff tool has a few command line options which you can use to control how the tool is started. The program is called |
12102 |
| 229 | 10610 | If specified, the image diff tool switches to the overlay mode (alpha blend). | 12131 |
| 230 | 10614 | If specified, the image diff tool fits both images together. | 12135 |
| 231 | 10672 | The depth combo box items relate to the |
12208 |
| 232 | 11018 | Every file and folder has a Subversion status value as reported by the Subversion library. In the command line client, these are represented by single letter codes, but in TortoiseSVN they are shown graphically using the icon overlays. Because the number of overlays is very limited, each overlay may represent one of several status values. | 12700 |
| 233 | 11058 | If an item has subversion status |
12740 |
| 234 | 11062 | An item can only have one Subversion status value. For example a file could be locally modified and it could be marked for deletion at the same time. Subversion returns a single status value - in this case |
12744 |
| 235 | 11066 | When TortoiseSVN displays the status recursively (the default setting), each folder displays an overlay reflecting its own status and the status of all its children. In order to display a single |
12748 |
| 236 | 11142 | Install Cygwin SSH daemon as described here: |
12843 |
| 237 | 11146 | Create a new Windows user account |
12847 |
| 238 | 11158 | Grab the tools we need for using SSH on the windows client from this site: |
12865 |
| 239 | 11166 | The next step is to create a key pair for authentication. There are two possible ways to create keys. The first is to create the keys with PuTTYgen on the client, upload the public key to your server and use the private key with PuTTY. The other is to create the key pair with the OpenSSH tool ssh-keygen, download the private key to your client and convert the private key to a PuTTY-style private key. | 12873 |
| 240 | 11174 | Login to the server as ssh-keygen -b 1024 -t dsa -N passphrase -f keyfile\n ls -l keyfile*\n |
12881 |
| 241 | 11178 | Append the public key to those in the cat keyfile.pub >> /home/svnuser/.ssh/authorized_keys\n |
12890 |
| 242 | 11182 | In order to use the private key we generated, we have to convert it to a putty format. This is because the private key file format is not specified by a standards body. After you download the private key file to your client PC, start PuTTYgen and use |
12897 |
| 243 | 11286 | The standard installer has support only for English, but you can download separate language packs and spell check dictionaries separately after installation. | 13049 |
| 244 | 11310 | The documentation has also been translated into several different languages. You can download translated manuals from the |
13075 |
Total:244
String marked as fuzzy is not in final shape.
| Index | Line | English | Line | Native |
| 1 | - | Although most people just download the installer, you also have full read access to the source code of this program. You can browse it on this link |
231 | TortoiseSVN est un projet Open Source. Cela signifie que vous avez un accès total au code source de ce programme. Vous pouvez y accéder avec ce lien |
| 2 | - | In 2002, Tim Kemp found that Subversion was a very good version control system, but it lacked a good GUI client. The idea for a Subversion client as a Windows shell integration was inspired by the similar client for CVS named TortoiseCVS. Tim studied the source code of TortoiseCVS and used it as a base for TortoiseSVN. He then started the project, registered the domain |
248 | En 2002, Tim Kemp a constaté que Subversion était un très bon système de contrôle de version, mais il lui manquait un bon client avec une interface graphique. L'idée d'un client Subversion comme une intégration du shell de Windows a été inspirée par le client semblable pour CVS nommé TortoiseCVS. |
| 3 | - | Around that time, Stefan Küng was looking for a good and free version control system and found Subversion and the source for TortoiseSVN. Since TortoiseSVN was still not ready for use, he joined the project and started programming. He soon rewrote most of the existing code and started adding commands and features, up to a point where nothing of the original code remained. | 253 | Tim a étudié le code source de TortoiseCVS et l'a utilisé comme base pour TortoiseSVN. Il a alors commencé le projet, a enregistré le domaine |
| 4 | - | As Subversion became more stable it attracted more and more users who also started using TortoiseSVN as their Subversion client. The user base grew quickly (and is still growing every day). That's when Lübbe Onken offered to help out with some nice icons and a logo for TortoiseSVN. He now takes care of the website and manages the many translations. | 258 | Comme Subversion est devenu plus stable, il a attiré de plus en plus d'utilisateurs qui ont aussi commencé à utiliser TortoiseSVN comme leur client Subversion. La base utilisateur a grandi rapidement (et grandit toujours chaque jour). C'est à ce moment que Lübbe Onken s'est proposé d'aider avec des icônes agréables et un logo pour TortoiseSVN. Et il s'occupe du site Web et gère la traduction. |
| 5 | - | This book is written for computer-literate folk who want to use Subversion to manage their data, but prefer to use a GUI client rather than a command line client. TortoiseSVN is a windows shell extension and it is assumed that the user is familiar with the windows explorer and how to use it. | 343 | Ce manuel est écrit pour les gens initiés à l'informatique qui veulent utiliser Subversion pour gérer leurs données, mais qui ne sont pas à l'aise pour utiliser le client en ligne de commande pour ce faire. Puisque TortoiseSVN est une extension du shell Windows, il est sous-entendu que l'utilisateur est familiarisé avec l'explorateur Windows et sait comment l'utiliser. |
| 6 | - | But what are the changes? Right click on one of the changed files and select |
583 | Pour fusionner la branche de fonction dans le tronc, vous devez aller sur une copie de travail du tronc. Sélectionnez |
| 7 | - | If you want to undo the effects of a particular revision, start with the Log dialog and find the offending revision. Select |
636 | Ou si vous voulez faire d'une révision précédente la nouvelle révision HEAD, faites |
| 8 | - | TortoiseSVN does not support |
1208 | Pour des problèmes de compatibilité, les accès aux référentiels BDB de type |
| 9 | - | import this structure into the repository via a |
1376 | importez cette structure dans le référentiel via un |
| 10 | - | You can get those three files directly from our source repository at |
2235 | Vous pouvez récupérer ces trois fichiers depuis notre référentiel : |
| 11 | - | 2945 | ||
| 12 | - | In windows explorer, |
3221 | Dans l'explorateur de référentiel, faites un |
| 13 | - | 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 <<<<<<< filename\n your changes\n =======\n code merged from repository\n >>>>>>> revision\n |
3708 | Un conflit de fichier arrive quand 2 développeurs our plus modifient un même fichier. Dans la mesure où Subversion ne sait rien de votre projet, il laisse la résolution des conflits à la charge des développeurs. Dès qu'un conflit est détecté, vous devriez ouvrir le fichier en question, et chercher les lignes commençant par \t<<<<<<< nom_de_fichier\n \t\tvos modifications\n \t=======\n \t\tcode fusionné depuis le référentiel\n \t>>>>>>> révision\n \t |
| 14 | - | Compare the selected revision with the previous revision. This works in a similar manner to comparing with your working copy. For folders this option will first show the changed files dialog allowing you to select files to compare. | 4386 | Compare la révision sélectionnée avec la révision précédente. Cette fonctionnalité est similaire à la comparaison avec votre copie de travail. |
| 15 | - | Show the changed files dialog allowing you to select files. Blame the selected revision, and the previous revision, and compare the results using a visual diff tool. (folders only). | 4395 | Annoter la révision sélectionnée et la révision précédente et comparer les résultats en utilisant un outil de comparaison. (juste valable pour les répertoires). |
| 16 | - | Click on the search icon to select which information you want to search in, and to choose |
4836 | Cliquez sur l'icone de recherche pour sélectionner le type d'information que vous souhaitez rechercher, et pour choisir le mode |
| 17 | - | Describing the use of regular expression searches is beyond the scope of this manual, but you can find online documentation and a tutorial at |
4858 | Si vous êtes peu familiers avec les expressions régulières, jetez un coup d'oeil à la documentation en ligne et au didactitiel à |
| 18 | - | You can also filter the path names in the bottom pane using the |
4867 | Vous pouvez aussi filtrer les noms de chemin dans le panneau du bas en utilisant la case à cocher |
| 19 | - | Edit properties at HEAD revision | 5959 | Temps d'attente maximum écoulé avant la mise à jour de la révision de tête (HEAD). |
| 20 | - | You can configure Subversion and TortoiseSVN to set properties automatically on files and folders when they are added to the repository. There are two ways of doing this. | 6012 | Vous pouvez configurer Subversion pour définir automatiquement des propriétés sur les fichiers et sur les dossiers lorsqu'ils sont ajoutés au référentiel. Lisez |
| 21 | - | In the Commit dialog you have the option to paste in the list of changed files, including the status of each file (added, modified, etc). |
6085 | Dans la boîte de dialogue Livrer, vous avez une option pour coller la liste des fichiers changés, en incluant le statut de chaque fichier (ajouté, modifié, etc). |
| 22 | - | TortoiseSVN can use spell checker modules which are also used by OpenOffice and Mozilla. If you have those installed this property will determine which spell checker to use, i.e. in which language the log messages for your project should be written. |
6090 | TortoiseSVN peut utiliser des modules de vérification orthographique qui sont aussi utilisés par OpenOffice et Mozilla. Si vous avez ceux-ci installés, cette propriété déterminera quel vérificateur d'orthographe utiliser, c'est-à-dire en quelle langue les commentaire de votre projet devraient être écrits. |
| 23 | - | Some |
6132 | Certaines propriétés |
| 24 | - | TortoiseSVN can integrate with some bug tracking tools. This uses project properties that start with |
6137 | TortoiseSVN peut s'intégrer à quelques outils de traque de bugs. Cela utilise des propriétés, qui commencent par |
| 25 | - | It can also integrate with some web-based repository browsers, using project properties that start with |
6142 | Il peut aussi s'intégrer à certains explorateurs de référentiel en ligne. Lisez |
| 26 | - | These special project properties must be set on |
6151 | Ces propriétés |
| 27 | - | If the external project is in the same repository, any changes you make there will be included in the commit list when you commit your main project. | 6257 | Si le projet externe est dans le même référentiel, les changements que vous y faites seront inclus dans la liste de livraisons quand vous livrerez votre projet principal. |
| 28 | - | Now everything is set up, all you have to do is click on the |
6765 | A présent que tout est correctement configuré, tout ce que vous avez à faire est de cliquer sur le bouton |
| 29 | - | Normally you will want to look at the conflicts and resolve them yourself. In that case, choose the |
6862 | Normalement vous allez vouloir voir les conflits et les résoudre. Dans ce cas, choisissez |
| 30 | - | Compare the folder with a previously marked folder, either as a unified diff, or as a list of changed files which can then be visually diffed using the default diff tool. This can be particularly useful for comparing two tags, or trunk and branch to see what changed. | 7352 | Si vous choisissez deux éléments, vous pouvez voir les différences soit avec des différences unifiées, soit comme une liste des fichiers qui peuvent être comparés visuellement en utilisant l'outil de comparaison par défaut. Cela peut être particulièrement utile pour comparer deux étiquettes pour voir ce qui a changé. |
| 31 | - | If you select two folders in the right pane, you can view the differences either as a unified-diff, or as a list of files which can be visually diffed using the default diff tool. | 7361 | Si vous choisissez deux éléments, vous pouvez voir les différences soit avec des différences unifiées, soit comme une liste des fichiers qui peuvent être comparés visuellement en utilisant l'outil de comparaison par défaut. Cela peut être particulièrement utile pour comparer deux étiquettes pour voir ce qui a changé. |
| 32 | - | You can also use the repository browser for drag-and-drop operations. If you drag a folder from explorer into the repo-browser, it will be imported into the repository. Note that if you drag multiple items, they will be imported in separate commits. | 7378 | Vous pouvez aussi utiliser l'explorateur de référentiel pour les opérations de glisser-déplacer. Si vous glissez un dossier de l'explorateur dans l'explorateur de référentiel, il sera importé dans le référentiel. Notez que si vous glisser plusieurs éléments, ils seront importés dans des livraisons séparées. |
| 33 | - | If you want to copy/move a file or folder to another location and also give it a new name at the same time, you can |
7387 | Si vous voulez copier/déplacer un fichier ou un dossier à un autre emplacement et lui donner aussi un nouveau nom en même temps, vous pouvez |
| 34 | - | Sometimes when you try to open a path you will get an error message in place of the item details. This might happen if you specified an invalid URL, or if you don't have access permission, or if there is some other server problem. If you need to copy this message to include it in an email, just right click on it and use |
7396 | Parfois quand vous essayerez d'ouvrir un chemin, vous obtiendrez un message d'erreur à la place des détails de l'élément. Cela pourrait arriver si vous spécifiez une URL invalide, ou si vous n'avez pas d'autorisation d'accès, ou s'il y a d'autres problèmes serveur. Si vous devez copier ce message pour l'inclure dans un e-mail, faites simplement un clic droit dessus et utilisez |
| 35 | - | In order to generate the graph, TortoiseSVN must fetch all log messages from the repository root. Needless to say this can take several minutes even with a repository of a few thousand revisions, depending on server speed, network bandwidth, etc. If you try this with something like the |
7425 | Pour générer le graphique, TortoiseSVN doit aller chercher tous les commentaires depuis la racine de référentiel. Inutile de dire cela peut prendre plusieurs minutes même avec un référentiel de quelques milliers de révisions, selon la vitesse du serveur, la bande passante du réseau, etc. Si vous essayez cela avec quelque chose comme le projet |
| 36 | - | The good news is that if you are using log caching, you only have to suffer this delay once. After that, log data is held locally. Log caching is enabled in TortoiseSVN's settings. | 7430 | La bonne nouvelle est que vous si mettez le journal en cache, vous n'aurez à attendre qu'une fois. Ensuite, ces données seront stockées localement. Ce paramètre est activé dans la page |
| 37 | - | Items which have been added, or created by copying another file/folder are shown using a rounded rectangle. The default colour is green. Tags and trunks are treated as a special case and use a different shade, depending on the |
7443 | Les éléments qui ont été ajoutés, ou créés en copiant un autre fichier/dossier sont affichés en utilisant un rectangle arrondi. |
| 38 | - | Deleted items eg. a branch which is no longer required, are shown using an octagon (rectangle with corners cut off). The default colour is red. | 7452 | Les éléments supprimés, une branche qui n'est plus exigée par exemple, sont montrées en utilisant un octogone (un rectangle avec des coins coupés). |
| 39 | - | Note that by default the graph only shows the points at which items were added, copied or deleted. Showing every revision of a project will generate a very large graph for non-trivial cases. If you really want to see |
7501 | Le graphique de révision montre plusieurs types de noeud : |
| 40 | - | If you select two revisions (Use |
7662 | Si vous sélectionnez deux révisions (faites un |
| 41 | - | Sometimes you may want a copy of your working tree without any of those |
7739 | Parfois vous pouvez vouloir une copie de votre arborescence de travail sans ces répertoires |
| 42 | - | If you execute this command on your working copy you'll be asked for a place to save the |
7756 | Parfois vous pouvez vouloir une copie de votre arborescence de travail sans ces répertoires |
| 43 | - | Another way to export from a working copy is to |
7761 | Une autre façon de faire une exportation consiste à |
| 44 | - | When exporting from a working copy, if the target folder already contains a folder of the same name as the one you are exporting, you will be given the option to overwrite the existing content, or to create a new folder with an automatically generated name, eg. |
7766 | Si le répertoire cible contient déjà un répertoire du même nom que celui que vous exportez, un nouveau répertoire sera créé avec un suffixe |
| 45 | - | 7836 | ||
| 46 | - | Set this to |
7942 | Mettez cela à |
| 47 | - | There are two ways to integrate TortoiseSVN with issue trackers. One is based on simple strings, the other is based on |
7947 | Il y a deux façons d'intégrer TortoiseSVN avec les traqueurs d'incidents. L'une est basée sur des chaînes simples, l'autre sur les |
| 48 | - | This property activates the bug tracking system in |
7956 | |
| 49 | - | This text is shown by TortoiseSVN on the commit dialog to label the edit box where you enter the issue number. If it's not set, |
7965 | Ce texte est affiché par TortoiseSVN sur la boîte de dialogue de livraison comme label pour la boîte de saisie où vous entrez le numéro d'incident. S'il n'est pas défini, |
| 50 | - | If set to |
7970 | Si elle est définie à |
| 51 | - | If only one expression is set, then the bare bug IDs must be matched in the groups of the regex string. Example: |
8003 | Si seule une expression est définie, alors l'ID du bug seul doit correspondre aux groupes de la chaîne regex. Exemple : |
| 52 | - | If you are unfamiliar with regular expressions, take a look at the introduction at |
8008 | Si vous êtes peu familiers avec les expressions régulières, jetez un coup d'oeil à la documentation en ligne et au didactitiel à |
| 53 | - | In the approach with |
8013 | Dans l'approche avec les |
| 54 | - | Because the issue tracker integration depends upon accessing subversion properties, you will only see the results when using a checked out working copy. Fetching properties remotely is a slow operation, so you will not see this feature in action from the repo browser unless you started the repo browser from your working copy. If you started the repo browser by entering the URL of the repository you won't see this feature. | 8044 | Le formattage dépend des propriétés d'accès de subversion, vous ne verrez que le résultat lorsque vous utiliserez une copie de travail exportée. Afficher les propriétés à distance étant une opération lente, vous ne pourrez pas l'effectuer depuis l'explorateur de référentiel. |
| 55 | - | This issue tracker integration is not restricted to TortoiseSVN; it can be used with any Subversion client. For more information, read the full |
8054 | Cette intégration de tracker d'incidents n'est pas limité à TortoiseSVN ; elle peut être utilisée avec n'importe quel client Subversion. Pour plus d'informations, lisez |
| 56 | - | Because the repo viewer integration depends upon accessing subversion properties, you will only see the results when using a checked out working copy. Fetching properties remotely is a slow operation, so you will not see this feature in action from the repo browser unless you started the repo browser from your working copy. If you started the repo browser by entering the URL of the repository you won't see this feature. | 8119 | Le formattage dépend des propriétés d'accès de subversion, vous ne verrez que le résultat lorsque vous utiliserez une copie de travail exportée. Afficher les propriétés à distance étant une opération lente, vous ne pourrez pas l'effectuer depuis l'explorateur de référentiel. |
| 57 | - | Check for updates | 8160 | Vérifier les modifications |
| 58 | - | 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 |
8165 | Si elle est cochée, TortoiseSVN entrera en contact avec son site de téléchargement une fois par semaine pour voir s'il y a une version plus récente du programme disponible. Utilisez |
| 59 | - | Global ignore patterns are used to prevent unversioned files from showing up e.g. in the commit dialog. Files matching the patterns are also ignored by an import. Ignore files or directories by typing in the names or extensions. Patterns are separated by spaces e.g. |
8202 | Les modèles d'exclusion globaux sont utilisés pour empêcher des fichiers non versionnés d'apparaître dans la boîte de dialogue de livraison par exemple. Les fichiers correspondant aux modèles sont aussi ignorés lors d'un import. Ignorez des fichiers ou des répertoires en saisissant les noms ou les extensions. Les modèles sont séparés par des espaces par exemple |
| 60 | - | This option tells TortoiseSVN to set the file dates to the last commit time when doing a checkout or an update. Otherwise TortoiseSVN will use the current date. If you are developing software it is generally best to use the current date because build systems normally look at the date stamps to decide which files need compiling. If you use last commit timeand revert to an older file revision, your project may not compile as you expect it to. |
8223 | Cette option indique à TortoiseSVN de mettre la date des fichiers à la date de dernière livraison lors d'une extraction ou d'une mise à jour. Autrement TortoiseSVN utilisera la date actuelle. Si vous développez des logiciels, il est généralement mieux d'utiliser la date actuelle parce que les systèmes de compilation regardent normalement les dates pour décider quels fichiers ont besoin d'être compilés. Si vous utilisez \"la date de dernière livraison\" et revenez à une révision de fichier plus vieille, votre projet peut ne pas compiler comme vous vous y attendez. |
| 61 | - | Use |
8232 | Utilisez |
| 62 | - | Limits the number of log messages that TortoiseSVN fetches when you first select |
8289 | Limite le nombre de commentaires que TortoiseSVN va d'abord chercher quand vous choisissez |
| 63 | - | Auto-close | 8318 | auto-props |
| 64 | - | The auto-completion parser can be quite slow if there are a lot of large files to check. This timeout stops the commit dialog being held up for too long. If you are missing important auto-completion information, you can extend the timeout. | 8411 | L'analyseur syntaxique d'autocomplétion peut être assez lent s'il y a beaucoup de grands fichiers à vérifier. Ce délai empêche la boîte de dialogue de livraison de se bloquer trop longtemps. Si vous manquez d'informations d'autocomplétion importantes, vous pouvez étendre le délai. |
| 65 | - | When you type in a log message in the commit dialog, TortoiseSVN stores it for possible re-use later. By default it will keep the last 25 log messages for each repository, but you can customize that number here. If you have many different repositories, you may wish to reduce this to avoid filling your registry. | 8428 | TortoiseSVN stocke les 25 derniers commentaires que vous avez entrés pour chaque référentiel. Vous pouvez personnaliser le nombre stocké ici. Si vous avez beaucoup de référentiels différents, vous pouvez vouloir le réduire pour éviter de remplir votre registre. |
| 66 | - | If your project is using the |
8473 | Si votre projet a la propriété |
| 67 | - | Filter match | 8566 | filtrer |
| 68 | - | Caches all status information in a separate process ( |
8735 | Met en cache toute l'information de statut dans un processus séparé ( |
| 69 | - | Advantage: the overlays show the status recursively, i.e. if a file deep inside a working copy is modified, all folders up to the working copy root will also show the modified overlay. And since the process can send notifications to the shell, the overlays on the left tree view usually change too. | 8740 | Avantage : les recouvrements montrent le statut récursivement, c'est-à-dire si un fichier est modifié dans les profondeurs d'une copie de travail, tous les dossiers jusqu'à la racine de la copie de travail montreront aussi le recouvrement modifié. Et puisque le processus peut envoyer des notifications au shell, les recouvrements sur l'arborescence gauche changent d'habitude aussi. |
| 70 | - | Disadvantage: Status information of files and folders is not shown in Explorer. To see if your working copies are modified, you have to use the Check for modificationsdialog. |
8777 | Inconvénient : L'information de statut des fichiers et des dossiers n'est pas affichée dans l'Explorateur. Pour voir si vos copies de travail sont modifiées, vous devez utiliser la boîte de dialogue \"Vérifier les modifications\". |
| 71 | - | Since it takes quite a while to fetch the status of a working copy, TortoiseSVN uses a cache to store the status so the explorer doesn't get hogged too much when showing the overlays. You can choose which type of cache TortoiseSVN should use according to your system and working copy size here: |
8782 | Puisque cela prend du temps de récupérer le statut d'une copie de travail, TortoiseSVN utilise un cache pour stocker le statut pour que l'explorateur ne soit pas trop bloqué en montrant les recouvrements. Vous pouvez choisir quel type de cache TortoiseSVN devrait utiliser selon votre système et la taille de la copie de travail ici : |
| 72 | - | By default, overlay icons and context menus will appear in all open/save dialogs as well as in Windows Explorer. If you want them to appear |
8787 | Par défaut, les icônes de recouvrement apparaîtront dans toutes les boîtes de dialogue Ouvrir/Enregistrer comme dans l'explorateur Windows. Si vous voulez qu'elles n'apparaissent |
| 73 | - | You can also choose to mark folders as modified if they contain unversioned items. This could be useful for reminding you that you have created new files which are not yet versioned. This option is only available when you use the |
8792 | Si vous sélectionnez l'option par défaut, vous pouvez aussi choisir de marquer les répertoires comme modifiés s'ils contiennent des éléments non versionnés. Cela peut être utile pour vous rappeler que vous avez créé de nouveaux fichiers qui ne sont pas encore versionnés. Cette option n'est disponible que lorsque vous utilisez l'option de statut de cache |
| 74 | - | The next group allows you to select which classes of storage should show overlays. By default, only hard drives are selected. You can even disable all icon overlays, but where's the fun in that? | 8797 | Cette page vous permet de choisir les éléments pour lesquels TortoiseSVN montrera les recouvrements d'icône. Les disques réseau peuvent être très lents, donc par défaut les icônes ne s'affichent pas pour les copies de travail placées sur les partages de réseau. Vous pouvez même désactiver tous les recouvrements d'icône, mais qu'y-a-t-il d'amusant à cela ? |
| 75 | - | The |
8810 | Les |
| 76 | - | The Settings Dialog, Icon Handlers Page | 8888 | La boîte de dialogue Configuration, page Ensemble d'icônes |
| 77 | - | If you need to set up per-repository proxy settings, you will need to use the Subversion |
8913 | Si vous devez mettre en place des réglages de proxy par référentiel, vous devez utiliser le fichier |
| 78 | - | If you use the |
9021 | Si vous utilisez la propriété |
| 79 | - | If you have configured an alternate diff tool, you can access TortoiseMerge |
9030 | À partir du menu contextuel de la boîte de dialogue vous pouvez afficher une comparaison des changements. Vérifiez les changements locaux que |
| 80 | - | DiffProgram for |
9101 | comparaisonpour les fichiers .jpg :-) Vous pouvez aussi associer la propriété |
| 81 | - | If you want to clear authentication data for one particular server only, read |
9178 | Si vous voulez effacer des données d'authentification seulement pour un serveur particulier, lisez |
| 82 | - | 9411 | ||
| 83 | - | Pre-connect | 9487 | Pre-commit |
| 84 | - | 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. | 9504 | Ensuite vous devez spécifier la ligne de commande à exécuter, en commençant par le chemin du script de hook ou de l'exécutable. Ce peut être un script de batch, un exécutable ou quelqu'autre fichier que le système sache exécuter, par exemple un script perl. |
| 85 | - | Sample client hook scripts can be found in the |
9581 | Vous pouvez récupérer ces trois fichiers depuis notre référentiel : |
| 86 | - | As of Version 1.3.0 of Subversion and TortoiseSVN, you can set the environment variable |
9678 | À partir de la version 1.3.0 de Subversion et de TortoiseSVN, vous pouvez définir la variable d'environnement |
| 87 | - | For more information, and other ways to avoid this problem in the first place, check out the article about this in our |
9683 | Pour plus d'informations et d'autres façons d'éviter ce problème en premier lieu, regarder l'article à ce sujet dans notre |
| 88 | - | You can specify a different location for the Subversion configuration file here. This will affect all TortoiseSVN operations. | 9700 | Vous pouvez spécifier un emplacement différent pour le fichier de configuration Subversion en utilisant l'emplacement du registre |
| 89 | - | To add a cache tray icon for the TSVNCache program, set this value to |
9709 | Pour ajouter une icône de notification de cache pour le programme TSVNCache, créez une clé |
| 90 | - | TortoiseSVN allows you to assign an external diff viewer. Most such viewers, however, are not suited for change blaming ( |
9774 | TortoiseSVN vous permet d'utiliser un comparateur de fichier tiers. Cependantn la plupart de ces logiciels ne sont pas adaptés à la gestion d'annotation ( |
| 91 | - | While working on TortoiseSVN we love to listen to music. And since we spend many hours on the project we need a |
9803 | Pendant que nous travaillons sur TortoiseSVN, nous aimons bien écouter de la musique. Et puisque nous passons beaucoup d'heures sur le projet, nous avons besoin de |
| 92 | - | Replaced with the current system date/time. This can be used to indicate the build time. Time formatting can be used as described for |
9965 | Remplacé par la date/heure actuelle du système. Cela peut être utile pour indiquer l'heure de compilation. Le format de l'heure est comme décrit ci-dessus. |
| 93 | - | \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 |
10227 | \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.NeedsLocking + \"\\n IsLocked = \" +\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.NeedsLocking + \"\\n IsLocked = \" +\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.NeedsLocking + \"\\n IsLocked = \" +\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.NeedsLocking + \"\\n IsLocked = \" +\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 |
| 94 | - | The following listing is an example on how to use the SubWCRev COM object from C#: |
10497 | Les exemples suivants montrent comment l'interface devrait être utilisée. |
| 95 | - | TortoiseSVN 1.5 and later can use plugins which implement the IBugtraqProvider interface. The interface provides a few methods which plugins can use to interact with the issue tracker. | 10530 | TortoiseSVN 1.5 peut être agrémenté de greffons qui ajouteront une interface pour IBugtraqProvider. Cette dernière fournira quelques méthodes que les greffons pourront utiliser pour s'interfacer avec le système de suivi d'anomalies logicielles. |
| 96 | - | This method is called from the settings dialog where the user can add and configure the plugin. The |
10564 | |
| 97 | - | 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., |
10600 | |
| 98 | - | The |
10837 | |
| 99 | - | Because TortoiseSVN is being developed all the time it is sometimes hard to keep the documentation completely up to date. We maintain an |
10850 | Parce que TortoiseSVN est développé tout le temps, il est parfois difficile de garder la documentation complètement à jour. Nous maintenons une |
| 100 | - | We also maintain a project |
10855 | Nous maintenons aussi un |
| 101 | - | The recommended way is by |
10900 | La façon recommandée est de |
| 102 | - | In the repository folder on the server, there's a sub-folder |
10933 | Dans le dossier du référentiel sur le serveur, il y a un sous-dossier |
| 103 | - | Select the revision you wish to revert. If you want to undo a range of revisions, select the first one and hold the |
11002 | Sélectionnez la révision que vous voulez annuler. Si vous voulez défaire une plage de révisions, sélectionnez la première et maintenez la touche Maj en choisissant la dernière. Notez que pour des révisions multiples, la plage doit être continue sans écarts. Faites un |
| 104 | - | Or if you want to make an earlier revision the new HEAD revision, |
11007 | Ou si vous voulez faire d'une révision précédente la nouvelle révision HEAD, faites |
| 105 | - | In the |
11029 | Dans le champ |
| 106 | - | The only way to remove data from the repository is to use the Subversion command line tool |
11058 | La seule façon de supprimer des données du référentiel est d'utiliser l'outil de ligne de commande de Subversion |
| 107 | - | If you want to compare two revisions in an item's history, for example revisions 100 and 200 of the same file, just use |
11079 | Si vous voulez comparer deux révisions dans l'historique d'un fichier, par exemple les révisions 100 et 200 du même fichier, utilisez simplement |
| 108 | - | If you want to compare the same item in two different trees, for example the trunk and a branch, you can use the repository browser to open up both trees, select the file in both places, then use |
11084 | Si vous voulez comparer le même fichier dans deux arborescences différentes, par exemple dans la version trunk et une branche, vous pouvez utiliser l'explorateur de référentiel pour ouvrir les deux arborescences, sélectionnez le fichier dans les deux emplacements, puis utilisez |
| 109 | - | If you want to compare two trees to see what has changed, for example the trunk and a tagged release, you can use |
11089 | Si vous voulez comparer deux arborescences pour voir ce qui a changé, par exemple le tronc et une sortie étiquetée, vous pouvez utiliser |
| 110 | - | Set the |
11114 | Définissez la propriété |
| 111 | - | Commit the new folder. Now when you update, Subversion will pull a copy of that project from its repository into your working copy. The sub-folders will be created automatically if required. Each time you update your main working copy, you will also receive the latest version of all external projects. | 11119 | Livrez le nouveau dossier. Maintenant quand vous mettrez à jour, Subversion récupérera une copie de ce projet de son référentiel vers votre copie de travail. Les sous-dossiers seront créés automatiquement au besoin. Chaque fois que vous mettrez à jour votre copie de travail principale, vous recevrez aussi la dernière version de tous les projets externes. |
| 112 | - | If you frequently need to open the repository browser at a particular location, you can create a desktop shortcut using the automation interface to TortoiseProc. Just create a new shortcut and set the target to: TortoiseProc.exe /command:repobrowser /path:\"url/to/repository\"\n |
11190 | Si vous devez fréquemment ouvrir l'explorateur de référentiel à un emplacement particulier, vous pouvez créer un raccourci sur le bureau en utilisant l'interface d'automatisation de TortoiseProc. Créez simplement un nouveau raccourci et définissez la cible : TortoiseProc.exe /command:repobrowser /path:\"url/vers/le/référentiel\" /notempfile\n |
| 113 | - | A good walk-through on how to do that can be found in the knowledge base article 314934 from Microsoft: |
11279 | Un bon guide sur la façon de faire cela peut être trouvé dans l'article de la base de connaissance 314934 de Microsoft : |
| 114 | - | Versions 1.3.0 and later of TortoiseSVN must be installed under |
11284 | Les versions 1.3.0 et supérieures de TortoiseSVN doivent être installées dans |
| 115 | - | Versions 1.4.0 and later of TortoiseSVN allow you to redirect that upgrade check to your intranet server. You can set the registry key 1.4.1.6000\n A new version of TortoiseSVN is available for you to download!\n http://192.168.2.1/downloads/TortoiseSVN-1.4.1.6000-svn-1.4.0.msi\n |
11317 | Les versions 1.4.0 et supérieures de TortoiseSVN vous permettent de rediriger cette vérification de mise à niveau vers votre serveur intranet. Vous pouvez définir la clé de base de registre 1.4.1.6000\n Un nouvelle version de TortoiseSVN est disponible au téléchargement !\n http://192.168.2.1/downloads/TortoiseSVN-1.4.1.6000-svn-1.4.0.msi\n |
| 116 | - | As of version 1.4.0 and later, the TortoiseSVN installer doesn't provide the user with the option to set the |
11348 | À partir des versions 1.4.0 et supérieures, l'installeur de TortoiseSVN ne fournit plus à l'utilisateur l'option pour mettre la variable d'environnement |
| 117 | - | To close the progress dialog at the end of a command automatically without using the permanent setting you can pass the parameter. |
11639 | Pour fermer la boîte de dialogue de progression automatiquement à la fin d'une commande sans utiliser le réglage permanent, vous pouvez lui passer le paramètre . |
| 118 | - | Opens the log dialog. The |
11751 | Ouvre la boîte de dialogue des commentaires. Le |
| 119 | - | Updates the working copy in |
11789 | Met à jour la copie de travail dans |
| 120 | - | Starts the external diff program specified in the TortoiseSVN settings. The |
11914 | Démarre le programme externe de comparaison indiqué dans la configuration de TortoiseSVN. Le |
| 121 | - | In the descriptions which follow, the URL for a repository location is shown simply as |
12185 | Dans les descriptions qui suivent, l'URL d'un référentiel est simplement affichée |
| 122 | - | Much of the information here comes from a tutorial provided by Marc Logemann, which has been archived at |
12792 | La plupart de ces informations est associé à un tutoriel fourni par Marc Logemann et qui peut être trouvé sur |
| 123 | - | 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 |
13065 | L'interface utilisateur de TortoiseSVN a été traduite dans beaucoup de langues différentes, donc vous devez être capables de télécharger un pack de langue qui réponde à vos besoins. Vous pouvez trouver les packs de langue sur notre |
| 124 | - | Each language pack is packaged as a |
13070 | Chaque pack de langue est empaqueté comme un installeur |
| 125 | - | 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. | 13095 | L'installeur ajoute automatiquement les dictionnaires d'anglais américains et britanniques. Si vous voulez d'autres langues, l'option la plus facile est d'installer simplement un des packs de langue de TortoiseSVN. Cela installera les fichiers de dictionnaire appropriés en même temps que l'interface utilisateur TortoiseSVN locale. La prochaine fois que vous redémarrez, le dictionnaire sera disponible aussi. |
Total:125
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><<<<<<<</literal>. The conflicting area is marked like this: <screen>\n <<<<<<< filename\n your changes\n =======\n code merged from repository\n >>>>>>> revision\n </screen> Also, for every conflicted file Subversion places three additional files in your directory: <placeholder-1/> |
3008 | Un conflit de fichier arrive quand 2 développeurs our plus modifient un même fichier. Dans la mesure où Subversion ne sait rien de votre projet, il laisse la résolution des conflits à la charge des développeurs. Dès qu'un conflit est détecté, vous devriez ouvrir le fichier en question, et chercher les lignes commençant par <literal><<<<<<<</literal>. La zone en conflit est marquée de cette manière: <screen>\n \t<<<<<<< nom_de_fichier\n \t\tvos modifications\n \t=======\n \t\tcode fusionné depuis le référentiel\n \t>>>>>>> révision\n \t</screen> De plus, pour chaque conflit Subversion place trois fichiers dans votre répertoire: <placeholder-1/> |
|
| 2 | 8784 | You can specify a different location for the Subversion configuration file here. This will affect all TortoiseSVN operations. | 8784 | Vous pouvez spécifier un emplacement différent pour le fichier de configuration Subversion en utilisant l'emplacement du registre <literal>HKCU\\Software\\TortoiseSVN\\ConfigDir</literal>. Ceci affectera toutes les opérations de TortoiseSVN. |
| 3 | To add a cache tray icon for the TSVNCache program, set this value to <literal>true</literal>. This is really only useful for developers as it allows you to terminate the program gracefully. | 8792 | Pour ajouter une icône de notification de cache pour le programme TSVNCache, créez une clé <literal>DWORD</literal> avec une valeur de 1 à <literal>HKCU\\Software\\TortoiseSVN\\CacheTrayIcon</literal>. C'est vraiment seulement utile pour les développeurs puisqu'il vous permet de fermer le programme proprement. | |
| 4 | TortoiseSVN allows you to assign an external diff viewer. Most such viewers, however, are not suited for change blaming (<xref linkend=\"tsvn-dug-blame-diffs\"/>), so you might wish to fall back to TortoiseMerge in this case. To do so, set this value to <literal>true</literal>. | 8856 | TortoiseSVN vous permet d'utiliser un comparateur de fichier tiers. Cependantn la plupart de ces logiciels ne sont pas adaptés à la gestion d'annotation (<xref linkend=\"tsvn-dug-blame-diffs\"/>), auquel cas, vous pourriez vouloir utiliser TortoiseMerge pour cela. Pour ce faire, créer une clé de type <literal>DWORD</literal> avec la valeur 1 dans la base de registre sous <literal>HKCU\\Software\\TortoiseSVN\\DiffBlamesWithTortoiseMerge</literal>. |
Total:4
PASS
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.
RC checking is currently off for this language. If you like enable it for your translation drop me an email.
