Bug 111955 - fileopen .602 text and garbage
Summary: fileopen .602 text and garbage
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Android Viewer (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: ARM Android
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-22 06:09 UTC by vihsa
Modified: 2023-08-17 03:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot of .602 (78.12 KB, image/png)
2017-08-22 06:12 UTC, vihsa
Details
Screenshot (230.06 KB, image/png)
2019-12-13 10:56 UTC, Michael Weghorn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vihsa 2017-08-22 06:09:47 UTC
Description:
.602 file displays english text and garbage on 5.0, 5.1, 5.2, 5.3, 5.4

Steps to Reproduce:
open cti_t602.602
https://opengrok.libreoffice.org/xref/core/sw/qa/core/data/602/pass/cti_t602.602

Actual Results:  
displays text and garbage

Expected Results:
display content properly

not sure whether the issue is due to missing fonts on device or the file itself

please find attachment screenshot of .602 document

repro:

5.0.0.0.alpha1+ [ build id: ab465b9 ]
5.1.0.0.alpha1+ [ build id: 1a6ec13 ]
5.1.0.0.alpha1+ [ build id: 5b791ec ]
5.2.0.0.alpha0+ [ build id: f6a74ce ]
5.3.0.0.alpha1+ [ build id: 4136757 ]
5.4.0.0.alpha0+ [ build id: 3902bb7 ]

os: android 5.1
device: lyf flame 3 [ ls-4001 ]


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Opera/9.80 (Android; Opera Mini/29.0.2254/66.318; U; en) Presto/2.12.423 Version/12.16
Comment 1 vihsa 2017-08-22 06:12:01 UTC
Created attachment 135715 [details]
screenshot of .602
Comment 2 raal 2018-01-06 13:02:07 UTC
I can confirm with LO 6.1, android 5.0
Comment 3 QA Administrators 2019-01-07 03:42:04 UTC Comment hidden (obsolete)
Comment 4 Michael Weghorn 2019-12-13 10:56:04 UTC
Created attachment 156551 [details]
Screenshot

Still the same with current master, and it works OK with desktop version of LibreOffice, s. attached screenshot that shows desktop version on the left and Android on the right.
At a quick glance, this looks like the file might be treated as plain text on Android.

Version: 6.5.0.0.alpha0+
Build ID: 64bf055db690
Android 10.0 on an x86 AVD
Comment 5 QA Administrators 2021-12-13 04:02:47 UTC Comment hidden (obsolete)
Comment 6 Michael Weghorn 2023-01-17 13:18:16 UTC
Is this issue still relevant?
Supporting more file formats presumably also means that the size of the APK will increase (due to more services that will have to be included), so I tend to suggest focusing on those that are particularly relevant.

In addition, the mechanism to open a file in Android Viewer currently depends on the Android system identifying the proper MIME type, which probably isn't the case for most of the proprietary and not so frequently used file types. (So supporting these might need some "open any file, ignore file type" handling instead (possibly hidden behind a setting?).)
Comment 7 QA Administrators 2023-07-17 03:14:37 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2023-08-17 03:19:13 UTC
Dear vihsa,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp