#5831 closed enhancement (fixed)
Inline help for "UTF-8 is recommended" needs replacing
Reported by: |
|
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)
Change History (13)
#2
@
16 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
#3
@
16 years ago
http://www.iana.org/assignments/character-sets
http://en.wikipedia.org/wiki/Character_encoding
I like the Idea to link on a page on codex and then do the updates in there.
#6
@
16 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...
#8
@
16 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.
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.