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 |
 |
 |
||
| Japanese |  |
 3 |
11 |
3 |
91 |
72 |
10 |
91/72 | 9 | Daisuke Deguchi (GUI), Kurasawa Nozomu (docs) | |
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.
| Index | Line | English | Line | Native |
| 1 | 2744 | The log message window also includes a filename and function auto-completion facility. This uses regular expressions to extract class and function names from the (text) files you are committing, as well as the filenames themselves. If a word you are typing matches anything in the list (after you have typed at least 3 characters, or pressed |
3414 | ログメッセージウィンドウは、ファイル名・関数の自動補完機構も持っています。コミットしようとしている (テキスト) ファイルから、クラス名や関数名を (ファイル名と同様に) 抽出するのに正規表現を使用します。入力している単語が (3 文字入力したり、 |
| 2 | 4127 | Describing the use of regular expression searches is beyond the scope of this manual, but you can find online documentation and a tutorial at |
4828(Fuzzy) | 正規表現になじみがなければ、 |
| 3 | 7192 | If you are unfamiliar with regular expressions, take a look at the introduction at |
7949 | 正規表現になじみがなければ、 |
Total:3
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.
| Index | Line | English | Line | Native |
| 1 | 2188 | Drag and Drop | 2837 | ドラッグ & ドロップ |
| 2 | 2196 | drag-n-drop | 2845 | ドラッグ&ドロップ |
| 3 | 2237 | Select all. This can be used if you get an error message and want to copy and paste into an email. Use Ctrl-A to select the error message and then ... | 2886 | すべて選択します。エラーメッセージが出て email にコピー & ペーストしたいときに使用できます。Ctrl-A でエラーメッセージを選択し…… |
| 4 | Simply right click on one of the headings of a column, choose <guimenuitem>More...</guimenuitem> from the context menu displayed. A dialog will appear where you can specify the columns and their order, which is displayed in the <quote>Detailed View</quote>. Scroll down until the entries starting with SVN come into view. Check the ones you would like to have displayed and close the dialog by pressing <guibutton>OK</guibutton>. The columns will be appended to the right of those currently displayed. You can reorder them by drag and drop, or resize them, so that they fit your needs. | 4064 | 単に列の見出しを右クリックして出てくるコンテキストメニューの、<guimenuitem>その他...</guimenuitem> を選んでください。<quote>詳細ビュー</quote> の列とその順番を設定するダイアログが表示されます。SVN で始まる項目が出てくるまでスクロールしてください。表示したい項目にチェックをつけ、<guibutton>OK</guibutton> を押してダイアログを閉じてください。元々表示していた項目の右に列が追加されているはずです。お好みに応じて、ドラッグ&ドロップで順番を変えたり大きさを変更してください。 | |
| 5 | 3511 | Once you have created a changelist you can drag and drop items into it, either from another changelist, or from Windows Explorer. Dragging from Explorer can be useful as it allows you to add items to a changelist before the file is modified. You could do that from the check-for-modifications dialog, but only by displaying all unmodified files. | 4197 | 一度更新リストを作成すると、別の更新リストや Windows エクスプローラから、項目をドラッグ & ドロップできます。エクスプローラからドラッグするのは、ファイルを変更する前に更新リストに追加できるので、便利です。更新チェックダイアログからも同じことができますが、未更新ファイルすべてを表示しなければなりません。 |
| 6 | To add files from outside your working copy you can use the drag-and-drop handler: <placeholder-1/> | 5339 | 作業コピーの外部にあるファイルを追加するには、以下のようにドラッグ&ドロップで操作できます。<placeholder-1/> | |
| 7 | 4640 | You can also add files within a working copy simply by left-dragging and dropping them onto the commit dialog. | 5343 | 作業コピーにあるファイルを、コミットダイアログへ単に左ドラッグ&ドロップしても追加できます。 |
| 8 | You can also copy or move versioned files within a working copy, or between two working copies, using the familiar cut-and-paste method. Use the standard Windows <action>Copy</action> or <action>Cut</action> to copy one or more versioned items to the clipboard. If the clipboard contains such versioned items, you can then use <menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>Paste</guimenuitem></menuchoice> (note: not the standard Windows <action>Paste</action>) to copy or move those items to the new working copy location. | 5385 | 作業コピーにあるバージョン管理下のファイルや、ふたつの作業コピーの間で、慣れたカット & ペーストでもコピーや移動を行えます。バージョン管理下のファイルをクリップボードにコピーするには、Windows 標準の <action>コピー</action> や <action>切り取り</action> を行ってください。クリップボードにバージョン管理下のファイルがある状態では、<menuchoice><guimenu>TortoiseSVN</guimenu><guimenuitem>貼り付け</guimenuitem></menuchoice> を利用し (注意: Windows 標準の <action>貼り付け</action> ではありません)、新しい作業コピーの場所にコピーや移動できます。 | |
| 9 | If you want to move files around inside your working copy, perhaps to a different sub-folder, use the right-mouse drag-and-drop handler: <placeholder-1/> | 5596 | 別のサブフォルダへなど、作業コピー内に移動する場合、右ドラッグ & ドロップハンドラを以下のように使用してください。<placeholder-1/> | |
| 10 | 6582 | 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. | 7339 | リポジトリブラウザをドラッグ & ドロップでも操作できます。エクスプローラからリポジトリブラウザへフォルダをドラッグすると、リポジトリにインポートを行います。複数の項目をドラッグすると、それぞれコミットを行うことに注意してください。 |
| 11 | Use PuTTYgen to generate a public-key/private-key pair and save it. Copy the public key to the server and append it to those in the <filename>.ssh</filename> folder within the <literal>svnuser</literal> home directory: <screen>\n cat keyfile.pub >> /home/svnuser/.ssh/authorized_keys\n </screen> |
12917 | 公開鍵・秘密鍵のペアを作成するのに PuTTYgen を使用して、保存してください。公開鍵をサーバにコピーし、<literal>svnuser</literal> のホームディレクトリにある <filename>.ssh</filename> フォルダに追加してください。 |
Total:11
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 | リポジトリが <filename>c:\\repos\\TestRepo</filename> にあり、サーバ名が <filename>localhost</filename> とすると、リポジトリブラウザに以下のように入力します。<screen>\n svn://localhost/repos/TestRepo\n </screen> |
|
| 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 | セキュリティを高め、URL を入力する時間を節約するために、--root スイッチを用いてサーバ上の指定したディレクトリにルートを設定し、そこだけアクセスするようにできます。<screen>\n svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n </screen> ガイドのように以前行ったテストの物を使用して、svnserve を以下のように実行します。<screen>\n svnserve.exe --daemon --root c:\\repos\n </screen> すると TortoiseSVN のリポジトリブラウザでは、次のように省略できるようになります。<screen>\n svn://localhost/TestRepo\n </screen> --root スイッチは、あなたのサーバの svnserve の場所と違うパーティションやドライブにリポジトリがある場合にも、指定する必要があることに注意してください。 |
|
| 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 | svnserve をネイティブ Windows サービスとしてインストールするには、以下のコマンドを 1 行で記述し、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> パスにスペースを含んでいる場合は、以下のように、(エスケープした) クォートでパスを囲んでください。<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> サービス作成後に、説明の追加もできます。これは Windows のサービスマネージャに表示されます。<screen>\n sc description svnserve \"Subversion server (svnserve)\"\n </screen> |
Total:3
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 | 1115 | You will also be asked whether you want to create a directory structure within the repository. Find out about layout options in |
|
| 2 | 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. | |
| 3 | 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. | |
| 4 | 1323 | Overriding Hooks | 1446 |
| 5 | 1327 | If a hook script rejects your commit then its decision is final. But you can build an override mechanism into the script itself using the You didn't say the magic word:-) |
1450 |
| 6 | 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. | 2936 |
| 7 | 2522 | In windows explorer, |
|
| 8 | 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 |
3418 |
| 9 | 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. | 3966 |
| 10 | 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 |
4811 |
| 11 | 4908 | Another way of moving or copying files is to use the Windows copy/cut commands. Select the files you want to copy, right-click and choose |
5612 |
| 12 | 5063 | Since revert is sometimes used to clean up a working copy, there is an extra button which allows you to delete unversioned items as well. When you click this button another dialog comes up listing all the unversioned items, which you can then select for deletion. | 5768 |
| 13 | 5226 | Edit properties at HEAD revision | |
| 14 | 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. | |
| 15 | 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. | 6132 |
| 16 | 5436 | When you add a property using the repo browser, only the standard |
6136 |
| 17 | 5440 | Properties cannot be set or deleted recursively using the repo browser. | 6140 |
| 18 | 5444 | Project properties will |
6144 |
| 19 | 5448 | 6148 | |
| 20 | 5685 | You can also create a branch or tag without having a working copy. To do that, open the repository browser. You can there drag folders to a new location. You have to hold down the |
6437 |
| 21 | 5689 | You can also drag a folder with the right mouse button. Once you release the mouse button you can choose from the context menu whether you want the folder to be moved or copied. Of course to create a branch or tag you must copy the folder, not move it. | 6441 |
| 22 | 5693 | Yet another way is from the log dialog. You can show the log dialog for e.g. trunk, select a revision (either the HEAD revision at the very top or an earlier revision), right-click and choose |
6445 |
| 23 | 5965 | The checkbox marked |
6718 |
| 24 | 6065 | Choosing |
|
| 25 | 6069 | Normally you will want to look at the conflicts and resolve them yourself. In that case, choose the |
|
| 26 | 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. |
|
| 27 | 7231 | For the same reason, project properties will not be propagated automatically when a child folder is added using the repo browser. | 7989 |
| 28 | 7339 | Check for updates | |
| 29 | 7343 | 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 |
|
| 30 | 7491 | Auto-close | |
| 31 | 7511 | Always close dialogs for local operations | |
| 32 | 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. | |
| 33 | 7735 | Filter match | |
| 34 | 7739 | When using filtering in the log dialog, search terms are highlighted in the results using this colour. | |
| 35 | 7971 | The |
|
| 36 | 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 |
|
| 37 | 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. | |
| 38 | 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 |
|
| 39 | 8031 | Enabled Overlay Handlers | |
| 40 | 8035 | The Settings Dialog, Icon Handlers Page | |
| 41 | 8039 | ||
| 42 | 8576 | Pre-connect | |
| 43 | 8580 | Called before an attempt to contact the repository. Called at most once in five minutes. | |
| 44 | 8592 | 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. | |
| 45 | 8672 | A small tool is included in the TortoiseSVN installation folder named |
|
| 46 | 8696 | This is the same as |
9499 |
| 47 | 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. | 9585 |
| 48 | 8788 | Set this to |
9594 |
| 49 | 8800 | If you don't want TortoiseSVN to show icons for the context menus in its own dialogs, set this value to |
9608 |
| 50 | 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 |
9612 |
| 51 | 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 |
9616 |
| 52 | 8812 | The commit and log dialog use styling (e.g. bold, italic) in commit messages (see |
9620 |
| 53 | 8816 | TortoiseSVN uses accelerators for its explorer context menu entries. Since this can lead to doubled accelerators (e.g. the |
9624 |
| 54 | 8820 | As with the explorer, TortoiseSVN shows additional commands if the |
9628 |
| 55 | 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 |
9647 |
| 56 | 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 |
9651 |
| 57 | 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 |
9655 |
| 58 | 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 |
9674 |
| 59 | 8864 | In most dialogs in TortoiseSVN, you can use |
9678 |
| 60 | 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 |
|
| 61 | 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 |
|
| 62 | 9240 | \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 |
|
| 63 | 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 |
10396 |
| 64 | 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. | 10438 |
| 65 | 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. | 10564 |
| 66 | 9317 | The |
10568 |
| 67 | 9321 | The |
10572 |
| 68 | 9325 | The |
10576 |
| 69 | 9329 | The |
10580 |
| 70 | 9333 | The |
10584 |
| 71 | 9350 | This method is called from the TortoiseSVN commit dialog when the user clicks on the plugin button. This method is called instead of |
10677 |
| 72 | 9354 | The parameter |
10681 |
| 73 | 9358 | The parameter |
10685 |
| 74 | 9362 | The return parameter |
10689 |
| 75 | 9366 | The |
10693 |
| 76 | 9379 | For the branch/tag dialog, the |
10727 |
| 77 | 9410 | This method is called from the settings dialog when the user clicks on the \"Options\" button that is shown if |
10839 |
| 78 | 9414 | The |
10843 |
| 79 | 9438 | 10868 | |
| 80 | 9442 | If you want to help out with the development of TortoiseSVN, then you should take part in discussions on |
10872 |
| 81 | 9446 | If you want to help with the translation of the TortoiseSVN user interface or the documentation, send an e-mail to |
10876 |
| 82 | 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. |
11218 |
| 83 | 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 |
| 84 | 10338 | Cleans up interrupted or aborted operations and unlocks the working copy in |
11831 |
| 85 | 10672 | The depth combo box items relate to the |
12212 |
| 86 | 11282 | Language Packs and Spell Checkers | 13054 |
| 87 | 11286 | The standard installer has support only for English, but you can download separate language packs and spell check dictionaries separately after installation. | 13058 |
| 88 | 11302 | The TortoiseSVN user interface has been translated into many different languages, so you may be able to download a language pack to suit your needs. You can find the language packs on our |
|
| 89 | 11306 | Each language pack is packaged as a |
|
| 90 | 11310 | The documentation has also been translated into several different languages. You can download translated manuals from the |
13082 |
| 91 | 11330 | The installer automatically adds the US and UK English dictionaries. If you want other languages, the easiest option is simply to install one of TortoiseSVN's language packs. This will install the appropriate dictionary files as well as the TortoiseSVN local user interface. After the installation finishes, the dictionary will be available too. |
Total:91
String marked as fuzzy is not in final shape.
| Index | Line | English | Line | Native |
| 1 | - | TortoiseSVN does not support |
1179 | TortoiseSVN の将来のバージョンでは、BDB リポジトリに対する |
| 2 | - | import this structure into the repository via a |
1343 | このフォルダの上で |
| 3 | - | The |
1400 | Subversion コマンドラインクライアントをインストールすると、 |
| 4 | - | 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. sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service\n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip\n start= auto\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 sc description svnserve \"Subversion server (svnserve)\"\n |
1650 | svnserve をネイティブ Windows サービスとしてインストールするには、以下のコマンドを 1 行で記述し、Windows の起動時に自動起動するサービスを作成してください。 sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service \n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip \n start= auto\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 sc description svnserve \"Subversion server (svnserve)\"\n |
| 5 | - | You can get those three files directly from our source repository at |
2204 | その 3 ファイルは |
| 6 | - | Next type the commands bin\\openssl rsa -in conf\\privkey.pem -out conf\\server.key\n bin\\openssl req -new -key conf\\server.key -out conf\\server.csr \\\n -config conf\\openssl.cnf\n bin\\openssl x509 -in conf\\server.csr -out conf\\server.cert\n -req -signkey conf\\server.key -days 4000\n bin\\openssl x509 -in conf\\server.cert -out conf\\server.der.crt\n -outform DER\n |
2563 | 次に以下のコマンドを入力してください。 bin\\openssl rsa -in conf\\privkey.pem -out conf\\server.key\n bin\\openssl req -new -key conf\\server.key -out conf\\server.csr \\\n -config conf\\openssl.cnf\n bin\\openssl x509 -in conf\\server.csr -out conf\\server.crt\n -req -signkey conf\\server.key -days 4000\n bin\\openssl x509 -in conf\\server.cert -out conf\\server.der.crt\n -outform DER\n |
| 7 | - | To summarise, the relevant lines of the Apache configuration are: SSLVerifyClient Optional\n \n ### Virtual host configuration for the PUBLIC host\n ### (not requiring a certificate)\n \n <VirtualHost 127.0.0.1:443>\n <Directory \"pathtopublicfileroot\">\n </Directory>\n </VirtualHost>\n \n ### Virtual host configuration for SUBVERSION\n ### (requiring a client certificate)\n <VirtualHost 127.0.0.1:443>\n <Directory \"subversion host root path\">\n SSLRequire %{SSL_CLIENT_VERIFY} eq \"SUCCESS\"\n </Directory>\n \n <Location /svn>\n DAV svn\n SVNParentPath /pathtorepository\n </Location>\n </VirtualHost>\n |
2696 | まとめると、Apache 設定ファイルの関係する行は、以下のようになります。 SSLVerifyClient Optional\n \n ### Virtual host configuration for the PUBLIC host \n ### (not requiring a certificate)\n \n <VirtualHost 127.0.0.1:443>\n <Directory \"pathtopublicfileroot\">\n </Directory>\n </VirtualHost>\n \n ### Virtual host configuration for SUBVERSION \n ### (requiring a client certificate)\n <VirtualHost 127.0.0.1:443>\n <Directory \"subversion host root path\">\n SSLRequire %{SSL_CLIENT_VERIFY} eq \"SUCCESS\"\n </Directory>\n \n <Location /svn>\n DAV svn\n SVNParentPath /pathtorepository\n </Location>\n </VirtualHost>\n |
| 8 | - | authentication cache | 2906 | 認証 |
| 9 | - | 2915 | ||
| 10 | - | If you are importing into an existing repository which already contains some projects, then the repository structure will already have been decided. If you are importing data into a new repository, then it is worth taking the time to think about how it will be organised. Read |
2991 | すでにいくつかのプロジェクトが登録されている、既存リポジトリにインポートする場合、リポジトリ構造はすでに決まっていることでしょう。新しいリポジトリにデータをインポートする場合には、どのようにリポジトリを構成するかを考えるのに、時間を費やす価値はあります。もっと深いアドバイスが必要であれば、 |
| 11 | - | 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 |
3678 | 競合は複数の開発者が、あるファイルの同じ行を変更した際に発生します。Subversion はプロジェクトについては何も知りませんから、開発者間の競合については解決できません。競合が報告されたら、問題のファイルを開き、 \t<<<<<<< filename\n \t\tあなたの変更\n \t=======\n \t\tリポジトリからマージされたコード\n \t>>>>>>> revision\n \t |
| 12 | - | Other tree conflicts | 3961 | ツリー競合 |
| 13 | - | Show changes made in the selected revision for the selected file. | 4592 | 選択した 1 ファイルのリビジョンログを表示します。 |
| 14 | - | Click on the search icon to select which information you want to search in, and to choose |
4806 | 検索アイコンをクリックして、検索したい情報を選択してください。また |
| 15 | - | Describing the use of regular expression searches is beyond the scope of this manual, but you can find online documentation and a tutorial at |
4828 | 正規表現になじみがなければ、 |
| 16 | - | You can also filter the path names in the bottom pane using the |
4837 | また、下部ペインのパス名を、 |
| 17 | - | Whilst you can copy or move files and folders |
5405 | |
| 18 | - | clean | 5742 | クリーンアップ |
| 19 | - | For project properties |
6114 | プロジェクト属性 |
| 20 | - | When you add new sub-folders to a working copy using TortoiseSVN, any project properties present in the parent folder will automatically be added to the new child folder too. | 6121 | TortoiseSVN で新しいサブフォルダを作成する際、親フォルダに設定されているプロジェクト属性は、新しいサブフォルダに自動的に追加されます。 |
| 21 | - | Limitations Using the Repository Browser | 6127 | リポジトリブラウザ |
| 22 | - | 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. | 6216 | 外部プロジェクトが同じリポジトリにある場合、メインプロジェクトをコミットしたときに、外部プロジェクトに行った変更もコミットされてしまいます。 |
| 23 | - | Other ways to create a branch or tag | 6432 | ブランチ・タグの作成 |
| 24 | - | Tags are typically used to create a static snapshot of the project at a particular stage. As such they are not normally used for development - that's what branches are for, which is the reason we recommended the |
6489 | タグは、典型的には、プロジェクトの特定の段階で静的スナップショットを作成するのに使います。通常は開発には使用しません。開発にはブランチを使用します。これが最初に |
| 25 | - | Now everything is set up, all you have to do is click on the |
6726 | すべての設定が終わって、 |
| 26 | - | You may decide that your local changes are much more important, so you want to discard the version from the repository and keep your local version. Or you might discard your local changes in favour of the repository version. This only relates to conflicting changes. Changes that can be merged are still merged. Only for the conflicting part your choice is used. | 6819 | あなたの行った変更のほうが重要で、リポジトリのものを破棄して手元のバージョンを保持するという判断もあり得ます。もしくはリポジトリのものを支持し、自分のした変更を破棄することもできます。どちらにしろ、マージは一切行いません。どちらかを選ぶことになります。 |
| 27 | - | From the context menu for that folder, click on All files. If you previously saved a patch to the clipboard, you can use |
7072 | フォルダのコンテキストメニューから、ファイルを開くダイアログボックスが現れ、適用するパッチファイルを選択できます。デフォルトでは すべてのファイルを選択できます。あらかじめパッチをクリップボードに保存していれば、 ファイルを開くダイアログの |
| 28 | - | Make a copy of the folder, either to a different part of the repository, or to a working copy rooted in the same repository. This can also be used to create a branch/tag without the need to have a working copy checked out. | 7302 | リポジトリの別の場所や、同じリポジトリに属する作業コピーにフォルダをコピーします。 |
| 29 | - | 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. | 7983 | リポジトリビューアとの統合は、subversion の属性にアクセスできることに依存しているため、チェックアウトした作業コピーを使用するときにだけ、結果を目にすることになります。リモートから属性を取得するのは遅い操作ですので、作業コピーからリポジトリブラウザを起動しない限り、作動中のこの機能をリポジトリブラウザから目にすることはないでしょう。リポジトリの URL を入力してリポジトリブラウザを起動した場合、この機能を目にすることになります。 |
| 30 | - | This issue tracker integration is not restricted to TortoiseSVN; it can be used with any Subversion client. For more information, read the full |
7993 | この課題追跡システムとの統合は、TortoiseSVN に限定されていません。ですから、いずれの Subversion クライアントでも使用できます。詳細は、TortoiseSVN のソースリポジトリにある、 |
| 31 | - | 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 |
8006 | そのようなインターフェースは、もちろん強くあなたの課題管理システムに特化しており、この部分を私たちは提供できません。また、そのようなプログラムの作成について説明するのは、このマニュアルの範疇を超えてしまいます。インターフェースの定義や、C#・C++/ATLで書かれたサンプルプラグインは、 |
| 32 | - | Set this property to the URL of your repo viewer to view changes to a specific file in a specific revision. It must be properly URI encoded and it has to contain |
8051 | 指定したリビジョン、指定したファイルの変更点を表示するリポジトリビューアの URL を、この属性にセットしてください。適切に URI エンコードされていなければならず、 |
| 33 | - | 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. | 8060 | リポジトリビューアとの統合は、subversion の属性にアクセスできることに依存しているため、チェックアウトした作業コピーを使用するときにだけ、結果を目にすることになります。リモートから属性を取得するのは遅い操作ですので、作業コピーからリポジトリブラウザを起動しない限り、作動中のこの機能をリポジトリブラウザから目にすることはないでしょう。リポジトリの URL を入力してリポジトリブラウザを起動した場合、この機能を目にすることになります。 |
| 34 | - | For example, with ExamDiff Pro: C:\\Path-To\\ExamDiff.exe %base %mine --left_display_name:%bname\n --right_display_name:%yname\n C:\\Path-To\\kdiff3.exe %base %mine --L1 %bname --L2 %yname\n C:\\Path-To\\WinMerge.exe -e -ub -dl %bname -dr %yname %base %mine\n C:\\Path-To\\compare.exe /max /wait /title1:%bname /title2:%yname\n %base %mine\n C:\\Path-To\\uc.exe %base %mine -title1 %bname -title2 %yname\n |
8899 | 以下に例を示します。ExamDiff Pro の場合: C:\\Path-To\\ExamDiff.exe %base %mine --left_display_name:%bname\n --right_display_name:%yname\n C:\\Path-To\\kdiff3.exe %base %mine --L1 %bname --L2 %yname\n C:\\Path-To\\WinMerge.exe -e -ub -dl %bname -dr %yname %base %mine\n C:\\Path-To\\compare.exe /max /wait /title1:%bname /title2:%yname\n %base %mine\n |
| 35 | - | Called before the actual Subversion update or switch begins. | 9375 | Subversion の更新を実際に始める前に呼ばれます。 |
| 36 | - | Called after the update, switch or checkout finishes (whether successful or not). | 9385 | 更新が完了した後で (成功・失敗に関わらず) 呼ばれます。 |
| 37 | - | Sample client hook scripts can be found in the |
9474 | クライアントフックスクリプトのサンプルは、 |
| 38 | - | If you want all users to use the same COM plugin for your project, you can specify the plugin also with the properties |
9507 | すべてのユーザが、あなたのプロジェクトで同じ COM プラグインを使用するようにしたいのであれば、プラグインを |
| 39 | - | Advanced Settings | 9576 | 差分 / マージの高度な設定 |
| 40 | - | You can specify a different location for the Subversion configuration file here. This will affect all TortoiseSVN operations. | 9589 | レジストリの |
| 41 | - | To add a cache tray icon for the TSVNCache program, set this value to |
9598 | TSVNCache プログラムのキャッシュトレイアイコンを追加するため、 |
| 42 | - | 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 |
9603 | これは Windows エクスプローラ以外のものを使用したり、コンテキストメニューが正しく表示できないといった問題が発生したりしたときに便利です。TortoiseSVN にシェルのコンテキストメニューのアイコンを表示させたくない場合、 |
| 43 | - | 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 |
9632 | 他の TortoiseSVN コマンド (更新、コミットなど) を実行している間、エクスプローラの状態オーバーレイアイコンを更新したくない場合、 |
| 44 | - | 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. | 9637 | |
| 45 | - | 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 |
9642 | Windows エクスプローラの詳細ビューに表示する、TortoiseSVN が追加する列は、通常、作業コピーのみに有効です。作業コピーのみではなく、どこでもこの列を表示するには、 |
| 46 | - | 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 |
9659 | コミットメッセージエディタの自動補完リストには、コミットするファイル名が表示されます。この名前から拡張子を除くには、 |
| 47 | - | 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. | 9664 | 別のブランチから、あるリビジョンをマージした際、マージ追跡情報が有効だと、そのリビジョン由来のログメッセージをまとめて、コミットログメッセージにします。変更するには、 |
| 48 | - | TortoiseSVN allows you to assign an external diff viewer. Most such viewers, however, are not suited for change blaming ( |
9669 | TortoiseSVN は外部 diff ビューアを使用できます。しかし、ほとんどのそのようなビューアは注釈履歴 ( |
| 49 | - | \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 |
10135 | \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 \t\t\t\t\"\\n Min Revision = \" + revObject1.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject1.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject1.Date + \n \t\t\t\t\"\\n URL = \" + revObject1.Url + \"\\n Author = \" + \n \t\t\t\trevObject1.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject1.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject1.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject1.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject1.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject1.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject1.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject1.LockComment;\n wcInfoString2 = \"Revision = \" + revObject2.Revision + \n \t\t\t\t\"\\n Min Revision = \" + revObject2.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject2.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject2.Date + \n \t\t\t\t\"\\n URL = \" + revObject2.Url + \"\\n Author = \" + \n \t\t\t\trevObject2.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject2.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject2.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject2.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject2.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject2.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject2.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject2.LockComment;\n wcInfoString3 = \"Revision = \" + revObject3.Revision + \n \t\t\t\t\"\\n Min Revision = \" + revObject3.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject3.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject3.Date + \n \t\t\t\t\"\\n URL = \" + revObject3.Url + \"\\n Author = \" + \n \t\t\t\trevObject3.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject3.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject3.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject3.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject3.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject3.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject3.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject3.LockComment;\n wcInfoString4 = \"Revision = \" + revObject4.Revision + \n \t\t\t\t\"\\n Min Revision = \" + revObject4.MinRev + \n \t\t\t\t\"\\n Max Revision = \" + revObject4.MaxRev + \n \t\t\t\t\"\\n Date = \" + revObject4.Date + \n \t\t\t\t\"\\n URL = \" + revObject4.Url + \"\\n Author = \" + \n \t\t\t\trevObject4.Author + \"\\n HasMods = \" + \n \t\t\t\trevObject4.HasModifications + \"\\n IsSvnItem = \" + \n \t\t\t\trevObject4.IsSvnItem + \"\\n NeedsLocking = \" + \n \t\t\t\trevObject4.NeedsLocking + \"\\n IsLocked = \" + \n \t\t\t\trevObject4.IsLocked + \"\\n LockCreationDate = \" + \n \t\t\t\trevObject4.LockCreationDate + \"\\n LockOwner = \" + \n \t\t\t\trevObject4.LockOwner + \"\\n LockComment = \" + \n \t\t\t\trevObject4.LockComment;\n \n WScript.Echo(wcInfoString1);\n WScript.Echo(wcInfoString2);\n WScript.Echo(wcInfoString3);\n WScript.Echo(wcInfoString4);\n \n |
| 50 | - | The following listing is an example on how to use the SubWCRev COM object from C#: |
10413 | 以下のサンプルでは、どのようにインターフェースを使用するべきかを示しています。 |
| 51 | - | 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. | 10446 | TortoiseSVN 1.5 では、IBugtraqProvider インターフェースを実装したプラグインを利用できます。このインターフェースは、プラグインが課題管理システムとやりとりするのに使用する、いくつかのメソッドを提供しています。 |
| 52 | - | This method is called from the settings dialog where the user can add and configure the plugin. The |
10480 | |
| 53 | - | 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., |
10516 | |
| 54 | - | 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 |
10722 | |
| 55 | - | The return parameter |
10731 | |
| 56 | - | 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 |
10787 | |
| 57 | - | This method is called from the settings dialog where the user can configure the plugins. If a plugin provides its own configuration dialog with |
10807 | |
| 58 | - | The |
10847 | |
| 59 | - | If you have a question which is not answered anywhere else, the best place to ask it is on one of the mailing lists: |
10880 | まだ誰も答えていないような質問があったら、メーリングリストで訊くのが一番です。 |
| 60 | - | As of version 1.4.0 and later, the TortoiseSVN installer doesn't provide the user with the option to set the |
11342 | バージョン 1.4.0 以降では、TortoiseSVN のインストーラは |
| 61 | - | /findregex | 11718 | /findtext |
| 62 | - | Opens the log dialog. The |
11751 | ログダイアログを開きます。 |
| 63 | - | /includeexternals | 11785 | /ignoreexternals |
| 64 | - | Updates the working copy in |
11790 | |
| 65 | - | /noui | 11826 | /noquestion |
| 66 | - | /line:xxx | 11912 | /rev:xxx |
| 67 | - | Starts the external diff program specified in the TortoiseSVN settings. The |
11917 | TortoiseSVN の設定で指定した外部 diff プログラムを起動します。 |
| 68 | - | In the descriptions which follow, the URL for a repository location is shown simply as |
12189 | 以下の説明では、リポジトリの位置を表す URL (例: |
| 69 | - | \n svn checkout [-depth ARG] [--ignore-externals] [-r rev] URL PATH\n |
12202 | \n svn checkout [-N] [--ignore-externals] [-r rev] URL PATH\n |
| 70 | - | \n svn info URL_of_WC\n svn update [-r rev] [-depth ARG] [--ignore-externals] PATH\n |
12252 | \n svn info URL_of_WC\n svn update [-r rev] [-N] [--ignore-externals] PATH\n |
| 71 | - | \n svn commit -m \"LogMessage\" [-depth ARG] [--no-unlock] PATH...\n |
12301 | \n svn commit -m \"LogMessage\" [-N] [--no-unlock] PATH...\n |
| 72 | - | Much of the information here comes from a tutorial provided by Marc Logemann, which has been archived at |
12796 | ここの情報の多くは、Marc Logemann が提供しているチュートリアル ( |
Total:72
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 | 競合は複数の開発者が、あるファイルの同じ行を変更した際に発生します。Subversion はプロジェクトについては何も知りませんから、開発者間の競合については解決できません。競合が報告されたら、問題のファイルを開き、<literal><<<<<<<</literal> で始まる行を探してください。競合のある箇所は以下のようにマークがつけられています。<screen>\n \t<<<<<<< filename\n \t\tあなたの変更\n \t=======\n \t\tリポジトリからマージされたコード\n \t>>>>>>> revision\n \t</screen> また、競合のあるファイルごとに Subversion は手元のディレクトリにファイルを 3 つ追加します。<placeholder-1/> |
|
| 2 | 8784 | You can specify a different location for the Subversion configuration file here. This will affect all TortoiseSVN operations. | 8784 | レジストリの <literal>HKCU\\Software\\TortoiseSVN\\ConfigDir</literal> を使用して、Subversion 設定ファイルの場所を異なる場所に指定できます。これは 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 | TSVNCache プログラムのキャッシュトレイアイコンを追加するため、<literal>HKCU\\Software\\TortoiseSVN\\CacheTrayIcon</literal> に <literal>DWORD</literal> キーを値 1 で作成してください。これによりプログラムを作法に則って終了させます。そのため実際には開発者のみに有用です。 | |
| 4 | 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 <literal>false</literal> if you don't want TortoiseSVN to show icons for the shell context menu items. Set this value to <literal>true</literal> to show the icons again. | 8796 | これは Windows エクスプローラ以外のものを使用したり、コンテキストメニューが正しく表示できないといった問題が発生したりしたときに便利です。TortoiseSVN にシェルのコンテキストメニューのアイコンを表示させたくない場合、<literal>HKCU\\Software\\TortoiseSVN\\ShowContextMenuIcons</literal> に <literal>DWORD</literal> のキーを値 0 で作成してください。またアイコンを表示する場合は、この値を 1 としてください。 | |
| 5 | 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 <literal>true</literal>. | 8824 | 他の TortoiseSVN コマンド (更新、コミットなど) を実行している間、エクスプローラの状態オーバーレイアイコンを更新したくない場合、<literal>HKCU\\Software\\TortoiseSVN\\BlockStatus</literal> に <literal>DWORD</literal> のキーを作成し、値を 1 としてください。 | |
| 6 | 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. | 8828 | <literal>HKCU\\Software\\TortoiseSVN\\UpdateCheckURL</literal> には TortoiseSVN の更新があった場合にダウンロードするテキストファイルの URL が格納されています。必要に応じて <literal>HKCU</literal> を <literal>HKLM</literal> に変更することもできますが、<literal>HKLM</literal> の設定を <literal>HKCU</literal> は上書きしてしまいます。企業の管理者が承認するまで TortoiseSVN の更新をさせないようにするのに便利だと思います。 |
| 7 | 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 <literal>true</literal>. Note that the extra columns are only available in XP. Vista and later doesn't support that feature any more. | 8832 | Windows エクスプローラの詳細ビューに表示する、TortoiseSVN が追加する列は、通常、作業コピーのみに有効です。作業コピーのみではなく、どこでもこの列を表示するには、<literal>HKCU\\Software\\TortoiseSVN\\ColumnsEveryWhere</literal> に <literal>DWORD</literal> キーを作成し、値を 1 としてください。 | |
| 8 | 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 <literal>true</literal>. | 8848 | コミットメッセージエディタの自動補完リストには、コミットするファイル名が表示されます。この名前から拡張子を除くには、<literal>HKCU\\Software\\TortoiseSVN\\AutocompleteRemovesExtensions</literal> に <literal>DWORD</literal> のキーを作成し、値を 1 としてください。 | |
| 9 | 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. | 8852 | 別のブランチから、あるリビジョンをマージした際、マージ追跡情報が有効だと、そのリビジョン由来のログメッセージをまとめて、コミットログメッセージにします。変更するには、<literal>HKCU\\Software\\TortoiseSVN\\MergeLogSeparator</literal> に <literal>SZ</literal> キーを作成し、お好みの文字列を設定してください。 |
| 10 | 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 は外部 diff ビューアを使用できます。しかし、ほとんどのそのようなビューアは注釈履歴 (<xref linkend=\"tsvn-dug-blame-diffs\"/>) には対応していません。そのため、このような場合に TortoiseMerge にフォールバックしたくなるかと思います。それには、<literal>HKCU\\Software\\TortoiseSVN\\DiffBlamesWithTortoiseMerge</literal> に <literal>DWORD</literal> キーを作成し、値を 1 としてください。 |
Total:10
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.
