Issue 128224 - Japanese Win10 default path file extraction problem
Summary: Japanese Win10 default path file extraction problem
Status: CONFIRMED
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: 4.1.6
Hardware: PC Windows 10
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-12 13:35 UTC by tada
Modified: 2024-02-20 14:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.7
Developer Difficulty: ---


Attachments
Screenshot, originally from another guy. (28.00 KB, image/jpeg)
2019-11-12 13:35 UTC, tada
no flags Details
FileNotFound error. Path with japanese characters (6.99 KB, image/png)
2019-11-12 13:45 UTC, tada
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description tada 2019-11-12 13:35:00 UTC
Created attachment 86759 [details]
Screenshot, originally from another guy.

I have an 'Extraction failed' installing OpenOffice in japanese windows 10 while the setup.exe (of OpenOffice 4.1.6 (en-US) Installation Files) is running and I was unable to install OpenOffice.

I had this same error:
https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=82487

I've done the following steps to get the error:
1) It was the first installation of OpenOffice in my PC (using Apache_OpenOffice_4.1.6_Win_x86_install_en-US.exe).
2) I've extracted and automatically it runs setup.exe.
3) Suddently appears an message box titled "Extraction failed" with the text something like "???????????????" (multiple question marks). See attachment (originally and extracted from https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=82487).
4) Then, the OpenOffice Installation Wizard appears. I couldn't finish the installation because a new message appeared: (something like) "file not found openoffice/openoffice1.cab".

I thougt:
The file openoffice1.cab was there. So, I've suspected about the path. The default path of "Installation File" extraction was in the desktop of the user folder. My username have an japanese character (something like "てすと") and the directory of setup.exe it contained japanese characters (something like C:/Users/てすと/Desktop/OpenOffice 4.1.6 (en-US) Installation Files)

I solved with:
I copied the content of "OpenOffice 4.1.6 (en-US) Installation Files" to the root folder (i.e., C:/OpenOffice 4.1.6 (en-US) Installation Files) and the problem was solved. I successfully installed the open office.
Comment 1 tada 2019-11-12 13:45:09 UTC
Created attachment 86760 [details]
FileNotFound error. Path with japanese characters
Comment 2 tada 2019-11-12 13:45:19 UTC
You can simply create a folder with japanese characters (i.e. "てすと") and copy the content of "OpenOffice 4.1.6 (en-US) Installation Files".

It will pop up the message box:
-------------------------------------
Error 1311. Source file not found:
C:\Users\myusername\Desktop\てすと\OpenOffice 4.1.7
(en-US) Installation Files\openoffice1.cab. Verify that
the file exists and that you can access it.
-------------------------------------
Comment 3 Matthias Seidel 2019-11-12 13:49:42 UTC
(In reply to tada from comment #2)
> You can simply create a folder with japanese characters (i.e. "てすと") and
> copy the content of "OpenOffice 4.1.6 (en-US) Installation Files".
> 
> It will pop up the message box:
> -------------------------------------
> Error 1311. Source file not found:
> C:\Users\myusername\Desktop\てすと\OpenOffice 4.1.7
> (en-US) Installation Files\openoffice1.cab. Verify that
> the file exists and that you can access it.
> -------------------------------------

Is this for 4.1.6 or 4.1.7?
Comment 4 oooforum (fr) 2019-11-12 14:50:02 UTC
Did you have posted this problem on our japanese forum?
https://forum.openoffice.org/ja/forum/

Error 1311 is a known issue fro mthe Windows Installer software and not OpenOffice.
Comment 5 Matthias Seidel 2019-11-12 17:12:00 UTC
Confirmed with AOO 4.1.7 on a German Windows 7 with a folder 'てすと'.
Most likely this is a problem with the Unicode characters.

I will build a patched version of 4.1.8 and will test again.