-
Suggestion
-
Resolution: Unresolved
SVNKit renders diffs with the file encoding specified in the 'file.encoding' FISHEYE_OPTS parameter, and UTF-8 by defualt. This can be problematic if a repository contains mixed file encodings because when non-UTF8 files are written to a UTF-8 file the line ending character can be clobbered and the contents of the next line can end up on the current line. This causes problems for FIshEye's diff parser because it expects the number of lines specified in the unified diff header to match the number of lines in the diff hunk.
Investigate what it will take to support mixed encoding repositories properly.
[FE-4477] Properly support SVN repositories with mixed character encodings
Fix Version/s | New: N/A [ 54414 ] |
Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
Labels | New: jac-cleanup-phase7 |
Workflow | Original: JAC Suggestion Workflow [ 3022166 ] | New: JAC Suggestion Workflow 3 [ 3641844 ] |
Component/s | New: Indexing [ 41890 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2948354 ] | New: JAC Suggestion Workflow [ 3022166 ] |
Workflow | Original: FECRU Development Workflow - Triage [ 945076 ] | New: Confluence Workflow - Public Facing v4 [ 2948354 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 126251 ] |
Workflow | Original: FECRU Development Workflow (Triage) [ 461481 ] | New: FECRU Development Workflow - Triage [ 945076 ] |