From f834bfb9b878c622f5aabeec169c3f2af8c81e25 Mon Sep 17 00:00:00 2001 From: stuconnolly Date: Wed, 17 Mar 2010 16:34:47 +0000 Subject: Consolidate all localizable content in the Resources/ directory and only use Interfaces/ for XIBs. This addresses the first point on issue #593. --- Resources/Help/topics/encoding.html | 73 +++++++++++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) create 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 new file mode 100755 index 00000000..adaed683 --- /dev/null +++ b/Resources/Help/topics/encoding.html @@ -0,0 +1,73 @@ + + +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