Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #613

Closed
Open
Created 13 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Files in DOS encoding (Cyrillic (Windows 866))

Closed

Files in DOS encoding (Cyrillic (Windows 866))

Created by: xbreaker

I'm create a repo and push files in DOS encoding, when I try to view this files in gitlabhq, I get a error 500 from server.

Changed file encoding to UTF-8 and push again - all russian words git considered changing, but now the file views normal, including commit, where I can see the deleted row in DOS encoding and the new lines in UTF-8 encoding.

Any ideas? How learn git system understand DOS encoding?

Linked issues
0

Related merge requests

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: xbreaker

    Stoped the nginx server and started gitlabhq as rails app. When I try to view file in DOS encoding:

    Started GET "/test/3abeffc0dd3bb1c9fd766dc6874492a00683b80c/tree/sk.mac" for 192.168.251.42 at 2012-03-30 10:34:25 +0400
    Processing by RefsController#tree as HTML
      Parameters: {"project_id"=>"test", "id"=>"3abeffc0dd3bb1c9fd766dc6874492a00683b80c", "path"=>"sk.mac"}
    could not find any magic files!
    could not find any magic files!
    could not find any magic files!
    could not find any magic files!
    could not find any magic files!
    could not find any magic files!
    could not find any magic files!
    could not find any magic files!
      Rendered refs/_tree_file.html.haml (80.2ms)
      Rendered refs/_tree.html.haml (86.1ms)
    cache: [GET /test/3abeffc0dd3bb1c9fd766dc6874492a00683b80c/tree/static.css] miss

    And in browser I get a 500 server error.

    Request URL:http://:3000/test/3abeffc0dd3bb1c9fd766dc6874492a00683b80c/tree/sk.mac
    Request Method:GET
    Status Code:500 Internal Server Error

    By Administrator on 2012-03-30T06:38:42 (imported from GitLab project)

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: dubcanada

    This is a charlock_holmes issue, you may want to look at https://github.com/brianmario/charlock_holmes/blob/master/README.md (under the Installation area) and try those commands. It might fix your issue.

    By Administrator on 2012-03-31T02:43:48 (imported from GitLab project)

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: xbreaker

    dubcanada thx for you comment. Yes, now I'm trying CharlockHolmes transcoding before the the view DOS file.

    By Administrator on 2012-03-31T07:07:41 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
Assign to
Milestone
No milestone
None
None
Time tracking
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
participants
Reference:

Menu

Projects Groups Snippets
Help