Menu

#129 Korean letters aren't valid in identifiers

2.3.22
closed-fixed
nobody
None
5
2015-02-28
2006-06-01
Anonymous
No

Dear Manager.

What can I do, if I want to use variable with unicode
(like $MY_KOREAN_LETTER )?

[I think that is because you implemented
SimpleCharStream read only ASCII characters (without
unicode processing).]

freemarker.core.ParseException: Token manager error:
freemarker.core.TokenMgrError: Lexical error at line
1, column 27. Encountered: "\uace0" (44256),
after : ""
at freemarker.template.Template.<init>
(Template.java:143)
at freemarker.template.Template.<init>
(Template.java:158)
at test.ManyTest.test1(ManyTest.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0
(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:154)

Discussion

  • Nobody/Anonymous

    Logged In: NO

    Strange... FreeMarker doesn't use US-ASCII, and in fact I
    have already used templates that used hunagrian variable
    names, which are not even ISO-8859-1. And they have worked.
    Still, it doesn't like that korean letter, despite
    Character.isLetter() says that it's a letter.

     
  • Dániel Dékány

    This was fixed in 2.3.19.

     
  • Dániel Dékány

    • status: open --> closed-fixed
    • Group: --> undecided
     
  • Dániel Dékány

    • status: closed-fixed --> open-accepted
     
  • Dániel Dékány

    • summary: freemarker.core.TokenMgrError: Lexical error --> Korean letters aren't valid in identifiers
     
  • Dániel Dékány

    • status: open-accepted --> open-fixed
    • Group: undecided --> 2.3.22
     
  • Dániel Dékány

    • Status: open-fixed --> closed-fixed
     

Log in to post a comment.