Prevent GIT from changing automatically character encoding
I face a problem as below. Please give me a solution. Thanks in advance!
I use Linux OS (ubuntu)
Initially, I checkout new branch with the file test.properties
file encoding:
test.properties: text/plain; charset=unknown-8bit
Intellij Seting file encoding:
on Browser, the text show like:
# 基本情報
I only add '#' character for one line, then I commit file, push my_branch to my repository
I run git diff command:
git diff
-# <8A><EE><96>{<8F><EE><95><F1>
+## u57FAu672Cu60C5u5831
.... other lines are also changed into UTF-8 encoding.
How can I prevent the problem? Simply, It just marks as below:
My expectation looks like this:
-# <8A><EE><96>{<8F><EE><95><F1>
+## <8A><EE><96>{<8F><EE><95><F1>
git intellij-idea property-files
edited Nov 16 '18 at 6:46
A.H.
46k117097
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
|
show 1 more comment
I face a problem as below. Please give me a solution. Thanks in advance!
I use Linux OS (ubuntu)
Initially, I checkout new branch with the file test.properties
file encoding:
test.properties: text/plain; charset=unknown-8bit
Intellij Seting file encoding:
on Browser, the text show like:
# 基本情報
I only add '#' character for one line, then I commit file, push my_branch to my repository
I run git diff command:
git diff
-# <8A><EE><96>{<8F><EE><95><F1>
+## u57FAu672Cu60C5u5831
.... other lines are also changed into UTF-8 encoding.
How can I prevent the problem? Simply, It just marks as below:
My expectation looks like this:
-# <8A><EE><96>{<8F><EE><95><F1>
+## <8A><EE><96>{<8F><EE><95><F1>
git intellij-idea property-files
edited Nov 16 '18 at 6:46
A.H.
46k117097
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
Could it be merely a matter of representation in the diff interface? Is the file coding really changed?
– matt
Nov 15 '18 at 3:52
@matt the file is also changed, when I open the file via browser. on browser, it shows ## u57FAu672Cu60C5u5831 instead of ## 基本情報 But, on IDE: it shows: ## 基本情報
– Mr Special
Nov 15 '18 at 3:55
First, read joelonsoftware.com/2003/10/08/… - then realize that Git itself doesn't even look at encoding, it just compares byte-strings. It leaves "encoding" up to other software. You need to convince the other software to deal with encoding in a way that behaves well for you; and Git is only going to deal with bytes.
– torek
Nov 15 '18 at 6:42
(Git does make one concession to encoding: it will, if you tell it to, put anencodingheader into a commit, to help other software decide how to treat the bytes in the commit log text.) Also, the reason these are comments is: it looks like IntelliJ does try to understand encodings, so maybe that's where to fiddle with this. But I know nothing about IntelliJ; this question is posted to git and gitlab, not intellij-idea, at least at the moment.
– torek
Nov 15 '18 at 6:42
@torek thanks your response. How can I put an encoding header into a commit ?
– Mr Special
Nov 15 '18 at 7:05
|
show 1 more comment
I face a problem as below. Please give me a solution. Thanks in advance!
I use Linux OS (ubuntu)
Initially, I checkout new branch with the file test.properties
file encoding:
test.properties: text/plain; charset=unknown-8bit
Intellij Seting file encoding:
on Browser, the text show like:
# 基本情報
I only add '#' character for one line, then I commit file, push my_branch to my repository
I run git diff command:
git diff
-# <8A><EE><96>{<8F><EE><95><F1>
+## u57FAu672Cu60C5u5831
.... other lines are also changed into UTF-8 encoding.
How can I prevent the problem? Simply, It just marks as below:
My expectation looks like this:
-# <8A><EE><96>{<8F><EE><95><F1>
+## <8A><EE><96>{<8F><EE><95><F1>
git intellij-idea property-files
edited Nov 16 '18 at 6:46
A.H.
46k117097
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
I face a problem as below. Please give me a solution. Thanks in advance!
I use Linux OS (ubuntu)
Initially, I checkout new branch with the file test.properties
file encoding:
test.properties: text/plain; charset=unknown-8bit
Intellij Seting file encoding:
on Browser, the text show like:
# 基本情報
I only add '#' character for one line, then I commit file, push my_branch to my repository
I run git diff command:
git diff
-# <8A><EE><96>{<8F><EE><95><F1>
+## u57FAu672Cu60C5u5831
.... other lines are also changed into UTF-8 encoding.
How can I prevent the problem? Simply, It just marks as below:
My expectation looks like this:
-# <8A><EE><96>{<8F><EE><95><F1>
+## <8A><EE><96>{<8F><EE><95><F1>
git intellij-idea property-files
git intellij-idea property-files
edited Nov 16 '18 at 6:46
A.H.
46k117097
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
edited Nov 16 '18 at 6:46
A.H.
46k117097
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
edited Nov 16 '18 at 6:46
A.H.
46k117097
edited Nov 16 '18 at 6:46
A.H.
46k117097
edited Nov 16 '18 at 6:46
A.H.
46k117097
46k117097
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
asked Nov 15 '18 at 3:46
Mr SpecialMr Special
12911
12911
Could it be merely a matter of representation in the diff interface? Is the file coding really changed?
– matt
Nov 15 '18 at 3:52
@matt the file is also changed, when I open the file via browser. on browser, it shows ## u57FAu672Cu60C5u5831 instead of ## 基本情報 But, on IDE: it shows: ## 基本情報
– Mr Special
Nov 15 '18 at 3:55
First, read joelonsoftware.com/2003/10/08/… - then realize that Git itself doesn't even look at encoding, it just compares byte-strings. It leaves "encoding" up to other software. You need to convince the other software to deal with encoding in a way that behaves well for you; and Git is only going to deal with bytes.
– torek
Nov 15 '18 at 6:42
(Git does make one concession to encoding: it will, if you tell it to, put anencodingheader into a commit, to help other software decide how to treat the bytes in the commit log text.) Also, the reason these are comments is: it looks like IntelliJ does try to understand encodings, so maybe that's where to fiddle with this. But I know nothing about IntelliJ; this question is posted to git and gitlab, not intellij-idea, at least at the moment.
– torek
Nov 15 '18 at 6:42
@torek thanks your response. How can I put an encoding header into a commit ?
– Mr Special
Nov 15 '18 at 7:05
|
show 1 more comment
Could it be merely a matter of representation in the diff interface? Is the file coding really changed?
– matt
Nov 15 '18 at 3:52
@matt the file is also changed, when I open the file via browser. on browser, it shows ## u57FAu672Cu60C5u5831 instead of ## 基本情報 But, on IDE: it shows: ## 基本情報
– Mr Special
Nov 15 '18 at 3:55
First, read joelonsoftware.com/2003/10/08/… - then realize that Git itself doesn't even look at encoding, it just compares byte-strings. It leaves "encoding" up to other software. You need to convince the other software to deal with encoding in a way that behaves well for you; and Git is only going to deal with bytes.
– torek
Nov 15 '18 at 6:42
(Git does make one concession to encoding: it will, if you tell it to, put anencodingheader into a commit, to help other software decide how to treat the bytes in the commit log text.) Also, the reason these are comments is: it looks like IntelliJ does try to understand encodings, so maybe that's where to fiddle with this. But I know nothing about IntelliJ; this question is posted to git and gitlab, not intellij-idea, at least at the moment.
– torek
Nov 15 '18 at 6:42
@torek thanks your response. How can I put an encoding header into a commit ?
– Mr Special
Nov 15 '18 at 7:05
Could it be merely a matter of representation in the diff interface? Is the file coding really changed?
– matt
Nov 15 '18 at 3:52
Could it be merely a matter of representation in the diff interface? Is the file coding really changed?
– matt
Nov 15 '18 at 3:52
@matt the file is also changed, when I open the file via browser. on browser, it shows ## u57FAu672Cu60C5u5831 instead of ## 基本情報 But, on IDE: it shows: ## 基本情報
– Mr Special
Nov 15 '18 at 3:55
@matt the file is also changed, when I open the file via browser. on browser, it shows ## u57FAu672Cu60C5u5831 instead of ## 基本情報 But, on IDE: it shows: ## 基本情報
– Mr Special
Nov 15 '18 at 3:55
First, read joelonsoftware.com/2003/10/08/… - then realize that Git itself doesn't even look at encoding, it just compares byte-strings. It leaves "encoding" up to other software. You need to convince the other software to deal with encoding in a way that behaves well for you; and Git is only going to deal with bytes.
– torek
Nov 15 '18 at 6:42
First, read joelonsoftware.com/2003/10/08/… - then realize that Git itself doesn't even look at encoding, it just compares byte-strings. It leaves "encoding" up to other software. You need to convince the other software to deal with encoding in a way that behaves well for you; and Git is only going to deal with bytes.
– torek
Nov 15 '18 at 6:42
(Git does make one concession to encoding: it will, if you tell it to, put an
encoding header into a commit, to help other software decide how to treat the bytes in the commit log text.) Also, the reason these are comments is: it looks like IntelliJ does try to understand encodings, so maybe that's where to fiddle with this. But I know nothing about IntelliJ; this question is posted to git and gitlab, not intellij-idea, at least at the moment.– torek
Nov 15 '18 at 6:42
(Git does make one concession to encoding: it will, if you tell it to, put an
encoding header into a commit, to help other software decide how to treat the bytes in the commit log text.) Also, the reason these are comments is: it looks like IntelliJ does try to understand encodings, so maybe that's where to fiddle with this. But I know nothing about IntelliJ; this question is posted to git and gitlab, not intellij-idea, at least at the moment.– torek
Nov 15 '18 at 6:42
@torek thanks your response. How can I put an encoding header into a commit ?
– Mr Special
Nov 15 '18 at 7:05
@torek thanks your response. How can I put an encoding header into a commit ?
– Mr Special
Nov 15 '18 at 7:05
|
show 1 more comment
1 Answer
1
active
oldest
votes
I've found out the cause. It comes from changing setting from IDE.
I unchecked Transparent native-to-ascii conversion as below: 
Ok, now the merge request only showed what was changed.
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53312134%2fprevent-git-from-changing-automatically-character-encoding%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've found out the cause. It comes from changing setting from IDE.
I unchecked Transparent native-to-ascii conversion as below:
Ok, now the merge request only showed what was changed.
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
add a comment |
I've found out the cause. It comes from changing setting from IDE.
I unchecked Transparent native-to-ascii conversion as below:
Ok, now the merge request only showed what was changed.
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
add a comment |
I've found out the cause. It comes from changing setting from IDE.
I unchecked Transparent native-to-ascii conversion as below:
Ok, now the merge request only showed what was changed.
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
I've found out the cause. It comes from changing setting from IDE.
I unchecked Transparent native-to-ascii conversion as below:
Ok, now the merge request only showed what was changed.
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
answered Nov 16 '18 at 6:33
Mr SpecialMr Special
12911
12911
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53312134%2fprevent-git-from-changing-automatically-character-encoding%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could it be merely a matter of representation in the diff interface? Is the file coding really changed?
– matt
Nov 15 '18 at 3:52
@matt the file is also changed, when I open the file via browser. on browser, it shows ## u57FAu672Cu60C5u5831 instead of ## 基本情報 But, on IDE: it shows: ## 基本情報
– Mr Special
Nov 15 '18 at 3:55
First, read joelonsoftware.com/2003/10/08/… - then realize that Git itself doesn't even look at encoding, it just compares byte-strings. It leaves "encoding" up to other software. You need to convince the other software to deal with encoding in a way that behaves well for you; and Git is only going to deal with bytes.
– torek
Nov 15 '18 at 6:42
(Git does make one concession to encoding: it will, if you tell it to, put an
encodingheader into a commit, to help other software decide how to treat the bytes in the commit log text.) Also, the reason these are comments is: it looks like IntelliJ does try to understand encodings, so maybe that's where to fiddle with this. But I know nothing about IntelliJ; this question is posted to git and gitlab, not intellij-idea, at least at the moment.– torek
Nov 15 '18 at 6:42
@torek thanks your response. How can I put an encoding header into a commit ?
– Mr Special
Nov 15 '18 at 7:05