Kiln » TortoiseHg » TortoiseHg
Clone URL:  
Pushed to one repository · View In Graph Contained in 2.0, 2.0.1, and 2.0.2

stable doc: some polish for intro.txt

Changeset 3c5630c86ded…

Parent 8b7856c7bfe0…

by Steve Borho

Changes to one file · Browse files at 3c5630c86ded Showing diff from parent 8b7856c7bfe0 Diff from another changeset...

Change 1 of 4 Show Entire File doc/​source/​intro.txt Stacked
 
64
65
66
67
68
 
 
69
70
71
 
74
75
76
77
 
78
79
80
81
82
83
84
85
86
 
 
 
87
88
 
89
90
91
 
116
117
118
119
120
121
122
 
 
123
124
125
 
135
136
137
138
 
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
 
64
65
66
 
 
67
68
69
70
71
 
74
75
76
 
77
78
79
80
81
82
83
 
 
 
84
85
86
87
 
88
89
90
91
 
116
117
118
 
 
 
 
119
120
121
122
123
 
133
134
135
 
136
137
138
139
140
141
142
 
 
 
 
 
 
 
 
143
@@ -64,8 +64,8 @@
 complete the install.    .. note:: - If you have a legacy version of TortoiseHg installed, the 1.0 - installer will ask that you to remove it. The uninstall can be + If you have a legacy version of TortoiseHg installed, the + installer will require that you to remove it. The uninstall can be   initiated from the control panel or the start menu.    .. warning:: @@ -74,18 +74,18 @@
  older TortoiseHg versions. This is not a problem with the newer MSI   packages.   -All legacy TortoiseHg installers (before version 1.0) were built with +Legacy TortoiseHg installers (prior to version 1.0) were built with  InnoSetup. They installed a TortoiseOverlay package as a separate  application, so you always saw both TortoiseHg and TortoiseOverlay as  two applications in the *Add/Remove Programs* control panel program.  (On x64 platforms, there were two TortoiseOverlays, one for x86  processes and one of x64 processes).   -The new MSI installers for TortoiseHg 1.0 and later include the -TortoiseOverlay packages as "merge modules" so they do not appear as -separate applications anymore. It should be safe to uninstall the older +The new MSI installers for TortoiseHg include the TortoiseOverlay +packages as "merge modules" so they do not appear as separate +applications anymore. It should be safe to uninstall the older  TortoiseOverlay applications from *Add/Remove Programs* after you -uninstall the legacy (<=0.9.3) TortoiseHg installer, unless you have +uninstalled the legacy (<=0.9.3) TortoiseHg installer, unless you have  other Tortoise products that still use the separate TortoiseOverlay MSI  approach (TortoiseCVS or TortoiseBZR).   @@ -116,10 +116,8 @@
   The TortoiseHg user interface has been translated into many languages.  Language packs are not required since all available languages are -installed. Look in :file:`C:\\Program Files\\TortoiseHg\\locale` for the -available languages. To enable a language just set the environment -variable ``LANGUAGE`` to the desidered language, e.g. for italian -``set LANGUAGE=it``. +installed by default. You can select your preferred :guilabel:`UI +Language` in the global settings tool.    The Windows shell extension context menus get their translations from  the Windows registry. Translations for many locales were installed @@ -135,19 +133,11 @@
   For Mac OS X, no packages are available but you can run thg and all the  dialogs via the source install method. For details, see -`Mac OS X <http://bitbucket.org/tortoisehg/thg/wiki/Home>`_. +`Mac OS X <http://bitbucket.org/tortoisehg/thg/wiki/developers/MacOSX>`_.    .. note::   If you install TortoiseHg from source, you need to add our   contrib/mergetools.rc file to your HGRC path in some way. One   approach is to %include it from your ~/.hgrc file.   -Language settings -^^^^^^^^^^^^^^^^^ - -The TortoiseHg tools use Python's -`gettext <http://docs.python.org/library/gettext.html>`_ library to -localize their text. To get localized dialogs, it is recommended that -you set the LANGUAGE environment variable to your locale of choice. -  .. vim: noet ts=4