Open Source Training Seminar FreePBX Paid Support

Ticket #1955 (reopened Bugs)

Opened 1 year ago

Last modified 2 months ago

Enable Non-Latin1 text and characters for name fields

Reported by: lazytt Assigned to:
Priority: minor Milestone: 3.0
Component: Languages / Translation Version:
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

This has been requested many times, so i decided to consolidate all the request here:

Lazytt: Most fields generate an error when I try to save them with hebrew text. (#1729)

andrew4455: The display name doesn't allow the inputting of data in Lastname, Firstname format. It seems the , character is invalid. This would be useful so that you can get alphabetically sorted lists by last name for extensions, and other features, such as FOP. (#1880)

djelibeybi: If you try entering a name like "Patrick O'Toole" in the Display Name field, FreePBX complains about not having an outbound CID configured. However, if you remove the apostrophe, it works fine. (#1532)


The reason for all the restriction is basically summed up by rob:

"...but allowing users to use ' in names won't be fixed for a while yet, possibly until 3.0, to avoid SQL injection errors."

Change History

06/25/07 07:23:28 changed by p_lindheimer

  • owner deleted.
  • version changed from 2.2.1 to 2.3-branch.
  • component changed from - choose - to Languages / Translation.

08/01/07 02:12:41 changed by wvroger

  • milestone changed from 2.3 to 3.0.

08/01/07 17:16:53 changed by p_lindheimer

  • version changed from 2.3-branch to SVN-HEAD.

12/05/07 08:40:45 changed by p_lindheimer

  • status changed from new to closed.
  • confirmation set to Confirmed.
  • resolution set to fixed.

The three tickets references all show closed so I am closing this based on that observation.

12/06/07 01:41:31 changed by lazytt

  • status changed from closed to reopened.
  • resolution deleted.

This has been requested many times, so I decided to consolidate all the request here 

consolidate:  to join together into one whole

see here for more info

12/06/07 02:12:53 changed by p_lindheimer

lazytt - the links is dead but, sorry, I mis-understood that you had closed the bugs because you opened this one in their place.

12/06/07 09:18:01 changed by pnlarsson

There is some intresting stuff going on in the asterisk trunk to support utf8:

http://svn.digium.com/view/asterisk/team/oej/calleridutf8/README.thisbranch?view=markup&pathrev=89568

and murfs:

http://svn.digium.com/view/asterisk/team/murf/utf8-whatif/

12/07/07 01:51:25 changed by lazytt

here is a hint. Most valuable is the lesson learned: 

LESSON LEARNED: KEEP EVERYTHING IN UTF-8, ABSOLUTELY EVERYWHERE, FROM DAY ONE.

You’ll be glad you did some day.

12/07/07 09:40:12 changed by p_lindheimer

lazytt:

The information is interesting and probably useful (I have not looked) to capture here. But I need a developer to join the team who has a vested interest in cleaning up the whole localization and language side of things. It's not a lack of interest on any of our parts, it's a lack of relative priority to us. If someone wants to come forward and get involved, we will provide access to them to help start working on this. (Dialplan and Code side).

02/09/08 12:38:38 changed by p_lindheimer

  • version deleted.
  • milestone changed from 2.4 to 3.0.

bumping to next milestone, can backport if appropriate.

07/05/08 14:04:26 changed by lazytt

  • milestone changed from 2.5 to 3.0.

bumping as i dont this happening any time soon

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads