zopencommunity / zopencommunity/gitport
Handling of mixed-codepage files in git
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 10
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
We have some mixed-codepage files that are in mostly ibm-1047 but mixed with other codepage such as Japanese.
We can use -text in .gitattributes to check in the files, however using this approach we will lose the ability to do blame/diff the part that are in text (ibm-1047 code).
Perhaps a solution will be to support zos-working-tree-encoding=ibm-1047 -text in .gitattributes?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how .gitattributes handles -text and text portions of mixed-codepage files, with particular attention to the proposed zos-working-tree-encoding=ibm-1047 -text form. Determine the relevant entry points and tests before implementing support. Done means mixed files can be checked in while preserving blame and diff for their ibm-1047 text portions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100