Issue: Japanese strings is collaped by File System connector

(1) Share

Report

Posted on by yoshihirok

1,724

I want to use Japanese string at path, filename, file content by File System connector.

Issue: Japanese string of filename, file content is collaped by File System connector.

Japanese strings of File name, File Path, File Content is collaped.

My environment of server.

OS: Windows Server 2012 R2 Standard Japanese

On-Premises data gateway: Install on this server.

File name in Japanese: bcd1 - コピー.txt

Trigger: File System - When a file is added or modifed

Regards,

Yoshihiro Kawabata

Categories:

General topics

All responses (7)

Answers (0)

Sort by

v-monli-msft Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

I have reported your issue to the product team. Thanks for your report.

Regards,

Mona
yoshihirok 1,724 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @v-monli-msft

Thank you for reporting.
I 'm waiting fix this issue.

Regards,
Yoshihiro Kawabata
masisley on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Yoshihiro,

I've reproed your problem and sent mail to the team that owns this connector. I'll report back once they've responded.

Best,

Mark
yoshihirok 1,724 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @masisley thank you reporting, sending to the team.

I 'm waiting the respond, or fix.

Regards,
Yoshihiro Kawabata
masisley on at

Like
a
(1)

Report
Copy link

Link copied!
Hi Yoshihiro,

Following is the response I received from the File connector owner:

"Potentially, there could be two known issues. Both of them belong to all file-based connectors:

Filename and path: currently we are working on it. The plan is to return only metadata from the trigger and let users to get a content in a following action by Id. Some connectors, like FTP, already have additional parameter “include file content” for the trigger.

File content: we faced a problem with “.txt” files with specific encoding like ISO-8859-1. In that case you can receive corrupted file’s content. You should use UTF-8 for the content encoding to avoid that or change file’s extension to “.bin”, for example, to preserve file’s content as is."
It looks like on your side, you could try using UTF-8 for file content. Unfortunately, we may have to wait for the mentioned improvements before filename is fully supported.

Best,

Mark
yoshihirok 1,724 on at

Like
a
(0)

Report
Copy link

Link copied!

HI @masisley thank you for your information.

Filename / Path:
I'm waiting to fix it.

File content:
I hope encoding option, th reason why a lot of case encoding is Shift-JIS in Japan.

Regards.
Yoshihiro Kawabata
dev001 2 on at

Like
a
(0)

Report
Copy link

Link copied!

@masisley
any update on this issue yet?
i got the same problem here :((