Enable Non-Latin1 text for name fields

ok. so it seems this would be the step to remove the restircion on the gui

/var/www/html/admin/common/script.js.php
line
-657 {   return ( ((c >= "a") && (c <= "z")) || ((c >= "A") && (c <= "Z")) || (c == " ") || (c == "&") || (c == "'") || (c == "(") || (c == ")") || (c == "-") || (c == "/"))

/var/www/html/admin/common/script.js.php
line
+657 {   return ( ((c >= "a") && (c <= "z")) || ((c >= "A") && (c <= "Z")) || ((c >= "א") && (c <= "ת")) || (c == " ") || (c == "&") || (c == "'") || (c == "(") || (c == ")") || (c == "-") || (c == "/"))

However the field gets written to the sql in giberish. Is the gui screwing it up? My browsers (firefox) encoding? Im using utf-8 does Linux have a problem with Hebrew?

Update: Thanks to cuco for this. The sql is actualy saving fine. The problem is mainly when the gui puts the extension name in the caller id field. A picture is worth a thousand words. have a look!

The checking for non Latin1 chars was done to avoid SQL injections. It's not a high priority to have UTF-8 support in field names, since anyway most of the devices will not be able to show BIDI or CJK.

I will find some time to fix the display issues, but I will leave the JS test, which means you cannot enter then from the WEB GUI. If those names are in the SVN, cool, freePBX will display them. But you will not be able to enter them.

(unless someone shows a better JS test for those strings)

I also changed the name of this bug from: "Enable Hebrew text for name fields" to: "Enable Non-Latin1 text for name fields"

I am pro this feature request, but just for documentation, will leave my experience with that, so if that happens again, people will have some clue about it.

I saw a really strange thing happening with asterisk when you use non-standard chars (anything not just letters and digits and spaces, specially letter with accents) in the extension name. It seems very harmless, but maybe the problem was because that names end up in the caller ID of the extension while making a call and asterisk goes crazy.

We spent a few months searching for the cause in an asterisk population of about 200 servers, and after we casually located and isolated it, it became somewhat clear (even not happening 100% of the time). The call will last for about 5 to 10 seconds and will drop, no explanation. (we had modified freepbx to allow accents).

Here in Brazil it is very common to have accents in letters in the persons names, so we had plenty and the problem was epidemic. After banning them, no more cases happened. This was with asterisk 1.0 (mainly) and asterisk 1.2 (a few).

Dup of #1955