Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2766

CSV importer always assumes default jvm character encoding

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Low Low
    • None
    • None
    • None
    • None

      This is a problem if the csv contains non-latin characters.

      I looked in the source code and crowd creates a new FileReader(). This constructor uses the platform default encoding which is usually not utf-8. We should force this to be utf-8. '

      Support case here:
      https://support.atlassian.com/browse/CWDSUP-6149

            [CWD-2766] CSV importer always assumes default jvm character encoding

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1509964 ] New: JAC Bug Workflow v3 [ 3364867 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392595 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1509964 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 364161 ] New: Simplified Crowd Development Workflow v2 [ 1392595 ]
            joe made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            joe made changes -
            Link New: This issue is superseded by CWD-2772 [ CWD-2772 ]

            joe added a comment -

            Crowd should be running with UTF-8. It isn't when it's started as a service, and that's a bug that needs to be fixed.

            joe added a comment - Crowd should be running with UTF-8. It isn't when it's started as a service, and that's a bug that needs to be fixed.
            joe made changes -
            Link New: This issue is related to CWD-2771 [ CWD-2771 ]

            joe added a comment -

            Crowd's startup scripts are already setting -Dfile.encoding=UTF-8 to force the JVM's default encoding, and misinterpreting UTF-8 shouldn't affect CSV tokenization. I'll take a look at the original CSV file.

            joe added a comment - Crowd's startup scripts are already setting -Dfile.encoding=UTF-8 to force the JVM's default encoding, and misinterpreting UTF-8 shouldn't affect CSV tokenization. I'll take a look at the original CSV file.
            RyanA created issue -

              Unassigned Unassigned
              rackley RyanA
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: