git/list[1] front-page[2] threads[3] people[4] search[5] about
 

jgit problems for file paths with non-ASCII characters

From
Marc Strapetz <marc.strapetz@syntevo.com>
Date
Nov 25, 2009, 13:47 UTC
Message-ID
<4B0D356D.1080709@syntevo.com>

I have noticed that jgit converts file paths to UTF-8 when querying the repository. Especially, org.eclipse.jgit.treewalk.filter.PathFilter#PathFilter performs this conversion:

  private PathFilter(final String s) {
    pathStr = s;
    pathRaw = Constants.encode(pathStr);
  }

Because of this conversion, a TreeWalk fails to identify a file with German umlauts. When using platform encoding to convert the file path to bytes:

  private PathFilter(final String s) {
    pathStr = s;
    pathRaw = s.getBytes();
  }

the TreeWalk works as expected. Actually, the file path seems to be stored with platform encoding in the repository.

Is this a bug or a misconfiguration of my repository? I'm using jgit (commit e16af839e8a0cc01c52d3648d2d28e4cb915f80f) on Windows.

Thanks!

-- Best regards, Marc Strapetz ============= syntevo GmbH http://www.syntevo.com http://blog.syntevo.com

Next: Robin Rosenberg
Message 1 of 10 in “jgit problems for file paths with non-ASCII characters”
  1. Marc StrapetzNov 25, 2009
  2. Robin RosenbergNov 25, 2009
  3. Shawn O. PearceNov 26, 2009
  4. Thomas SingerNov 26, 2009
  5. Johannes SchindelinNov 26, 2009
  6. Thomas SingerNov 26, 2009
  7. Shawn O. PearceNov 26, 2009
  8. Robin RosenbergNov 26, 2009
  9. Marc StrapetzNov 26, 2009
  10. Shawn O. PearceNov 26, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.