You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@creadur.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2011/08/15 07:06:27 UTC

[jira] [Commented] (RAT-96) Check source files for unexpected encodings

    [ https://issues.apache.org/jira/browse/RAT-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084963#comment-13084963 ] 

Stefan Bodewig commented on RAT-96:
-----------------------------------

Encodings are pretty hard to detect.  Current trunk of the license scanning RAT (what initially was RAT) will flag files that contain characters that cannot be decoded using the platform's default as binaries, which should give you a clue. 

The license adding part of RAT  will be seriously thrown off by text files that use a different encoding than the platform's default.

> Check source files for unexpected encodings
> -------------------------------------------
>
>                 Key: RAT-96
>                 URL: https://issues.apache.org/jira/browse/RAT-96
>             Project: RAT
>          Issue Type: New Feature
>            Reporter: Sebb
>
> Idea for possible enhancement:
> Source files with characters in encodings other than ASCII can easily get mangled, so it might be worth offering a tool to report these.
> For example, I have come across Javadoc which uses dashes instead of hyphens, and at some point the encoded dash got corrupted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira