You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix that strtoupper can't handle non ascii chars
Fixed by not using strtoupper or by using it prior
to the translation of the corresponding string.
fixes #8163
I'd opt for not utilizing strtoupper or any other function like this, just put those strings already upper cased in the translation catalog.
Every call to Host::getStateText($state, true) and Service::getStateText($state, true) is wrapped with strtoupper. There's no need for this in case the catalog already has the upper cased version. (Note the second parameter being true)
Updated by elippmann on 2015-01-16 08:20:44 +00:00
Hi Johannes,
Johannes wrote:
I'd opt for not utilizing strtoupper or any other function like this, just put those strings already upper cased in the translation catalog.
This would require us to provide both the vanilla string and a upper-case one for all strings we want to have upper-case. And this means always one extra string for translation.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8163
Created by ccesario on 2015-01-05 18:13:48 +00:00
Assignee: jmeyer
Status: Resolved (closed on 2015-01-22 13:37:39 +00:00)
Target Version: 2.0.0-beta2
Last Update: 2015-01-22 13:37:39 +00:00 (in Redmine)
It seem that strtoupper() function does not work with accented chars.
Currently to fix it this function solves the problem.
I don't know if this is the better wway, but fix the problem
It is attached 2 images, before and after usage mb_convert_case()
Attachments
Changesets
2015-01-22 13:37:07 +00:00 by jmeyer 6845480
2015-04-09 11:08:49 +00:00 by jmeyer bc6a086
2015-04-10 10:17:52 +00:00 by jmeyer a51b93e
The text was updated successfully, but these errors were encountered: