Make WordPress Core

Opened 16 years ago

Closed 14 years ago

#8496 closed defect (bug) (duplicate)

Not all strings can make use of HTML entities

Reported by: xibe's profile xibe Owned by: nbachiyski's profile nbachiyski
Milestone: Priority: normal
Severity: normal Version: 2.7
Component: I18N Keywords:
Focuses: Cc:

Description

As a follow-up to #8464, a lot of other strings in WP cannot make us of entities in their translation, for fear of failure.

Some strings belong to a sent e-mail:

/wp-admin/includes/upgrade.php:163

/wp-includes/pluggable.php:949 to 956 + 958 to 963 + 965 to 970 + 973 + 974 + 1029
+ 1031 to 1033 + 1036 + 1038 to 1040 + 1043 + 1045 to 1049 + 1053 to 1055 + 1057
+ 1061 + 1085 + 1086 + 1106 to 1108 + 1110 + 1115 + 1116 + 1119

/wp-login.php:146 + 181 + 182

One is displayed in an alert():

/wp-includes/script-loader.php:50

Some are displayed throught Javascript, and thus entities fail:

/wp-includes/js/tinymce/langs/wp-langs.php:421 + 422

While not all can be fixed in the same way as #8464, it would be nice to be freed of this limitation for translations.

Change History (6)

#1 @markjaquith
16 years ago

  • Milestone changed from 2.7 to 2.8

#2 @nbachiyski
16 years ago

Those in upgrade.php in wp-langs.php actually readily accept entities. Those in the mails have to be fixed, though.

#3 @Denis-de-Bernardy
16 years ago

  • Milestone changed from 2.8 to Future Release

punting from lack of patch

#4 @Denis-de-Bernardy
16 years ago

  • Milestone changed from Future Release to 2.9

#5 @azaozz
15 years ago

  • Milestone changed from 2.9 to Future Release

No patch, no interest.

#6 @ocean90
14 years ago

  • Keywords i18n needs-patch removed
  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.