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

[QnA maker] When exporting letters with accents, output is not correct. #1057

Closed
ancorrg opened this issue Nov 20, 2020 · 2 comments
Closed
Assignees
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. customer-reported Issue is created by anyone that is not a collaborator in the repository.

Comments

@ancorrg
Copy link

ancorrg commented Nov 20, 2020

Versions

@microsoft/botframework-cli/4.11.0 win32-x64 node-v12.19.0
Powhershell

Describe the bug

I'm trying to export an existing kb from a qnamaker service and replace another one in other service with its contents. The original KB is in spanish and has accents and ñ characters. When I export the KB, the content is encoded in a way that can't be used in the destination KB.

To Reproduce

Steps to reproduce the behavior:

1 bf qnamkaer:kb:export --kbId {id} --subscriptionKey {key} --qnaFormat > qnaEs.qna
2 bf qnamaker:kb:replace --in qnaEs.qna --kbId {destinationKB} --subscriptionKey {destinationKey}

Expected behavior

The commands should export and import special characters for languages that are not english.

Additional context

[bug]

@munozemilio munozemilio self-assigned this Nov 20, 2020
@johnataylor johnataylor added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Issue is created by anyone that is not a collaborator in the repository. labels Nov 20, 2020
@munozemilio
Copy link
Member

Hello @ancorrg. Thanks a lot for reporting this issue. I just created a kb with special characters in it and the command is working fine which suggests the issue might be on the powershell configuration. You can double check this by running the command on a different terminal like bash.
This is what my test looked like:
Screen Shot 2020-11-23 at 4 52 52 PM
Let me know if changing the configuration for PS worked for you.

@feich-ms
Copy link
Contributor

@munozemilio there is another issue here microsoft/botframework-solutions#3723 to track the similar issue, I made a PR #1065 to add --out support for kb export. Hope this works. Could you help to review?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. customer-reported Issue is created by anyone that is not a collaborator in the repository.
Projects
None yet
Development

No branches or pull requests

4 participants