From 8cc14843405c47206bace3c36f6102f293bde970 Mon Sep 17 00:00:00 2001 From: stuconnolly Date: Tue, 26 Jun 2012 09:21:07 +0000 Subject: Remove ancient help docs that we're never going to use. --- Resources/Help/topics/encoding.html | 73 ------------------------------------- 1 file changed, 73 deletions(-) delete mode 100755 Resources/Help/topics/encoding.html (limited to 'Resources/Help/topics/encoding.html') diff --git a/Resources/Help/topics/encoding.html b/Resources/Help/topics/encoding.html deleted file mode 100755 index adaed683..00000000 --- a/Resources/Help/topics/encoding.html +++ /dev/null @@ -1,73 +0,0 @@ - - -Sequel Pro Help - Text Encoding - - - - - - - - -
- - - - - - - - - -
- -

Text Encoding

-
- -
- -
-Back to the main menu -
-
- - You may choose the type of encoding for the data (text) that is stored in your MySQL database. There are two -places to choose the encoding: the Preferences pane or the encoding pull-down bar at the bottom left of the application window. There -are over 20 encodings for you to choose from. -
-
-In the Preferences Pane - - - - -
- -
    -
  • Open up the "Preferences Pane" of Sequel Pro
  • -
  • From the pull-down at the bottom left of the preferences window, labelled "Default Encoding", choose an option.
  • -
  • The encoding you choose will be the default encoding for all future databases
  • -
-
-
-In the Application Window - - - - -
- -
    -
  • In the main application window there will be a pull-down at the bottom left of the window labelled "Encoding".
  • -
  • From the pull-down choose an encoding option.
  • -
  • The encoding you choose will be the default encoding for all future databases
  • -
-
- - - -
- - - \ No newline at end of file -- cgit v1.2.3