Wrong type of quotes are hard coded

[toscho]

WordPress uses smart quotes, which are wrong in non-english texts.

Additionally the WordPress code and the default theme have german, swiss and french »quotes« hard coded as arrows. Using » and « as arrows violates aestethic, orthographic and unicode rules.

Typography should never be hard coded in a software that is used in different languages. So we need the ability to set correct quotes in the language packs or in an option, and the arrows should be real arrows (​http://www.alanwood.net/unicode/arrows.html).

See also: ​http://comox.textdrive.com/pipermail/wp-hackers/2009-February/024671.html

[ryan]

Localizations can already replace wptexturize with their own function or remove texturization entirely. We could make this a little easier with hooks inside wptexturize().

[toscho]

List of all occurences of guillemets (» and «) in the WordPress code

[toscho]

Many occurences of » and « in the list (attachment) are already set in (). But most translators don’t know enough about typography to take care of them. Replacing the defaults with real arrows would really help.

[toscho]

Ooops, trac eat my code.
function

__();

[jidanni]

Note this is not just an i18n issue,
see #9100.

One might think one could just use the methods of
#8929 to turn off wptexturize(), however there are some independent
occurrences of wptexturize() scattered throughout the code, beyond any
filter's grasp.

One might also think that a hook could be added at the beginning of
wptexturize(), giving one the opportunity just to return the input
unscathed. However, as wptexturize() is used in many different roles
beyond just rendering text for browsing, who knows what that might
break.

For goodness sakes. WordPress should give the user an option to just opt-out of
wptexturize() (#9100). Would MediaWiki ever think of letting one opt-in?

[ryan]

See #8536