search

nbuytaert1 / apex-select2

Select lists in Oracle APEX as they should be
https://apex.oracle.com/pls/apex/f?p=64237:20
GNU General Public License v2.0
56 stars 18 forks source link

No Matches Message not translated #59

Open p3t3r opened 8 years ago

p3t3r commented 8 years ago

Hello,

I found a bug where the No Matches Message is not translated. The attribute has the "Translatable" property set to "Yes". It shows up in the translation repository, where I translate the string. But in the Apex page it is not translated, but still the original message. The strange thing is, is that other messages are correctly translated , for instance the "Searching Message". Looking at the render function of the plugin, there seems not difference in the way the attributes are retrieved:

l_no_matches_msg gt_string := p_plugin.attribute_01; l_input_too_short_msg gt_string := p_plugin.attribute_02; l_selection_too_big_msg gt_string := p_plugin.attribute_03; l_searching_msg gt_string := p_plugin.attribute_04; l_null_optgroup_label_app gt_string := p_plugin.attribute_05; l_loading_more_results_msg gt_string := p_plugin.attribute_06; l_look_and_feel gt_string := p_plugin.attribute_07;

Can you reproduce this ?

Regards, Peter

nbuytaert1 commented 8 years ago

Hey Peter,

That's pretty weird because, like you said, all messages are treated the same way. I'll try to reproduce this bug when I find the time. What version of APEX are you on by the way?

p3t3r commented 8 years ago

Hey Nick,

I'm on version 4.2.3.

I've already tried to create an extra attribute (8) , but that attribute is also not translated. When I set attribute 4 to "Translatable" is "no" then this is (as expected) also not translated.

Peter