Community
Participate
Working Groups
Remote file types like "executable" are determined by matching the classification with preset textual patterns. This matching is currently based on English and has no translation. Because of this, when running in other languages, such as Japanese, the classifier is not able to determine whether or not a given file is an executable or not and in turn, actions that are contributed to work against "executable" files don't work in these environments. While it would be nice to see the classification field displayed in the appropriate language when viewing the property sheet, I think having the correct function is more important. For file classification, we can run the "file" command using LANG=en_US but also provide the option (via a JVM property) to use the default language.
Created attachment 198726 [details] patch to default classification LANG to en_US
Xuan, could you please review this?
The fix looks good. Thanks.
Thanks for the review, Xuan.