Dear Atlassian-team
I'm Japanese and am currently using Japanese character(Shift-JIS) set.
I would like to inquire the regarding the source code comment from PullRequest.
The comment were unreadable. The correct character should be UTF-8, however the
one I got is SJIS code.
I tried fixing it by switching the google chrome extension character set to Shift-JIS
but it didn't work out.
Do you have any ideas/ways on how to solve this issue.
Sincerely yours,
Jun Takaba
Hi @Jun Takaba,
Thank you for reporting this.
Are you able to reproduce this issue? I can open a bug report for our development team to investigate and it would be helpful to see an instance of this issue occurring for the purposes of the investigation.
I have created a public repo in one of my workspaces and also a PR in it:
https://bitbucket.org/teamfortesting/test-repo/pull-requests/1
Would it be possible for you to leave a comment in that PR using the same characters that do not get encoded correctly, so we can look into itthis? I can then create a bug report and also link to this example so we can investigate further.
Please feel free to let me know if you have any questions.
Kind regards,
Theodora
Dear @Theodora Boudale
Thank you for your reply.
And I couldn't reproduce this issue on follwong URL, because this issue happen in text.
https://bitbucket.org/teamfortesting/test-repo/pull-requests/1
Attahced picture (sample_pullrequest.png) is a sampel PllRequest for understanding this issue.
- Shift-JIS_text.txt
- line 3: Yellow line is a text by using Shift-JIS (text garbled happen)
- UTF-8_text.txt
- line 2: This text is created by UTF-8 and we can read it.
Do you have any ideas/ways on how to solve this issue.
Best Regards,
Jun Takab
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Jun Takaba,
I'm afraid this is a known issue on Bitbucket Cloud. Currently, Bitbucket Cloud supports only the UTF-8 format. As a result, it will treat files with other encoding formats as a UTF-8 format, that's why you're seeing the garbled or byte text in your encoded file.
We have the below feature request to allow specifying a repository's encoding:
I have linked your question internally to the feature request. Our development team will update the above request when there is any progress made. Hence I would suggest keeping a watch and vote for it. Do note that all feature requests are implemented with this policy in mind:
Kind regards,
Caroline
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your information.
I could understand this issue's status.
I will watch following ticket.
https://jira.atlassian.com/browse/BCLOUD-7239
Best Regards,
Jun Takaba
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.