scanner - uses ISO8859-1
It should handle utf8 in newer versions (from R12B-5?)
When R13B comes around, should use the improved scanner from OTP
When R13B comes around, should use the improved scanner from OTP
Leave a comment
on 2009-04-09 07:39 *
By Vlad Dumitrescu
Milestone changed from 0.7 to backlog
Milestone changed from 0.7 to backlog
Updating tickets (#217, #218, #219, #220, #221, #223, #224, #229, #239, #240, #241, #244, #245, #261, #265, #274, #278, #280, #281, #283, #285, #298, #307, #318, #326, #331, #332, #335, #336, #338, #342, #348, #216, #237, #247, #255, #264, #277, #321, #328, #113, #114, #129, #131, #211, #222, #231, #242, #256, #323, #325, #150, #172, #252, #276, #291, #294, #316, #317, #339, #340, #343, #44, #195, #234, #249, #313, #314, #344, #228, #160, #173, #235, #238)
on 2009-04-09 07:46 *
By Vlad Dumitrescu
Milestone changed from backlog to 1.0
Milestone changed from backlog to 1.0
Updating tickets (#133, #134, #40, #55, #79, #98, #113, #114, #120, #125, #129, #131, #137, #147, #157, #176, #177, #179, #204, #211, #222, #228, #256, #323, #325, #41, #45, #46, #52, #57, #61, #64, #76, #83, #93, #95, #100, #111, #115, #119, #130, #135, #145, #148, #149, #150, #152, #155, #156, #159, #163, #164, #168, #170, #172, #173, #181, #182)
on 2009-07-17 13:52 *
By Vlad Dumitrescu
Status changed from New to Invalid
Status changed from New to Invalid
For now, one shouldn't have UTF-8 text in source files: http://erlang.org/doc/apps/stdlib/unicode_usage.html
2.3 Basic language support for Unicode
First of all, Erlang is still defined to be written in the ISO-latin-1 character set. Functions have to be named in that character set, atoms are restricted to ISO-latin-1 and regular strings are still lists of characters 0..255 in the ISO-latin-1 encoding. This has not (yet) changed, but the language has been slightly extended to cope with Unicode characters and encodings.
....
Also the source code is (for now) still expected to be written using the ISO-latin-1 character set, why Unicode characters beyond that range cannot be entered in string literals.
2.3 Basic language support for Unicode
First of all, Erlang is still defined to be written in the ISO-latin-1 character set. Functions have to be named in that character set, atoms are restricted to ISO-latin-1 and regular strings are still lists of characters 0..255 in the ISO-latin-1 encoding. This has not (yet) changed, but the language has been slightly extended to cope with Unicode characters and encodings.
....
Also the source code is (for now) still expected to be written using the ISO-latin-1 character set, why Unicode characters beyond that range cannot be entered in string literals.