OSDN Git Service

Add Document from TortoiseSVN 15285
authorFrank Li <lznuaa@gmail.com>
Sun, 8 Feb 2009 07:50:54 +0000 (15:50 +0800)
committerFrank Li <lznuaa@gmail.com>
Sun, 8 Feb 2009 07:50:54 +0000 (15:50 +0800)
967 files changed:
doc/API/Doxyfile [new file with mode: 0644]
doc/API/DoxyfileSVN [new file with mode: 0644]
doc/Aspell/Readme.txt [new file with mode: 0644]
doc/Aspell/TortoiseSVN.tmpl.pws [new file with mode: 0644]
doc/Aspell/append.bat [new file with mode: 0644]
doc/Aspell/aspell.in [new file with mode: 0644]
doc/Aspell/de.pws [new file with mode: 0644]
doc/Aspell/en.pws [new file with mode: 0644]
doc/Aspell/removetags.xsl [new file with mode: 0644]
doc/Aspell/ru.pws [new file with mode: 0644]
doc/AutolistDoc.txt [new file with mode: 0644]
doc/MailingListAnswers.txt [new file with mode: 0644]
doc/Screenshots.txt [new file with mode: 0644]
doc/UploadDocs.bat [new file with mode: 0644]
doc/build-zh_CN.txt [new file with mode: 0644]
doc/doc.build [new file with mode: 0644]
doc/doc.build.include [new file with mode: 0644]
doc/doc.build.user.tmpl [new file with mode: 0644]
doc/images/adjustimages.bat [new file with mode: 0644]
doc/images/de/Authenticate.png [new file with mode: 0644]
doc/images/de/BlameDialog.png [new file with mode: 0644]
doc/images/de/Checkout.png [new file with mode: 0644]
doc/images/de/Commit.png [new file with mode: 0644]
doc/images/de/CommitProgress.png [new file with mode: 0644]
doc/images/de/CommitSpellcheck.png [new file with mode: 0644]
doc/images/de/CompareRevisions.png [new file with mode: 0644]
doc/images/de/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/de/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/de/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/de/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/de/Copy.png [new file with mode: 0644]
doc/images/de/CreatePatch.png [new file with mode: 0644]
doc/images/de/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/de/GetLock.png [new file with mode: 0644]
doc/images/de/Import.png [new file with mode: 0644]
doc/images/de/LogContextMenu.png [new file with mode: 0644]
doc/images/de/LogContextMenu1.png [new file with mode: 0644]
doc/images/de/LogContextMenu2.png [new file with mode: 0644]
doc/images/de/LogMessages.png [new file with mode: 0644]
doc/images/de/Merge.png [new file with mode: 0644]
doc/images/de/Properties.png [new file with mode: 0644]
doc/images/de/PropertyAdd.png [new file with mode: 0644]
doc/images/de/PropertyList.png [new file with mode: 0644]
doc/images/de/Relocate.png [new file with mode: 0644]
doc/images/de/RepoStatus.png [new file with mode: 0644]
doc/images/de/Repobrowser.png [new file with mode: 0644]
doc/images/de/Revert.png [new file with mode: 0644]
doc/images/de/RevisionGraph.png [new file with mode: 0644]
doc/images/de/RightDragMenu.png [new file with mode: 0644]
doc/images/de/SettingsColors.png [new file with mode: 0644]
doc/images/de/SettingsContext.png [new file with mode: 0644]
doc/images/de/SettingsDialog.png [new file with mode: 0644]
doc/images/de/SettingsDialog2.png [new file with mode: 0644]
doc/images/de/SettingsLogStats.png [new file with mode: 0644]
doc/images/de/SettingsMain.png [new file with mode: 0644]
doc/images/de/SettingsOverlay.png [new file with mode: 0644]
doc/images/de/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/de/SettingsProgs.png [new file with mode: 0644]
doc/images/de/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/de/SettingsProxy.png [new file with mode: 0644]
doc/images/de/SettingsSavedData.png [new file with mode: 0644]
doc/images/de/StatsByAuthPie.png [new file with mode: 0644]
doc/images/de/StatsByAuthor.png [new file with mode: 0644]
doc/images/de/StatsByWeek.png [new file with mode: 0644]
doc/images/de/Switch.png [new file with mode: 0644]
doc/images/de/TMerge_OnePane.png [new file with mode: 0644]
doc/images/de/TMerge_Open.png [new file with mode: 0644]
doc/images/de/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/de/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/de/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/de/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/de/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/de/TortoiseBlame.png [new file with mode: 0644]
doc/images/de/TortoiseIDiff.png [new file with mode: 0644]
doc/images/de/UpdateFinished.png [new file with mode: 0644]
doc/images/de/ch02dia1.png [new file with mode: 0644]
doc/images/de/ch02dia2.png [new file with mode: 0644]
doc/images/de/ch02dia3.png [new file with mode: 0644]
doc/images/de/ch02dia4.png [new file with mode: 0644]
doc/images/de/ch02dia5.png [new file with mode: 0644]
doc/images/de/mergeprinciple.png [new file with mode: 0644]
doc/images/en/ActionAddedIcon.png [new file with mode: 0644]
doc/images/en/ActionDeletedIcon.png [new file with mode: 0644]
doc/images/en/ActionModifiedIcon.png [new file with mode: 0644]
doc/images/en/ActionReplacedIcon.png [new file with mode: 0644]
doc/images/en/AddedIcon.png [new file with mode: 0644]
doc/images/en/Authenticate.png [new file with mode: 0644]
doc/images/en/BlameDialog.png [new file with mode: 0644]
doc/images/en/Bullet.gif [new file with mode: 0644]
doc/images/en/Changelist.png [new file with mode: 0644]
doc/images/en/Checkout.png [new file with mode: 0644]
doc/images/en/Commit.png [new file with mode: 0644]
doc/images/en/CommitProgress.png [new file with mode: 0644]
doc/images/en/CommitSpellcheck.png [new file with mode: 0644]
doc/images/en/CompareRevisions.png [new file with mode: 0644]
doc/images/en/ConflictIcon.png [new file with mode: 0644]
doc/images/en/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/en/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/en/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/en/ContextMenuFileIgnore.png [new file with mode: 0644]
doc/images/en/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/en/Copy.png [new file with mode: 0644]
doc/images/en/CreatePatch.png [new file with mode: 0644]
doc/images/en/DeletedIcon.png [new file with mode: 0644]
doc/images/en/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/en/ExportURL.png [new file with mode: 0644]
doc/images/en/GetLock.png [new file with mode: 0644]
doc/images/en/IgnoredIcon.png [new file with mode: 0644]
doc/images/en/Import.png [new file with mode: 0644]
doc/images/en/InSubVersionIcon.png [new file with mode: 0644]
doc/images/en/IssueTrackerQuery.png [new file with mode: 0644]
doc/images/en/LockedIcon.png [new file with mode: 0644]
doc/images/en/LogContextMenu.png [new file with mode: 0644]
doc/images/en/LogContextMenu1.png [new file with mode: 0644]
doc/images/en/LogContextMenu2.png [new file with mode: 0644]
doc/images/en/LogMergeTrack.png [new file with mode: 0644]
doc/images/en/LogMessages.png [new file with mode: 0644]
doc/images/en/MergeAll.png [new file with mode: 0644]
doc/images/en/MergeConflictCallback.png [new file with mode: 0644]
doc/images/en/MergeWizardOptions.png [new file with mode: 0644]
doc/images/en/MergeWizardRange.png [new file with mode: 0644]
doc/images/en/MergeWizardReintegrate.png [new file with mode: 0644]
doc/images/en/MergeWizardTree.png [new file with mode: 0644]
doc/images/en/ModifiedIcon.png [new file with mode: 0644]
doc/images/en/Overlays.png [new file with mode: 0644]
doc/images/en/Properties.png [new file with mode: 0644]
doc/images/en/PropertyAdd.png [new file with mode: 0644]
doc/images/en/PropertyList.png [new file with mode: 0644]
doc/images/en/ReadOnlyIcon.png [new file with mode: 0644]
doc/images/en/Relocate.png [new file with mode: 0644]
doc/images/en/RepoStatus.png [new file with mode: 0644]
doc/images/en/Repobrowser.png [new file with mode: 0644]
doc/images/en/RevGraphCollapse.png [new file with mode: 0644]
doc/images/en/RevGraphExpand.png [new file with mode: 0644]
doc/images/en/RevGraphJoin.png [new file with mode: 0644]
doc/images/en/RevGraphSplit.png [new file with mode: 0644]
doc/images/en/Revert.png [new file with mode: 0644]
doc/images/en/RevisionGraph.png [new file with mode: 0644]
doc/images/en/RightDragMenu.png [new file with mode: 0644]
doc/images/en/SettingsBlame.png [new file with mode: 0644]
doc/images/en/SettingsColors.png [new file with mode: 0644]
doc/images/en/SettingsContext.png [new file with mode: 0644]
doc/images/en/SettingsDialog.png [new file with mode: 0644]
doc/images/en/SettingsDialog2.png [new file with mode: 0644]
doc/images/en/SettingsHookEdit.png [new file with mode: 0644]
doc/images/en/SettingsHooks.png [new file with mode: 0644]
doc/images/en/SettingsIssueTracker.png [new file with mode: 0644]
doc/images/en/SettingsLogCache.png [new file with mode: 0644]
doc/images/en/SettingsLogStats.png [new file with mode: 0644]
doc/images/en/SettingsMain.png [new file with mode: 0644]
doc/images/en/SettingsOverlay.png [new file with mode: 0644]
doc/images/en/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/en/SettingsProgs.png [new file with mode: 0644]
doc/images/en/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/en/SettingsProxy.png [new file with mode: 0644]
doc/images/en/SettingsSavedData.png [new file with mode: 0644]
doc/images/en/StatsByAuthPie.png [new file with mode: 0644]
doc/images/en/StatsByAuthor.png [new file with mode: 0644]
doc/images/en/StatsByDate.png [new file with mode: 0644]
doc/images/en/Switch.png [new file with mode: 0644]
doc/images/en/TMerge_OnePane.png [new file with mode: 0644]
doc/images/en/TMerge_Open.png [new file with mode: 0644]
doc/images/en/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/en/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/en/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/en/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/en/TMerge_Toolbar.png [new file with mode: 0644]
doc/images/en/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/en/TMerge_lineadded.png [new file with mode: 0644]
doc/images/en/TMerge_lineconflicted.png [new file with mode: 0644]
doc/images/en/TMerge_lineconflictedignored.png [new file with mode: 0644]
doc/images/en/TMerge_lineedited.png [new file with mode: 0644]
doc/images/en/TMerge_lineequal.png [new file with mode: 0644]
doc/images/en/TMerge_lineremoved.png [new file with mode: 0644]
doc/images/en/TMerge_linewhitespace.png [new file with mode: 0644]
doc/images/en/Tortoise.png [new file with mode: 0644]
doc/images/en/TortoiseBlame.png [new file with mode: 0644]
doc/images/en/TortoiseIDiff.png [new file with mode: 0644]
doc/images/en/UnversionedIcon.png [new file with mode: 0644]
doc/images/en/UpdateFinished.png [new file with mode: 0644]
doc/images/en/background.png [new file with mode: 0644]
doc/images/en/backgrounddraft.png [new file with mode: 0644]
doc/images/en/caution.png [new file with mode: 0644]
doc/images/en/caution_sml.png [new file with mode: 0644]
doc/images/en/ch02dia1.png [new file with mode: 0644]
doc/images/en/ch02dia2.png [new file with mode: 0644]
doc/images/en/ch02dia3.png [new file with mode: 0644]
doc/images/en/ch02dia4.png [new file with mode: 0644]
doc/images/en/ch02dia5.png [new file with mode: 0644]
doc/images/en/ch02dia6.png [new file with mode: 0644]
doc/images/en/ch02dia7.png [new file with mode: 0644]
doc/images/en/important.png [new file with mode: 0644]
doc/images/en/important_sml.png [new file with mode: 0644]
doc/images/en/link.png [new file with mode: 0644]
doc/images/en/mergeprinciple.png [new file with mode: 0644]
doc/images/en/note.png [new file with mode: 0644]
doc/images/en/svn_move.png [new file with mode: 0644]
doc/images/en/svn_move.swf [new file with mode: 0644]
doc/images/en/tip.png [new file with mode: 0644]
doc/images/en/tip_sml.png [new file with mode: 0644]
doc/images/en/tortoisemerge_logo_hor468x64.png [new file with mode: 0644]
doc/images/en/tortoisesvn_logo_hor468x64.png [new file with mode: 0644]
doc/images/en/upgradecheck.png [new file with mode: 0644]
doc/images/en/warning.png [new file with mode: 0644]
doc/images/en/warning_sml.png [new file with mode: 0644]
doc/images/es/Authenticate.png [new file with mode: 0644]
doc/images/es/BlameDialog.png [new file with mode: 0644]
doc/images/es/Checkout.png [new file with mode: 0644]
doc/images/es/Commit.png [new file with mode: 0644]
doc/images/es/CommitProgress.png [new file with mode: 0644]
doc/images/es/CommitSpellcheck.png [new file with mode: 0644]
doc/images/es/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/es/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/es/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/es/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/es/Copy.png [new file with mode: 0644]
doc/images/es/CreatePatch.png [new file with mode: 0644]
doc/images/es/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/es/GetLock.png [new file with mode: 0644]
doc/images/es/Import.png [new file with mode: 0644]
doc/images/es/LogContextMenu.png [new file with mode: 0644]
doc/images/es/LogContextMenu1.png [new file with mode: 0644]
doc/images/es/LogContextMenu2.png [new file with mode: 0644]
doc/images/es/LogMessages.png [new file with mode: 0644]
doc/images/es/Merge.png [new file with mode: 0644]
doc/images/es/Properties.png [new file with mode: 0644]
doc/images/es/PropertyAdd.png [new file with mode: 0644]
doc/images/es/PropertyList.png [new file with mode: 0644]
doc/images/es/Relocate.png [new file with mode: 0644]
doc/images/es/RepoStatus.png [new file with mode: 0644]
doc/images/es/Repobrowser.png [new file with mode: 0644]
doc/images/es/Revert.png [new file with mode: 0644]
doc/images/es/RevisionGraph.png [new file with mode: 0644]
doc/images/es/RightDragMenu.png [new file with mode: 0644]
doc/images/es/SettingsColors.png [new file with mode: 0644]
doc/images/es/SettingsContext.png [new file with mode: 0644]
doc/images/es/SettingsDialog.png [new file with mode: 0644]
doc/images/es/SettingsDialog2.png [new file with mode: 0644]
doc/images/es/SettingsMain.png [new file with mode: 0644]
doc/images/es/SettingsOverlay.png [new file with mode: 0644]
doc/images/es/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/es/SettingsProgs.png [new file with mode: 0644]
doc/images/es/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/es/SettingsProxy.png [new file with mode: 0644]
doc/images/es/SettingsSavedData.png [new file with mode: 0644]
doc/images/es/StatsByAuthPie.png [new file with mode: 0644]
doc/images/es/StatsByAuthor.png [new file with mode: 0644]
doc/images/es/StatsByWeek.png [new file with mode: 0644]
doc/images/es/Switch.png [new file with mode: 0644]
doc/images/es/TMerge_OnePane.png [new file with mode: 0644]
doc/images/es/TMerge_Open.png [new file with mode: 0644]
doc/images/es/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/es/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/es/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/es/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/es/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/es/TortoiseBlame.png [new file with mode: 0644]
doc/images/es/TortoiseIDiff.png [new file with mode: 0644]
doc/images/es/UpdateFinished.png [new file with mode: 0644]
doc/images/es/ch02dia1.png [new file with mode: 0644]
doc/images/es/ch02dia2.png [new file with mode: 0644]
doc/images/es/ch02dia3.png [new file with mode: 0644]
doc/images/es/ch02dia4.png [new file with mode: 0644]
doc/images/es/ch02dia5.png [new file with mode: 0644]
doc/images/es/ch02dia6.png [new file with mode: 0644]
doc/images/es/ch02dia7.png [new file with mode: 0644]
doc/images/es/mergeprinciple.png [new file with mode: 0644]
doc/images/es/upgradecheck.png [new file with mode: 0644]
doc/images/fi/Authenticate.png [new file with mode: 0644]
doc/images/fi/BlameDialog.png [new file with mode: 0644]
doc/images/fi/Changelist.png [new file with mode: 0644]
doc/images/fi/Checkout.png [new file with mode: 0644]
doc/images/fi/Commit.png [new file with mode: 0644]
doc/images/fi/CommitProgress.png [new file with mode: 0644]
doc/images/fi/CommitSpellcheck.png [new file with mode: 0644]
doc/images/fi/CompareRevisions.png [new file with mode: 0644]
doc/images/fi/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/fi/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/fi/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/fi/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/fi/Copy.png [new file with mode: 0644]
doc/images/fi/CreatePatch.png [new file with mode: 0644]
doc/images/fi/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/fi/ExportURL.png [new file with mode: 0644]
doc/images/fi/GetLock.png [new file with mode: 0644]
doc/images/fi/Import.png [new file with mode: 0644]
doc/images/fi/IssueTrackerQuery.png [new file with mode: 0644]
doc/images/fi/LogContextMenu.png [new file with mode: 0644]
doc/images/fi/LogContextMenu1.png [new file with mode: 0644]
doc/images/fi/LogContextMenu2.png [new file with mode: 0644]
doc/images/fi/LogMergeTrack.png [new file with mode: 0644]
doc/images/fi/LogMessages.png [new file with mode: 0644]
doc/images/fi/MergeAll.png [new file with mode: 0644]
doc/images/fi/MergeConflictCallback.png [new file with mode: 0644]
doc/images/fi/MergeWizardOptions.png [new file with mode: 0644]
doc/images/fi/MergeWizardRange.png [new file with mode: 0644]
doc/images/fi/MergeWizardReintegrate.png [new file with mode: 0644]
doc/images/fi/MergeWizardTree.png [new file with mode: 0644]
doc/images/fi/Properties.png [new file with mode: 0644]
doc/images/fi/PropertyAdd.png [new file with mode: 0644]
doc/images/fi/PropertyList.png [new file with mode: 0644]
doc/images/fi/Relocate.png [new file with mode: 0644]
doc/images/fi/RepoStatus.png [new file with mode: 0644]
doc/images/fi/Repobrowser.png [new file with mode: 0644]
doc/images/fi/Revert.png [new file with mode: 0644]
doc/images/fi/RevisionGraph.png [new file with mode: 0644]
doc/images/fi/RightDragMenu.png [new file with mode: 0644]
doc/images/fi/SettingsBlame.png [new file with mode: 0644]
doc/images/fi/SettingsColors.png [new file with mode: 0644]
doc/images/fi/SettingsContext.png [new file with mode: 0644]
doc/images/fi/SettingsDialog.png [new file with mode: 0644]
doc/images/fi/SettingsDialog2.png [new file with mode: 0644]
doc/images/fi/SettingsHookEdit.png [new file with mode: 0644]
doc/images/fi/SettingsHooks.png [new file with mode: 0644]
doc/images/fi/SettingsIssueTracker.png [new file with mode: 0644]
doc/images/fi/SettingsLogCache.png [new file with mode: 0644]
doc/images/fi/SettingsLogStats.png [new file with mode: 0644]
doc/images/fi/SettingsMain.png [new file with mode: 0644]
doc/images/fi/SettingsOverlay.png [new file with mode: 0644]
doc/images/fi/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/fi/SettingsProgs.png [new file with mode: 0644]
doc/images/fi/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/fi/SettingsProxy.png [new file with mode: 0644]
doc/images/fi/SettingsSavedData.png [new file with mode: 0644]
doc/images/fi/StatsByAuthPie.png [new file with mode: 0644]
doc/images/fi/StatsByAuthor.png [new file with mode: 0644]
doc/images/fi/StatsByDate.png [new file with mode: 0644]
doc/images/fi/Switch.png [new file with mode: 0644]
doc/images/fi/TMerge_OnePane.png [new file with mode: 0644]
doc/images/fi/TMerge_Open.png [new file with mode: 0644]
doc/images/fi/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/fi/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/fi/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/fi/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/fi/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/fi/TortoiseBlame.png [new file with mode: 0644]
doc/images/fi/TortoiseIDiff.png [new file with mode: 0644]
doc/images/fi/UpdateFinished.png [new file with mode: 0644]
doc/images/fi/ch02dia1.png [new file with mode: 0644]
doc/images/fi/ch02dia2.png [new file with mode: 0644]
doc/images/fi/ch02dia3.png [new file with mode: 0644]
doc/images/fi/ch02dia4.png [new file with mode: 0644]
doc/images/fi/ch02dia5.png [new file with mode: 0644]
doc/images/fi/mergeprinciple.png [new file with mode: 0644]
doc/images/fi/upgradecheck.png [new file with mode: 0644]
doc/images/fr/Authenticate.png [new file with mode: 0644]
doc/images/fr/BlameDialog.png [new file with mode: 0644]
doc/images/fr/Checkout.png [new file with mode: 0644]
doc/images/fr/Commit.png [new file with mode: 0644]
doc/images/fr/CommitProgress.png [new file with mode: 0644]
doc/images/fr/CommitSpellcheck.png [new file with mode: 0644]
doc/images/fr/CompareRevisions.png [new file with mode: 0644]
doc/images/fr/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/fr/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/fr/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/fr/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/fr/Copy.png [new file with mode: 0644]
doc/images/fr/CreatePatch.png [new file with mode: 0644]
doc/images/fr/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/fr/GetLock.png [new file with mode: 0644]
doc/images/fr/Import.png [new file with mode: 0644]
doc/images/fr/LogContextMenu.png [new file with mode: 0644]
doc/images/fr/LogContextMenu1.png [new file with mode: 0644]
doc/images/fr/LogContextMenu2.png [new file with mode: 0644]
doc/images/fr/LogMessages.png [new file with mode: 0644]
doc/images/fr/Merge.png [new file with mode: 0644]
doc/images/fr/Properties.png [new file with mode: 0644]
doc/images/fr/PropertyAdd.png [new file with mode: 0644]
doc/images/fr/PropertyList.png [new file with mode: 0644]
doc/images/fr/Relocate.png [new file with mode: 0644]
doc/images/fr/RepoStatus.png [new file with mode: 0644]
doc/images/fr/Repobrowser.png [new file with mode: 0644]
doc/images/fr/Revert.png [new file with mode: 0644]
doc/images/fr/RevisionGraph.png [new file with mode: 0644]
doc/images/fr/RightDragMenu.png [new file with mode: 0644]
doc/images/fr/SettingsColors.png [new file with mode: 0644]
doc/images/fr/SettingsContext.png [new file with mode: 0644]
doc/images/fr/SettingsDialog.png [new file with mode: 0644]
doc/images/fr/SettingsDialog2.png [new file with mode: 0644]
doc/images/fr/SettingsMain.png [new file with mode: 0644]
doc/images/fr/SettingsOverlay.png [new file with mode: 0644]
doc/images/fr/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/fr/SettingsProgs.png [new file with mode: 0644]
doc/images/fr/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/fr/SettingsProxy.png [new file with mode: 0644]
doc/images/fr/SettingsSavedData.png [new file with mode: 0644]
doc/images/fr/StatsByAuthPie.png [new file with mode: 0644]
doc/images/fr/StatsByAuthor.png [new file with mode: 0644]
doc/images/fr/StatsByWeek.png [new file with mode: 0644]
doc/images/fr/Switch.png [new file with mode: 0644]
doc/images/fr/TMerge_OnePane.png [new file with mode: 0644]
doc/images/fr/TMerge_Open.png [new file with mode: 0644]
doc/images/fr/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/fr/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/fr/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/fr/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/fr/TortoiseBlame.png [new file with mode: 0644]
doc/images/fr/UpdateFinished.png [new file with mode: 0644]
doc/images/fr/ch02dia1.png [new file with mode: 0644]
doc/images/fr/ch02dia2.png [new file with mode: 0644]
doc/images/fr/ch02dia3.png [new file with mode: 0644]
doc/images/fr/ch02dia4.png [new file with mode: 0644]
doc/images/fr/ch02dia5.png [new file with mode: 0644]
doc/images/fr/mergeprinciple.png [new file with mode: 0644]
doc/images/fr/svn_move.swf [new file with mode: 0644]
doc/images/fr/upgradecheck.png [new file with mode: 0644]
doc/images/id/Authenticate.png [new file with mode: 0644]
doc/images/id/BlameDialog.png [new file with mode: 0644]
doc/images/id/Checkout.png [new file with mode: 0644]
doc/images/id/Commit.png [new file with mode: 0644]
doc/images/id/CommitProgress.png [new file with mode: 0644]
doc/images/id/CommitSpellcheck.png [new file with mode: 0644]
doc/images/id/CompareRevisions.png [new file with mode: 0644]
doc/images/id/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/id/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/id/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/id/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/id/Copy.png [new file with mode: 0644]
doc/images/id/CreatePatch.png [new file with mode: 0644]
doc/images/id/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/id/GetLock.png [new file with mode: 0644]
doc/images/id/Import.png [new file with mode: 0644]
doc/images/id/LogContextMenu.png [new file with mode: 0644]
doc/images/id/LogContextMenu1.png [new file with mode: 0644]
doc/images/id/LogContextMenu2.png [new file with mode: 0644]
doc/images/id/LogMessages.png [new file with mode: 0644]
doc/images/id/Merge.png [new file with mode: 0644]
doc/images/id/Overlays.png [new file with mode: 0644]
doc/images/id/Properties.png [new file with mode: 0644]
doc/images/id/PropertyAdd.png [new file with mode: 0644]
doc/images/id/PropertyList.png [new file with mode: 0644]
doc/images/id/Relocate.png [new file with mode: 0644]
doc/images/id/RepoStatus.png [new file with mode: 0644]
doc/images/id/Repobrowser.png [new file with mode: 0644]
doc/images/id/Revert.png [new file with mode: 0644]
doc/images/id/RevisionGraph.png [new file with mode: 0644]
doc/images/id/RightDragMenu.png [new file with mode: 0644]
doc/images/id/SettingsColors.png [new file with mode: 0644]
doc/images/id/SettingsContext.png [new file with mode: 0644]
doc/images/id/SettingsDialog.png [new file with mode: 0644]
doc/images/id/SettingsDialog2.png [new file with mode: 0644]
doc/images/id/SettingsMain.png [new file with mode: 0644]
doc/images/id/SettingsOverlay.png [new file with mode: 0644]
doc/images/id/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/id/SettingsProgs.png [new file with mode: 0644]
doc/images/id/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/id/SettingsProxy.png [new file with mode: 0644]
doc/images/id/SettingsSavedData.png [new file with mode: 0644]
doc/images/id/StatsByAuthPie.png [new file with mode: 0644]
doc/images/id/StatsByAuthor.png [new file with mode: 0644]
doc/images/id/StatsByWeek.png [new file with mode: 0644]
doc/images/id/Switch.png [new file with mode: 0644]
doc/images/id/TMerge_OnePane.png [new file with mode: 0644]
doc/images/id/TMerge_Open.png [new file with mode: 0644]
doc/images/id/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/id/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/id/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/id/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/id/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/id/TortoiseBlame.png [new file with mode: 0644]
doc/images/id/TortoiseIDiff.png [new file with mode: 0644]
doc/images/id/UpdateFinished.png [new file with mode: 0644]
doc/images/id/ch02dia1.png [new file with mode: 0644]
doc/images/id/ch02dia2.png [new file with mode: 0644]
doc/images/id/ch02dia3.png [new file with mode: 0644]
doc/images/id/ch02dia4.png [new file with mode: 0644]
doc/images/id/ch02dia5.png [new file with mode: 0644]
doc/images/id/ch02dia6.png [new file with mode: 0644]
doc/images/id/ch02dia7.png [new file with mode: 0644]
doc/images/id/mergeprinciple.png [new file with mode: 0644]
doc/images/id/upgradecheck.png [new file with mode: 0644]
doc/images/ja/ActionAddedIcon.png [new file with mode: 0644]
doc/images/ja/ActionDeletedIcon.png [new file with mode: 0644]
doc/images/ja/ActionModifiedIcon.png [new file with mode: 0644]
doc/images/ja/ActionReplacedIcon.png [new file with mode: 0644]
doc/images/ja/AddedIcon.png [new file with mode: 0644]
doc/images/ja/Authenticate.png [new file with mode: 0644]
doc/images/ja/BlameDialog.png [new file with mode: 0644]
doc/images/ja/Bullet.gif [new file with mode: 0644]
doc/images/ja/Changelist.png [new file with mode: 0644]
doc/images/ja/Checkout.png [new file with mode: 0644]
doc/images/ja/Commit.png [new file with mode: 0644]
doc/images/ja/CommitProgress.png [new file with mode: 0644]
doc/images/ja/CommitSpellcheck.png [new file with mode: 0644]
doc/images/ja/CompareRevisions.png [new file with mode: 0644]
doc/images/ja/ConflictIcon.png [new file with mode: 0644]
doc/images/ja/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/ja/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/ja/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/ja/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/ja/Copy.png [new file with mode: 0644]
doc/images/ja/CreatePatch.png [new file with mode: 0644]
doc/images/ja/DeletedIcon.png [new file with mode: 0644]
doc/images/ja/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/ja/ExportURL.png [new file with mode: 0644]
doc/images/ja/GetLock.png [new file with mode: 0644]
doc/images/ja/IgnoredIcon.png [new file with mode: 0644]
doc/images/ja/Import.png [new file with mode: 0644]
doc/images/ja/InSubVersionIcon.png [new file with mode: 0644]
doc/images/ja/IssueTrackerQuery.png [new file with mode: 0644]
doc/images/ja/LockedIcon.png [new file with mode: 0644]
doc/images/ja/LogContextMenu.png [new file with mode: 0644]
doc/images/ja/LogContextMenu1.png [new file with mode: 0644]
doc/images/ja/LogContextMenu2.png [new file with mode: 0644]
doc/images/ja/LogMergeTrack.png [new file with mode: 0644]
doc/images/ja/LogMessages.png [new file with mode: 0644]
doc/images/ja/MergeAll.png [new file with mode: 0644]
doc/images/ja/MergeConflictCallback.png [new file with mode: 0644]
doc/images/ja/MergeWizardOptions.png [new file with mode: 0644]
doc/images/ja/MergeWizardRange.png [new file with mode: 0644]
doc/images/ja/MergeWizardReintegrate.png [new file with mode: 0644]
doc/images/ja/MergeWizardTree.png [new file with mode: 0644]
doc/images/ja/ModifiedIcon.png [new file with mode: 0644]
doc/images/ja/Overlays.png [new file with mode: 0644]
doc/images/ja/Properties.png [new file with mode: 0644]
doc/images/ja/PropertyAdd.png [new file with mode: 0644]
doc/images/ja/PropertyList.png [new file with mode: 0644]
doc/images/ja/ReadOnlyIcon.png [new file with mode: 0644]
doc/images/ja/Relocate.png [new file with mode: 0644]
doc/images/ja/RepoStatus.png [new file with mode: 0644]
doc/images/ja/Repobrowser.png [new file with mode: 0644]
doc/images/ja/Revert.png [new file with mode: 0644]
doc/images/ja/RevisionGraph.png [new file with mode: 0644]
doc/images/ja/RightDragMenu.png [new file with mode: 0644]
doc/images/ja/SettingsBlame.png [new file with mode: 0644]
doc/images/ja/SettingsColors.png [new file with mode: 0644]
doc/images/ja/SettingsContext.png [new file with mode: 0644]
doc/images/ja/SettingsDialog.png [new file with mode: 0644]
doc/images/ja/SettingsDialog2.png [new file with mode: 0644]
doc/images/ja/SettingsHookEdit.png [new file with mode: 0644]
doc/images/ja/SettingsHooks.png [new file with mode: 0644]
doc/images/ja/SettingsIssueTracker.png [new file with mode: 0644]
doc/images/ja/SettingsLogCache.png [new file with mode: 0644]
doc/images/ja/SettingsLogStats.png [new file with mode: 0644]
doc/images/ja/SettingsMain.png [new file with mode: 0644]
doc/images/ja/SettingsOverlay.png [new file with mode: 0644]
doc/images/ja/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/ja/SettingsProgs.png [new file with mode: 0644]
doc/images/ja/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/ja/SettingsProxy.png [new file with mode: 0644]
doc/images/ja/SettingsSavedData.png [new file with mode: 0644]
doc/images/ja/StatsByAuthPie.png [new file with mode: 0644]
doc/images/ja/StatsByAuthor.png [new file with mode: 0644]
doc/images/ja/StatsByDate.png [new file with mode: 0644]
doc/images/ja/Switch.png [new file with mode: 0644]
doc/images/ja/TMerge_OnePane.png [new file with mode: 0644]
doc/images/ja/TMerge_Open.png [new file with mode: 0644]
doc/images/ja/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/ja/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/ja/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/ja/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/ja/TMerge_Toolbar.png [new file with mode: 0644]
doc/images/ja/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/ja/TMerge_lineadded.png [new file with mode: 0644]
doc/images/ja/TMerge_lineconflicted.png [new file with mode: 0644]
doc/images/ja/TMerge_lineconflictedignored.png [new file with mode: 0644]
doc/images/ja/TMerge_lineedited.png [new file with mode: 0644]
doc/images/ja/TMerge_lineequal.png [new file with mode: 0644]
doc/images/ja/TMerge_lineremoved.png [new file with mode: 0644]
doc/images/ja/TMerge_linewhitespace.png [new file with mode: 0644]
doc/images/ja/Tortoise.png [new file with mode: 0644]
doc/images/ja/TortoiseBlame.png [new file with mode: 0644]
doc/images/ja/TortoiseIDiff.png [new file with mode: 0644]
doc/images/ja/UnversionedIcon.png [new file with mode: 0644]
doc/images/ja/UpdateFinished.png [new file with mode: 0644]
doc/images/ja/background.png [new file with mode: 0644]
doc/images/ja/backgrounddraft.png [new file with mode: 0644]
doc/images/ja/caution.png [new file with mode: 0644]
doc/images/ja/caution_sml.png [new file with mode: 0644]
doc/images/ja/ch02dia1.png [new file with mode: 0644]
doc/images/ja/ch02dia2.png [new file with mode: 0644]
doc/images/ja/ch02dia3.png [new file with mode: 0644]
doc/images/ja/ch02dia4.png [new file with mode: 0644]
doc/images/ja/ch02dia5.png [new file with mode: 0644]
doc/images/ja/ch02dia6.png [new file with mode: 0644]
doc/images/ja/ch02dia7.png [new file with mode: 0644]
doc/images/ja/important.png [new file with mode: 0644]
doc/images/ja/important_sml.png [new file with mode: 0644]
doc/images/ja/link.png [new file with mode: 0644]
doc/images/ja/mergeprinciple.png [new file with mode: 0644]
doc/images/ja/note.png [new file with mode: 0644]
doc/images/ja/svn_move.png [new file with mode: 0644]
doc/images/ja/svn_move.swf [new file with mode: 0644]
doc/images/ja/tip.png [new file with mode: 0644]
doc/images/ja/tip_sml.png [new file with mode: 0644]
doc/images/ja/tortoisemerge_logo_hor468x64.png [new file with mode: 0644]
doc/images/ja/tortoisesvn_logo_hor468x64.png [new file with mode: 0644]
doc/images/ja/upgradecheck.png [new file with mode: 0644]
doc/images/ja/warning.png [new file with mode: 0644]
doc/images/ja/warning_sml.png [new file with mode: 0644]
doc/images/ru/Authenticate.png [new file with mode: 0644]
doc/images/ru/BlameDialog.png [new file with mode: 0644]
doc/images/ru/Checkout.png [new file with mode: 0644]
doc/images/ru/Commit.png [new file with mode: 0644]
doc/images/ru/CommitProgress.png [new file with mode: 0644]
doc/images/ru/CommitSpellcheck.png [new file with mode: 0644]
doc/images/ru/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/ru/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/ru/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/ru/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/ru/Copy.png [new file with mode: 0644]
doc/images/ru/CreatePatch.png [new file with mode: 0644]
doc/images/ru/GetLock.png [new file with mode: 0644]
doc/images/ru/Import.png [new file with mode: 0644]
doc/images/ru/LogContextMenu.png [new file with mode: 0644]
doc/images/ru/LogContextMenu1.png [new file with mode: 0644]
doc/images/ru/LogContextMenu2.png [new file with mode: 0644]
doc/images/ru/LogMessages.png [new file with mode: 0644]
doc/images/ru/Merge.png [new file with mode: 0644]
doc/images/ru/Properties.png [new file with mode: 0644]
doc/images/ru/Relocate.png [new file with mode: 0644]
doc/images/ru/RepoStatus.png [new file with mode: 0644]
doc/images/ru/Repobrowser.png [new file with mode: 0644]
doc/images/ru/Revert.png [new file with mode: 0644]
doc/images/ru/RevisionGraph.png [new file with mode: 0644]
doc/images/ru/SettingsColors.png [new file with mode: 0644]
doc/images/ru/SettingsContext.png [new file with mode: 0644]
doc/images/ru/SettingsDialog.png [new file with mode: 0644]
doc/images/ru/SettingsDialog2.png [new file with mode: 0644]
doc/images/ru/SettingsMain.png [new file with mode: 0644]
doc/images/ru/SettingsOverlay.png [new file with mode: 0644]
doc/images/ru/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/ru/SettingsProgs.png [new file with mode: 0644]
doc/images/ru/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/ru/SettingsProxy.png [new file with mode: 0644]
doc/images/ru/Switch.png [new file with mode: 0644]
doc/images/ru/TMerge_OnePane.png [new file with mode: 0644]
doc/images/ru/TMerge_Open.png [new file with mode: 0644]
doc/images/ru/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/ru/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/ru/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/ru/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/ru/mergeprinciple.PNG [new file with mode: 0644]
doc/images/sl/Authenticate.png [new file with mode: 0644]
doc/images/sl/BlameDialog.png [new file with mode: 0644]
doc/images/sl/Changelist.png [new file with mode: 0644]
doc/images/sl/Checkout.png [new file with mode: 0644]
doc/images/sl/Commit.png [new file with mode: 0644]
doc/images/sl/CommitProgress.png [new file with mode: 0644]
doc/images/sl/CommitSpellcheck.png [new file with mode: 0644]
doc/images/sl/CompareRevisions.png [new file with mode: 0644]
doc/images/sl/ContextMenuDirControl.png [new file with mode: 0644]
doc/images/sl/ContextMenuDirNoControl.png [new file with mode: 0644]
doc/images/sl/ContextMenuFileControl.png [new file with mode: 0644]
doc/images/sl/ContextMenuFileNoControl.png [new file with mode: 0644]
doc/images/sl/Copy.png [new file with mode: 0644]
doc/images/sl/CreatePatch.png [new file with mode: 0644]
doc/images/sl/ExplorerFileMenuFileShortcut.png [new file with mode: 0644]
doc/images/sl/ExportURL.png [new file with mode: 0644]
doc/images/sl/GetLock.png [new file with mode: 0644]
doc/images/sl/Import.png [new file with mode: 0644]
doc/images/sl/IssueTrackerQuery.png [new file with mode: 0644]
doc/images/sl/LogContextMenu.png [new file with mode: 0644]
doc/images/sl/LogContextMenu1.png [new file with mode: 0644]
doc/images/sl/LogContextMenu2.png [new file with mode: 0644]
doc/images/sl/LogMergeTrack.png [new file with mode: 0644]
doc/images/sl/LogMessages.png [new file with mode: 0644]
doc/images/sl/MergeAll.png [new file with mode: 0644]
doc/images/sl/MergeConflictCallback.png [new file with mode: 0644]
doc/images/sl/MergeWizardOptions.png [new file with mode: 0644]
doc/images/sl/MergeWizardRange.png [new file with mode: 0644]
doc/images/sl/MergeWizardReintegrate.png [new file with mode: 0644]
doc/images/sl/MergeWizardTree.png [new file with mode: 0644]
doc/images/sl/Overlays.png [new file with mode: 0644]
doc/images/sl/Properties.png [new file with mode: 0644]
doc/images/sl/PropertyAdd.png [new file with mode: 0644]
doc/images/sl/PropertyList.png [new file with mode: 0644]
doc/images/sl/Relocate.png [new file with mode: 0644]
doc/images/sl/RepoStatus.png [new file with mode: 0644]
doc/images/sl/Repobrowser.png [new file with mode: 0644]
doc/images/sl/Revert.png [new file with mode: 0644]
doc/images/sl/RevisionGraph.png [new file with mode: 0644]
doc/images/sl/RightDragMenu.png [new file with mode: 0644]
doc/images/sl/SettingsBlame.png [new file with mode: 0644]
doc/images/sl/SettingsColors.png [new file with mode: 0644]
doc/images/sl/SettingsContext.png [new file with mode: 0644]
doc/images/sl/SettingsDialog.png [new file with mode: 0644]
doc/images/sl/SettingsDialog2.png [new file with mode: 0644]
doc/images/sl/SettingsHookEdit.png [new file with mode: 0644]
doc/images/sl/SettingsHooks.png [new file with mode: 0644]
doc/images/sl/SettingsIssueTracker.png [new file with mode: 0644]
doc/images/sl/SettingsLogCache.png [new file with mode: 0644]
doc/images/sl/SettingsLogStats.png [new file with mode: 0644]
doc/images/sl/SettingsMain.png [new file with mode: 0644]
doc/images/sl/SettingsOverlay.png [new file with mode: 0644]
doc/images/sl/SettingsOverlayChooser.png [new file with mode: 0644]
doc/images/sl/SettingsProgs.png [new file with mode: 0644]
doc/images/sl/SettingsProgsAdv.png [new file with mode: 0644]
doc/images/sl/SettingsProxy.png [new file with mode: 0644]
doc/images/sl/SettingsSavedData.png [new file with mode: 0644]
doc/images/sl/StatsByAuthPie.png [new file with mode: 0644]
doc/images/sl/StatsByAuthor.png [new file with mode: 0644]
doc/images/sl/StatsByDate.png [new file with mode: 0644]
doc/images/sl/Switch.png [new file with mode: 0644]
doc/images/sl/TMerge_OnePane.png [new file with mode: 0644]
doc/images/sl/TMerge_Open.png [new file with mode: 0644]
doc/images/sl/TMerge_PatchWindow.png [new file with mode: 0644]
doc/images/sl/TMerge_SettingsColors.png [new file with mode: 0644]
doc/images/sl/TMerge_SettingsGeneral.png [new file with mode: 0644]
doc/images/sl/TMerge_ThreePane.png [new file with mode: 0644]
doc/images/sl/TMerge_Toolbar.png [new file with mode: 0644]
doc/images/sl/TMerge_TwoPane.png [new file with mode: 0644]
doc/images/sl/Thumbs.db [new file with mode: 0644]
doc/images/sl/TortoiseBlame.png [new file with mode: 0644]
doc/images/sl/TortoiseIDiff.png [new file with mode: 0644]
doc/images/sl/UpdateFinished.png [new file with mode: 0644]
doc/images/sl/mergeprinciple.png [new file with mode: 0644]
doc/images/sl/upgradecheck.png [new file with mode: 0644]
doc/issuetrackers.txt [new file with mode: 0644]
doc/logo/Dialog_raw.psd [new file with mode: 0644]
doc/logo/TortoiseCheckout.png [new file with mode: 0644]
doc/logo/tortoisemerge_logo_hor468x64.png [new file with mode: 0644]
doc/logo/tortoisemerge_logo_hor468x64.psd [new file with mode: 0644]
doc/logo/tortoisesvn_logo_hor468x64.png [new file with mode: 0644]
doc/logo/tortoisesvn_logo_hor468x64.psd [new file with mode: 0644]
doc/logo/tsvn_logo.svg [new file with mode: 0644]
doc/logo/tsvn_logo_front.eps [new file with mode: 0644]
doc/logo/tsvn_logo_front.svg [new file with mode: 0644]
doc/logo/tsvn_rolleyes.gif [new file with mode: 0644]
doc/logo/turtle_black_border.psd [new file with mode: 0644]
doc/po/TortoiseMerge.pot [new file with mode: 0644]
doc/po/TortoiseMerge_de.po [new file with mode: 0644]
doc/po/TortoiseMerge_es.po [new file with mode: 0644]
doc/po/TortoiseMerge_fi.po [new file with mode: 0644]
doc/po/TortoiseMerge_fr.po [new file with mode: 0644]
doc/po/TortoiseMerge_hr.po [new file with mode: 0644]
doc/po/TortoiseMerge_id.po [new file with mode: 0644]
doc/po/TortoiseMerge_ja.po [new file with mode: 0644]
doc/po/TortoiseMerge_nl.po [new file with mode: 0644]
doc/po/TortoiseMerge_ru.po [new file with mode: 0644]
doc/po/TortoiseMerge_sk.po [new file with mode: 0644]
doc/po/TortoiseMerge_sl.po [new file with mode: 0644]
doc/po/TortoiseMerge_sr_spc.po [new file with mode: 0644]
doc/po/TortoiseMerge_sr_spl.po [new file with mode: 0644]
doc/po/TortoiseMerge_zh_CN.po [new file with mode: 0644]
doc/po/TortoiseSVN.pot [new file with mode: 0644]
doc/po/TortoiseSVN_de.po [new file with mode: 0644]
doc/po/TortoiseSVN_es.po [new file with mode: 0644]
doc/po/TortoiseSVN_fa.po [new file with mode: 0644]
doc/po/TortoiseSVN_fi.po [new file with mode: 0644]
doc/po/TortoiseSVN_fr.po [new file with mode: 0644]
doc/po/TortoiseSVN_id.po [new file with mode: 0644]
doc/po/TortoiseSVN_ja.po [new file with mode: 0644]
doc/po/TortoiseSVN_nl.po [new file with mode: 0644]
doc/po/TortoiseSVN_ru.po [new file with mode: 0644]
doc/po/TortoiseSVN_sk.po [new file with mode: 0644]
doc/po/TortoiseSVN_sl.po [new file with mode: 0644]
doc/po/TortoiseSVN_sr_spc.po [new file with mode: 0644]
doc/po/TortoiseSVN_sr_spl.po [new file with mode: 0644]
doc/po/TortoiseSVN_zh_CN.po [new file with mode: 0644]
doc/readme.txt [new file with mode: 0644]
doc/source/Hacking.txt [new file with mode: 0644]
doc/source/Pubdate.none [new file with mode: 0644]
doc/source/Pubdate.tmpl [new file with mode: 0644]
doc/source/dtd/dblite.dtd [new file with mode: 0644]
doc/source/dtd/docbook41/calstblx.dtd [new file with mode: 0644]
doc/source/dtd/docbook41/dbcentx.mod [new file with mode: 0644]
doc/source/dtd/docbook41/dbgenent.ent [new file with mode: 0644]
doc/source/dtd/docbook41/dbhierx.mod [new file with mode: 0644]
doc/source/dtd/docbook41/dbnotnx.mod [new file with mode: 0644]
doc/source/dtd/docbook41/dbpoolx.mod [new file with mode: 0644]
doc/source/dtd/docbook41/docbook.cat [new file with mode: 0644]
doc/source/dtd/docbook41/docbookx.dtd [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-amsa.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-amsb.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-amsc.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-amsn.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-amso.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-amsr.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-box.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-cyr1.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-cyr2.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-dia.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-grk1.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-grk2.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-grk3.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-grk4.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-lat1.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-lat2.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-num.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-pub.ent [new file with mode: 0644]
doc/source/dtd/docbook41/ent/iso-tech.ent [new file with mode: 0644]
doc/source/dtd/docbook41/soextblx.dtd [new file with mode: 0644]
doc/source/dtd/readme-dblite.html [new file with mode: 0644]
doc/source/en/SubWCRev.txt [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_app_automation.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_app_shortcuts.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_basics.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_dug.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_dug_conflicts.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_dug_controls.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_dug_icons.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_dug_open.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_dug_settings.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_dug_views.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_introduction.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tme_preface.xml [new file with mode: 0644]
doc/source/en/TortoiseMerge/tortoisemerge.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tortoisesvn.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_app_admins.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_app_automation.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_app_cli.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_app_faq.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_app_howto.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_app_internals.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_app_ssh.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_basics.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_add.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_blame.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_branchtag.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_bugtracker.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_changelist.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_checkout.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_cleanup.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_commit.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_conflicts.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_copy.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_diff.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_export.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_general.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_ignore.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_import.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_locking.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_log.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_merge.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_patch.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_propertypage.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_relocate.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_rename.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_repobrowser.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_repoviewer.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_revert.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_revgraph.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_aspdotnet.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_blame.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_general.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_hooks.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_logcache.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_network.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_overlays.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_progs.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_registry.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_settings_saved.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_update.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_dug/dug_wcstatus.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_introduction.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_preface.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_repository/checkout_links.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_repository/repository.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_repository/repository_backup.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_repository/repository_create.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_repository/repository_hooks.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_server/server.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_server/server_apache.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_server/server_svn.xml [new file with mode: 0644]
doc/source/en/TortoiseSVN/tsvn_subwcrev.xml [new file with mode: 0644]
doc/source/en/Version.in [new file with mode: 0644]
doc/source/en/glossary.xml [new file with mode: 0644]
doc/source/en/wishlist.xml [new file with mode: 0644]
doc/source/styles_chm.css [new file with mode: 0644]
doc/source/styles_html.css [new file with mode: 0644]
doc/source/styles_site.css [new file with mode: 0644]
doc/templates/revisions_de.sxd [new file with mode: 0644]
doc/templates/revisions_en.sxd [new file with mode: 0644]
doc/templates/revisions_es.sxd [new file with mode: 0644]
doc/templates/revisions_ru.sxd [new file with mode: 0644]
doc/test/MakeTest.bat [new file with mode: 0644]
doc/test/footnote1.txt [new file with mode: 0644]
doc/test/footnote2.txt [new file with mode: 0644]
doc/test/footnote3.txt [new file with mode: 0644]
doc/test/subwcrev1.txt [new file with mode: 0644]
doc/test/subwcrev2.txt [new file with mode: 0644]
doc/test/subwcrev3.txt [new file with mode: 0644]
doc/xml2po-modes/docbook.py [new file with mode: 0644]
doc/xml2po-modes/empty.py [new file with mode: 0644]
doc/xml2po-modes/gs.py [new file with mode: 0644]
doc/xml2po.py [new file with mode: 0644]
doc/xsl/de/userconfig.template.xml [new file with mode: 0644]
doc/xsl/defaults.xsl [new file with mode: 0644]
doc/xsl/el/userconfig.template.xml [new file with mode: 0644]
doc/xsl/en/userconfig.template.xml [new file with mode: 0644]
doc/xsl/es/userconfig.template.xml [new file with mode: 0644]
doc/xsl/fa/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/fa/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/fa/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/fa/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/fa/userconfig.template.xml [new file with mode: 0644]
doc/xsl/fi/userconfig.template.xml [new file with mode: 0644]
doc/xsl/fonts/arial.xml [new file with mode: 0644]
doc/xsl/fonts/arialbd.xml [new file with mode: 0644]
doc/xsl/fonts/arialbi.xml [new file with mode: 0644]
doc/xsl/fonts/ariali.xml [new file with mode: 0644]
doc/xsl/fonts/cour.xml [new file with mode: 0644]
doc/xsl/fonts/courbd.xml [new file with mode: 0644]
doc/xsl/fonts/courbi.xml [new file with mode: 0644]
doc/xsl/fonts/couri.xml [new file with mode: 0644]
doc/xsl/fonts/iqraa.xml [new file with mode: 0644]
doc/xsl/fonts/msgothic.xml [new file with mode: 0644]
doc/xsl/fonts/msmincho.xml [new file with mode: 0644]
doc/xsl/fonts/msyh.xml [new file with mode: 0644]
doc/xsl/fonts/msyhbd.xml [new file with mode: 0644]
doc/xsl/fonts/simhei.xml [new file with mode: 0644]
doc/xsl/fonts/simsun.xml [new file with mode: 0644]
doc/xsl/fonts/times.xml [new file with mode: 0644]
doc/xsl/fonts/timesbd.xml [new file with mode: 0644]
doc/xsl/fonts/timesbi.xml [new file with mode: 0644]
doc/xsl/fonts/timesi.xml [new file with mode: 0644]
doc/xsl/fr/userconfig.template.xml [new file with mode: 0644]
doc/xsl/hr/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/hr/htmldefaults.xsl [new file with mode: 0644]
doc/xsl/hr/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/hr/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/hr/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/hr/userconfig.template.xml [new file with mode: 0644]
doc/xsl/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/id/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/id/userconfig.template.xml [new file with mode: 0644]
doc/xsl/ja/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/ja/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/ja/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/ja/lang.build [new file with mode: 0644]
doc/xsl/ja/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/ja/userconfig.template.xml [new file with mode: 0644]
doc/xsl/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/profile-mode.xsl [new file with mode: 0644]
doc/xsl/profile.xsl [new file with mode: 0644]
doc/xsl/ru/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/ru/htmldefaults.xsl [new file with mode: 0644]
doc/xsl/ru/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/ru/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/ru/lang.build [new file with mode: 0644]
doc/xsl/ru/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/ru/userconfig.template.xml [new file with mode: 0644]
doc/xsl/sk/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/sk/htmldefaults.xsl [new file with mode: 0644]
doc/xsl/sk/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/sk/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/sk/userconfig.template.xml [new file with mode: 0644]
doc/xsl/sl/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/sl/htmldefaults.xsl [new file with mode: 0644]
doc/xsl/sl/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/sl/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/sl/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/sl/userconfig.template.xml [new file with mode: 0644]
doc/xsl/sr_spc/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/sr_spc/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/sr_spc/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/sr_spc/lang.build [new file with mode: 0644]
doc/xsl/sr_spc/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/sr_spc/userconfig.template.xml [new file with mode: 0644]
doc/xsl/sr_spl/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/sr_spl/htmldefaults.xsl [new file with mode: 0644]
doc/xsl/sr_spl/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/sr_spl/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/sr_spl/lang.build [new file with mode: 0644]
doc/xsl/sr_spl/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/sr_spl/userconfig.template.xml [new file with mode: 0644]
doc/xsl/zh_CN/htmlchunk.xsl [new file with mode: 0644]
doc/xsl/zh_CN/htmlhelp.xsl [new file with mode: 0644]
doc/xsl/zh_CN/htmlsingle.xsl [new file with mode: 0644]
doc/xsl/zh_CN/lang.build [new file with mode: 0644]
doc/xsl/zh_CN/pdfdoc.xsl [new file with mode: 0644]
doc/xsl/zh_CN/userconfig.template.xml [new file with mode: 0644]

diff --git a/doc/API/Doxyfile b/doc/API/Doxyfile
new file mode 100644 (file)
index 0000000..e62e63a
--- /dev/null
@@ -0,0 +1,1144 @@
+# Doxyfile 1.3.5\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored\r
+# The format is:\r
+#       TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+#       TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ")\r
+\r
+#---------------------------------------------------------------------------\r
+# Project related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded \r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME           = TortoiseSVN\r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number. \r
+# This could be handy for archiving the generated documentation or \r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER         = $LastChangedRevision: 10696 $\r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) \r
+# base path where the generated documentation will be put. \r
+# If a relative path is entered, it will be relative to the location \r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY       = output\doxygen\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all \r
+# documentation generated by doxygen is written. Doxygen will use this \r
+# information to generate all constant output in the proper language. \r
+# The default language is English, other supported languages are: \r
+# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, \r
+# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en \r
+# (Japanese with English messages), Korean, Norwegian, Polish, Portuguese, \r
+# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.\r
+\r
+OUTPUT_LANGUAGE        = English\r
+\r
+# This tag can be used to specify the encoding used in the generated output. \r
+# The encoding is not always determined by the language that is chosen, \r
+# but also whether or not the output is meant for Windows or non-Windows users. \r
+# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES \r
+# forces the Windows encoding (this is the default for the Windows binary), \r
+# whereas setting the tag to NO uses a Unix-style encoding (the default for \r
+# all platforms other than Windows).\r
+\r
+USE_WINDOWS_ENCODING   = YES\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will \r
+# include brief member descriptions after the members that are listed in \r
+# the file and class documentation (similar to JavaDoc). \r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC      = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend \r
+# the brief description of a member or function before the detailed description. \r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the \r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF           = YES\r
+\r
+# This tag implements a quasi-intelligent brief description abbreviator \r
+# that is used to form the text in various listings. Each string \r
+# in this list, if found as the leading text of the brief description, will be \r
+# stripped from the text and the result after processing the whole list, is used \r
+# as the annotated text. Otherwise, the brief description is used as-is. If left \r
+# blank, the following values are used ("$name" is automatically replaced with the \r
+# name of the entity): "The $name class" "The $name widget" "The $name file" \r
+# "is" "provides" "specifies" "contains" "represents" "a" "an" "the"\r
+\r
+ABBREVIATE_BRIEF       = \r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then \r
+# Doxygen will generate a detailed section even if there is only a brief \r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC    = NO\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited \r
+# members of a class in the documentation of that class as if those members were \r
+# ordinary class members. Constructors, destructors and assignment operators of \r
+# the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB  = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full \r
+# path before files name in the file list and in the header files. If set \r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES        = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag \r
+# can be used to strip a user-defined part of the path. Stripping is \r
+# only done if one of the specified strings matches the left-hand part of \r
+# the path. It is allowed to use relative paths in the argument list.\r
+\r
+STRIP_FROM_PATH        = \r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter \r
+# (but less readable) file names. This can be useful is your file systems \r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES            = NO\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen \r
+# will interpret the first line (until the first dot) of a JavaDoc-style \r
+# comment as the brief description. If set to NO, the JavaDoc \r
+# comments will behave just like the Qt-style comments (thus requiring an \r
+# explicit @brief command for a brief description.\r
+\r
+JAVADOC_AUTOBRIEF      = NO\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen \r
+# treat a multi-line C++ special comment block (i.e. a block of //! or /// \r
+# comments) as a brief description. This used to be the default behaviour. \r
+# The new default is to treat a multi-line C++ comment block as a detailed \r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the DETAILS_AT_TOP tag is set to YES then Doxygen \r
+# will output the detailed description near the top, like JavaDoc.\r
+# If set to NO, the detailed description appears after the member \r
+# documentation.\r
+\r
+DETAILS_AT_TOP         = YES\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented \r
+# member inherits the documentation from any documented member that it \r
+# re-implements.\r
+\r
+INHERIT_DOCS           = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC \r
+# tag is set to YES, then doxygen will reuse the documentation of the first \r
+# member in the group (if any) for the other members of the group. By default \r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC   = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab. \r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE               = 4\r
+\r
+# This tag can be used to specify a number of aliases that acts \r
+# as commands in the documentation. An alias has the form "name=value". \r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to \r
+# put the command \sideeffect (or @sideeffect) in the documentation, which \r
+# will result in a user-defined paragraph with heading "Side Effects:". \r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES                = \r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources \r
+# only. Doxygen will then generate output that is more tailored for C. \r
+# For instance, some of the names that are used will be different. The list \r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C  = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources \r
+# only. Doxygen will then generate output that is more tailored for Java. \r
+# For instance, namespaces will be presented as packages, qualified scopes \r
+# will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA   = NO\r
+\r
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of \r
+# the same type (for instance a group of public functions) to be put as a \r
+# subgroup of that type (e.g. under the Public Functions section). Set it to \r
+# NO to prevent subgrouping. Alternatively, this can be done per class using \r
+# the \nosubgrouping command.\r
+\r
+SUBGROUPING            = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Build related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in \r
+# documentation are documented, even if no documentation was available. \r
+# Private class members and static file members will be hidden unless \r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL            = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class \r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE        = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file \r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC         = NO\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) \r
+# defined locally in source files will be included in the documentation. \r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES  = YES\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all \r
+# undocumented members of documented classes, files or namespaces. \r
+# If set to NO (the default) these members will be included in the \r
+# various overviews, but no documentation section is generated. \r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS     = NO\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all \r
+# undocumented classes that are normally visible in the class hierarchy. \r
+# If set to NO (the default) these classes will be included in the various \r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES     = NO\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all \r
+# friend (class|struct|union) declarations. \r
+# If set to NO (the default) these declarations will be included in the \r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS  = NO\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any \r
+# documentation blocks found inside the body of a function. \r
+# If set to NO (the default) these blocks will be appended to the \r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS      = NO\r
+\r
+# The INTERNAL_DOCS tag determines if documentation \r
+# that is typed after a \internal command is included. If the tag is set \r
+# to NO (the default) then the documentation will be excluded. \r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS          = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate \r
+# file names in lower-case letters. If set to YES upper-case letters are also \r
+# allowed. This is useful if you have classes or files whose names only differ \r
+# in case and if your file system supports case sensitive file names. Windows \r
+# users are advised to set this option to NO.\r
+\r
+CASE_SENSE_NAMES       = YES\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen \r
+# will show members with their full class and namespace scopes in the \r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES       = NO\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen \r
+# will put a list of the files that are included by a file in the documentation \r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES     = YES\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] \r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO            = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen \r
+# will sort the (detailed) documentation of file and class members \r
+# alphabetically by member name. If set to NO the members will appear in \r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS       = YES\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or \r
+# disable (NO) the todo list. This list is created by putting \todo \r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST      = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or \r
+# disable (NO) the test list. This list is created by putting \test \r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST      = NO\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or \r
+# disable (NO) the bug list. This list is created by putting \bug \r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST       = YES\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or \r
+# disable (NO) the deprecated list. This list is created by putting \r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= NO\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional \r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS       = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines \r
+# the initial value of a variable or define consists of for it to appear in \r
+# the documentation. If the initializer consists of more lines than specified \r
+# here it will be hidden. Use a value of 0 to hide initializers completely. \r
+# The appearance of the initializer of individual variables and defines in the \r
+# documentation can be controlled using \showinitializer or \hideinitializer \r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES  = 30\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated \r
+# at the bottom of the documentation of classes and structs. If set to YES the \r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES        = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated \r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET                  = YES\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are \r
+# generated by doxygen. Possible values are YES and NO. If left blank \r
+# NO is used.\r
+\r
+WARNINGS               = NO\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings \r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will \r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED   = NO\r
+\r
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for \r
+# potential errors in the documentation, such as not documenting some \r
+# parameters in a documented function, or documenting parameters that \r
+# don't exist or using markup commands wrongly.\r
+\r
+WARN_IF_DOC_ERROR      = NO\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that \r
+# doxygen can produce. The string should contain the $file, $line, and $text \r
+# tags, which will be replaced by the file and line number from which the \r
+# warning originated and the warning text.\r
+\r
+WARN_FORMAT            = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning \r
+# and error messages should be written. If left blank the output is written \r
+# to stderr.\r
+\r
+WARN_LOGFILE           = \r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain \r
+# documented source files. You may enter file names like "myfile.cpp" or \r
+# directories like "/usr/src/myproject". Separate the files or directories \r
+# with spaces.\r
+\r
+INPUT                  = ..\src ..\build.txt\r
+\r
+# If the value of the INPUT tag contains directories, you can use the \r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \r
+# and *.h) to filter out the source-files in the directories. If left \r
+# blank the following patterns are tested: \r
+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp \r
+# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc\r
+\r
+FILE_PATTERNS          = \r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories \r
+# should be searched for input files as well. Possible values are YES and NO. \r
+# If left blank NO is used.\r
+\r
+RECURSIVE              = YES\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should \r
+# excluded from the INPUT source files. This way you can easily exclude a \r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE                = ..\src\TortoisePlink ..\ext ..\src\Utils\hunspell ..\src\Utils\NewMenu ..\src\Utils\scintilla ..\src\Utils\TreePropSheet\r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories \r
+# that are symbolic links (a Unix filesystem feature) are excluded from the input.\r
+\r
+EXCLUDE_SYMLINKS       = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the \r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude \r
+# certain files from those directories.\r
+\r
+EXCLUDE_PATTERNS       = \r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or \r
+# directories that contain example code fragments that are included (see \r
+# the \include command).\r
+\r
+EXAMPLE_PATH           = \r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the \r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \r
+# and *.h) to filter out the source-files in the directories. If left \r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS       = \r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be \r
+# searched for input files to be used with the \include or \dontinclude \r
+# commands irrespective of the value of the RECURSIVE tag. \r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE      = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or \r
+# directories that contain image that are included in the documentation (see \r
+# the \image command).\r
+\r
+IMAGE_PATH             = ..\src ..\src\Utils ..\src\Utils\MiscUI\r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should \r
+# invoke to filter for each input file. Doxygen will invoke the filter program \r
+# by executing (via popen()) the command <filter> <input-file>, where <filter> \r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an \r
+# input file. Doxygen will then use the output that the filter program writes \r
+# to standard output.\r
+\r
+INPUT_FILTER           = \r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using \r
+# INPUT_FILTER) will be used to filter the input files when producing source \r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES    = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will \r
+# be generated. Documented entities will be cross-referenced with these sources. \r
+# Note: To get rid of all source code in the generated output, make sure also \r
+# VERBATIM_HEADERS is set to NO.\r
+\r
+SOURCE_BROWSER         = NO\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body \r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES         = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct \r
+# doxygen to hide any special comment blocks from generated source code \r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS    = YES\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES (the default) \r
+# then for each documented function all documented \r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = YES\r
+\r
+# If the REFERENCES_RELATION tag is set to YES (the default) \r
+# then for each documented function all documented entities \r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION    = YES\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen \r
+# will generate a verbatim copy of the header file for each class for \r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS       = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index \r
+# of all compounds will be generated. Enable this if the project \r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX     = YES\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then \r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns \r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX    = 5\r
+\r
+# In case all classes in a project start with a common prefix, all \r
+# classes will be put under the same header in the alphabetical index. \r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that \r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX          = C\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will \r
+# generate HTML output.\r
+\r
+GENERATE_HTML          = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT            = html\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for \r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank \r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION    = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for \r
+# each generated HTML page. If it is left blank doxygen will generate a \r
+# standard header.\r
+\r
+HTML_HEADER            = \r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for \r
+# each generated HTML page. If it is left blank doxygen will generate a \r
+# standard footer.\r
+\r
+HTML_FOOTER            = \r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading \r
+# style sheet that is used by each HTML page. It can be used to \r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen \r
+# will generate a default style sheet. Note that doxygen will try to copy \r
+# the style sheet file to the HTML output directory, so don't put your own \r
+# stylesheet in the HTML output directory as well, or it will be erased!\r
+\r
+HTML_STYLESHEET        = \r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, \r
+# files or namespaces will be aligned in HTML using tables. If set to \r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS     = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files \r
+# will be generated that can be used as input for tools like the \r
+# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) \r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP      = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can \r
+# be used to specify the file name of the resulting .chm file. You \r
+# can add a path in front of the file if the result should not be \r
+# written to the html output directory.\r
+\r
+CHM_FILE               = TortoiseAPI.chm\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag \r
+# controls if a separate .chi index file is generated (YES) or that \r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI           = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag \r
+# controls whether a binary table of contents is generated (YES) or a \r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC             = NO\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members \r
+# to the contents of the HTML help documentation and to the tree view.\r
+\r
+TOC_EXPAND             = NO\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at \r
+# top of each HTML page. The value NO (the default) enables the index and \r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX          = NO\r
+\r
+# This tag can be used to set the number of enum values (range [1..20]) \r
+# that doxygen will group on one line in the generated HTML documentation.\r
+\r
+ENUM_VALUES_PER_LINE   = 4\r
+\r
+# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be\r
+# generated containing a tree-like index structure (just like the one that \r
+# is generated for HTML Help). For this to work a browser that supports \r
+# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, \r
+# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are \r
+# probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW      = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be \r
+# used to set the initial width (in pixels) of the frame in which the tree \r
+# is shown.\r
+\r
+TREEVIEW_WIDTH         = 250\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will \r
+# generate Latex output.\r
+\r
+GENERATE_LATEX         = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT           = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be \r
+# invoked. If left blank `latex' will be used as the default command name.\r
+\r
+LATEX_CMD_NAME         = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to \r
+# generate index for LaTeX. If left blank `makeindex' will be used as the \r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME     = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact \r
+# LaTeX documents. This may be useful for small projects and may help to \r
+# save some trees in general.\r
+\r
+COMPACT_LATEX          = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used \r
+# by the printer. Possible values are: a4, a4wide, letter, legal and \r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE             = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX \r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES         = \r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for \r
+# the generated latex document. The header should contain everything until \r
+# the first chapter. If it is left blank doxygen will generate a \r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER           = \r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated \r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will \r
+# contain links (just like the HTML output) instead of page references \r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS         = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of \r
+# plain latex in the generated Makefile. Set this option to YES to get a \r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX           = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. \r
+# command to the generated LaTeX files. This will instruct LaTeX to keep \r
+# running if errors occur, instead of asking the user for help. \r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE        = NO\r
+\r
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not \r
+# include the index chapters (such as File Index, Compound Index, etc.) \r
+# in the output.\r
+\r
+LATEX_HIDE_INDICES     = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output \r
+# The RTF output is optimized for Word 97 and may not look very pretty with \r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF           = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT             = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact \r
+# RTF documents. This may be useful for small projects and may help to \r
+# save some trees in general.\r
+\r
+COMPACT_RTF            = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated \r
+# will contain hyperlink fields. The RTF file will \r
+# contain links (just like the HTML output) instead of page references. \r
+# This makes the output suitable for online browsing using WORD or other \r
+# programs which support those fields. \r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS         = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's \r
+# config file, i.e. a series of assignments. You only have to provide \r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE    = \r
+\r
+# Set optional variables used in the generation of an rtf document. \r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE    = \r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will \r
+# generate man pages\r
+\r
+GENERATE_MAN           = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT             = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to \r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION          = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, \r
+# then it will generate one additional man file for each entity \r
+# documented in the real man page(s). These additional files \r
+# only source the real man page, but without them the man command \r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS              = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will \r
+# generate an XML file that captures the structure of \r
+# the code including all documentation.\r
+\r
+GENERATE_XML           = NO\r
+\r
+# The XML_OUTPUT tag is used to specify where the XML pages will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `xml' will be used as the default path.\r
+\r
+XML_OUTPUT             = xml\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema, \r
+# which can be used by a validating XML parser to check the \r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA             = \r
+\r
+# The XML_DTD tag can be used to specify an XML DTD, \r
+# which can be used by a validating XML parser to check the \r
+# syntax of the XML files.\r
+\r
+XML_DTD                = \r
+\r
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will \r
+# dump the program listings (including syntax highlighting \r
+# and cross-referencing information) to the XML output. Note that \r
+# enabling this will significantly increase the size of the XML output.\r
+\r
+XML_PROGRAMLISTING     = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will \r
+# generate an AutoGen Definitions (see autogen.sf.net) file \r
+# that captures the structure of the code including all \r
+# documentation. Note that this feature is still experimental \r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF   = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will \r
+# generate a Perl module file that captures the structure of \r
+# the code including all documentation. Note that this \r
+# feature is still experimental and incomplete at the \r
+# moment.\r
+\r
+GENERATE_PERLMOD       = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate \r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able \r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX          = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be \r
+# nicely formatted so it can be parsed by a human reader.  This is useful \r
+# if you want to understand what is going on.  On the other hand, if this \r
+# tag is set to NO the size of the Perl module output will be much smaller \r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY         = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file \r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. \r
+# This is useful so different doxyrules.make files included by the same \r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX = \r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor   \r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will \r
+# evaluate all C-preprocessor directives found in the sources and include \r
+# files.\r
+\r
+ENABLE_PREPROCESSING   = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro \r
+# names in the source code. If set to NO (the default) only conditional \r
+# compilation will be performed. Macro expansion can be done in a controlled \r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION        = NO\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES \r
+# then the macro expansion is limited to the macros specified with the \r
+# PREDEFINED and EXPAND_AS_PREDEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF     = NO\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files \r
+# in the INCLUDE_PATH (see below) will be search if a #include is found.\r
+\r
+SEARCH_INCLUDES        = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that \r
+# contain include files that are not input files but should be processed by \r
+# the preprocessor.\r
+\r
+INCLUDE_PATH           = \r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard \r
+# patterns (like *.h and *.hpp) to filter out the header-files in the \r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will \r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS  = \r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that \r
+# are defined before the preprocessor is started (similar to the -D option of \r
+# gcc). The argument of the tag is a list of macros of the form: name \r
+# or name=definition (no spaces). If the definition and the = are \r
+# omitted =1 is assumed.\r
+\r
+PREDEFINED             = "DECLARE_INTERFACE(name)=class name" \\r
+"STDMETHOD(result,name)=virtual result name" \\r
+"PURE= = 0" \\r
+THIS_= \\r
+THIS= \\r
+DECLARE_REGISTRY_RESOURCEID=// \\r
+DECLARE_PROTECT_FINAL_CONSTRUCT=// \\r
+"DECLARE_AGGREGATABLE(Class)= " \\r
+"DECLARE_REGISTRY_RESOURCEID(Id)= " \\r
+DECLARE_MESSAGE_MAP = \\r
+BEGIN_MESSAGE_MAP=/* \\r
+END_MESSAGE_MAP=*/// \\r
+BEGIN_COM_MAP=/* \\r
+END_COM_MAP=*/// \\r
+BEGIN_PROP_MAP=/* \\r
+END_PROP_MAP=*/// \\r
+BEGIN_MSG_MAP=/* \\r
+END_MSG_MAP=*/// \\r
+BEGIN_PROPERTY_MAP=/* \\r
+END_PROPERTY_MAP=*/// \\r
+BEGIN_OBJECT_MAP=/* \\r
+END_OBJECT_MAP()=*/// \\r
+DECLARE_VIEW_STATUS=// \\r
+"STDMETHOD(a)=HRESULT a" \\r
+"ATL_NO_VTABLE= " \\r
+"__declspec(a)= " \\r
+BEGIN_CONNECTION_POINT_MAP=/* \\r
+END_CONNECTION_POINT_MAP=*/// \\r
+"DECLARE_DYNAMIC(class)= " \\r
+"IMPLEMENT_DYNAMIC(class1, class2)= " \\r
+"DECLARE_DYNCREATE(class)= " \\r
+"IMPLEMENT_DYNCREATE(class1, class2)= " \\r
+"IMPLEMENT_SERIAL(class1, class2, class3)= " \\r
+"DECLARE_MESSAGE_MAP()= " \\r
+TRY=try \\r
+"CATCH_ALL(e)= catch(...)" \\r
+END_CATCH_ALL= \\r
+"THROW_LAST()= throw"\\r
+"RUNTIME_CLASS(class)=class" \\r
+"MAKEINTRESOURCE(nId)=nId" \\r
+"IMPLEMENT_REGISTER(v, w, x, y, z)= " \\r
+"ASSERT(x)=assert(x)" \\r
+"ASSERT_VALID(x)=assert(x)" \\r
+"TRACE0(x)=printf(x)" \\r
+"OS_ERR(A,B)={ #A, B }" \\r
+__cplusplus \\r
+"DECLARE_OLECREATE(class)= " \\r
+"BEGIN_DISPATCH_MAP(class1, class2)= " \\r
+"INTERFACE_PART(class, id, name)= " \\r
+"END_INTERFACE_MAP()=" \\r
+"DISP_FUNCTION(class, name, function, result, id)=" \\r
+"END_DISPATCH_MAP()=" \\r
+"IMPLEMENT_OLECREATE2(class, name, id1, id2, id3, id4, id5, id6, id7, id8, id9, id10, id11)="\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then \r
+# this tag can be used to specify a list of macro names that should be expanded. \r
+# The macro definition that is found in the sources will be used. \r
+# Use the PREDEFINED tag if you want to use a different macro definition.\r
+\r
+EXPAND_AS_DEFINED      = \r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then \r
+# doxygen's preprocessor will remove all function-like macros that are alone \r
+# on a line, have an all uppercase name, and do not end with a semicolon. Such \r
+# function macros are typically used for boiler-plate code, and will confuse the \r
+# parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS   = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::addtions related to external references   \r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES option can be used to specify one or more tagfiles. \r
+# Optionally an initial location of the external documentation \r
+# can be added for each tagfile. The format of a tag file without \r
+# this location is as follows: \r
+#   TAGFILES = file1 file2 ... \r
+# Adding location for the tag files is done as follows: \r
+#   TAGFILES = file1=loc1 "file2 = loc2" ... \r
+# where "loc1" and "loc2" can be relative or absolute paths or \r
+# URLs. If a location is present for each tag, the installdox tool \r
+# does not have to be run to correct the links.\r
+# Note that each tag file must have a unique name\r
+# (where the name does NOT include the path)\r
+# If a tag file is not located in the directory in which doxygen \r
+# is run, you must also specify the path to the tagfile here.\r
+\r
+TAGFILES               = \r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create \r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE       = \r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed \r
+# in the class index. If set to NO only the inherited external classes \r
+# will be listed.\r
+\r
+ALLEXTERNALS           = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed \r
+# in the modules index. If set to NO, only the current project's groups will \r
+# be listed.\r
+\r
+EXTERNAL_GROUPS        = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script \r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH              = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool   \r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will \r
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or \r
+# super classes. Setting the tag to NO turns the diagrams off. Note that this \r
+# option is superseded by the HAVE_DOT option below. This is only a fallback. It is \r
+# recommended to install and use dot, since it yields more powerful graphs.\r
+\r
+CLASS_DIAGRAMS         = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide \r
+# inheritance and usage relations if the target is undocumented \r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS   = NO\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is \r
+# available from the path. This tool is part of Graphviz, a graph visualization \r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section \r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT               = YES\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen \r
+# will generate a graph for each documented class showing the direct and \r
+# indirect inheritance relations. Setting this tag to YES will force the \r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH            = NO\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen \r
+# will generate a graph for each documented class showing the direct and \r
+# indirect implementation dependencies (inheritance, containment, and \r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH    = YES\r
+\r
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and \r
+# collaboration diagrams in a style similar to the OMG's Unified Modeling \r
+# Language.\r
+\r
+UML_LOOK               = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the \r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS     = NO\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT \r
+# tags are set to YES then doxygen will generate a graph for each documented \r
+# file showing the direct and indirect include dependencies of the file with \r
+# other documented files.\r
+\r
+INCLUDE_GRAPH          = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and \r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each \r
+# documented header file showing the documented files that directly or \r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH      = YES\r
+\r
+# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will \r
+# generate a call dependency graph for every global function or class method. \r
+# Note that enabling this option will significantly increase the time of a run. \r
+# So in most cases it will be better to enable call graphs for selected \r
+# functions only using the \callgraph command.\r
+\r
+CALL_GRAPH             = NO\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen \r
+# will graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY    = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images \r
+# generated by dot. Possible values are png, jpg, or gif\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT       = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be \r
+# found. If left blank, it is assumed the dot tool can be found on the path.\r
+\r
+DOT_PATH               = \r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that \r
+# contain dot files that are included in the documentation (see the \r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS           = \r
+\r
+# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width \r
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than \r
+# this value, doxygen will try to truncate the graph, so that it fits within \r
+# the specified constraint. Beware that most browsers cannot cope with very \r
+# large images.\r
+\r
+MAX_DOT_GRAPH_WIDTH    = 1024\r
+\r
+# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height \r
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than \r
+# this value, doxygen will try to truncate the graph, so that it fits within \r
+# the specified constraint. Beware that most browsers cannot cope with very \r
+# large images.\r
+\r
+MAX_DOT_GRAPH_HEIGHT   = 1024\r
+\r
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the \r
+# graphs generated by dot. A depth value of 3 means that only nodes reachable \r
+# from the root by following a path via at most 3 edges will be shown. Nodes that \r
+# lay further from the root node will be omitted. Note that setting this option to \r
+# 1 or 2 may greatly reduce the computation time needed for large code bases. Also \r
+# note that a graph may be further truncated if the graph's image dimensions are \r
+# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). \r
+# If 0 is used for the depth value (the default), the graph is not depth-constrained.\r
+\r
+MAX_DOT_GRAPH_DEPTH    = 0\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will \r
+# generate a legend page explaining the meaning of the various boxes and \r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND        = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will \r
+# remove the intermediate dot files that are used to generate \r
+# the various graphs.\r
+\r
+DOT_CLEANUP            = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::addtions related to the search engine   \r
+#---------------------------------------------------------------------------\r
+\r
+# The SEARCHENGINE tag specifies whether or not a search engine should be \r
+# used. If set to NO the values of all tags below this one will be ignored.\r
+\r
+SEARCHENGINE           = NO\r
+\r
diff --git a/doc/API/DoxyfileSVN b/doc/API/DoxyfileSVN
new file mode 100644 (file)
index 0000000..fde1b85
--- /dev/null
@@ -0,0 +1,1029 @@
+# Doxyfile 1.3-rc1\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored\r
+# The format is:\r
+#       TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+#       TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ")\r
+\r
+#---------------------------------------------------------------------------\r
+# General configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded \r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME           = Subversion\r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number. \r
+# This could be handy for archiving the generated documentation or \r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER         = \r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) \r
+# base path where the generated documentation will be put. \r
+# If a relative path is entered, it will be relative to the location \r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY       = output/doxygen\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all \r
+# documentation generated by doxygen is written. Doxygen will use this \r
+# information to generate all constant output in the proper language. \r
+# The default language is English, other supported languages are: \r
+# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, \r
+# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en \r
+# (Japanese with english messages), Korean, Norwegian, Polish, Portuguese, \r
+# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish and Ukrainian.\r
+\r
+OUTPUT_LANGUAGE        = English\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in \r
+# documentation are documented, even if no documentation was available. \r
+# Private class members and static file members will be hidden unless \r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL            = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class \r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE        = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file \r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC         = NO\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) \r
+# defined locally in source files will be included in the documentation. \r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES  = YES\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all \r
+# undocumented members of documented classes, files or namespaces. \r
+# If set to NO (the default) these members will be included in the \r
+# various overviews, but no documentation section is generated. \r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS     = NO\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all \r
+# undocumented classes that are normally visible in the class hierarchy. \r
+# If set to NO (the default) these class will be included in the various \r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES     = NO\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all \r
+# friend (class|struct|union) declarations. \r
+# If set to NO (the default) these declarations will be included in the \r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS  = NO\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any \r
+# documentation blocks found inside the body of a function. \r
+# If set to NO (the default) these blocks will be appended to the \r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS      = NO\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will \r
+# include brief member descriptions after the members that are listed in \r
+# the file and class documentation (similar to JavaDoc). \r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC      = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend \r
+# the brief description of a member or function before the detailed description. \r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the \r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF           = YES\r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then \r
+# Doxygen will generate a detailed section even if there is only a brief \r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC    = NO\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited \r
+# members of a class in the documentation of that class as if those members were \r
+# ordinary class members. Constructors, destructors and assignment operators of \r
+# the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB  = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full \r
+# path before files name in the file list and in the header files. If set \r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES        = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag \r
+# can be used to strip a user defined part of the path. Stripping is \r
+# only done if one of the specified strings matches the left-hand part of \r
+# the path. It is allowed to use relative paths in the argument list.\r
+\r
+STRIP_FROM_PATH        = \r
+\r
+# The INTERNAL_DOCS tag determines if documentation \r
+# that is typed after a \internal command is included. If the tag is set \r
+# to NO (the default) then the documentation will be excluded. \r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS          = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate \r
+# file names in lower case letters. If set to YES upper case letters are also \r
+# allowed. This is useful if you have classes or files whose names only differ \r
+# in case and if your file system supports case sensitive file names. Windows \r
+# users are adviced to set this option to NO.\r
+\r
+CASE_SENSE_NAMES       = YES\r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter \r
+# (but less readable) file names. This can be useful is your file systems \r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES            = NO\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen \r
+# will show members with their full class and namespace scopes in the \r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES       = NO\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen \r
+# will generate a verbatim copy of the header file for each class for \r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS       = YES\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen \r
+# will put list of the files that are included by a file in the documentation \r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES     = YES\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen \r
+# will interpret the first line (until the first dot) of a JavaDoc-style \r
+# comment as the brief description. If set to NO, the JavaDoc \r
+# comments  will behave just like the Qt-style comments (thus requiring an \r
+# explict @brief command for a brief description.\r
+\r
+JAVADOC_AUTOBRIEF      = YES\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen \r
+# treat a multi-line C++ special comment block (i.e. a block of //! or /// \r
+# comments) as a brief description. This used to be the default behaviour. \r
+# The new default is to treat a multi-line C++ comment block as a detailed \r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the DETAILS_AT_TOP tag is set to YES then Doxygen \r
+# will output the detailed description near the top, like JavaDoc.\r
+# If set to NO, the detailed description appears after the member \r
+# documentation.\r
+\r
+DETAILS_AT_TOP         = NO\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented \r
+# member inherits the documentation from any documented member that it \r
+# reimplements.\r
+\r
+INHERIT_DOCS           = YES\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] \r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO            = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen \r
+# will sort the (detailed) documentation of file and class members \r
+# alphabetically by member name. If set to NO the members will appear in \r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS       = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC \r
+# tag is set to YES, then doxygen will reuse the documentation of the first \r
+# member in the group (if any) for the other members of the group. By default \r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC   = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab. \r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE               = 8\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or \r
+# disable (NO) the todo list. This list is created by putting \todo \r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST      = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or \r
+# disable (NO) the test list. This list is created by putting \test \r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST      = YES\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or \r
+# disable (NO) the bug list. This list is created by putting \bug \r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST       = YES\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or \r
+# disable (NO) the deprecated list. This list is created by putting \r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= YES\r
+\r
+# This tag can be used to specify a number of aliases that acts \r
+# as commands in the documentation. An alias has the form "name=value". \r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to \r
+# put the command \sideeffect (or @sideeffect) in the documentation, which \r
+# will result in a user defined paragraph with heading "Side Effects:". \r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES                = "copyright=@if copyrights" \\r
+                         "endcopyright=@endif"\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional \r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS       = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines \r
+# the initial value of a variable or define consist of for it to appear in \r
+# the documentation. If the initializer consists of more lines than specified \r
+# here it will be hidden. Use a value of 0 to hide initializers completely. \r
+# The appearance of the initializer of individual variables and defines in the \r
+# documentation can be controlled using \showinitializer or \hideinitializer \r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES  = 30\r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources \r
+# only. Doxygen will then generate output that is more tailored for C. \r
+# For instance some of the names that are used will be different. The list \r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C  = YES\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources \r
+# only. Doxygen will then generate output that is more tailored for Java. \r
+# For instance namespaces will be presented as packages, qualified scopes \r
+# will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA   = NO\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated \r
+# at the bottom of the documentation of classes and structs. If set to YES the \r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES        = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated \r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET                  = NO\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are \r
+# generated by doxygen. Possible values are YES and NO. If left blank \r
+# NO is used.\r
+\r
+WARNINGS               = YES\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings \r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will \r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED   = YES\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that \r
+# doxygen can produce. The string should contain the $file, $line, and $text \r
+# tags, which will be replaced by the file and line number from which the \r
+# warning originated and the warning text.\r
+\r
+WARN_FORMAT            = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning \r
+# and error messages should be written. If left blank the output is written \r
+# to stderr.\r
+\r
+WARN_LOGFILE           = \r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain \r
+# documented source files. You may enter file names like "myfile.cpp" or \r
+# directories like "/usr/src/myproject". Separate the files or directories \r
+# with spaces.\r
+\r
+INPUT                  = ..\ext\Subversion\subversion/include\r
+\r
+# If the value of the INPUT tag contains directories, you can use the \r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \r
+# and *.h) to filter out the source-files in the directories. If left \r
+# blank the following patterns are tested: \r
+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp \r
+# *.h++ *.idl *.odl\r
+\r
+FILE_PATTERNS          = *.h\r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories \r
+# should be searched for input files as well. Possible values are YES and NO. \r
+# If left blank NO is used.\r
+\r
+RECURSIVE              = NO\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should \r
+# excluded from the INPUT source files. This way you can easily exclude a \r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE                = \r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories \r
+# that are symbolic links (a Unix filesystem feature) are excluded from the input.\r
+\r
+EXCLUDE_SYMLINKS       = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the \r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude \r
+# certain files from those directories.\r
+\r
+EXCLUDE_PATTERNS       = \r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or \r
+# directories that contain example code fragments that are included (see \r
+# the \include command).\r
+\r
+EXAMPLE_PATH           = \r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the \r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \r
+# and *.h) to filter out the source-files in the directories. If left \r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS       = \r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be \r
+# searched for input files to be used with the \include or \dontinclude \r
+# commands irrespective of the value of the RECURSIVE tag. \r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE      = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or \r
+# directories that contain image that are included in the documentation (see \r
+# the \image command).\r
+\r
+IMAGE_PATH             = \r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should \r
+# invoke to filter for each input file. Doxygen will invoke the filter program \r
+# by executing (via popen()) the command <filter> <input-file>, where <filter> \r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an \r
+# input file. Doxygen will then use the output that the filter program writes \r
+# to standard output.\r
+\r
+INPUT_FILTER           = \r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using \r
+# INPUT_FILTER) will be used to filter the input files when producing source \r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES    = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will \r
+# be generated. Documented entities will be cross-referenced with these sources.\r
+\r
+SOURCE_BROWSER         = YES\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body \r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES         = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct \r
+# doxygen to hide any special comment blocks from generated source code \r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS    = NO\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES (the default) \r
+# then for each documented function all documented \r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = YES\r
+\r
+# If the REFERENCES_RELATION tag is set to YES (the default) \r
+# then for each documented function all documented entities \r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION    = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index \r
+# of all compounds will be generated. Enable this if the project \r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX     = NO\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then \r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns \r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX    = 5\r
+\r
+# In case all classes in a project start with a common prefix, all \r
+# classes will be put under the same header in the alphabetical index. \r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that \r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX          = \r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will \r
+# generate HTML output.\r
+\r
+GENERATE_HTML          = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT            = html\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for \r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank \r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION    = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for \r
+# each generated HTML page. If it is left blank doxygen will generate a \r
+# standard header.\r
+\r
+HTML_HEADER            = \r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for \r
+# each generated HTML page. If it is left blank doxygen will generate a \r
+# standard footer.\r
+\r
+HTML_FOOTER            = \r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user defined cascading \r
+# style sheet that is used by each HTML page. It can be used to \r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen \r
+# will generate a default style sheet\r
+\r
+HTML_STYLESHEET        = \r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, \r
+# files or namespaces will be aligned in HTML using tables. If set to \r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS     = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files \r
+# will be generated that can be used as input for tools like the \r
+# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) \r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP      = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can \r
+# be used to specify the file name of the resulting .chm file. You \r
+# can add a path in front of the file if the result should not be \r
+# written to the html output dir.\r
+\r
+CHM_FILE               = SubversionAPI.chm\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag \r
+# controls if a separate .chi index file is generated (YES) or that \r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI           = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag \r
+# controls whether a binary table of contents is generated (YES) or a \r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC             = NO\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members \r
+# to the contents of the Html help documentation and to the tree view.\r
+\r
+TOC_EXPAND             = NO\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at \r
+# top of each HTML page. The value NO (the default) enables the index and \r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX          = NO\r
+\r
+# This tag can be used to set the number of enum values (range [1..20]) \r
+# that doxygen will group on one line in the generated HTML documentation.\r
+\r
+ENUM_VALUES_PER_LINE   = 1\r
+\r
+# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be\r
+# generated containing a tree-like index structure (just like the one that \r
+# is generated for HTML Help). For this to work a browser that supports \r
+# JavaScript and frames is required (for instance Mozilla, Netscape 4.0+, \r
+# or Internet explorer 4.0+). Note that for large projects the tree generation \r
+# can take a very long time. In such cases it is better to disable this feature. \r
+# Windows users are probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW      = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be \r
+# used to set the initial width (in pixels) of the frame in which the tree \r
+# is shown.\r
+\r
+TREEVIEW_WIDTH         = 250\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will \r
+# generate Latex output.\r
+\r
+GENERATE_LATEX         = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT           = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be \r
+# invoked. If left blank `latex' will be used as the default command name.\r
+\r
+LATEX_CMD_NAME         = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to \r
+# generate index for LaTeX. If left blank `makeindex' will be used as the \r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME     = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact \r
+# LaTeX documents. This may be useful for small projects and may help to \r
+# save some trees in general.\r
+\r
+COMPACT_LATEX          = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used \r
+# by the printer. Possible values are: a4, a4wide, letter, legal and \r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE             = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX \r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES         = \r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for \r
+# the generated latex document. The header should contain everything until \r
+# the first chapter. If it is left blank doxygen will generate a \r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER           = \r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated \r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will \r
+# contain links (just like the HTML output) instead of page references \r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS         = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of \r
+# plain latex in the generated Makefile. Set this option to YES to get a \r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX           = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. \r
+# command to the generated LaTeX files. This will instruct LaTeX to keep \r
+# running if errors occur, instead of asking the user for help. \r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE        = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output \r
+# The RTF output is optimised for Word 97 and may not look very pretty with \r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF           = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT             = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact \r
+# RTF documents. This may be useful for small projects and may help to \r
+# save some trees in general.\r
+\r
+COMPACT_RTF            = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated \r
+# will contain hyperlink fields. The RTF file will \r
+# contain links (just like the HTML output) instead of page references. \r
+# This makes the output suitable for online browsing using WORD or other \r
+# programs which support those fields. \r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS         = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's \r
+# config file, i.e. a series of assigments. You only have to provide \r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE    = \r
+\r
+# Set optional variables used in the generation of an rtf document. \r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE    = \r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will \r
+# generate man pages\r
+\r
+GENERATE_MAN           = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put. \r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be \r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT             = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to \r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION          = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, \r
+# then it will generate one additional man file for each entity \r
+# documented in the real man page(s). These additional files \r
+# only source the real man page, but without them the man command \r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS              = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will \r
+# generate an XML file that captures the structure of \r
+# the code including all documentation. Note that this \r
+# feature is still experimental and incomplete at the \r
+# moment.\r
+\r
+GENERATE_XML           = NO\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema, \r
+# which can be used by a validating XML parser to check the \r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA             = \r
+\r
+# The XML_DTD tag can be used to specify an XML DTD, \r
+# which can be used by a validating XML parser to check the \r
+# syntax of the XML files.\r
+\r
+XML_DTD                = \r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will \r
+# generate an AutoGen Definitions (see autogen.sf.net) file \r
+# that captures the structure of the code including all \r
+# documentation. Note that this feature is still experimental \r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF   = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will \r
+# generate a Perl module file that captures the structure of \r
+# the code including all documentation. Note that this \r
+# feature is still experimental and incomplete at the \r
+# moment.\r
+\r
+GENERATE_PERLMOD       = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate \r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able \r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX          = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be \r
+# nicely formatted so it can be parsed by a human reader.  This is useful \r
+# if you want to understand what is going on.  On the other hand, if this \r
+# tag is set to NO the size of the Perl module output will be much smaller \r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY         = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file \r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. \r
+# This is useful so different doxyrules.make files included by the same \r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX = \r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor   \r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will \r
+# evaluate all C-preprocessor directives found in the sources and include \r
+# files.\r
+\r
+ENABLE_PREPROCESSING   = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro \r
+# names in the source code. If set to NO (the default) only conditional \r
+# compilation will be performed. Macro expansion can be done in a controlled \r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION        = YES\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES \r
+# then the macro expansion is limited to the macros specified with the \r
+# PREDEFINED and EXPAND_AS_PREDEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF     = NO\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files \r
+# in the INCLUDE_PATH (see below) will be search if a #include is found.\r
+\r
+SEARCH_INCLUDES        = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that \r
+# contain include files that are not input files but should be processed by \r
+# the preprocessor.\r
+\r
+INCLUDE_PATH           = \r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard \r
+# patterns (like *.h and *.hpp) to filter out the header-files in the \r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will \r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS  = \r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that \r
+# are defined before the preprocessor is started (similar to the -D option of \r
+# gcc). The argument of the tag is a list of macros of the form: name \r
+# or name=definition (no spaces). If the definition and the = are \r
+# omitted =1 is assumed.\r
+\r
+PREDEFINED             = DOXYGEN_SHOULD_SKIP_THIS\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then \r
+# this tag can be used to specify a list of macro names that should be expanded. \r
+# The macro definition that is found in the sources will be used. \r
+# Use the PREDEFINED tag if you want to use a different macro definition.\r
+\r
+EXPAND_AS_DEFINED      = \r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then \r
+# doxygen's preprocessor will remove all function-like macros that are alone \r
+# on a line, have an all uppercase name, and do not end with a semicolon. Such \r
+# function macros are typically used for boiler-plate code, and will confuse the \r
+# parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS   = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::addtions related to external references   \r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES tag can be used to specify one or more tagfiles.\r
+\r
+TAGFILES               = \r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create \r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE       = \r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed \r
+# in the class index. If set to NO only the inherited external classes \r
+# will be listed.\r
+\r
+ALLEXTERNALS           = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed \r
+# in the modules index. If set to NO, only the current project's groups will \r
+# be listed.\r
+\r
+EXTERNAL_GROUPS        = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script \r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH              = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool   \r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will \r
+# generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or \r
+# super classes. Setting the tag to NO turns the diagrams off. Note that this \r
+# option is superceded by the HAVE_DOT option below. This is only a fallback. It is \r
+# recommended to install and use dot, since it yield more powerful graphs.\r
+\r
+CLASS_DIAGRAMS         = YES\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide \r
+# inheritance and usage relations if the target is undocumented \r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS   = YES\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is \r
+# available from the path. This tool is part of Graphviz, a graph visualization \r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section \r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT               = YES\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen \r
+# will generate a graph for each documented class showing the direct and \r
+# indirect inheritance relations. Setting this tag to YES will force the \r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH            = YES\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen \r
+# will generate a graph for each documented class showing the direct and \r
+# indirect implementation dependencies (inheritance, containment, and \r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH    = YES\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the \r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS     = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT \r
+# tags are set to YES then doxygen will generate a graph for each documented \r
+# file showing the direct and indirect include dependencies of the file with \r
+# other documented files.\r
+\r
+INCLUDE_GRAPH          = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and \r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each \r
+# documented header file showing the documented files that directly or \r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH      = YES\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen \r
+# will graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY    = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images \r
+# generated by dot. Possible values are png, jpg, or gif\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT       = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be \r
+# found. If left blank, it is assumed the dot tool can be found on the path.\r
+\r
+DOT_PATH               = \r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that \r
+# contain dot files that are included in the documentation (see the \r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS           = \r
+\r
+# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width \r
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than \r
+# this value, doxygen will try to truncate the graph, so that it fits within \r
+# the specified constraint. Beware that most browsers cannot cope with very \r
+# large images.\r
+\r
+MAX_DOT_GRAPH_WIDTH    = 1024\r
+\r
+# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height \r
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than \r
+# this value, doxygen will try to truncate the graph, so that it fits within \r
+# the specified constraint. Beware that most browsers cannot cope with very \r
+# large images.\r
+\r
+MAX_DOT_GRAPH_HEIGHT   = 1024\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will \r
+# generate a legend page explaining the meaning of the various boxes and \r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND        = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will \r
+# remove the intermedate dot files that are used to generate \r
+# the various graphs.\r
+\r
+DOT_CLEANUP            = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::addtions related to the search engine   \r
+#---------------------------------------------------------------------------\r
+\r
+# The SEARCHENGINE tag specifies whether or not a search engine should be \r
+# used. If set to NO the values of all tags below this one will be ignored.\r
+\r
+SEARCHENGINE           = NO\r
+\r
+# The CGI_NAME tag should be the name of the CGI script that \r
+# starts the search engine (doxysearch) with the correct parameters. \r
+# A script with this name will be generated by doxygen.\r
+\r
+CGI_NAME               = search.cgi\r
+\r
+# The CGI_URL tag should be the absolute URL to the directory where the \r
+# cgi binaries are located. See the documentation of your http daemon for \r
+# details.\r
+\r
+CGI_URL                = \r
+\r
+# The DOC_URL tag should be the absolute URL to the directory where the \r
+# documentation is located. If left blank the absolute path to the \r
+# documentation, with file:// prepended to it, will be used.\r
+\r
+DOC_URL                = \r
+\r
+# The DOC_ABSPATH tag should be the absolute path to the directory where the \r
+# documentation is located. If left blank the directory on the local machine \r
+# will be used.\r
+\r
+DOC_ABSPATH            = \r
+\r
+# The BIN_ABSPATH tag must point to the directory where the doxysearch binary \r
+# is installed.\r
+\r
+BIN_ABSPATH            = /usr/local/bin/\r
+\r
+# The EXT_DOC_PATHS tag can be used to specify one or more paths to \r
+# documentation generated for other projects. This allows doxysearch to search \r
+# the documentation for these projects as well.\r
+\r
+EXT_DOC_PATHS          = \r
diff --git a/doc/Aspell/Readme.txt b/doc/Aspell/Readme.txt
new file mode 100644 (file)
index 0000000..f59ceb1
--- /dev/null
@@ -0,0 +1,37 @@
+Install Aspell and all the Aspell dictionaries you need.\r
+The Windows port is not currently maintained, but you can get\r
+the 0.5 version from http://aspell.net/win32/\r
+This has installers for the program and the dictionaries.\r
+\r
+Activate spellchecking by setting two properties in doc/doc.build.user.\r
+\r
+<property name="spellcheck" value="true"/> \r
+<property name="path.spellcheck" value="C:\Path\to\your\Aspell.exe"/>\r
+\r
+You may have to use the DOS 8.3 version if the path includes spaces,\r
+as the Aspell.bat batch file doesn't handle them well.\r
+eg. for the default installation use:\r
+<property name="path.spellcheck" value="C:\Progra~1\Aspell\bin\aspell.exe"/>\r
+\r
+This folder contains spellchecker dictionaries for Aspell. \r
+One for each language and a generic template file that is copied to each language.\r
+\r
+TortoiseSVN.tmpl.pws:\r
+  Generic dictionary of terms & Keywords used in the TortoiseSVN manual. \r
+  This file is language independent and is copied to each target language \r
+  (named temp.pws), when the translation takes place.\r
+\r
+de.pws, en.pws, ...:\r
+  Dictionaries of terms for each language.\r
+\r
+The process is still kludgy:\r
+- Aspell doesn't work for Asian languages (yet). No fix available.\r
+- It needs a batch file to run Aspell from nant due to IO \r
+  redirection problems. No fix found for this.\r
+- It will fail if <NN>.pws doesn't exist yet. \r
+  Create a text file <NN>.pws that just contains the line:\r
+  "personal_ws-1.1 <NN> 0" where <NN> is the country code.\r
+  Look in de.pws or en.pws for examples. \r
+  Add your terms after this line.\r
+\r
+The output of the spellchecking process is written to "spellcheck_<NN>.log".\r
diff --git a/doc/Aspell/TortoiseSVN.tmpl.pws b/doc/Aspell/TortoiseSVN.tmpl.pws
new file mode 100644 (file)
index 0000000..9883802
--- /dev/null
@@ -0,0 +1,92 @@
+personal_ws-1.1 $LANG$ 0\r
+Araxis\r
+autolist\r
+autoprops\r
+BDB\r
+BOM\r
+CollabNet\r
+CR\r
+CVS\r
+CSV\r
+Cygwin\r
+DeltaV\r
+dll\r
+DNS\r
+DSA\r
+ExamDiff\r
+exe\r
+frontpage\r
+FSFS\r
+Google\r
+GPL\r
+Gurtle\r
+hostname\r
+html\r
+http\r
+httpd\r
+https\r
+IBugTraqProvider\r
+IIS\r
+IP\r
+KDiff\r
+keygen\r
+Küng\r
+LDAP\r
+LF\r
+Lübbe\r
+Logemann\r
+MFC\r
+Mozilla\r
+MSDN\r
+msi\r
+Müller\r
+NotePad\r
+NTLM\r
+Onken\r
+OpenOffice\r
+OpenSSH\r
+OpenSSL\r
+Pageant\r
+Plink\r
+perl\r
+Photoshop\r
+php\r
+pre\r
+PrestoSoft\r
+PuTTY\r
+PuTTYgen\r
+SASL\r
+SciTE\r
+SMB\r
+SourceForge\r
+ssl\r
+sspi\r
+stdout\r
+stderr\r
+Subversion\r
+SubWCRev\r
+svn\r
+svnserve\r
+Syneapps\r
+TortoiseBlame\r
+TortoiseCVS\r
+TortoiseIDiff\r
+TortoiseHG\r
+TortoiseMerge\r
+TortoisePlink\r
+TortoiseProc\r
+TortoiseSVN\r
+trac\r
+TSVNCache\r
+UNC\r
+unicode\r
+USB\r
+UTF\r
+UUID\r
+ViewVC\r
+WebDAV\r
+WebSVN\r
+WinMerge\r
+xml\r
+XSL\r
+XP\r
diff --git a/doc/Aspell/append.bat b/doc/Aspell/append.bat
new file mode 100644 (file)
index 0000000..49d2a69
--- /dev/null
@@ -0,0 +1,3 @@
+@echo off\r
+rem NAnt doesn't seem able to append one file to another\r
+type %1 >> %2\r
diff --git a/doc/Aspell/aspell.in b/doc/Aspell/aspell.in
new file mode 100644 (file)
index 0000000..74c4cec
--- /dev/null
@@ -0,0 +1,8 @@
+@echo off\r
+rem parameters\r
+rem %1 = path to spellcheck executable\r
+rem %2 = language\r
+rem %3 = name of the file to check\r
+rem %4 = name of the logfile\r
+echo --- %3 > %4\r
+"$XSLTProcPath$\xsltproc.exe" --nonet .\aspell\removetags.xsl %3 | %1 --mode=sgml --encoding=utf-8 --add-extra-dicts=./ASpell/%2.pws --add-extra-dicts=./ASpell/Temp.pws --lang=%2 list check >> %4\r
diff --git a/doc/Aspell/de.pws b/doc/Aspell/de.pws
new file mode 100644 (file)
index 0000000..fd24d87
--- /dev/null
@@ -0,0 +1,179 @@
+personal_ws-1.1 de 0\r
+Aktionsskript\r
+Aktionsskripte\r
+Aktionsskripten\r
+Aktionsskripts\r
+Änderungsdatum\r
+Änderungsliste\r
+Änderungslisten\r
+Anmeldedaten\r
+Anmeldename\r
+Annotiere\r
+annotieren\r
+Annotierens\r
+annotierte\r
+Annotierung\r
+Annotierungen\r
+auschecken\r
+ausgecheckt\r
+ausgecheckte\r
+BASE\r
+Basisdatei\r
+Basispfad\r
+Baumstruktur\r
+Benutzernamen\r
+Berkeley\r
+Bildlaufleiste\r
+branches\r
+COM\r
+Dateibaum\r
+Dateibaumes\r
+Dateidatum\r
+Dateieigenschaften\r
+Dateiendung\r
+Dateiendungen \r
+Dateiliste\r
+Dateinamens\r
+Dateipfades\r
+Dateiserver\r
+Dateiservers\r
+Dateiversion\r
+Datenintegration\r
+Diff\r
+Dreifenstersicht\r
+Dreiwegevergleich\r
+Einfenstersicht\r
+Eingabefeldes\r
+Einstellungsdialog\r
+Eintragsnummer\r
+Eintragsnummern\r
+Elternordner\r
+Ergebnisdatei\r
+Explorer\r
+Explorers\r
+Externals\r
+Fehlerverfolgungssystem\r
+Fehlerverfolgungssystemen\r
+Fenstertitel\r
+Fenstertiteln\r
+Fortschrittsdialog\r
+Funktionszweig\r
+Funktionszweiges\r
+Gruppenrichtlinien\r
+GUI\r
+Harry\r
+HEAD\r
+HEX\r
+Hilfetexte\r
+Hinweistext\r
+ID\r
+IDs\r
+Installationsverzeichnis\r
+Installer\r
+Informationsspalte\r
+Kemp\r
+Kombinationsliste\r
+Kommandozeilenbefehl\r
+Kommandozeilenbefehle\r
+Kommandozeilenparameter\r
+Konflikteditor\r
+Konflikteditoren\r
+Kontextmenü\r
+Kontextmenüs\r
+Large\r
+Linksklick\r
+Linkspfeil\r
+Logmeldung\r
+Logmeldungen\r
+loszulassen\r
+Mausrad\r
+Maustaste\r
+Mauszeiger\r
+Menübefehl\r
+Menüeintrag\r
+Menüeinträge\r
+Menüleiste\r
+Navigationsleiste\r
+Netzwerkfreigabe\r
+Netzwerkfreigaben\r
+Netzwerklaufwerke\r
+Notepad\r
+OK\r
+Ordners\r
+Ordnerstruktur\r
+Originaldatei\r
+Passphrase\r
+Passwortdatei\r
+Patchdatei\r
+Patchdateien\r
+Patchliste\r
+Projektarchiv\r
+Projektarchivbetrachter\r
+Projektarchivbetrachtern\r
+Projektarchivbetrachters\r
+Projektarchive\r
+Projektarchiven\r
+Projektarchivs\r
+Projektdatei\r
+Projekteigenschaft\r
+Projekteigenschaften\r
+Rechnername\r
+Rechnernamen\r
+Rechtschreibkorrektur\r
+Rechtsklick\r
+Rechtspfeil\r
+Revisionsbereich\r
+Revisionsgraph\r
+Revisionsgraphen\r
+Revisionsnummern\r
+Sally\r
+Schaltfläche\r
+Schaltflächen\r
+Source\r
+SSH\r
+Stammes\r
+Statusinformation\r
+Statusleiste\r
+Statusprüfung\r
+Steuerelement\r
+Steuerelemente\r
+Strg\r
+tags\r
+Tastaturkürzel\r
+Textdateien\r
+trunk\r
+umplatzieren\r
+umplatziert\r
+Umsch\r
+Unterordner\r
+Unterprojekte\r
+unversionierte\r
+unversionierten\r
+unversioniertes\r
+URI\r
+Vergleichsprogramm\r
+versioniert\r
+versionierte\r
+versioniertem\r
+versionierten\r
+versionierter\r
+versioniertes\r
+Versionierung\r
+Versionskontrolle\r
+Versionskontrollsystem\r
+Versionskontrollsysteme\r
+Versionskontrollsystemen\r
+Versionskontrollsystems\r
+Vollzugriff\r
+Werkzeugleiste\r
+Web\r
+Webseite\r
+Webseiten\r
+Windows\r
+Zeitstempel\r
+Zieldatei\r
+Zielordner\r
+Zugriffsmethode\r
+zurückzuholen\r
+Zusammenführens\r
+Zweifenstersicht\r
diff --git a/doc/Aspell/en.pws b/doc/Aspell/en.pws
new file mode 100644 (file)
index 0000000..0c8ab5b
--- /dev/null
@@ -0,0 +1,80 @@
+personal_ws-1.1 en 0\r
+APIs\r
+Auth\r
+backend\r
+CamelCase\r
+CDs\r
+changelist\r
+changelists\r
+changeset\r
+changesets\r
+checkbox\r
+checkboxes\r
+checkins\r
+CLI\r
+combobox\r
+comboboxes\r
+committer\r
+config\r
+ctrl\r
+deselect\r
+DLLs\r
+Donators\r
+DVDs\r
+eg\r
+filepaths\r
+filesystem\r
+globbing\r
+hackability\r
+HeadURL\r
+IDE\r
+IDs\r
+inline\r
+intranet\r
+lightbox\r
+LoadModule's\r
+locator\r
+LogMessage\r
+metadata\r
+mousewheel\r
+Nr\r
+online\r
+passphrase\r
+plugin\r
+plugins\r
+popup\r
+prev\r
+regex\r
+regexes\r
+repo\r
+revprop\r
+revprops\r
+SCM\r
+screenshot\r
+screenshots\r
+spellchecker\r
+submenu\r
+timestamp\r
+toolbar\r
+tooltip\r
+TortoiseMerge's\r
+TortoiseSVN's\r
+uncheck\r
+unchecking\r
+unmergeable\r
+unversion\r
+unversioned\r
+UPPERcase\r
+upperCASE\r
+upwards\r
+URLs\r
+UUIDs\r
+username\r
+usernames\r
+versioned\r
+versioning\r
+webviewer\r
+whitespace\r
+whitespaces\r
+wildcard\r
+wildcards\r
diff --git a/doc/Aspell/removetags.xsl b/doc/Aspell/removetags.xsl
new file mode 100644 (file)
index 0000000..f9d2b3a
--- /dev/null
@@ -0,0 +1,18 @@
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"\r
+               version='1.0'>\r
+\r
+  <xsl:output method="xml"\r
+              encoding="UTF-8"\r
+              indent="no"/>\r
+\r
+  <xsl:template match="screen|literal|filename|programlisting|option|primary"/>\r
+  <xsl:template match='*[@condition="pot"]'/>\r
+  <xsl:template match="comment()"/>\r
+\r
+  <xsl:template match="node() | @*">\r
+    <xsl:copy>\r
+      <xsl:apply-templates select="@* | node()"/>\r
+    </xsl:copy>\r
+  </xsl:template>\r
+  \r
+</xsl:stylesheet>\r
diff --git a/doc/Aspell/ru.pws b/doc/Aspell/ru.pws
new file mode 100644 (file)
index 0000000..eb3646b
--- /dev/null
@@ -0,0 +1,372 @@
+personal_ws-1.1 ru 0\r
+Access\r
+address\r
+Alt\r
+and\r
+Apache\r
+API\r
+ASCII\r
+ASPDOTNETHACK\r
+Auth\r
+Authentication\r
+authoritative\r
+Auto\r
+BASE\r
+Basic\r
+bbe\r
+Berkeley\r
+Beyond\r
+bin\r
+Blame\r
+Book\r
+branches\r
+byte\r
+CD\r
+change\r
+cheap\r
+check\r
+CLI\r
+COM\r
+command\r
+commit\r
+Compare\r
+Computer\r
+Configuration\r
+connection\r
+Conversions\r
+copies\r
+CRT\r
+ctrl\r
+Cyrus\r
+daemon\r
+Data\r
+database\r
+date\r
+DB\r
+Delete\r
+denied\r
+Diff\r
+DOS\r
+DVD\r
+english\r
+Explorer\r
+externals\r
+false\r
+FAQ\r
+Filesystem\r
+for\r
+Format\r
+freeware\r
+FS\r
+General\r
+GNU\r
+GPO\r
+Green\r
+HEAD\r
+Host\r
+ID\r
+IDE\r
+IE\r
+IEEE\r
+Import\r
+Interface\r
+Internet\r
+issue\r
+issues\r
+Kemp\r
+key\r
+Large\r
+Layer\r
+License\r
+limit\r
+Line\r
+Linux\r
+LOCAL\r
+login\r
+maker\r
+management\r
+Marc\r
+mark\r
+Max\r
+ME\r
+Merge\r
+Microsoft\r
+mime\r
+name\r
+NET\r
+ng\r
+Nigel\r
+non\r
+NT\r
+obj\r
+of\r
+Open\r
+or\r
+order\r
+out\r
+output\r
+patch\r
+per\r
+Perforce\r
+preferred\r
+private\r
+Pro\r
+project\r
+protocol\r
+Public\r
+RCS\r
+revprop\r
+root\r
+SAMBA\r
+Save\r
+saved\r
+Scintilla\r
+SCM\r
+Security\r
+Serdyuk\r
+server\r
+SERVICE\r
+Session\r
+sessions\r
+shareware\r
+Simon\r
+Simple\r
+shift\r
+skin\r
+software\r
+sounds\r
+Source\r
+SP\r
+SSH\r
+standard\r
+Stefan\r
+Style\r
+SUMMARY\r
+Support\r
+SYSTEM\r
+tarball\r
+TCP\r
+telnet\r
+The\r
+Tigris\r
+Tim\r
+TM\r
+to\r
+Tortoise\r
+true\r
+type\r
+UK\r
+Unable\r
+Unified\r
+Unix\r
+update\r
+URI\r
+URL\r
+US\r
+User\r
+using\r
+vendor\r
+version\r
+Vista\r
+Visual\r
+Vladimir\r
+VS\r
+Win\r
+Windows\r
+write\r
+XOR\r
+zipped\r
+Á×ÔÏÚÁ×ÅÒÛÅÎÉÅ\r
+Á×ÔÏÚÁ×ÅÒÛÅÎÉÅÍ\r
+Á×ÔÏÚÁ×ÅÒÛÅÎÉÑ\r
+á×ÔÏÚÁËÒÙÔÉÅ\r
+Á×ÔÏÚÁÐÕÓËÁ\r
+Á×ÔÏÓ×ÏÊÓÔ×\r
+Á×ÔÏÓ×ÏÊÓÔ×Á\r
+Á×ÔÏÓ×ÏÊÓÔ×ÁÍÉ\r
+ÁÔÏÍÁÒÎÏÓÔØ\r
+ÁÕÔÅÎÔÉÆÉËÁÃÉÏÎÎÙÅ\r
+ÁÕÔÅÎÔÉÆÉÃÉÒÏ×ÁÌÁ\r
+ÁÕÔÅÎÔÉÆÉÃÉÒÏ×ÁÔØÓÑ\r
+ÁÕÔÅÎÔÉÆÉÃÉÒÕÅÍÙÅ\r
+ÁÕÔÅÎÔÉÆÉÃÉÒÕÅÍÙÊ\r
+ÁÕÔÅÎÔÉÆÉÃÉÒÕÅÔ\r
+ÂÉÔÎÏÊ\r
+×ÅÂ\r
+×ÅÒÓÉÏÎÎÕÀ\r
+×ÅÒÓÉÒÏ×ÁÌÉ\r
+×ÅÒÓÉÒÏ×ÁÎ\r
+×ÅÒÓÉÒÏ×ÁÎÉÅ\r
+×ÅÒÓÉÒÏ×ÁÎÉÑ\r
+×ÅÒÓÉÒÏ×ÁÎÎÁÑ\r
+×ÅÒÓÉÒÏ×ÁÎÎÏÇÏ\r
+×ÅÒÓÉÒÏ×ÁÎÎÏÅ\r
+×ÅÒÓÉÒÏ×ÁÎÎÏÊ\r
+×ÅÒÓÉÒÏ×ÁÎÎÏÍÕ\r
+×ÅÒÓÉÒÏ×ÁÎÎÙÅ\r
+×ÅÒÓÉÒÏ×ÁÎÎÙÊ\r
+×ÅÒÓÉÒÏ×ÁÎÎÙÍ\r
+×ÅÒÓÉÒÏ×ÁÎÎÙÍÉ\r
+×ÅÒÓÉÒÏ×ÁÎÎÙÈ\r
+×ÅÒÓÉÒÏ×ÁÎÙ\r
+×ÅÒÓÉÒÕÀÔÓÑ\r
+÷åòèîéêÒÅÇÉÓÔÒ\r
+÷ÎÕÔÒÉÓÔÒÏÞÎÙÅ\r
+×ÎÕÔÒÉÓÔÒÏÞÎÙÍÉ\r
+×ÎÕÔÒÉÓÔÒÏÞÎÙÈ\r
+÷CÍÅÛÁÎÎÏÍóÔÉÌÅ\r
+Ä×ÕÈÐÁÎÅÌØÎÏÍ\r
+Ä×ÕÈÐÁÎÅÌØÎÙÊ\r
+Ä×ÕÈÐÁÎÅÌØÎÙÍ\r
+Ä×ÕÈÛÁÇÏ×ÏÇÏ\r
+Ä×ÕÈÛÁÇÏ×ÙÊ\r
+ÄÏÎÁÓÔÒÁÉ×ÁÔØ\r
+ÄÏÎÁÓÔÒÏÊËÉ\r
+ÚÁ×ÅÒÛÅÎÉÊ\r
+ÚÁ×ÅÒÛÅÎÉÑÈ\r
+ÚÁËÜÛÉÒÏ×ÁÎÎÏÅ\r
+ÚÁËÜÛÉÒÏ×ÁÎÎÙÅ\r
+ÚÁËÜÛÉÒÏ×ÁÎÎÙÍÉ\r
+ÚÁËÜÛÉÒÏ×ÁÎÎÙÈ\r
+ÚÁÜËÒÁÎÉÒÏ×ÁÎÎÙÅ\r
+ÉÎÔÒÁÎÅÔ\r
+ëÁÒÎÅÇÉ\r
+ëÅÍÐ\r
+ëÅÍÐÕ\r
+ëÕÎÇ\r
+ëÕÎÇÕ\r
+ËÜÛ\r
+ËÜÛÁ\r
+ËÜÛÅ\r
+ËÜÛÉÒÏ×ÁÎÉÅ\r
+ËÜÛÉÒÏ×ÁÎÉÅÍ\r
+ËÜÛÉÒÏ×ÁÎÉÑ\r
+ËÜÛÉÒÏ×ÁÎÎÙÅ\r
+ËÜÛÉÒÕÅÔ\r
+ËÜÛÉÒÕÅÔÓÑ\r
+ËÜÛÉÒÕÀÔÓÑ\r
+ËÜÛÉÒÕÀÝÉÊ\r
+ìÁÄÖÕ\r
+ì÷ó\r
+ÌÅËÓÉÞÅÓËÉ\r
+ìÏÇÅÍÁÎÎÏÍ\r
+ìÀÂÂÅ\r
+ÍÁÌÏÚÎÁËÏÍÙ\r
+íÂ\r
+íÅÌÌÏÎÁ\r
+ÍÅÓÔÏÐÏÌÏÖÅÎÉÑÍ\r
+ÍÎÏÇÏÓÔÒÏÞÎÙÊ\r
+îÁÊÄÖÅÌÏÍ\r
+ÎÅÁÕÔÅÎÔÉÆÉÃÉÒÏ×ÁÎÎÙÈ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÁÑ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÏÇÏ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÏÅ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÏÊ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÏÍ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÕÀ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÙÅ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÙÊ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÙÍ\r
+ÎÅ×ÅÒÓÉÒÏ×ÁÎÎÙÈ\r
+îÅÚÁÂÌÏËÉÒÏ×ÁÎÎÙÅ\r
+ÎÅÚÁËÜÛÉÒÏ×ÁÎÎÙÅ\r
+ÎÅÚÁÆÉËÓÉÒÏ×ÁÎÎÙÅ\r
+ÎÅÚÁÆÉËÓÉÒÏ×ÁÎÎÙÈ\r
+ÎÅÚÁÛÉÆÒÏ×ÁÎÎÏÊ\r
+ÎÅÉÚ×ÌÅÞ£ÎÎÙÅ\r
+ÎÅÉÚÍÅΣÎÎÏÊ\r
+îÅÉÚÍÅΣÎÎÙÅ\r
+îÅÉÚÍÅΣÎÎÙÊ\r
+ÎÅÉÚÍÅΣÎÎÙÍ\r
+ÎÅÉÚÍÅΣÎÎÙÈ\r
+ÎÅÏÂßÅÄÉÎÑÅÍÙÅ\r
+ÎÅÏÂßÅÄÉÎÑÅÍÙÍÉ\r
+ÎÅÐÏÌÕÞÅÎÎÙÈ\r
+ÎÅÒÅËÕÒÓÉ×ÎÁÑ\r
+ÎÅÕÌÁÖÅÎÎÙÈ\r
+ÎÅÕÓÐÅÛÎÏ\r
+ÎÅÕÓÐÅÛÎÏÊ\r
+ïÂßÅÄÉÎ\r
+ÏÄÎÏÂÕË×ÅÎÎÙÍ\r
+ÏÄÎÏËÌÁ×ÉÛÎÙÈ\r
+ÏÄÎÏÐÁÎÅÌØÎÏÍ\r
+ÏÄÎÏÐÁÎÅÌØÎÙÊ\r
+ÏÄÎÏÐÁÎÅÌØÎÙÍ\r
+ÏÄÎÏÓÔÒÏÞÎÏÅ\r
+ïë\r
+ïÎËÅÎ\r
+ïÎËÅÎÕ\r
+ÏÔ×ÅÔ×ÉÔØ\r
+ÏÔÎÉÍÁÅÍÏÇÏ\r
+ÐÅÒÅÎÁÐÒÁ×ÉÔØ\r
+ðÅÒÅÎÁÐÒÁ×ÌÅÎÉÅ\r
+ðÅÒÅÏÔËÒÙ×ÁÔØ\r
+ÐÅÒÅÐÒÏÓÍÁÔÒÉ×ÁÅÔ\r
+ÐÅÒÅÒÁÚÂÉÔ\r
+ÐÅÒÅÕÐÏÒÑÄÏÞÉ×ÁÎÉÉ\r
+ðÅÔÒÁËÏ×\r
+ÐÉËÓÅÌÁÈ\r
+ÐÉËÓÅÌÏ×\r
+ðë\r
+ÐÏÄ×ÅÔËÕ\r
+ÐÏÄ×ÉÓÛÉÈ\r
+ÐÏÄÐÁÐËÁ\r
+ÐÏÄÐÁÐËÁÈ\r
+ÐÏÄÐÁÐËÅ\r
+ÐÏÄÐÁÐËÉ\r
+ÐÏÄÐÁÐËÕ\r
+ÐÏÄÐÁÐÏË\r
+ÐÏÄÐÒÏÅËÔ\r
+ÐÏÄÐÒÏÅËÔÁ\r
+ÐÏÄÐÒÏÅËÔÁÍ\r
+ÐÏÄÐÒÏÅËÔÁÍÉ\r
+ÐÏÄÐÒÏÅËÔÙ\r
+ÐÏÏÞÅÒ£ÄÎÏÓÔØ\r
+ÐÒÅÄÏÂÒÁÂÏÔËÕ\r
+òÁÚ×ÅÒÓÉÒÏ×ÁÎÉÅ\r
+ÒÁÚ×ÅÒÓÉÒÏ×ÁÔØ\r
+ÒÁÚËÏÍÍÅÎÔÉÒÏ×ÁÔØ\r
+ÒÁÚËÏÍÍÅÎÔÉÒÕÊÔÅ\r
+ÒÁÚÏÔÍÅÔÉÔØ\r
+ÒÁÚÏÔÍÅÔØÔÅ\r
+ÒÁÚÏÔÍÅÞÁÔØ\r
+ÒÅÆÁËÔÏÒÉÎÇÁ\r
+óÁÊÍÏÎÕ\r
+óÁÊÒÕÓ\r
+óÁÌÌÉ\r
+Ó×ÅÖÅÄÏÂÁ×ÌÅÎÎÙÍ\r
+Ó×ÅÖÅÓÇÅÎÅÒÉÒÏ×ÁÎÎÙÍ\r
+Ó×ÅÖÅÓÏÚÄÁÎÎÏÅ\r
+Ó×ÅÖÅÓÏÚÄÁÎÎÙÈ\r
+ÓÇÅÎÅÒÉÒÏ×ÁÎÎÙÊ\r
+ÓÇÅÎÅÒÉÒÏ×ÁÎÎÙÍ\r
+ÓÅÍÁÎÔÉÞÅÓËÉ\r
+ÓÅÒ×ÅÒÎÙÅ\r
+ÓÅÒ×ÅÒÎÙÈ\r
+ÓÌÉ×ÁÅÍÙÈ\r
+óÔÅÆÁÎ\r
+óÔÅÆÁÎÕ\r
+ÔÁÂÕÌ\r
+ÔÁÊÍÁÕÔ\r
+ÔÁÊÍÁÕÔÁ\r
+ôÉÍ\r
+ôÉÍÕ\r
+ÔÒÅÅ\r
+ÔÒÅÊ\r
+ÔÒ£ÈÐÁÎÅÌØÎÏÍ\r
+ÔÒ£ÈÐÁÎÅÌØÎÙÊ\r
+ÔÒÕÄÎÏÞÉÔÁÅÍÙÍ\r
+ÔÒÕÄÏÚÁÔÒÁÔÎÙÊ\r
+ÔÒÕÄÏÚÁÔÒÁÔÎÙÍ\r
+ÔÕÎÎÅÌÉÒÏ×ÁÎ\r
+ÕÐÏÒÑÄÏÞÉ×ÁÎÉÅ\r
+ÕÐÏÒÑÄÏÞÉ×ÁÎÉÑ\r
+ÕÓÔÁÎÏ×ÝÉË\r
+ÕÓÔÁÎÏ×ÝÉËÁ\r
+ÆÌÜÛ\r
+þÁ÷Ï\r
+ÛÅÓÔÎÁÄÃÁÔÉÒÉÞÎÏÍ\r
+ÛÅÓÔÎÁÄÃÁÔÉÒÉÞÎÙÊ\r
+ÜÌÅËÔÒÏÐÏÞÔÅ\r
+ÜÌÅËÔÒÏÐÏÞÔÙ\r
+ÀÎÉËÏÄÏÍ\r
diff --git a/doc/AutolistDoc.txt b/doc/AutolistDoc.txt
new file mode 100644 (file)
index 0000000..74d9116
--- /dev/null
@@ -0,0 +1,43 @@
+As of revision 2659, TSVN now can parse all the files listed and checked\r
+in the commit dialog for words to use in the autocompletion list. This\r
+is a very handy feature when writing log messages since it helps you\r
+refer to changed methods, class names, ...\r
+\r
+The parsing of the files is done with regexes, and those regexes are\r
+kept in {ProgramFiles}\TortoiseSVN\bin in autolist.txt. In our source\r
+tree, that file lives at trunk/src/TortoiseSVNSetup/include/autolist.txt\r
+\r
+The installed file gets replaced whenever TSVN is upgraded (because bad\r
+regexes can cause the commit dialog to crash), so anything you add there\r
+will be lost on upgrade.\r
+\r
+Versions of TSVN later than 1.4 look for an additional file at\r
+%APPDATA%\TortoiseSVN\autolist.txt, which is where you can put user-\r
+defined regexes in addition to the standard ones.\r
+\r
+So here's how you can help:\r
+- find a filetype/programming language you know well\r
+- decide what of a typical file of that type you'd want in the\r
+  autocompletion list. Usually, you'd want method/function names,\r
+  class names, interface names. But maybe not variable names since\r
+  then the autocompletion list could get just too big!\r
+- write a regex to parse for those strings\r
+- test your regex on as many files you can find\r
+- improve the regex and test again.\r
+- test the whole thing with TSVN directly\r
+- send us your regex string with the filetype you want it to apply to,\r
+  and maybe some testfiles too.\r
+\r
+To help you with this task, there's a little tool to test your regex\r
+strings on files located here:\r
+http://tortoisesvn.tigris.org/files/documents/406/20668/RegExpTest.exe\r
+Just enter your regex string and drag the files you want to test it with\r
+over the dialog. The parsed strings will be listed at the bottom of the\r
+dialog.\r
+\r
+If you are unfamiliar with regular expressions, take a look at the online\r
+documentation and tutorial at http://www.regular-expressions.info/\r
+\r
+Note that TSVN also uses regex groups and you can specify the flags to\r
+use in the autolist.txt file like this:\r
+(MULTILINE|NOCASE|GLOBAL) .txt, .pic = (regex-string)\r
diff --git a/doc/MailingListAnswers.txt b/doc/MailingListAnswers.txt
new file mode 100644 (file)
index 0000000..a0ccb60
--- /dev/null
@@ -0,0 +1,123 @@
+This file serves as a template for standard answers which can\r
+be used on the mailing list. This might help avoid rude answers\r
+to some special users.\r
+\r
+General\r
+-------\r
+You do not receive a proper reply from us, because:\r
+( ) It looks like you haven't read the docs yet\r
+( ) Your bug report is incomplete or not a bug at all\r
+( ) Your feature request is not specified in enough detail\r
+( ) You are violating our list etiquette\r
+( ) We are just in a bad mood\r
+\r
+To avoid further problems on this list, please read the appropriate\r
+documentation first:\r
+\r
+The TortoiseSVN documentation is located here:\r
+http://tortoisesvn.tigris.org/docs.html\r
+\r
+Or you can read the help file on your own PC:\r
+StartMenu->TortoiseSVN->Help\r
+\r
+Please read our FAQ for answers to some common problems:\r
+http://tortoisesvn.sourceforge.net/?q=node/1\r
+\r
+Check these instructions if you want to report a bug:\r
+http://tortoisesvn.tigris.org/reportbugs.html\r
+\r
+Our rules for this list are found here:\r
+http://tortoisesvn.tigris.org/list_etiquette.html\r
+\r
+\r
+\r
+RTFM\r
+----\r
+This is a predefined answer to your question. You're getting this \r
+instead of a real answer to your question because it seems you \r
+haven't read the documentation yet.\r
+Please read our docs and the FAQ first. If you then still have \r
+some questions, you can come back to the mailing list and ask \r
+again. But if you do, make sure you give as much detail about \r
+your problem as possible.\r
+The docs are located here:\r
+http://tortoisesvn.tigris.org/docs.html\r
+\r
+The FAQ is located here:\r
+http://tortoisesvn.sourceforge.net/?q=node/1\r
+\r
+\r
+BUG\r
+---\r
+This is a predefined answer to your bugreport. You're getting this\r
+because your bug report is incomplete, and we cannot tell whether\r
+this is a real bug or simply user error.\r
+Please read about how to report a bug here:\r
+http://tortoisesvn.tigris.org/reportbugs.html\r
+The documentation is located here:\r
+http://tortoisesvn.tigris.org/docs.html\r
+\r
+and most important our rules for the mailing list:\r
+http://tortoisesvn.tigris.org/list_etiquette.html\r
+\r
+If you're done reading that and you still think you've found a bug in\r
+TortoiseSVN then please come back to this mailing list with as much\r
+information as you can give us about the bug.\r
+\r
+\r
+Etiquette\r
+---------\r
+This is a predefined answer to your mail. You get this because your mail\r
+was written in an offensive tone which doesn't belong on this list.\r
+There are some rules for people using this mailing list. Please read them \r
+carefully and of course try to follow those rules. Otherwise you might get \r
+unsubscribed from the list or your mails won't be moderated through anymore.\r
+The rules are located here:\r
+http://tortoisesvn.tigris.org/list_etiquette.html\r
+\r
+\r
+Feature Request:\r
+----------------\r
+This is a predefined answer to your feature request. You're getting this\r
+instead of a real answer because you wrote your request in a very demanding tone.\r
+Requesting a feature should be written friendly, they're after all _requests_ \r
+and not demands. In an open source project you can't demand a feature. \r
+The developers don't get paid, they're spending their free time on this\r
+project for free. You're using a free program, you don't pay anything for it.\r
+So please behave civil and ask nicely for a new feature. Explain what you want,\r
+and why you need it. If it makes sense for a majority of users your request will\r
+make it on the todo list. Always keep in mind that we will fix bugs before we \r
+add new features.\r
+To avoid further problems on this list, please read our rules for this list:\r
+http://tortoisesvn.tigris.org/list_etiquette.html\r
+\r
+Top Posting:\r
+------------\r
+A: Because it messes up the order in which people normally read text.\r
+Q: Why is top-posting such a bad thing?\r
+A: Top-posting.\r
+Q: What is the most annoying thing on usenet and mailing lists?\r
+\r
+CrashReport fixed:\r
+------------------\r
+Hi,\r
+Thanks for sending the crashreport. We analyzed your crashreport and \r
+fixed the bug which caused the crash. You can now either wait for \r
+the next release or use the next nightly build. The link to the nightly\r
+builds is on our download page.\r
+\r
+CrashReport outdated:\r
+---------------------\r
+Hi,\r
+Thanks for sending the crashreport, but please understand that we don't\r
+have the time to analyze crashreports for old versions.\r
+Please update to the latest released version. If the crash still occurs\r
+with that release, you can send again a crashreport.\r
+\r
+CrashReport library:\r
+--------------------\r
+Hi,\r
+Thanks for sending the crashreport. We analyzed your crashreport, but\r
+unfortunately the bug is not in TortoiseSVN itself but in one of the\r
+libraries TortoiseSVN uses. We will discuss this with the developers\r
+of that library and try to get this bug fixed.\r
diff --git a/doc/Screenshots.txt b/doc/Screenshots.txt
new file mode 100644 (file)
index 0000000..7306605
--- /dev/null
@@ -0,0 +1,347 @@
+Grabbing Screenshots for TortoiseSVN Docs\r
+=========================================\r
+This file is a guide to grabbing screenshots for the user manual.\r
+Although there are not many hard and fast rules, some screenshots need\r
+care to set up as they are demonstrating a range of features.\r
+\r
+To help with consistency, some of these instructions are presented\r
+as a TortoiseProc.exe command line. These assume that the TSVN\r
+bin directory is in the PATH and that you have a doc folder checked\r
+out at C:\TortoiseSVN\Doc. Adjust the path according to your location.\r
+\r
+If you do not already have a screen capture/image viewer program,\r
+download a free copy of IrfanView from www.irfanview.com\r
+\r
+You will also need to ensure that the screenshots are at the correct\r
+DPI setting and size to fit the page. Fortunately this is easy as you\r
+can use the AdjustImages.bat script which does the conversion for you.\r
+This script requires NConvert.exe which you can download from\r
+http://www.xnview.com\r
+\r
+From the images directory you can simply run adjustimages to check all\r
+images in all languages - it could take a long time. You can check\r
+specific languages or images using a single parameter, eg.\r
+adjustimages en\*.png\r
+adjustimages en\Rev*.png\r
+\r
+\r
+General rules for all screenshots\r
+=================================\r
+Use PNG format\r
+8 bit colour depth (256 colours)\r
+Windows XP style preferred\r
+\r
+Test Repository\r
+===============\r
+We now have a batch file to create a repository and some working copies\r
+in various states of modification and conflict. In the test folder,\r
+create a file called DocPath.txt which contains the path to your doc\r
+folder, but with forward slashes and URI escaping of spaces and other\r
+funny characters. Now simply run MakeTest.bat to create the test folders\r
+in the 'temp' subfolder.\r
+\r
+Instructions for each screenshot\r
+================================\r
+Authenticate.png\r
+       You will have to clear authentication to make this one appear.\r
+       Do this temporarily for the TSVN repo by renaming\r
+       [Application Data]\Subversion\auth\svn.simple\f55fc06b366775f8c026407285be8070\r
+\r
+BlameDialog.png\r
+       Blame any file\r
+\r
+ch02dia1-7.png\r
+       These are 'borrowed' from the Subversion Book\r
+\r
+Changelist.png\r
+       Use the 'doc' test WC.\r
+       Open the commit dialog and add dug_blame.xml to a new changelist 'Blame doc update'.\r
+       Screenshot shows context menu for the changelist.\r
+       Remove dug_blame.xml from the changelist.\r
+\r
+Checkout.png\r
+       Just pretend to checkout the TSVN doc folder:\r
+       TortoiseProc.exe /command:checkout /path:"C:\TortoiseSVN\Doc" /url:"http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/doc"\r
+\r
+Commit.png\r
+       Use the 'doc' test WC.\r
+       Modify server.xml in the 'ext' folder\r
+       Open the commit dialog for the 'doc' folder\r
+       Type a message with spelling problem, eg.\r
+               Update documentation to explain new Frobnicate checkbox.\r
+       Right click on dug_blame and include context menu in screenshot.\r
+       This setup is also used for CommitSpellCheck.png and CreatePatch.png\r
+\r
+CommitSpellcheck.png\r
+       As above, but right click on the mis-spelled word to get the context menu.\r
+\r
+CommitProgress.png\r
+       Capture the progress dialog at the end of any commit.\r
+\r
+ContextMenuDirControl.png\r
+       In explorer, right click on a versioned folder (eg. TSVN doc folder) and\r
+       capture the main context menu and the large TSVN sub m