Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with japanese. #151

Closed
loongdefect opened this Issue Aug 8, 2018 · 10 comments

Comments

Projects
None yet
3 participants
@loongdefect
Copy link

commented Aug 8, 2018

Hi all,
I create document with data have text is japanese.
But when insert to cosmos DB it display is ????.
I using .Net display is ok.
You can make request with header "application/json;charset=UTF-8"

Reagrds,

@PlagueHO

This comment has been minimized.

Copy link
Owner

commented Aug 13, 2018

Hi @loongdefect - thank you for raising this! I'll try and get this change through in the weekend. Thanks for your patience.

@PlagueHO

This comment has been minimized.

Copy link
Owner

commented Aug 17, 2018

Hi @loongdefect - can you give me an example of your usage so I can ensure I'm testing for it and the problem is solved?

@PlagueHO PlagueHO self-assigned this Aug 17, 2018

@loongdefect

This comment has been minimized.

Copy link
Author

commented Aug 24, 2018

Hi @PlagueHO ,
Json Example:

$json = @{
                        name = "杉本 司"
                        username = "杉本 司"
                        firstname = "司"
                        lastname = "杉本"
                    }
@PlagueHO

This comment has been minimized.

Copy link
Owner

commented Aug 24, 2018

Thank you @loongdefect - I'll put some tests together to cover this and add the required changes this weekend. Thank you!

@eladhay

This comment has been minimized.

Copy link

commented Oct 21, 2018

Hi,
Any news on this? I have the same issue with Hebrew text.
I'm guessing all Unicode characters need to be supported.

@PlagueHO PlagueHO added in progress and removed help wanted labels Oct 21, 2018

@PlagueHO

This comment has been minimized.

Copy link
Owner

commented Oct 21, 2018

Hi @eladhay - this one slipped my mind, but I'm trying to sort it now. Just to confirm, this is when calling New-CosmosDbDocument that problems occur or also in Get-CosmosDbDocument?

@PlagueHO

This comment has been minimized.

Copy link
Owner

commented Oct 21, 2018

Also @eladhay - are you using UTF8 in the Id as well or just the body - any example PowerShell you're using would be very helpful so I can use it to generate tests for your specific scenarios. Thank you!

@PlagueHO PlagueHO closed this in ed63d69 Oct 22, 2018

@eladhay

This comment has been minimized.

Copy link

commented Oct 22, 2018

Both for New-CosmosDbDocument and Get-CosmosDbDocument. In my case, the Ids are numbers.
Here's my PowerShell example. I replaced the variables for hard-coded values.

$instituteDocument = @" {"id": "123456", "displayName": "אהבה", "city": "כפר ביאליק", "principalName": "יסודי ועליונה", "ageGroup": "משה אופניק", "type": "מיוחד", "inspection": "ממלכתי", "sector": "משולב`"
}
"@;

Send the document creation request.

New-CosmosDbDocument -Context:$cosmosDbContext -CollectionId:'Institutions' -DocumentBody:$instituteDocument;
`

@PlagueHO

This comment has been minimized.

Copy link
Owner

commented Oct 22, 2018

I'm just releasing the change to PowerShell Gallery now. It'll be part of 2.1.10.

It adds a new -Encoding parameter to New-CosmosDBDocument and Set-CosmosDBDocument that can be set to 'UTF-8'.

@PlagueHO

This comment has been minimized.

Copy link
Owner

commented Oct 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.