[
https://issues.apache.org/jira/browse/UIMA-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868626#action_12868626
]
Jörn Kottmann commented on UIMA-1782:
-------------------------------------
In case an invalid encoding is chosen the dialog now shows a page error message
telling the user about the problem.
> Encoding of text files during import should be confugurable
> -----------------------------------------------------------
>
> Key: UIMA-1782
> URL: https://issues.apache.org/jira/browse/UIMA-1782
> Project: UIMA
> Issue Type: Improvement
> Components: CasEditor
> Affects Versions: 2.3
> Reporter: Thomas Hampp
> Assignee: Jörn Kottmann
> Fix For: 2.3.1
>
>
> During import of text files into a corpus it seems to be impossible to
> control the encoding used. Looks like the default platform encoding is used
> (Latin 1 on Western Windows systems). The Eclipse default encoding settings
> for text files don't seem to affect import encoding. That makes it impossible
> to import documents with international characters in UTF8.
> Ideally the encoding should be selectable in a drop down field in the import
> wizard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
