Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-2244

Committing without -m or --file commandilne options nullifies the "log-encoding" config setting and the "--encoding" option

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.1.x
    • Fix Version/s: 1.2.0
    • Component/s: cmdline client
    • Labels:
      None
    • Environment:

      Linux

      Description

      I set my log-encoding option to euc-kr and that option always works if I pass 
      log messages with -m or --file switch.
      When committing without -m and --file switches, however, neither the config 
      setting "log-encoding" nor the switch "--encoding" seem to work after editting 
      log messages in an external editor (vi in my case).
      The situation follows :
      
       > svn commit   (log-encoding has been set to euc-kr inside a config file)
      
       ... editing the log message (including some euc-kr characters) in vi
       ... and exit
      
       svn: Commit failed (details follow):
       svn: Valid UTF-8 data
       (hex: 5b 42 75 66 66 65 72 20 64 65 73 63 72 69 70 74 6f 72)
       followed by invalid UTF-8 sequence
       (hex: c0 c7 20 76)
      
      Things are the same even when I pass the --encoding euc-kr switch to svn 
      command.
      The same text that I edited in the vi is accepted as a log message when passed 
      using -m or --file switch.
      

      Original issue reported by autumnway

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              subversion-importer Subversion Importer
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: