[asterisk-bugs] [Asterisk 0014022]: AEL ¯o("arg") with UTF-8 argument incorrectly compiles into dialplan
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Dec 10 10:44:57 CST 2008
The following issue has been ASSIGNED.
======================================================================
http://bugs.digium.com/view.php?id=14022
======================================================================
Reported By: wetwired
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 14022
Category: PBX/pbx_ael
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: 1.4.22
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-12-05 02:34 CST
Last Modified: 2008-12-10 10:44 CST
======================================================================
Summary: AEL ¯o("arg") with UTF-8 argument incorrectly
compiles into dialplan
Description:
AEL ¯o expression used with UTF-8 argument (Russian in my case)
incorrectly compiles into dialplan. It was broken in Asterisk 1.4.22-rc4.
In Asterisk 1.4.22-rc3 and earlier and also in 1.6.0.1 everything is OK.
======================================================================
----------------------------------------------------------------------
(0096103) svnbot (reporter) - 2008-12-10 10:44
http://bugs.digium.com/view.php?id=14022#c96103
----------------------------------------------------------------------
Repository: asterisk
Revision: 162671
U branches/1.4/pbx/ael/ael.flex
U branches/1.4/pbx/ael/ael_lex.c
------------------------------------------------------------------------
r162671 | murf | 2008-12-10 10:44:56 -0600 (Wed, 10 Dec 2008) | 22 lines
(closes issue http://bugs.digium.com/view.php?id=14022)
Reported by: wetwired
Tested by: murf
I checked, and I added a mod to the trunk version
of Asterisk that would make it 8-bit transparent
on 27 Nov 2007, but I made no such updates to
1.4. My best guess is that 1.4 was released, and
it was not appropriate to commit an enhancement.
But I'm going to add the same fixes to 1.4 now,
for the following reasons:
1. wetwired is correct; 1.4 is **mostly** 8-bit
transparent now. This is because the lexical
token forming rules use . in most 'word'
state continuances. It's just the beginning
of a 'word' that is picky.
2. Accepting 8-bit chars in some places and
not others leads to bug reports like this.
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=162671
Issue History
Date Modified Username Field Change
======================================================================
2008-12-10 10:44 svnbot Note Added: 0096103
2008-12-10 10:44 svnbot Status feedback => assigned
======================================================================
More information about the asterisk-bugs
mailing list