Non-ASCII file names are not displayed correctly by Android apps |
||
Issue description(reported by yawano@) Steps to reproduce: 1. Put any file on Drive with a file name which contains 2 bytes characters. e.g. "Chromebookについて.pdf" 2. Go to Files app, and open the file with an Android app. e.g. Google PDF viewer. 3. 2 bytes characters part of the file name is escaped. e.g. "Chromebook%E3%81....." Expected behavior: Those characters are not escaped. Observed behavior: 2 bytes characters are escaped.
,
Jan 29 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/31233e09db9e32c9bf7e26e774f86502c5c85379 commit 31233e09db9e32c9bf7e26e774f86502c5c85379 Author: Ryo Hashimoto <hashimoto@chromium.org> Date: Mon Jan 29 03:36:37 2018 arc: Unescape file name for ArcFileSystemHost::GetFileName GURL::ExtractFileName() does not unescape the string. Bug: 806192 Test: unit_tests --gtest_filter="ArcFileSystemBridgeTest.*" Change-Id: I31409e7554ae361de9cca809dfbe1a6ef6111b0e Reviewed-on: https://chromium-review.googlesource.com/888189 Reviewed-by: Hidehiko Abe <hidehiko@chromium.org> Commit-Queue: Ryo Hashimoto <hashimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#532314} [modify] https://crrev.com/31233e09db9e32c9bf7e26e774f86502c5c85379/chrome/browser/chromeos/arc/fileapi/arc_file_system_bridge.cc [modify] https://crrev.com/31233e09db9e32c9bf7e26e774f86502c5c85379/chrome/browser/chromeos/arc/fileapi/arc_file_system_bridge_unittest.cc
,
Jan 29 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by hashimoto@chromium.org
, Jan 26 2018