Wording for "Default" encoding in Create Database Sheet is ambiguous

[GoogleCodeExporter]

What steps will reproduce the problem?
1. MySQL character_set and collation set to utf8
2. Sequel Pro -> Preferences -> Default Encoding: UTF-8
3. Add new table - Encoding: Default
4. Table Info -> Encoding: cp1252 (latin1), Collation: latin1_swedish_ci

What is the expected output? What do you see instead?

Table Info -> Encoding: utf8, Collation: utf8_general_ci

What version of Sequel Pro are you using? What version of MySQL are you
connecting to on the server?

- Sequel Pro 0.9.9.1
- MySQL 5.1.57-rel12.8-log, Percona Server (GPL), 12.8, Revision 232

Original issue reported on code.google.com by arcl...@gmail.com on 8 Dec 2011 at 4:20

[GoogleCodeExporter]

Sequel Pro is behaving correct.
However the wording is confusing here.
Instead of "Default" we should probably use "Default (Server)" or "Server 
default"

Original comment by schlabbe...@gmail.com on 3 Mar 2012 at 6:57

• Changed state: Accepted
• Added labels: Component-UI, Easy, Priority-Low, Type-Enhancement, Usability

[GoogleCodeExporter]

On second though:
"Default" is never a good option as the user often doesn't know what that means.
So we should either 
* always select UTF-8 as Default
* Show the server default eg. "Server Default (cp1512)"

Original comment by schlabbe...@gmail.com on 3 Mar 2012 at 7:01

• Changed title: Wording for "Default" encoding in Create Database Sheet is ambiguous

[GoogleCodeExporter]

Original comment by stuart02 on 10 Jun 2012 at 6:19

• Changed state: Started

[GoogleCodeExporter]

Original comment by stuart02 on 10 Jun 2012 at 6:19

• Removed labels: Easy

[GoogleCodeExporter]

Implemented in r3686.

Original comment by stuart02 on 10 Jun 2012 at 9:29

• Changed state: Implemented