WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 4 years ago

#5831 closed enhancement (fixed)

Inline help for "UTF-8 is recommended" needs replacing

Reported by: lloydbudd Owned by:
Milestone: 2.9 Priority: normal
Severity: normal Version: 2.8.4
Component: Charset Keywords: has-patch tested commit
Focuses: Cc:

Description

Inline help for "UTF-8 is recommended" needs replacing

ENV: WP trunk r6800 (2.4-bleeding)

At Settings > Reading (wp-admin/options-reading.php) the last setting is "Encoding for pages and feeds:" and below the field it reads "The character encoding you write your blog in (UTF-8 is recommended)"

Recommended links to http://developer.apple.com/documentation/macos8/TextIntlSvcs/TextEncodingConversionManager/TEC1.5/TEC.b0.html

That Apple.com page reads at the top

Legacy Document
Important: The information in this document is obsolete and should not be used for new development.

Further, I can't see how it really helps. There is no language about recommendation there only a table of possible encodings.

Attachments (2)

5831-admin-copy-reading-charset-change.diff (1010 bytes) - added by jamierumbelow 5 years ago.
Slightly changed wording and URL change in copy
5831.patch (1.1 KB) - added by hakre 5 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 darkdragon6 years ago

I do think that is the point, but there is probably a better resource for possible encodings. WordPress.org could also include a list of possible encodings, but since it is probably better to not have user change it, I would just remove the link entirely.

A competent user can find the correct encoding on their own, in my humble opinion.

comment:2 Denis-de-Bernardy5 years ago

  • Component changed from Administration to Charset
  • Keywords close added
  • Milestone changed from 2.9 to Future Release
  • Type changed from defect (bug) to enhancement

comment:4 hakre5 years ago

  • Keywords needs-patch added

comment:5 hakre5 years ago

  • Keywords close removed

comment:6 jamierumbelow5 years ago

  • Keywords has-patch added; needs-patch removed

I've changed the wording somewhat, changed the URL (to point to Wikipedia) and added a patch...

jamierumbelow5 years ago

Slightly changed wording and URL change in copy

comment:7 Denis-de-Bernardy5 years ago

  • Milestone changed from Future Release to 2.9

comment:8 hakre5 years ago

I do not like the wording-change. UTF-8 should be favorized extremely, so I see no "but". It's more likely that using everything else as encoding than 7bit Ascii, Latin-1 or UTF8 is doing sort of harakiri with wordpress.

IMHO the recommended type (in the status quo) should be ASCII 7Bit. This is the safest way to work with WordPress right now but it might not be accepted by most of it's users. So the recommendation now is UTF-8. And I think it is a good recommendation.

Wording should reflect that because most users do not understand the topic. Even many programmers have fear to deal with encodings properly.

Is there an argument against linking to WordPress Codex? This would make it much more flexible for the translators as well. And the WordPress community can take care of explanations and hints there far better then on wikipedia.org.

hakre5 years ago

comment:9 hakre5 years ago

  • Version set to 2.8.4

slightly adopted the wording and added a link to codex encoding information.

comment:10 hakre5 years ago

  • Keywords tested commit added

comment:11 westi4 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [12101]) Improve the inline documentation about character sets and link to up-to-date resources. Fixes #5831 props hakre.

Note: See TracTickets for help on using tickets.