View Issue Details

IDProjectCategoryView StatusLast Update
0005412mantisbtfilterspublic2006-02-04 05:47
Reportersogabeseiji Assigned Tojlatour  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Versiongit trunk 
Summary0005412: Custom field's value is not correctly displayed in Japanese (also I18N language)
Description

If custom field's value is Japanese(also I18N), it is not correctly displyed in view_all_bug_page.php.

When custom field's value is 'XXXX'(Japanese KANJI), '¤Æ¤¹¤È' is displayed.

Additional Information

core/filter_api.php 2594 line,
echo '<option value="' . htmlentities( $t_item ) . '" ';
change to
echo '<option value="' . htmlspecialchars( $t_item ) . '" ';
because 'htmlentities' is not ready for I18N.

We Japanese always rewrite it. As for this, it must be no problem for english.

TagsNo tags attached.

Relationships

duplicate of 0003634 closedjlatour wrong charset in error messages 

Activities

ryandesign

ryandesign

2005-11-16 06:14

reporter   ~0011619

In the current CVS head, the code says

echo '<option value="' . string_html_entities( $t_item ) . '" ';

That function returns this value:

htmlentities( $p_string, ENT_COMPAT, lang_get( 'charset' ) );

So I'm hoping this issue has already been solved. If you find that the current CVS head still does not work properly for custom fields in Japanese, please let us know. (In fact, if you find that it does work properly, please let us know that as well so that we can mark this issue as resolved.)

ryandesign

ryandesign

2005-11-16 06:24

reporter   ~0011620

According to 0003634 I think this was fixed in 1.0.0rc2.

sogabeseiji

sogabeseiji

2005-11-18 04:35

reporter   ~0011631

Thanks, It worked properly.