[ https://issues.apache.org/jira/browse/OLINGO-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580002#comment-14580002 ]
Michael Bolz commented on OLINGO-689: ------------------------------------- Hi [~Sebastien], during my validation I found the same restriction of Java 6 in which the {{Pattern}} only supports {{\xhh}} for hexadecimal value. Unfortunately we decided to only use Java 6 for Olingo V2, so it will be not possible to use your suggested solution. I will check for another solution and how Olingo can/should support the unicode characters allowed in the OData V2 specification. Best regards, Michael > Olingo 2 unicode name suport > ---------------------------- > > Key: OLINGO-689 > URL: https://issues.apache.org/jira/browse/OLINGO-689 > Project: Olingo > Issue Type: Bug > Components: odata2-core > Affects Versions: V2 2.0.4 > Environment: Windows 7 64 bit > Reporter: Sébastien Lévêque > Assignee: Michael Bolz > Attachments: Test.java > > > It’s seem that are some issues with regular expression in class > EdmNamedImplProv. > > The first one is about \\u00C0\\u00D6 part. It should be \\u00C0-\\u00D6 as > it’s only alphabetic characters. > With current implementation Õ Ä can’t be used but Ö À can be used. > > The second issue is about \\x10000-\\xEFFFF, range only available for first > character, but not the following ones (another bug ?). > \x????? is not supported in regular expression. > It should be \x?? (2 and only 2 characters) or \x{?????}. > This part is splited like \\x10, 0 (twice), 0 to \\xEF, F (3 time). > This make some characters valid at first position like numeric characters or > "×" (\u00D7) multiplication sign. > But at the beginning of the expression there is > \\u00C0\\u00D6\\u00D8-\\u00F6, means that \u00D7 should not be allowed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)