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

Use of invalid encoding: GB18030 #187

Closed
Ghabry opened this Issue Sep 13, 2016 · 6 comments

Comments

Projects
None yet
2 participants
@Ghabry
Member

Ghabry commented Sep 13, 2016

Download from the Baidu server: https://pan.baidu.com/share/link?shareid=3561336958&uk=590550462

In the end the user tried Simplified chinese (CP936) but the files are still not found! :o

Codepage № 54936

The bad thing here is not that the detection fails but that the first detected encoding is not even in our data file >.>

The logfile of a chinese user playing Wadanohara (大海原与大海原 ver1.03【丝绮拉工作室汉化】) reports:

[2016-09-11 00:32:58] Debug: CLI: --project-path /storage/emulated/0/easyrpg/games/wadanohara ver1.03/data --save-path /storage/emulated/0/easyrpg/games/wadanohara ver1.03/data --encoding auto 
[2016-09-11 00:32:58] Debug: Opened audio at 44100 Hz (stereo), format: S16LSB
[2016-09-11 00:32:58] Debug: Bad encoding: GB18030. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/ƒ^ƒCƒgƒ‹ (!)
[2016-09-11 00:32:58] Debug: Detected encoding: ibm-5348_P100-1997. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/�^�C�g�‹ (!)
[2016-09-11 00:32:58] Debug: Detected encoding: ibm-5346_P100-1998. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/荞荃荧莋 (!)
[2016-09-11 00:32:58] Debug: Detected encoding: UTF-16BE. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/広䎃枃讃 (!)
[2016-09-11 00:32:58] Debug: Detected encoding: UTF-16LE. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/� (!)
[2016-09-11 00:32:58] Debug: Detected encoding: Big5. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Bad encoding: IBM424_rtl. Trying next.
[2016-09-11 00:32:58] Debug: Bad encoding: IBM424_ltr. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/ƒ^ƒCƒgƒ‹ (!)
[2016-09-11 00:32:58] Debug: Detected encoding: windows-1254. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/ƒ^ƒCƒgƒ‹ (!)
[2016-09-11 00:32:58] Debug: Detected encoding: ibm-5349_P100-1998. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Bad encoding: IBM420_ltr. Trying next.
[2016-09-11 00:32:58] Debug: Cannot find: Title/ѓ^ѓCѓgѓ‹ (!)
[2016-09-11 00:32:58] Debug: Detected encoding: ibm-5347_P100-1998. Files not found. Trying next.
[2016-09-11 00:32:58] Debug: Detected encoding: GB18030
[2016-09-11 00:32:58] Error: Invalid encoding: GB18030.
@Ghabry

This comment has been minimized.

Show comment
Hide comment
@Ghabry

Ghabry Sep 13, 2016

Member

Btw extracting with unar will detect the wrong encoding.

Extract with unar -e GB18030. The game itself works fine with codepage 936. (minus missing glyphs)

Member

Ghabry commented Sep 13, 2016

Btw extracting with unar will detect the wrong encoding.

Extract with unar -e GB18030. The game itself works fine with codepage 936. (minus missing glyphs)

@Ghabry

This comment has been minimized.

Show comment
Hide comment
@Ghabry

Ghabry Sep 13, 2016

Member

This brings Mojibake to a new level. When you extract the archive as Japanese you get "システム(新)" for the system file. Extracted with simplified chinese gives "僔僗僥儉(奀)".m(

Member

Ghabry commented Sep 13, 2016

This brings Mojibake to a new level. When you extract the archive as Japanese you get "システム(新)" for the system file. Extracted with simplified chinese gives "僔僗僥儉(奀)".m(

@fdelapena

This comment has been minimized.

Show comment
Hide comment
@fdelapena

fdelapena Oct 13, 2016

Contributor

The bad thing here is not that the detection fails but that the first detected encoding is not even in our data file >.>

Then this is a building specific issue missing some alias encoding for simplified Chinese in reader_util, however the bad unpacker detection part seems to be out of our scope, isn't it?

Contributor

fdelapena commented Oct 13, 2016

The bad thing here is not that the detection fails but that the first detected encoding is not even in our data file >.>

Then this is a building specific issue missing some alias encoding for simplified Chinese in reader_util, however the bad unpacker detection part seems to be out of our scope, isn't it?

@Ghabry

This comment has been minimized.

Show comment
Hide comment
@Ghabry

Ghabry Oct 13, 2016

Member

the unpacking is indeed not our problem

Member

Ghabry commented Oct 13, 2016

the unpacking is indeed not our problem

@Ghabry

This comment has been minimized.

Show comment
Hide comment
@Ghabry

Ghabry Oct 13, 2016

Member

except if we add "play from zip" support, then we can guess the codepage in the zip, too. (yeeaaah)

Member

Ghabry commented Oct 13, 2016

except if we add "play from zip" support, then we can guess the codepage in the zip, too. (yeeaaah)

@Ghabry

This comment has been minimized.

Show comment
Hide comment
@Ghabry

Ghabry Feb 21, 2017

Member

This mojibake-zip is a nice test for @ChristianBreitwieser zip support.

Member

Ghabry commented Feb 21, 2017

This mojibake-zip is a nice test for @ChristianBreitwieser zip support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment