Created attachment 116630 [details]
GBK encoded file
GBK encoded Chinese text can't be read,while another application such as kate in KDE can decode it ok.
Created attachment 116631 [details]
screen shot of Libreoffice and kate
On pc Debian x86-64 with master sources updated yesterday, I could reproduce this.
I noticed this on console:
warn:legacy.osl:3197:1:sw/source/filter/ascii/parasc.cxx:265: Autodetect of text import without nag dialog must have failed
warn:vcl:3197:1:vcl/generic/fontmanager/fontconfig.cxx:863: In glyph fallback throwing away the language property of hi because the detected script for '0xc7e' is Telugu and that language doesn't make sense. Autodetecting instead.
Caolan: one for you? (vcl + language/font detection)
It can be read, it just can't auto-detect the format. You need to use file->open and select the "text - choose encoding" filter, the press ok, and then select "Chinese simplified (GB-18030)" as the encoding here.
Yes,I can read if using Caolán McNamara 's method, but common user can't find this 'text - choose encoding' menu,we suggest Libre office should support auto-detect encoding mechanism,just as MS Office,so I suggest to REOPEN this case to track this requirement.
IMO non utf-8 text is just archaic at this point
Set to NEW, lowered priority and adjusted summary.
Created attachment 122949 [details]
1040044624.DOC - document de test
Created attachment 122950 [details]
Testing document rendered winth LO 188.8.131.52 under Windows 7 x86
Created attachment 122951 [details]
Testing document rendered winth MS Word 2010 under Win7 x86
Removing unrelated debian bug from 'See Also', and changing to 'enhancement', as charset auto-detection isn't implemented.
(In reply to Caolán McNamara from comment #5)
> IMO non utf-8 text is just archaic at this point
Caolán, unfortunately while this may be true for Europe and the US, it's definitely not true for China. GB18030 is the standard in China and a requirement for software that is distributed there.