You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Assigned) (JIRA)" <ji...@apache.org> on 2011/10/03 21:24:34 UTC

[jira] [Assigned] (JENA-129) RIOT not parsing UTF combining characters correctly

     [ https://issues.apache.org/jira/browse/JENA-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne reassigned JENA-129:
----------------------------------

    Assignee: Andy Seaborne
    
> RIOT not parsing UTF combining characters correctly
> ---------------------------------------------------
>
>                 Key: JENA-129
>                 URL: https://issues.apache.org/jira/browse/JENA-129
>             Project: Jena
>          Issue Type: Bug
>          Components: RIOT
>         Environment: Java 1.6, Windows 7, ARQ 2.8.8
>            Reporter: Tim Harsch
>            Assignee: Andy Seaborne
>              Labels: RIOT
>
> Background on the issue can be found at the list archive:
> http://mail-archives.apache.org/mod_mbox/incubator-jena-users/201110.mbox/%3C4E88320C.8040300@apache.org%3E
> RIOT failed to parse the SPARQL 1.0 DAWG test: "i18n/normalization-01.ttl".
> In offline email Andy also noted:
> I see one oddity:
> [[
> ==== DAWG-Final/i18n/normalization-02.ttl
> WARN  [line: 7, col: 8 ] Bad IRI: <eXAMPLE://a/b/%63/%7bfoo%7d#xyz>
> Code: 8/NON_INITIAL_DOT_SEGMENT in PATH: The path contains a segment
> /../ not at the beginning of a relative reference, or it contains a /./
> These should be removed.
> ]]
> because the test is on the input, not the resultant form used for toString.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira