https://bugzilla.novell.com/show_bug.cgi?id=755414 https://bugzilla.novell.com/show_bug.cgi?id=755414#c3 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@suse.com Platform|Other |All Summary|YCP substring() function is |YCP string builtins like |not UTF-8 safe |the substring() function | |are not UTF-8 safe OS/Version|Other |All --- Comment #3 from Johannes Meixner <jsmeix@suse.com> 2012-04-04 10:04:13 UTC --- Extra functions for UTF8 encoded strings are not needed because since ever the YCP data type string consist of UNICODE characters encoded in UTF8. See the documentation e.g. old one for SLE10 http://doc.opensuse.org/projects/YaST/SLES10/tdg/id_ycp_data_string.html and the same in newer one e.g. for openSUSE 11.3 http://doc.opensuse.org/projects/YaST/openSUSE11.3/tdg/id_ycp_data_string.ht... Therefore all "YCP String Builtins" as listed in http://doc.opensuse.org/projects/YaST/openSUSE11.3/tdg/Book-YaSTReference.ht... must work with UTF8 encoded strings. In this context https://bugzilla.novell.com/show_bug.cgi?id=446996#c16 "Multibyte strings are an area of the YCP language that missed the train when SUSE switched to UTF8 arouns SL 8" looks really surprising - at least from my point of view - oor I completely misunderstand something here... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.