scanner is confused by utf8 text
In R13 the restriction to Latin1 is lifted, we have to support utf8: use R13 scanner and also see if Eclipse's encoding settings have to be adjusted.
Leave a comment
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 09:54 *
By Vlad Dumitrescu
Milestone changed from backlog to 1.0
Milestone changed from backlog to 1.0
Updating tickets (#194, #200, #208, #217, #218, #220, #221, #224, #229, #241, #245, #252, #261, #265, #274, #276, #278, #280, #281, #283, #285, #291, #294, #298, #307, #316, #317, #318, #326, #331, #332, #335, #336, #338, #339, #342, #343, #348, #56, #69, #87, #106, #144, #166, #195, #198, #234, #255, #264, #277, #313, #328, #344, #123)
Updating tickets (#384, #389, #396, #64, #291, #352, #358, #393, #398, #399, #41, #46, #52, #57, #61, #83, #93, #100, #111, #115, #135, #145, #148, #149, #152, #155, #159, #163, #181, #182, #194, #200, #208, #217, #218, #220, #221, #224, #229, #261, #265, #274, #280, #281, #283, #285, #294, #298, #307, #316, #318, #331, #332, #335, #336, #338, #348)
on 2009-07-17 15:54 *
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.